Description: Before performing cross-system restart, automatic restart management (ARM) waits for member cleanup for the terminated system to complete. ARM proceeds with cross-system restart if cleanup takes longer than a certain amount of time. Before z/OS V1R13, this time was two minutes. Starting with z/OS V1R13 and after the PTFs for APAR OA35357 applied to z/OS V1R13 and z/OS V1R12, the CLEANUP_TIMEOUT parameter can be used to indicate that ARM is to wait additional time for member cleanup for a terminated system to complete. The default for this new parameter is five minutes. That is, ARM will wait five minutes for member cleanup for a terminated system to complete before performing cross-system restart for an element. To get the two-minute timeout behavior that existed before the default change, CLEANUP_TIMEOUT(120) must be added to the ARM policy.
When a CLEANUP_TIMEOUT value greater than 120 is specified (or defaulted to), and additional delay is introduced to wait for member cleanup processing to complete, message IXC815I is issued to the system log to record the delay in performing restart processing.
IXC815I MEMBER CLEANUP FOR SYSTEM sysname1 NUMBER sysnum1 INCOMPLETE.
JOBNAME jobname, ELEMENT elementname RESTART IS DELAYED FOR UP TO dec SECOND(S).
RESTART IS FOR THE FAILURE OF SYSTEM sysname2 NUMBER sysnum2.If the member cleanup does not occur within the time specified by the CLEANUP_TIMEOUT parameter, automatic restart management will proceed with processing the element for cross-system restart, and, if CLEANUP_TIMEOUT(120) is not being used, the system issues message IXC815I to the system log to record the time out.
IXC815I MEMBER CLEANUP FOR SYSTEM sysname1 NUMBER sysnum1 INCOMPLETE.
JOBNAME jobname, ELEMENT elementname RESTART DELAY TIMED OUT AFTER dec SECOND(S).
| Element or feature: | BCP. |
| When change was introduced: | z/OS V1R13, and rolled back to z/OS V1R12, z/OS V1R11, and z/OS V1R10 by APAR OA35357. |
| Applies to migration from: | z/OS V1R12 without the PTFs for OA35357 applied. |
| Timing: | Before the first IPL of z/OS V2R1. |
| Is the migration action required? | Yes, if a five-minute timeout for member cleanup is not acceptable. |
| Target system hardware requirements: | None. |
| Target system software requirements: | None. |
| Other system (coexistence or fallback) requirements: | The new five minute default, or any use of the CLEANUP_TIMEOUT parameter other than CLEANUP_TIMEOUT(120), is not fully effective until all systems in the sysplex have support for the CLEANUP_TIMEOUT parameter. APAR OA35357 provides support for the CLEANUP_TIMEOUT parameter. |
| Restrictions: | None |
| System impacts: | None. |
| Related IBM Health Checker for z/OS check: | None. |
Steps to take: If you prefer to use the two minute value for ARM restart processing, do the following:
Reference information: For details, see the topic "Automatic restart management parameters for administrative data utility" in the chapter "Administrative data utility" in z/OS MVS Setting Up a Sysplex.