Log streams and expected output
Investigating the logging and tracing output for the application server is an excellent way to observe performance, diagnose problems, and gain a general understanding of how the application server is working within your environment. The expected output locations for logging and trace information can be different depending on the operating system on which the application server is running.
Note: 這個主題參照一或多個應用程式伺服器日誌檔。
此外,在分散式和 IBM® i 系統上,另外也建議您可以配置伺服器來使用「高效能可延伸記載 (HPEL)」日誌和追蹤基礎架構,而不使用 SystemOut.log、SystemErr.log, trace.log 及 activity.log 檔案。HPEL 與原生 z/OS® 記載機能也可以一起使用。如果您使用 HPEL,則可以從伺服器設定檔 bin 目錄,利用 LogViewer 指令行工具來存取您所有的日誌和追蹤資訊。請參閱有關利用 HPEL 疑難排解應用程式的資訊,以取得更多使用 HPEL 的相關資訊。
![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
![[IBM i]](../images/iseries.gif)
Log or trace stream | Expected output - basic log and trace mode | Expected output - HPEL log and trace mode |
---|---|---|
Java™ trace | Trace.log. You must have tracing enabled. |
|
Java logs |
|
|
System.out stream |
|
|
System.err stream | SystemErr.log |
|
cout (the C or C++ output stream) | Native stdout | Native stdout |
cerr (the C or C++ error stream) | Native stderr | Native stderr |
Figure 1. Distributed and IBM i
- Basic log and trace mode. Distributed and IBM i - Basic log and trace mode

Figure 2. Distributed and IBM i - HPEL log and trace mode. Distributed and IBM i - HPEL log and trace mode

![[z/OS]](../images/ngzos.gif)
Log or trace stream | Expected output - traditional log and trace mode | Expected output - HPEL log and trace mode |
---|---|---|
Java trace | SYSPRINT![]() |
|
Java logs (Audit level) | Transformed into write-to-operator (WTO) output to the hard copy logging stream | Same outputs as traditional log and trace mode, plus the following:
|
Java logs (other levels) | SYSOUT or your configured error stream | Same outputs as traditional log and trace mod, plus the following:
|
System.out | SYSPRINT |
|
System.err | SYSOUT |
|
cout (the C or C++ output stream) | SYSPRINT | SYSPRINT |
cerr (the C or C++ error stream) | SYSOUT | SYSOUT |
Native trace | SYSPRINT![]() |
SYSPRINT![]() |
Native Message logs | SYSOUT or your configured error stream | SYSOUT or your configured error stream |
Note: 這個主題參照一或多個應用程式伺服器日誌檔。
此外,在分散式和 IBM i 系統上,另外也建議您可以配置伺服器來使用「高效能可延伸記載 (HPEL)」日誌和追蹤基礎架構,而不使用 SystemOut.log、SystemErr.log, trace.log 及 activity.log 檔案。HPEL 與原生 z/OS 記載機能也可以一起使用。如果您使用 HPEL,則可以從伺服器設定檔 bin 目錄,利用 LogViewer 指令行工具來存取您所有的日誌和追蹤資訊。請參閱有關利用 HPEL 疑難排解應用程式的資訊,以取得更多使用 HPEL 的相關資訊。
When
considering the direction of log and trace streams, keep in mind the
following acronyms and abbreviations:- cerr
- C or C++ error steam
- cout
- C or C++ output steam
- DD
- Data Description statements
- HFS
- Hierarchical File System
- JCL
- Job Control Language
- JES
- Job Entry Subsystem
- MVS™
- Multiple Virtual Storage
- WTO
- Write-to-operator
- WTOR
- Write-to-operator with reply
Figure 3. z/OS - Traditional
log and trace mode. z/OS -
Traditional log and trace mode

Figure 4. z/OS - HPEL log
and trace mode. z/OS -
HPEL log and trace mode
