CONSOLxx is an installation-created member of parmlib
in which you can define a console configuration to meet the particular
needs of your installation.
In CONSOLxx, you define multiple console support (MCS),
SNA multiple console support (SMCS) consoles, and hardware management
console multiple console support (HMCS) consoles. You define the specific
characteristics of MCS, SMCS, HMCS, subsystem consoles and the system
console. You might need to have PF keys on one console issue one group
of system commands while on another console you need the PF keys set
to issue a different set of commands. You might need to have particular
messages routed to one console, and you may want those messages deleted
in a certain way. You might need a cluster of consoles to serve different
functions for a subsystem. One console in the cluster may display,
in a particular format, only the messages associated with a particular
group of routing codes. Through CONSOLxx, you can specify the configuration
and have the system automatically initialize the consoles.
Note: In
a sysplex environment, the limit of consoles you can define varies
depending on the operation mode of the console support. In shared
mode, up to 99 MCS, SMCS, HMCS, and subsystem consoles can be defined
per sysplex. In distributed mode, up to 250 MCS, SMCS, HMCS, and subsystem
consoles can be defined per z/OS® image.
For more information about operation modes, see
z/OS MVS Planning: Operations.
Through CONSOLxx, you can specify initialization values
for all console configurations. For example, you can define the characteristics
of the hardcopy message set and set routing codes for messages that
do not have routing information. You can specify the parmlib member
that contains tracing options for the operations services (OPS) component.
You also can specify the operator logon requirements for the consoles
at your installation (except the system console). Setting operator
logon requirements depends on the security policy in effect at your
installation. For information about how operator logon requirements
relate to securing access to system commands, and examples of defining
consoles through CONSOLxx, see z/OS MVS Planning: Operations.
You can use some operator commands to dynamically
change the console attributes. In distributed mode, the changes made
by such commands are only effective when the console is active. The
CONSOLxx values will be used the next time the console is activated.
In both shared and distributed mode, for the most part, operator commands
cannot change the attributes of an inactive console. See Related commands for more information.
SET CON= can be used to dynamically add a console definition
and to dynamically change console settings and attributes.
Note: MCS consoles are locally attached to the system
through control devices that do not support Systems Network Architecture
(SNA) protocols. SMCS consoles use z/OS Communications
Server to communicate with the system and may be remotely attached
to the system. SMCS consoles are only available for use when the z/OS Communications Server is active.
HMCS consoles are on the Hardware Management Console Integrated 3270
Console window.