Use the HARDCPY form of the VARY command to do the following:
- Change the set of messages included
in the hardcopy message set
- Assign either SYSLOG or OPERLOG to be the hardcopy medium
- Stop the hardcopy medium.
The system establishes hardcopy processing during system initialization
based on the HARDCOPY statement in the CONSOLxx member of Parmlib.
The ROUTCODE and CMDLEVEL parameters define messages that are included
in the hardcopy message set.
The syntax of the VARY HARDCPY command is:
V [OPERLOG],HARDCPY[,CMDS|,NOCMDS|,STCMDS|,INCMDS]
|SYSLOG [,AROUT=(rtcode[,rtcode]...)]
[,DROUT=(rtcode[,rtcode]...)]
[,ROUT={ALL|NONE }]
{(rtcode[,rtcode]...)}
[,OFF[,UNCOND]]
|
- OPERLOG
- The operations log is to be activated or deactivated.
When
you omit the SYSLOG or OPERLOG operands, the system changes what goes
into the hardcopy log, rather than the hardcopy log medium.
- SYSLOG
- The system log is to become the hardcopy medium.
- HARDCPY
- The system changes the hardcopy medium or the hardcopy message
set, or both, depending on the options specified.
The following NOCMDS, INCMDS, STCMDS, and CMDS options correspond
to the CMDLEVEL specifications of the HARDCOPY statement:
- NOCMDS
- The system is not to include operator commands or their responses
in the hardcopy message set.
Note: If hardcopy support is
required and you specify NOCMDS, the system will not allow NOCMDS
and will choose CMDLEVEL=CMDS. (Hardcopy support is required when
one or more display consoles are defined in a system.)
- INCMDS
- The system is to include operator commands and their responses,
excluding any status displays, in the hardcopy message set.
- STCMDS or CMDS
- The system includes all operator and system commands, their
responses, and status displays in the hardcopy message set. As of z/OS® V1R8,
STCMDS and CMDS are equivalent.
Note: The following descriptor codes are associated with
the above options:
Options |
Descriptor Codes |
NOCMDS |
None |
INCMDS |
5 |
STCMDS |
5, 8, 9 |
CMDS |
5, 8, 9 |
- OFF
- The system is to stop the hardcopy medium.
If
you do not specify SYSLOG or OPERLOG, the system defaults to the hardcopy
medium (SYSLOG) if it is active; otherwise, the system rejects the
command. The system will not deactivate the operations log unless
OPERLOG is specified. If you specify OPERLOG, the operations log must
be active.
The system rejects this command if it would result
in both the hardcopy log and the operations log becoming inactive.
When
OFF is specified without UNCOND, it must be the last parameter.
- UNCOND
- Use UNCOND with OFF to specify that the system is to stop the
hardcopy medium. The system saves messages depending on the hardcopy
medium status:
Hardcopy medium and state |
Whether messages are saved |
Only SYSLOG is active and is varied off with
UNCOND |
Yes |
Only OPERLOG is active and is varied off with
UNCOND |
No |
Both SYSLOG and OPERLOG are active and SYSLOG
is varied off with UNCOND |
Yes |
Both SYSLOG and OPERLOG are active and OPERLOG
is varied off with UNCOND |
No |
Note: - Messages are saved for SYSLOG until the LOGLIM value
is reached, after which the messages will then be discarded.
- If the hardcopy medium is SYSLOG, and SYSLOG has never been activated
in the system, messages will not be saved.
The use of UNCOND should be a temporary measure, and
should be done only as a last resort in order to repair hardcopy functions.
The installation might lose messages from hardcopy if too long a period
elapses before the hardcopy medium is restored. The system issues
message IEE012A when messages are no longer being saved.
When
UNCOND is specified with OFF, UNCOND must be the last parameter.
- ROUT=
- The system is to include messages with the specified routing
code or codes in the hardcopy message set. In addition to the routing
codes you specify, the hardcopy message set also includes messages
with the minimum set of routing codes (1,2,3,4,7,8,10, and 42) established
at initialization by the HARDCOPY statement of CONSOLxx.
- ALL
- All routing codes (1-128) are used to select messages for the
hardcopy message set.
- NONE
- No routing codes are used to select messages for the hardcopy
message set.
- rtcode
- rtcode — rtcode
- The specified routing code or codes are used to select messages
for the hardcopy message set. rtcode is a decimal number
from 1 to 128. You can specify a single routing code, a range of
routing codes, or a combination of both.
- AROUT
- The system is to include messages with the specified routing
code or codes in the hardcopy message set, in addition to any messages
included because of prior routing code specifications.
- rtcode
- rtcode — rtcode
- The specified routing code or codes, in addition to currently
used routing codes, are used to select messages for the hardcopy message
set. rtcode is a decimal number from 1 to 128. You can
specify a single routing code, a range of routing codes, or a combination
of both.
- DROUT
- The system is to stop including messages with the specified
routing code or codes in the hardcopy message set.
- rtcode
- rtcode — rtcode
- The specified routing code or codes are no longer used to select
messages for the hardcopy message set. rtcode is a decimal
number from 1 to 128. You can specify a single routing code, a range
of routing codes, or a combination of both.
Note: At system initialization, processing of the
HARDCOPY statement of the CONSOLxx member of Parmlib sets up a minimum
set of routing codes (1,2,3,4,7,8,10, and 42) in addition to any other
specified for the hardcopy message set.
The system processes the ROUT, AROUT, and DROUT operands in the
order that you specify them.
Example 1:
To include all operator commands, responses, and status displays
(except dynamic status displays) in the hardcopy message set, enter:
V ,HARDCPY,STCMDS
Example 2:
To have the hardcopy message set recorded on the system log, enter:
V SYSLOG,HARDCPY
Example 3:
To add routing codes 11, 12, 13, 17, and 44 to the routing codes
already defined for the hardcopy message set, enter:
V ,HARDCPY,AROUT=(11-13,17,44)
Example 4:
To have the hardcopy message set recorded on the operations log,
enter:
V OPERLOG,HARDCPY