You can define separate CONSOLxx members for each system in the sysplex. Like Figure 1, Figure 1, shows SYA with three physically attached consoles (CON1, CON2, and CON3) and SYB with one physically attached console (CON4). Console statements are defined in two CONSOLxx members, one for each system in the sysplex.

Figure 1. Console Configuration in a Sysplex with Two Systems and Four MCS Consoles

The following are the CONSOLxx statements for each system in this configuration:

This configuration provides great flexibility for consoles in the sysplex. You can define consoles based on the needs of each system. However, depending on when the systems join the sysplex, the scope of the CONSOLxx keywords can affect how the consoles operate in the sysplex.

For CONSOLxx keywords with sysplex scope, keyword values apply to all the systems in the sysplex. For example, the RMAX keyword in CONSOLxx defines the maximum number of replies for the sysplex. It is specified, or defaulted to, by the first system to enter the sysplex. Subsequent CONSOLxx RMAX values will be ignored and the value can only be altered through command (K M,RMAX). Since the first system governs the value it is important to understand the scope of the CONSOLxx keywords.

For CONSOLxx keywords with system scope, keyword values apply only to the system where the consoles are physically attached. For example, the MPF keyword in CONSOLxx for SYB indicates that MPFLST01 is active when SYB is initialized. However, because MPF has system scope, the default for MPF used on SYA indicates that SYA does not perform MPF message processing. In a sysplex that uses unique CONSOLxx members, it is therefore important to understand the scope of CONSOLxx keywords for each system.