IBM OS/390 User Manual
23.3.1 SYSLOG
The system log (SYSLOG) is a data set residing in the primary job entry
subsystem
subsystem
′
s spool space. It can be used by application and system
programmers to record communications about problem programs and system
functions. The operator can use the LOG command to add an entry to the system
log.
functions. The operator can use the LOG command to add an entry to the system
log.
SYSLOG is queued for printing when the number of messages recorded reaches
a threshold specified at system initialization. The operator can force the system
log data set to be queued for printing before the threshold is reached by issuing
the WRITELOG command. As part of the WRITELOG command, pick a SYSOUT
class that is not used for normal printing so it is not printed unintentionally.
a threshold specified at system initialization. The operator can force the system
log data set to be queued for printing before the threshold is reached by issuing
the WRITELOG command. As part of the WRITELOG command, pick a SYSOUT
class that is not used for normal printing so it is not printed unintentionally.
23.3.2 Printing SYSLOG
SYSLOG is so voluminous that you would not want to print the entire data set.
Use SDSF to browse it and print portions by allocating SYSOUT data sets
through JES.
Use SDSF to browse it and print portions by allocating SYSOUT data sets
through JES.
Archive it using a spool archiving mechanism to save it for future problem
determination and auditing purposes.
determination and auditing purposes.
23.4 OPERLOG
The operations log (OPERLOG) is an MVS system logger application that records
and merges messages about programs and system functions (the hardcopy
message set) from each system in a sysplex that activates OPERLOG. Use
OPERLOG rather than the system log (SYSLOG) as your hardcopy medium when
you need a permanent log about operating conditions and maintenance for all
systems in a sysplex. Only the systems in a sysplex that have specified and
activated the operations log will have their records sent to OPERLOG.
and merges messages about programs and system functions (the hardcopy
message set) from each system in a sysplex that activates OPERLOG. Use
OPERLOG rather than the system log (SYSLOG) as your hardcopy medium when
you need a permanent log about operating conditions and maintenance for all
systems in a sysplex. Only the systems in a sysplex that have specified and
activated the operations log will have their records sent to OPERLOG.
The operations log is operationally independent of the system log. An installation
can choose to run with either or both of the logs. If you choose to use the
operations log as a replacement for SYSLOG, you can prevent the future use of
SYSLOG; once the operations log is started with the SYSLOG not active, enter
the WRITELOG CLOSE command.
can choose to run with either or both of the logs. If you choose to use the
operations log as a replacement for SYSLOG, you can prevent the future use of
SYSLOG; once the operations log is started with the SYSLOG not active, enter
the WRITELOG CLOSE command.
In a single system environment, OPERLOG can reside on DASD, otherwise it is
written to a coupling facility structure. When installation defined thresholds are
reached, the system logger stores log data on DASD log data sets. You should
use System Managed Storage (SMS) and DFHSM to manage the DASD log data
sets. See
written to a coupling facility structure. When installation defined thresholds are
reached, the system logger stores log data on DASD log data sets. You should
use System Managed Storage (SMS) and DFHSM to manage the DASD log data
sets. See
OS/390 MVS Setting Up a Sysplex, GC28-1779 for details.
23.4.1 Printing OPERLOG
OPERLOG is so huge that you would not want to print the entire log stream. Use
SDSF to browse it and print portions by allocating SYSOUT data sets for JES to
print.
SDSF to browse it and print portions by allocating SYSOUT data sets for JES to
print.
394
VSE to OS/390 Migration Workbook