Ensure that your sysplex uses the distributed mode of console operation
Description
In z/OS V2R3, z/OS consoles must be operated in distributed mode, rather than shared mode. Your sysplex must be migrated to distributed mode before you can add a z/OS V2R3 system to the sysplex.
Distributed mode was introduced in z/OS V1R10; it became the default mode in z/OS V1R13.
As of V2R3, the IBMCNZ,CNZ_CONSOLE_OPERATING_MODE health check is removed.
Table 1 provides more details about the migration action. Use this information to plan your changes to the system.
Element or feature: | BCP |
---|---|
When change was introduced: | See Statement of direction: IBM z/OS IBM United States Software Announcement 212-086 April 11, 2012 |
Applies to migration from: | z/OS V2R2 and z/OS V2R1. |
Timing: | Before installing z/OS V2R3. |
Is the migration action required? | Yes, if you are using shared mode. |
Target system hardware requirements: | None. |
Target system software requirements: | None. |
Other system (coexistence or fallback) requirements: | None. |
Restrictions: | None. |
System impacts: | If your sysplex is not operating in distributed mode, you cannot add a z/OS V2R3 system to the sysplex. |
Related IBM Health Checker for z/OS check: | Use health check IBMCNZ,CNZ_CONSOLE_OPERATING_MODE to determine whether your
sysplex is operating in the distributed console mode, which is preferred. This health check:
|
Steps to take
To run in distributed mode, you must perform a sysplex-wide migration to distributed mode. You can do so through a sysplex-wide IPL or dynamically, by using the command SETCON MODE=DISTRIBUTED. To perform the migration, all of your systems must be z/OS V1R10 or later.
Reference information
For more information about distributed mode, see z/OS MVS Planning: Operations.