Explanation
The system log (SYSLOG) is not active for one of
these reasons:
- The system failed to initialize the system log. The system issues
message IEE533E before this message to indicate that this is the problem.
- Recursive abends have occurred in more than one system log data
set. The system issues message IEE769E before this message to indicate
that this is the problem.
- The SYSLOG function is ending because of a WRITELOG CLOSE or HALT
command. The system issues message IEE043I before this message to
indicate that this is the cause.
System action
The system makes the system log unavailable. The
system converts any WTL macros to WTO macros and sends the messages
to the console with master authority under message IEE147I.
Operator response
Depending on the reason for the failure, perform
the following:
- In case 1, the system tries to initialize the log with a WRITELOG
START command. Look for messages that indicate that the system log
has started. If these do not appear, enter a WRITELOG START command
to start the system log (followed by VARY SYSLOG,HARDCPY if the system
log is to be the hardcopy medium). If the system issues message IEE037D
again and use of the system log is critical, re-IPL.
- In case 2, contact the system programmer. If the system log function
is desired, initialize the system log again by entering a WRITELOG
START command (followed by VARY SYSLOG,HARDCPY if the system log is
to be the hardcopy medium)..
- In case 3, if the system log function is desired, initialize the
system log again by entering a WRITELOG START command (followed by
VARY SYSLOG,HARDCPY if the system log is to be the hardcopy medium).
System programmer response
Search problem reporting data bases
for a fix for the problem. If no fix exists, contact the IBM® Support
Center.
Source
Module
Routing code
Descriptor code