Starting Your Product › Configure Your Product › Required Manual Configuration › Restart Manager Usage

Restart Manager Usage

The Restart Manager provides the capability to restart CA MIM components automatically after a failure or to perform a planned restart on a single system. When used with CA MII, the restart manager maintains the integrity of global resources throughout the restart process. Local ENQ/DEQ activity is suspended for managed QNAMEs from the instant a failure is detected or a SHUTDOWN RESTART command is issued. Activity remains suspended until the restart is complete and normal global operation resumes.

To activate the Restart Manager, specify PGM=MIMDRRM on the EXEC statement of the CA MIM proc.

Additional requirements:

• Restart Manager requires the use of a STEPLIB; adding the CA MIM load library to the LINKLST is not sufficient. When no STEPLIB DD statement is present, CA MIM terminates with ABEND U40, reason code 164 (X’A4’).
• Restart Manager requires that only partitioned data sets (PDS) are specified on the STEPLIB, MIMCNTL, and MIMMSGS DD statements. When any of those DD statements refer to a PDSE, CA MIM terminates with ABEND U40, reason code (X’A8’).
• Restart Manager requires that CA MIM be started SUB=MSTR. This requirement is already met when MIM is started through the Early Start mechanism. When CA MIM is started through a START command, code the SUB=MSTR keyword on the command. When CA MIM is started without the SUB=MSTR keyword, MIM terminates with ABEND U40, reason code 169 (X’A9’).

We recommend that GDIF be started under the control of the Restart Manager, with the Early Startup mechanism. This procedure provides the maximum protection for global resources by commencing global management as soon as possible during the IPL, and by maintaining global integrity during restart processing.

Note: GDIF is the only CA MIM facility that exploits the Restart Manager. All other CA MIM facilities function normally with the Restart Manager but do not necessarily take advantage of it.

Restart Manager behavior and usage:

• To activate changes to the CA MIM JCL PROC, do not use a SHUTDOWN RESTART command. Instead, issue a SHUTDOWN LOCAL command followed by an MVS START.
• Use the SHUTDOWN RESTART command to activate changes to INIT values that do not need to be consistent across systems. For example, you can change MIMINIT PAGEFIX=COND and do a SHUTDOWN RESTART and the change is in effect.
• During a restart, CA MIM can ignore ALLOCATE initialization statements for checkpoint files and control files. CA MIM continues to use control files and checkpoint files that are allocated before the restart.
• During a restart, CA MIM ignores MIMINIT CHKPTDSN parameters. MIM continues to use checkpoint files that are allocated before the restart.
• Restart Manager does not attempt a restart when CA MIM abends within 60 seconds of initialization. Abends that occur early after initialization are most likely the result of incorrect parameters that require user intervention.
• When used in conjunction with WAITSTATE, CA MIM places the system into a disabled wait state when the restart attempt fails.
• During a restart, Restart Manager forces REUSE=YES. To force REUSE=NO, issue a SHUTDOWN LOCAL, followed by an MVS START.