Advanced Topics › How You Dynamically Change Which Devices Are Managed › Resynchronization: RESYNCH Command

Resynchronization: RESYNCH Command

The DEVLIST, DEVCLASS, and COMMANDS parameters on the RESYNCH command, the SETOPTION RESYNCH command, and the MIMINIT statement control the actions of CA MIA during device resynchronization.

If the DEVLIST, DEVCLASS, and COMMANDS parameters are not specified on the RESYNCH command, then CA MIA uses the SETOPTION RESYNCH command. If those parameters are not on the SETOPTION RESYNCH command, then CA MIA uses the DEVLIST, DEVCLASS, and COMMANDS settings on the MIMINIT statement.

For example, to issue a RESYNCH command that dynamically updates the managed device list for CA MIA and places all tape devices under CA MIA control, issue the following command:

RESYNCH DEVCLASS=TAPE

In this example, CA MIA uses TAPE for the DEVCLASS option, which temporarily overrides the value set on the SETOPTION RESYNCH command for DEVCLASS. The values for the COMMANDS and DEVLIST options remain the same.

Notes:

• When a task is in the tape allocation process and a resynchronization occurs that removes all the devices requested by the task from CA MIA management, CA MIA discontinues the cross-system serialization of the allocation. However, CA MIA may continue its involvement in some parts of the allocation until the allocation completes. For example, if the task should go into allocation recovery, then CA MIA manages the recovery until the allocation recovery messages are responded to.
• The RESYNCH command is a local command. That is, it only takes effect on the system where it is issued. If the devices managed by CA MIA are to be changed on more than one system, then the RESYNCH command must be issued on each system that requires the change.
• The SETOPTION RESYNCH SAMEDEVS parameter does not apply to resynchronizations performed due to the RESYNCH command. SAMEDEVS is only valid for automatic resynchronizations through an HCD ACTIVATE.
• Any RESYNCH option, except the SAMEDEVS option, can be overridden dynamically when using the RESYNCH command.
• The RESYNCH parameters are available on both the SETOPTION TPCF and SETOPTION GTAF commands. Setting the RESYNCH parameters with one of these SETOPTION commands automatically sets the same values for the other SETOPTION command.
• It is possible to RESYNCH a device out of CA MIA control and have the device still exist on the system. These are the devices that CA MIA will schedule OFFLINE.

  If a device is RESYNCHed out of CA MIA control due to an HCD ACTIVATE configuration change, the device is being deleted by z/OS. To be deleted, the device must already be OFFLINE, and it will not exist after the ACTIVATE completes; the CA MIA OFFLINE processing is not relevant in this case.

  Note: For more information, see the CA MIM Statement and Command Reference Guide.