Controlling the hardcopy log
The hardcopy log records command and message traffic for your systems. MVS™ and
JES3 provide three forms of the hardcopy log:
- OPERLOG
- centrally records command and message traffic for systems in a sysplex in Message Data Block (MDB) format
- JES3 DLOG
- centrally records command and message traffic for systems in a JES3 complex in JES3 format. The JES3 DLOG is written to SYSLOG on the global processor.
- SYSLOG
- individually records command and message traffic for each system in MVS format
You must have at least one active hardcopy log on each of your systems.
OPERLOG is controlled on each processor using the VARY OPERLOG command.
When you use the disk log facility, the log is spun off at installation-defined intervals and processed by JES3 output service according to the DLOG output class. If DLOG is active, you can force the log to be spun off before the installation-defined threshold occurs by entering the MVS WRITELOG command on the global. For example, to spin off the DLOG and direct it to output class D, enter WRITELOG D.
The JES3 DLOG is controlled using the *MODIFY O,DLOG=ON|OFF command. SYSLOG on the global processor must be active when DLOG is active.