INIT, DEFAULT, and HARDCOPY statements define general
characteristics for all MCS, HMCS, and SMCS consoles
in the system or sysplex.
The INIT statement
You use the INIT statement to control basic initialization
values for all MCS,
HMCS or SMCS consoles in the
configuration. INIT lets you control the following:
- Specification of the console group parmlib member.
- Certain console screen functions for all consoles
(activating the PFKTABxx member to control the PFK tables for MCS, HMCS and SMCS consoles, displaying certain information
for mount messages, and specifying the command delimiter for operator
input of multiple commands)
- Message processing (such as activating MPF, AMRF,
and the IEAVMXIT message processing exit; and controlling WTO and
WTOR messages, the hardcopy message set, and MMS for message translation).
- The SMCS VTAM® application
for controlling SMCS consoles.
After IPL, operators can use the SET command to change some values
defined on the INIT statement. See Table 1,
which summarizes console functions that you control on the INIT statement:
The DEFAULT statement
You use the DEFAULT statement to control certain default
values for MCS,
HMCS and SMCS consoles in the
configuration. DEFAULT lets you specify console attributes that control
the following for an MCS,
HMCS and SMCS console
configuration:
- Console security by specifying operator logon options
- Certain console screen functions for all consoles (ability for
operators to hold messages on the screen)
- Routing for messages without routing codes or other message queuing
information, and routing for synchronous messages that bypass normal
message queuing
- Determining the maximum value for operator REPLY ids.
Unlike values in CONSOLE and INIT, operators cannot
change individual DEFAULT statement values. Operators must re-IPL
the system, or, in some cases, the sysplex, with the CONSOLxx member
that contains the new DEFAULT statement.
Table 2 summarizes console functions
that you can control using the DEFAULT statement:
Table 2. Summary of DEFAULT
statement functionsTask |
DEFAULT statement keyword |
MVS command
to change value |
See topic |
---|
Controlling
console security: |
- Operator logon to MCS, HMCS and SMCS consoles
|
LOGON1 |
V CN(...),LOGON= |
Using RACF to control command authority and operator logon |
Controlling
the console screen function: |
- Freezing the display of messages on MCS, HMCS or
SMCS console screens
|
HOLDMODE |
Must re-IPL |
Temporarily suspending the screen roll |
Controlling
message routing: |
- Assigning routing codes for messages without any specified target
|
ROUTCODE |
Must re-IPL |
Handling messages without routing codes |
- Assigning the name of a console group to receive
synchronous messages
|
SYNCHDEST |
Activate another CNGRPxx member (SET
CNGRP) that defines the same console group but with different console
members. |
Display of synchronous messages |
Controlling
message processing: |
- Maximum number of REPLY ids
|
RMAX |
CONTROL M,RMAX |
Controlling WTO and WTOR message buffers |
Note: 1. VARY CN(),LOGON
can be used to change attribute of an inactive SMCS (only) console.
|
The HARDCOPY statement: You
can use the optional HARDCOPY statement to define the characteristics
of the hardcopy message set and specify the hardcopy medium. You can
control how to record messages and commands for the system. After
IPL, operators can use the VARY command to do the following:
- Change the set of messages included in the hardcopy message set
- Assign SYSLOG and/or OPERLOG as the hardcopy medium
For information about using the VARY command, see z/OS MVS System Commands.
For information about hardcopy processing, see Hardcopy processing.
Table 3 summarizes console functions
you can control using the HARDCOPY statement:
Table 3. Summary of HARDCOPY
statement functionsTask |
HARDCOPY statement keyword |
MVS command
to change value |
See topic |
---|
Controlling
logging and system recording: |
Note: If the Hardcopy function is important to you, you should
use both SYSLOG and OPERLOG.
|
DEVNUM |
VARY OPERLOG,HARDCPY
VARY
SYSLOG,HARDCPY
|
Hardcopy processing |
- Routing codes for the hardcopy message set
|
ROUTCODE |
VARY OPERLOG|SYSLOG,HARDCPY,AROUT
VARY
OPERLOG|SYSLOG,HARDCPY,DROUT
|
Hardcopy processing |
- Hardcopy of commands by level
|
CMDLEVEL |
VARY OPERLOG|SYSLOG,HARDCPY,cmdlevel |
Hardcopy processing |
- Defining year format in SYSLOG
|
HCFORMAT |
Must re-IPL |
Hardcopy processing |