Additional P/DAS considerations

Depending on your installation and operations, consider the following items as you plan for P/DAS operations:

Ensure that a JES3 restart or reinitialization uses the new device addresses that result from a P/DAS operation. The JES3 INISH deck must reflect the new device addresses for devices involved in a P/DAS operation. This includes devices that are part of a JES3 spool volume.
Ensure that automatic procedures do not involve a device that P/DAS is switching, as I/O cannot occur during a switch operation.
You can swap the SYSRES volume, provided that the volume meets the other P/DAS requirements.
Do not use either the PPRC CSUSPEND QUIESCE option or the CGROUP FREEZE option in conjunction with P/DAS functions.
Consider assigning a device the same device address on all systems in a sysplex environment. Operations such as P/DAS are easier when affected devices have the same device addresses within all systems.
P/DAS supports operations between 3390, RAMAC, and ESS devices. However, you might want to run the latest level of ICKDSF to ensure that the VTOC reflects the proper device characteristics.
The system operator must be aware of when a P/DAS function has occurred before a system IPL, and ensure that the proper volume is placed online after the IPL.
During IPL, the system operator is prompted to select which volume to place online in situations where both the primary and secondary volumes are operational and have the same volume serial number.
Be aware that when P/DAS reestablishes a pair in the opposite direction, it establishes the new pair with the CRIT(NO) option.
P/DAS operates with volumes that were established with either the CRIT(YES) or CRIT(NO) keywords. P/DAS must reestablish the pair with the CRIT(NO) option because the volume pair will subsequently become suspended. To reestablish the pair with the CRIT(YES) option, issue a CSUSPEND command, then a CESTPAIR command with RESYNC and CRIT(YES) parameters.
Do not configure P/DAS to swap between installation-static and dynamic UCBs, as the results are unpredictable.
Do not involve volumes that contain sysplex control data sets in P/DAS volume pair operations.
If volume pairs are in PPRC extended distance mode, convert the pairs to synchronous mode to allow them to reach DUPLEX status before a swap operation begins. This ensures that the volume pairs are in sync and all updates are copied to the secondary.