Take into account the following considerations when you are using
CONSOLxx in a sysplex:
- When two or more systems in a sysplex require a CONSOLxx member,
you can do one of the following:
- Code a separate CONSOLxx member for each system in the sysplex
(the least efficient method).
- Code a single CONSOLxx member for all systems in your sysplex.
Specify parameters with sysplex scope to be used by all systems
in the sysplex. Consider using system symbols to represent unique
values in the member.
- CONSOLxx parameters with sysplex scope are valid only for
the first system that enters a sysplex. Because these parameters
are ignored by systems that later join a sysplex, you do not need
to set them up to specify unique values for different systems in a
multisystem environment. For a complete list of parameters in CONSOLxx
that have sysplex scope, refer to z/OS MVS Planning: Operations.
If
different systems require unique values on parameters that do not
have sysplex scope, you can use system symbols to represent those
unique values in a shared CONSOLxx member. When each system processes
CONSOLxx, it replaces the system symbols with the values it has defined
to them. See Sharing parmlib definitions.
- A named console can be defined on multiple systems, but can only
be active on one system at one time.
- The system uses default values for the CONSOLxx statements INIT,
HARDCOPY, and DEFAULT if you do not code them. If the default values
for these statements are acceptable to your installation, do not code
them for the systems in your multisystem environment.
- In distributed mode, the console attributes specified in CONSOLxx
are used whenever the console is activated. If the VARY command changes
the attributes of an active console, those changes remain until the
console is deactivated. The CONSOLxx values will then be used the
next time the console is activated. In both shared and distributed
mode, for the most part, the VARY command can not change the attributes
of an inactive console.
- For a complete list of the CONSOLxx values that can be changed
by operator command, the sysplex or system scope of the values, and
whether or not these values are restored to CONSOLxx parmlib member
settings or IBM® defaults by
a single system IPL or by reinitialization of the sysplex, see the
topic "Summary of CONSOLxx and Commands to Change Values" in z/OS MVS Planning: Operations.