When the operator initializes an MVS™ system with CONSOLxx, the console definitions and attributes are in effect for the system. MCS, HMCS and SMCS consoles defined by CONSOLE statements are active, and the values specified for INIT and DEFAULT , and HARDCOPY control console operations for the system. Operators can use the CONTROL, MONITOR, SET, and VARY commands to change many of the definitions after the system is active.
In a sysplex, certain CONSOLxx keywords have sysplex scope. When a system with those keywords is first IPLed into a sysplex, the keyword values are in effect for the entire sysplex.
For example, NAME on the CONSOLE statement has sysplex scope. NAME specifies a unique name that identifies the console within the sysplex.
For INIT and DEFAULT keywords that have sysplex scope, CONSOLxx for the first system that joins the sysplex determines the values in effect for all systems in the sysplex. When other systems join the sysplex, MVS ignores changes to keyword values with sysplex scope defined in CONSOLxx for those systems. For example, if the action message retention facility (AMRF) is active in CONSOLxx for the first system that joins the sysplex, the sysplex ignores the AMRF keyword specified for other systems that join, and the action message retention facility is active for all systems in the sysplex.
CONSOLxx keywords that have system scope apply only to the system on which they are defined. For example, UNIT for CONSOLE and all keywords for HARDCOPY have system scope. The device type (UNIT) for the console applies only to the system where the console is attached. Similarly, the hardcopy log specifications for HARDCOPY apply only to the local system where CONSOLxx is defined.
See Table 1 and Table 2 to check which keywords on each CONSOLxx statement are system or sysplex in scope.
Understanding the scope of CONSOLxx keywords is important when you plan your console configuration for a sysplex. Depending on the needs of your installation and the scope of CONSOLxx keywords, you can specify CONSOLxx for systems in a sysplex in different ways. Consider the following ways to define CONSOLxx in a sysplex:
The method you choose depends on how you want to use the console device numbers. If you want to define a console with the same device number on two different systems, the consoles must have different names. Therefore, if you use the same device numbers for consoles across the sysplex, you must use option 2, or option 1 with symbolics. If the sysplex requires unique console device numbers, you can use any of the methods.