The steps defined to run in the Swap Audit are the actions that Robot HA performs to determine your readiness to run a role swap.

Step Name Description Can Edit Run? Can Edit Stop? Can Edit Rcvr?

Roles are *PROD and *BACKUP

The current system needs to be set to role *PROD and the target needs to be set to *BACKUP. Also, the TCP/IP servers must be active on both systems.

     

RELMOD on target and source are equal

RELMODS must match on source and target. Both the source and target need to be at the same release.

     

User defined before audit exit point

The user defined program added to this step is run. The program can pass back error information that will be written to audit history. For an example, see member BEFOREAPI in RBTHALIB/RHASAMPLE.  

*CFG sync'd to *BACKUP

Sync attribute for *CFG from *PROD to *BACKUP needs to exist on the production system. If not found, one is created and synchronization will be attempted. If found, but it is late or lagging, synchronization will be attempted.    

*CFG sync'd from *BACKUP

Sync attribute for *CFG from *BACKUP to *PROD needs to exist on the backup system. If not found, one is created and synchronization will be attempted. If found, but it is late or lagging, synchronization will be attempted.    

Product lib sync'd to *BACKUP

Sync attribute for library RBTHALIB from *PROD to *BACKUP needs to exist on the production system. If not found, one is created and synchronization will be attempted. If found, but it is late or lagging, synchronization will be attempted.    

Product lib sync'd from *BACKUP

Sync attribute for library RBTHALIB from *BACKUP to *PROD needs to exist on the backup system. If not found, one is created and synchronization will be attempted. If found, but it is late or lagging, synchronization will be attempted.    

*USRPRF sync'd to *BACKUP

Sync attribute for *USRPRF from *PROD to *BACKUP needs to exist on the production system. If not found, one is created and synchronization will be attempted. If found, but it is late or lagging, synchronization will be attempted.

*AUTL sync'd to *BACKUP

Sync attribute for *AUTL from *PROD to *BACKUP needs to exist on the production system. If not found, one is created and synchronization will be attempted. If found, but it is late or lagging, synchronization will be attempted.

RSFUSER sync'd to *BACKUP

Sync attribute for library RSFUSER from *PROD to *BACKUP needs to exist on the production system. If not found, one is created and synchronization will be attempted. If found, but it is late or lagging, synchronization will be attempted.    

QSTRUPPGM's are different

Retrieves the Primary and Secondary startup programs as defined in the INZRSFHA command and checks that the names and/or libraries of those programs are different. Also, verifies that the programs exist on the *PROD and *BACKUP systems.  

System startup pgm sync'd to *BACKUP

Retrieves the Primary and Secondary startup programs as defined in the INZRSFHA command and checks that the names and/or libraries of those programs are different. Also, verifies that the programs exist on the *PROD and *BACKUP systems.

Sync attribute for the startup program from *PROD to *BACKUP needs to exist on the production system. If the sync entry is not found, one is created and synchronization will be attempted. If found, but it is late or lagging, synchronization will be attempted.

   

System startup pgm sync'd from *BACKUP

Retrieves the Primary and Secondary startup programs as defined in the INZRSFHA command and checks that the names and/or libraries of those programs are different. Also, verifies that the programs exist on the *PROD and *BACKUP systems.

Sync attribute for the startup program from *BACKUP to *PROD needs to exist on the backup system. If the sync entry is not found, one is created and synchronization will be attempted. If found, but it is late or lagging, synchronization will be attempted.

 

 

Groups are sync'd to *BACKUP

Verifies that all Group sync attribute entries from your *PROD to your *BACKUP system are not late or lagging. If they are late or lagging, synchronization will be attempted.    

Libraries are sync'd to *BACKUP

Verifies that all Library sync attribute entries from your *PROD to your *BACKUP system are not late or lagging. If they are late or lagging, synchronization will be attempted.

 

 

IFS directories are sync'd to *BACKUP

Verifies that all IFS sync attribute entries from your *PROD to your *BACKUP system are not late or lagging. If they are late or lagging, synchronization will be attempted.

   

Identify libraries not sync'd

Finds libraries that do not have sync attributes set up that match the pattern defined in the step. A record of those libraries found is written to history.  

User defined after audit exit point

The user defined program added to this step is run. The program can pass back error information that will be written to audit history. For an example, see member AFTERAPI in RBTHALIB/RHASAMPLE.  

Swap Audit Stop/Recover Matrix:

See the table below for the run definition of Stop and Recover within the Audit Steps

Stop Recover Scenerio Description

N

N

A step failure is neither recovered nor does it stop processing. The audit process will continue to the next step and flag the failure.

N

Y

An attempt to recover will be made after a step failure. The audit process will continue regardless of the outcome of the recovery.

Y

N

A failure in the step will stop the audit process. No attempt at recovery of the step will be attempted.

Y

Y

A step failure will stop the audit process if the step cannot be recovered. However, if the step recovers successfully, the audit process will continue.


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: March 08, 2018