![[z/OS]](../images/ngzos.gif)
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:
Note: 這個主題參照一或多個應用程式伺服器日誌檔。
此外,在分散式和 IBM® i 系統上,另外也建議您可以配置伺服器來使用「高效能可延伸記載 (HPEL)」日誌和追蹤基礎架構,而不使用 SystemOut.log、SystemErr.log, trace.log 及 activity.log 檔案。HPEL 與原生 z/OS 記載機能也可以一起使用。如果您使用 HPEL,則可以從伺服器設定檔 bin 目錄,利用 LogViewer 指令行工具來存取您所有的日誌和追蹤資訊。請參閱有關利用 HPEL 疑難排解應用程式的資訊,以取得更多使用 HPEL 的相關資訊。
Procedure
- Because WebSphere Application Server for z/OS is predefined as a z/OS system logger application, you can use a log stream as the product's error log. By doing so, you can direct error information to a coupling facility log stream, which provides sysplex-wide error logging, or to a DASD-only log stream, which provides single system-only error logging.
- You can set up a common log stream for all WebSphere Application Server for z/OS servers, or individual log streams for each application server. Local z/OS client ORBs can also log data in log streams. The system logger APIs are unauthorized, but log stream resources can be protected using security products such as RACF®.
- You can use the WebSphere variable ras_time_local to control whether timestamps in the error log appear in local time (ras_time_local=1) or Greenwich Mean Time (GMT)(ras_time_local=0), which is the default.
- For additional information about z/OS log stream requirements, access the z/OS MVS™ Setting up a Sysplex, SA22-7625 available on the z/OS Library web page