Steps for application groups included in procedures - assure_mimix - 10.0

Assure MIMIX Administrator Reference

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software
Version
10.0
Language
English
Product name
Assure MIMIX
Title
Assure MIMIX Administrator Reference
Copyright
2023
First publish date
1999
ft:lastEdition
2024-06-11
ft:lastPublication
2024-06-11T18:33:16.692940

Table 120 includes step programs for application groups that are shipped with MIMIX and identifies the procedures where they are used. The values for the Used in Procedure column indicate the following:

  • ‘R’  - The step is required and cannot be changed or disabled.

  • ‘C’  - The step is included and can be changed or disabled.

  • ‘D’ - The step is included, shipped disabled, and can be enabled.

  • ‘M’ - The step is included when the application group type is a *DB2MIRROR, and can be changed or disabled.

  • Blank - The step is not used in the procedure

    Step programs for data and application groups R=required (cannot change or disable)                                                   C=can change or disable                                                    D=shipped disabled (can enable)                                M=included for *DB2MIRROR (can change or disable )                                  Blank=step not used in the procedure

    Step

    / Step Program Name

    Step

    Description

    Where Step Runs Used in Procedure
      Type Node END ENDIMMED ENDTGT ENSREPLSCD PRECHECK PRECHKVRT RUNBACKUP START SWTPLAN SWTUNPLAN SWTVRT

    BACKUPAPP

    Backup user application.

    This step can be customized to perform any actions necessary to back up the production application.

    Application Group

    Backup

    C

    ENDUSRAPP

    End user application.

    This step can be customized to perform any actions necessary to end the production application.

    .

    Application Group

    Primary

    C

    ENDUSRAPPV

    End user application on virtual switch test node.

    This step can be customized to perform any actions necessary to end the user application that was started as part of a virtual switch test.

      

    Application Group

    New Primary

    D

    MCENDAGMON

    End application group status monitor.

    This step ends the application group status monitor.

    Application Group

    All

    M

    M

    MCSTRAGMON

    Start application group status monitor.

    This step starts the application group status monitor.

    Application Group

    All

    M

    MIRCHGROLE

    Change role for secondary DB2 Mirror site nodes.

    This step changes the role of the node entries for the secondary DB2 Mirror site.

    Application Group

    Primary

    R

    MIRDSBSCD

    Disable data groups for secondary DB2 Mirror site’s secondary node.

    The step disables data groups for the secondary node of each secondary DB2 Mirror site.

    Data Group

    Primary

    R

    MIRENBSCD

    Enable data groups for secondary DB2 Mirror site’s primary node.

    This step enables data groups for the primary node of each secondary DB2 Mirror site.

    Data Group

    Primary

    R

    MIRENDMIR

    End data groups controlled to secondary DB2 Mirror site’s secondary node.

    This step ends the data groups in a controlled manner for the secondary node of the each secondary Db2 Mirror site.

    Data Group

    Primary

    R

    MIRSETSEQ

    Set sequence number for data group to secondary DB2 Mirror site’s primary node.

    This step sets the starting sequence number for each data group replicating to the primary node of each secondary DB2 Mirror site.

    Data Group

    Primary

    R

    MIRSTRSCD

    Start data group to secondary DB2 Mirror site’s primary node.

    This step starts the data groups to the primary node of each secondary DB2 Mirror site.

    Data Group

    Primary

    R

    MIRSWTSCD

    Switch data group to secondary DB2 Mirror site’s primary node.

    This step switches the data groups to the primary node of each secondary DB2 Mirror site.

    Data Group

    Primary

    R

    MXAPYSSB

    Apply staged system settings on backup

    This step applies staged system settings on the backup node.

    Data Group

    New Primary

    C

    C

    C

    MXAPYSSVS

    VS recovery of captured target system settings

    This step applies system settings that were captured on the target node before virtual switch testing to the backup node during virtual switch recovery.

    Data Group

    New Primary

    C

    MXAUDACT

    Audit activity verification.

    This step checks for active audits.

    .

    Data Group

    New Primary

    C

    C

    C

    C

    C

    MXAUDCMPLY

    Audit compliance verification.

    This step checks for audits that are out of compliance.

    .

    Data Group

    New Primary

    C

    C

    C

    C

    C

    MXAUDNORUN

    Audit not run verification.

    This step checks for audits that have failed or not run.

    .

    Data Group

    New Primary

    C

    C

    C

    C

    C

    MXCAPSSTGT

    Capture target system settings to a library

    This step captures the system settings on the target node to a library.

    Data Group

    New Primary

    C

     MXCHGDG

    Change data group.

    This step enables and disables data groups in multi-management environments based on the recovery domain and current node roles. New starting points are created for data groups that are enabled.

    .

    Data Group

    New Primary

    C

    C

    C

    MXCHGDGDIR

    Change data group direction.

    This step changes the direction of replication for the data group.

    .

    Data Group

    New Primary

    R

    R

    MXCHGSYSJ

    Changes audit journal receivers.

    This step changes the system journal to a new receiver.

    .

    Application Group

    New Primary

    C

    C

    MXCHGUSRJ

    Changes user journal receivers.

    This step changes the user journal to a new receiver.  

    .

    Data Group

    New Primary

    C

    C

    MXCHKAPMNT

    Check AP maintenance status.

    This step checks the status of access path maintenance files and attempts to repair error if found.

    Data Group

    New Primary

    C

    C

    C

    C

    C

    MXCHKCFG

    Configuration verification.

    This step verifies that data groups are switchable. Data groups with replicate nodes are not checked.

    .

    Data Group

    New Primary

    C

    C

    C

    C

    C

    MXCHKCOM

    Communications verification.

    This step verifies the communication links are active among all nodes in the recovery domain for the application group.

    .

    Application Group

    Local

    R

    R

    R

    R

    MXCHKDGEND

    Checks for ended data group, maximum of 30 checks.

    This step periodically checks the data group status to verify that replication processes are ended. The RJ Link status is not checked. If processes are not ended, a 10 second delay occurs before status is checked again. The step fails if replication processes are not ended after 30 checks.

    .

    Data Group

    New Primary

    D

    MXCHKDGSTR

    Checks for started data group, max. of 30 checks.

    This step periodically checks the data group status to verify that replication processes are started. If processes are not started, a 10 second delay occurs before status is checked again. The step fails if replication processes are not started after 30 checks.

    In the procedure SWTVRT, this step program is used twice. On the first occurrence, the step is required (cannot be changed or disabled). On the second occurrence, the step can be changed or disabled.

    Data Group

    New Primary

    D

    R

    MXCHKRCY

    Checks for new and in-progress recoveries.

    This step checks for objects that MIMIX has identified as needing correction and which have not been corrected yet. These objects may not be synchronized among the recovery domain nodes.

    Data Group

    New Primary

    C

    C

    D

    D

    D

    MXCHKRJB

    Checks for replicated jobs.

    This step checks to see if there are remaining replicated jobs on the current source node of the data group. This step fails if there are any remaining replicated jobs.

    Note: Removed from SWTUNPLAN procedure for instances running MIMIX 9.0.09.00 and higher.

    Data Group

    Primary

    C

    C

    MXCHKTJI

    Checks that Target Journal Inspection is active.

    This step checks that Target Journal Inspection is configured and active.

    Data Group

    New Primary

    C

    R

    MXCHKVRTN

    Check the virtual switch status.

    This step verifies that the status of the data groups in the application group are not in a virtual switch status that would prevent a planned or unplanned switch from occurring.

    Data Group

    New Primary

    R

    MXCKDSBCST

    Checks data group for constraints disabled by MIMIX.

    This step verifies that there are no disabled constraints that were disabled by MIMIX on any of the backup or replicate nodes.

    Note: In service pack 9.0.20.00 and higher, this step replaces MXCKDCSTB which ran on a backup node, and MXCKDCSTR which ran on a replicate node.

    Data Group

    Target

    C

    C

    C

    C

    C

    MXCKDGEAPY

    Checks if applies and APM are ended, max. 1 hour.

    This step periodically checks the data group status to verify that replication apply and access path maintenance processes are ended. If the processes are not ended, a 10 second delay occurs before status is checked again. The step will fail if the processes are not ended in 1 hour.

    Data Group

    Local

    D

    R

    MXCKPRCACT

    Checks application group for active procedures.

    This step verifies that there are no active procedures for the application group.

    Application Group

    Local

    C

    MXCKRCYCMP

    Checks for virtual switch recovery to be completed.

    In MIMIX instances 8.1.13.00 and higher, this step waits for virtual switch recovery to complete.

    Data Group

    New Primary

    R

    MXCKTGTJRN

    Checks that target journaling is configured.

    This step verifies that target journaling is configured to Yes for the resource group and data groups.

    Data Group

    New Primary

    C

    R

    MXCLUNO

    Checks that application group is not type *CLU.

    This step verifies that the application group is not configured to use IBM Clustering.

    Application Group

    New Primary

    C

    MXDBERR

    Database error verification.

    This step checks the data group for objects or files not journaled on the source node, in error, with repairs in progress, or with failed recoveries.

    .

    Data Group

    New Primary

    C

    C

    C

    C

    C

    MXDBPND

    Ensures there are no pending database transactions.

    This step checks for active commit cycles or unprocessed entries in the data group.

    .

    Data Group

    New Primary

    C

    C

    C

    MXDGDSBPCY

    Disable recovery policies.

    This step is used during an unplanned switch to disable automatic replication recovery and audit recovery policies as well as the policy for recovery of objects only on the target system. Following an unplanned switch, it is recommended that these policies remain disabled until after journal analysis and manual correction are completed.

    Data Group

    New Primary

    R

    MXDGNOKEY

    Checks that keyed replication is not configured.

    This step verifies that the data group is not configured to use keyed replication.

    Data Group

    New Primary

    C

    R

    MXDSBCSTV

    Disable constraints for virtual switch recovery.

    This step disables all foreign key constraints on the target node during virtual switch recovery.

    Data Group

    New Primary

    R

    MXDSBTRG

    Disable triggers on target in virt. switch testing.

    This step disables all triggers on the target node during virtual switch testing.

    Data Group

    New Primary

    R

    MXENBCST

     Enable foreign key constraints previously disabled.

    This step enables all foreign key constraints that were previously disabled by MIMIX on all backup and replicate nodes.

    Note: In service pack 9.0.20.00 and higher, this step replaces MXECSTB which ran on a backup node, and MXECSTR which ran on a replicate node.

    Data Group

    Target

    D

    D

    C

    C

    C

    R

    MXENBCSTNC

    Enable foreign key constraints without checking.

    This step enables all foreign key constraints that were previously disabled by MIMIX on all backup and replicate nodes without checking the data in the referenced files.

    Note: In service pack 9.0.20.00 and higher, this step replaces MXECSTNCB which ran on a backup node, and MXECSTNCR which ran on a replicate node.
    Note: If you modify the SWTUNPLAN procedure to enable this step, MIMIX-disabled constraints are always enabled without checking the data in the referenced files, and without other checks, such as for the existence of open commits. It is possible that constraints will be in violation due to different apply sessions ending at different points on the journal and that DB2 for IBM i will not be aware of constraint violations. Subsequent database corruption or application failures may occur.

    D

    D

    D

    D

    D

    D

    MXENBCSTV

    Enable constraints after virtual switch recovery.

    In MIMIX instances 8.1.13.00 and higher, this step enables all foreign key constraints if the data group is not configured to manage constraints.

    In MIMIX instances prior to 8.1.13.00, this step waits for virtual switch recovery to complete. Then it enables all foreign key constraints if the data group is not configured to manage constraints.

    Data Group

    New Primary

    R

    MXENBTRG

    Enable triggers on target.

     This step enables triggers on the target node that were previously disabled by MIMIX.

    .

    Data Group

    New Primary

    R

    R

    R

    MXENDAUD

    End and prevent audits during virtual switch.

    This step ends active audits. Future audits are prevented from running for a data group during a virtual switch.

    Data Group

    New Primary

    R

    MXENDDG

    End data group controlled.

    This step ends the data group in a controlled manner. A timeout of 3600 seconds is allowed for the data group to end.

    Data Group

    Local

    C

    C

    R

    MXENDDGAPY

    End data group applies controlled.

    This step ends apply processes running on the target node for the data group in a controlled manner.

    As a general guideline, to ensure this step operation is successful when used in a procedure, use this step in conjunction with the following steps and in this order:

    • MXSTRDG

    • MXCHKDGSTR

    • MXENDDGAPY

    • MXCKDGEAPY

    Data Group

    New Primary

    D

    R

    MXENDDGDB

    End data group DBAPY processes with controlled end.

    This step ends the data group database apply processes in a controlled manner. RJ links are not ended.

    Data Group

    Local

    D

    MXENDDGIM

    End data group immediate.

    This step ends the data group immediately.

    .

    Data Group

    New Primary

    R

    MXENDDGNMX

    End data group controlled with no timeout maximum.

    This step ends the data group in a controlled manner with no timeout maximum. RJ links are not ended.

    Data Group

    Local

    D

    MXENDDGTGT

    End target data group controlled.

    This step ends the processes running on the target node for the data group in a controlled manner.

    .

    Data Group

    New Primary

    R

    MXENDDGUNP

    End data group controlled for an unplanned switch.

    This step ends the processes running on the target node for the data group in a controlled manner during an unplanned switch using a timeout of 3600 seconds. If the timeout is reached before the controlled end is completed, an inquiry message is issued. Errors are ignored.

    .

    Data Group

    New Primary

    R

     MXENDJRNT

    End journaling on the new target node.

    This step ends journaling on the new target node when the data group is not configured for journaling on the target node.

    .

    Data Group

    New Primary

    C

    C

    MXENDRJLNK

    End remote journal link.

    This step ends the remote journaling link from the old source node to the old target node.

    Data Group

    New Primary

    C

    MXFAILRCY

    Fails new or in-progress recoveries.

    This step checks for objects on a backup or replicate node that MIMIX has identified as needing correction. Objects that have not been corrected will be changed to an error status.

    Note: In service pack 9.0.20.00 and higher, this step replaces MXFAILRCYB which ran on a backup node, and MXFAILRCYR which ran on a replicate node.

    Data Group

    Target

    C

    C

    C

    MXFAILRCYV

    Fails remaining recoveries from virtual switch.

    This step checks for objects that MIMIX has identified as needing correction during virtual switch testing that it could not recover during virtual switch recovery. Objects which have not been corrected will have an error status.

    Data Group

    New Primary

    R

    MXNFYERR

    Notification error verification.

    This step checks for unacknowledged error notifications for the data group.

    .

    Data Group

    New Primary

    C

    C

    C

    C

    C

    MXNOINTRA

    Checks that data groups are not INTRA.

    This step verifies that the data group is not configured for INTRA (replication to the same node).

    Data Group

    New Primary

    C

    R

    MXNOSYSJRN

    Checks for user journal cooperative processing.

    This step verifies that a data group is not configured with Cooperative processing type of Use System Journal.

    Data Group

    New Primary

    C

    R

    MXOBJERR

    Object error verification.

     This step checks if there are failed object activity entries for the data group.

    .

    Data Group

    New Primary

    C

    C

    C

    C

    C

    MXOBJJRN

    Checks that objects are journaled on the target.

    This step verifies that the objects are correctly journaled on the target node.

    Data Group

    New Primary

    C

    R

    MXOBJPND

    Ensure there are no pending object transactions.

    This step checks for pending object activity entries for the data group.

    .

    Data Group

    New Primary

    C

    C

    C

    MXRMVRJB

    Removes all replicated jobs.

    This step removes all replicated jobs from the new source node to prevent the jobs from being submitted to run.

    Data Group

    New Primary

    D

    D

    MXSBMAUD

    Run priority audits after virtual switch recovery.

    This step submits prioritized audits on the same node where the step program is running to correct objects changed on the target node when recovering from a virtual switch. This is done regardless of whether prioritized auditing is enabled.

    Data Group

    New Primary

    C

    MXSBMRJB

    Submits all replicated jobs.

    This step submits all replicated jobs on the new source node, allowing the jobs to run.

    Data Group

    New Primary

    D

    D

    MXSBMRJBN

    Submits all new (not started) replicated jobs.

    This step submits all replicated jobs that had not yet been started on their original source node to run on the new source node.

    Data Group

    New Primary

    D

    D

    MXSETDGJA

    Set journal analysis indicator for data group.

     This step sets a flag for a data group that has been part of an unplanned switch to indicate that journal analysis should be performed and manual correction should be completed before the data group is started.

    Data Group

    New Primary

    R

    MXSETRJBI

    Set replicated jobs indicator.

    This step sets an indicator if there are remaining replicated jobs on the new source node for the data group. The data group cannot be switched again until all remaining replicated jobs are submitted or removed.

    Data Group

    New Primary

    R

    R

    MXSETSTRJ

    Set journal starting points.

    This step sets the starting point for the data group that is in switch mode. A journal entry is sent to notify Target Journal Inspection about this event.

    .

    Data Group

    New Primary

    R

    R

    MXSETSWTN

    Set switch type to none.

    This step sets the switch type used by other step programs to none.

    Data Group

    All Nodes

    R

    R

    R

    R

    R

    MXSETSWTNP

    Set switch type to none on the new primary node

    This step sets the switch type used by other step programs to none.

    Data Group

    New primary

    R

    MXSETSWTP

    Sets switch type to planned.

    This step sets the switch type used by other step programs to planned.

    .

    Data Group

    New Primary

    R

    MXSETSWTUN

    Sets switch type to unplanned.

    This step sets the switch type used by other step programs to unplanned.

    .

    Data Group

    New Primary

    R

    MXSETTJIVS

    Set Target Journal Insp. for virt. switch testing.

    This step changes the target journal inspection job to a virtual switch testing mode so that it does not send target journal inspection notifications while the application group is in a virtual switch.

    Data Group

    New Primary

    R

    MXSETVRTN

    Set virtual switch status to *NONE.

    This step sets virtual switch status to completed.

    Data Group

    New Primary

    R

    R

    R

    R

    R

    R

    R

    MXSETVRTS

    Set virtual switch status to *STARTING.

    This step sets the virtual switch status to starting.

    Data Group

    New Primary

    R

    MXSETVRTT

    Set virtual switch status to *TESTING.

    This step sets virtual switch status to testing.

    Data Group

    New Primary

    R

    MXSTRDG

    Start data group.

    This step starts the data group using the last processed receiver and sequence number. If a data group cannot be started because it requires pending entries to be cleared, a second start request is issued which clears pending entries.

    .

    Data Group

    Local

    D

    R

    R

    MXSTRDGTGT

    Start data group target node processing.

    This step starts the target node processes for the data group beginning with the last processed entry for the receiver and sequence number.

    Data Group

    New Primary

    R

    MXSTRJRNP

    Start user journaling on both peer nodes.

    This step starts journaling of files, data areas, data queues, and IFS objects configured for user journal replication on the peer nodes of the related data groups.

    Note: This step is available on systems running MIMIX 9.0.13.00 or higher when the Assure MIMIX for IBM Db2 Mirror licensed feature is present.

    Data Group

    Peer

    R

    MXSTRJRNS

    Starts journaling on the new source node.

    This step starts journaling for all applicable objects on the new source node of the data group if the data group does not allow journaling on target. This includes files and any data areas, data queues, and IFS objects configured for user journal replication.

    .

    Data Group

    New Primary

    R

    R

    MXSWTCMP

    Denotes the end of a switch procedure.

    This step sets the switch to complete for a data group when the switch has completed.  

    .

    Data Group

    New Primary

    R

    R

    MXTGTJRNB

    Set file journal image to *BOTH on target node.

    This step changes files on the target to use both before and after journaling images.

    Data Group

    New Primary

    C

    MXTGTJRNFE

    Set target files to configured file journal image.

    This step changes files on the target to use the configured journaling image as represented by the file selection rules.

    Data Group

    New Primary

    C

    MXUPDNOD

    Update node roles after switch.

    This step updates node roles after a switch has completed.

    .

    Application Group

    New Primary

    R

    R

    MXVRTRCY

    Start recovery processing of virtual switch.

    This step starts the recovery phase of a virtual switch.

    Data Group

    New Primary

    R

    MXWAITRJB

    Wait for replicated jobs to be submitted/removed.

    This step waits for all replicated jobs on the new source node to be manually submitted or removed.

    Data Group

    New Primary

    C

    C

    SECACTBACK

    Activate Assure Security backup inst on *NEWPRIM.

    This step activates the Assure Security backup instance on the new primary node.

    Application Group

    New Primary

    D

    D

    SECACTPROD

    Activate Assure Security prod inst on *NEWPRIM.

    This step activates the Assure Security production instance on the new primary node.

    Application Group

    New Primary

    D

    D

    D

    SECDABACK

    Deactivate Assure Security backup inst on *PRIMARY.

    This step deactivates the Assure Security backup instance on the primary node.

    Application Group

    Primary

    D

    D

    SECDAPROD

    Deactivate Assure Security prod inst on *PRIMARY.

    This step deactivates the Assure Security production instance on the primary node.

    Application Group

    Primary

    D

    SECSWTP

    Start Assure Security backup inst planned SWTAG.

    This step initiates a planned switch of the application group controlling the Assure Security backup instance.

    Application Group

    Local

    D

    SECSWTUNP

    Start Assure Security backup inst unplanned SWTAG.

    This step initiates an unplanned switch of the application group controlling the Assure Security backup instance.

    Application Group

    Local

    D

    STRUSRAPP

    Start user application.

    This step can be customized to perform any actions necessary to start the production application.

    .

    Application Group

    New Primary

    C

    C

    STRUSRAPPV

    Start user application on virtual switch test node.

    This step can be customized to perform any actions necessary to start the user application as part of a virtual switch test.

    Application Group

    New Primary

    D