[z/OS]

Setting up the error log

WebSphere® Application Server for z/OS® uses an error log to record error information when an unexpected condition or failure is detected within the product's own code. You can use the log stream to record activity and help diagnose problems.

About this task

Unexpected conditions or failures include:
  • Assertion failures
  • Unrecoverable error conditions
  • Failures related to vital resources, such as memory
  • Operating system exceptions
  • Programming defects in WebSphere Application Server for z/OS code.
Note: This topic references one or more of the application server log files. As a recommended alternative, you can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM® i systems. You can also use HPEL in conjunction with your native z/OS logging facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.

Procedure


Icon that indicates the type of topic Task topic



Timestamp icon Last updated: March 5, 2017 17:29
File name: ttrb_errorlog.html