z/OS MVS Setting Up a Sysplex
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Operations log and logrec application recovery

z/OS MVS Setting Up a Sysplex
SA23-1399-00

Each system logger application will issue messages to indicate that an error has occurred and explain it:
  • OPERLOG: If operations log encounters an unrecoverable error, such as a damaged log stream or coupling facility structure, the system attempts to switch to a different hardcopy medium, such as SYSLOG or a device, based on what is defined on the HARDCOPY statement in the CONSOLxx parmlib member. (See z/OS MVS Initialization and Tuning Reference for more the CONSOLxx parmlib member.)

    If an error occurs, the operations log issues message IEE316I indicating that OPERLOG has failed, the system where it has failed, and possibly some additional explanation of the problem. Message IEE316I might show some return and reason codes returned to operations log from system logger service; look these up in the z/OS MVS Programming: Assembler Services Guide. Operations log issues message IEE710I showing the hardcopy medium that is active after OPERLOG fails.

  • Logrec log stream: If logrec encounters a system logger error, logrec issues system message IFB100E explaining the problem. See the explanation of message IFB100E in z/OS MVS System Messages, Vol 8 (IEF-IGD).

    If the error is recoverable, logrec resumes writing to the log stream. If the error is unrecoverable, an operator action might be required to switch hardcopy recording mediums or to resume writing to the log stream.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014