Differentiate the GDPS operations for the Normal CFs and the Standby CFs that are normally deactivated

Differentiate the GDPS operations for the "Normal" CFs and the "Standby" CFs that are normally deactivated.

The customers need that the GDPS in its Coupling Facility operations differentiates between the "Normal" Coupling Facilities and the "Standby" Coupling Facilities that are normally deactivated.

This could be implemented in panel VPCPSPM5 Sysplex Resource Management adding a field that identified the CF like “Normal” (that are normally activated) or “Standby” (that are normally deactivated) and in REXX VPCESPM4 that process the statement SYSPLEX CF and options in Sysplex Resource Management panel.

For the “Normal” CFs the operations that the GDPS issues would have to be the same as before the application of the PTF for APAR PI50270 (included in the base code of GDPS V3R13) and according to the documentation in manual ZG24-6703-28 GDPS/PPRC V3R13 Installation and Customization Guide in chapter 5.7.2 Working with Coupling Facilities:

“For any non-operational CF, GDPS attempts to enable these CFs by stopping maintenance mode and configuring and varying on the appropriate chpids and paths for the subject CF. The panel action fails if any CF in the target site cannot be made operational.”

Therefore:

If the PATHs are LOGICAL OFFLINE in message IXL150I GDPS must issue commands V PATH ONLINE.

If CHPIDs are OFFLINE:
NO COUPLING CHANNEL PATH STATUS AVAILABLE
COUPLING CHANNELS DEFINED TO THIS FACILITY
in message IXL150I GDPS must issue commands CF CHP ONLINE and V PATH ONLINE.

If the CF can be made operational (PATHs and CHPIDs are ONLINE) GDPS must issue command SETXCF STOP,MAINTMODE,CFNAME=. On the contrary if the CF cannot be made operational GDPS don't must issue command SETXCF STOP,MAINTMODE,CFNAME= to avoid that a non-operative CF is without maintenance mode which could bring about problems in XCF.

If any CF in the target site cannot be made operational for example because it is Deactivated or SHUTDOWN, GDPS must fail statement SYSPLEX CF with a RC=8 or message “CF Configuration change FAILED” for the operations via panel options.


For the “Standby” CFs (that are normally deactivated) the operations that GDPS issues would have to be the same as described in a APAR PI50270:

“Ignore CFs that are deactivated at the time the SYSPLEX='CF NORMAL' is executed”.

Therefore:
Do not issue commands V PATH ONLINE, CF CHP ONLINE if the CF is Deactivated (PHYSICAL PATH NOT AVAILABLE in msg IXL150I).
Do not issue command SETXCF STOP,MAINTMODE,CFNAME= .
Gives back RC=0 for the statement SYSPLEX CF if the “Standby” CF cannot be made operational.