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: Cette rubrique fait référence à un ou plusieurs des fichiers journaux de serveur d'applications. Il est recommandé de configurer le serveur de telle sorte qu'il utilise l'infrastructure de journalisation et de trace HPEL (High Performance Extensible Logging) à la place des fichiers SystemOut.log, SystemErr.log, trace.log et activity.log sur les systèmes distribués et IBM® i. Vous pouvez également utiliser HPEL conjointement avec vos fonctions de journalisation z/OS® natives. Si vous utilisez l'infrastructure HPEL, vous pouvez accéder à toutes les informations de journalisation et de trace en utilisant l'outil de ligne de commande LogViewer à partir de votre répertoire bin de profil de serveur. Pour plus d'informations sur l'utilisation de HPEL, voir les informations sur l'utilisation de HPEL en vue du traitement des incidents liés aux applications.
[AIX Solaris HP-UX Linux Windows][IBM i]
Table 1. Log and trace output for distributed and IBM i. This table lists the expected output for logging and tracing output streams for distributed and IBM i operating systems
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.
  • HPEL trace repository.
  • HPEL TextLog*.log, when you enable this log.
Java logs
  • Trace.log, when you enable tracing.
  • Activity.log. The Activity.log file is also directed to the Showlog output.
  • SystemOut.log
  • HPEL log repository
  • HPEL TextLog*.log, when you enable this log.
System.out stream
  • Trace.log
  • SystemOut.log
  • HPEL log repository
  • HPEL TextLog*.log, when you enable this log.
System.err stream SystemErr.log
  • HPEL log repository
  • HPEL TextLog*.log, when you enable this 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 modeGraphical representation of logging on distributed and IBM i
Figure 2. Distributed and IBM i - HPEL log and trace mode. Distributed and IBM i - HPEL log and trace modeGraphical representation of HPEL log and trace on distributed and IBM i
[z/OS]
Table 2. Log and trace output for z/OS. This table lists the expected output for logging and tracing output streams when the application server is installed on z/OS.
Log or trace stream Expected output - traditional log and trace mode Expected output - HPEL log and trace mode
Java trace SYSPRINT
Eviter les incidents Eviter les incidents: Trace information, which includes events at the Fine, Finer and Finest levels, is written only to this output. If you do not enable diagnostic trace, setting the log detail level to Fine, Finer, or Finest does not affect the logged data.gotcha
  • HPEL trace repository
  • HPEL TextLog*.log, when you enable this log
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:
  • HPEL log repository
  • HPEL TextLog*.log, when you enable this log
Java logs (other levels) SYSOUT or your configured error stream Same outputs as traditional log and trace mod, plus the following:
  • HPEL log repository
  • HPEL TextLog*.log, when you enable this log
System.out SYSPRINT
  • HPEL log repository
  • HPEL TextLog*.log, when you enable this log
System.err SYSOUT
  • HPEL log repository
  • HPEL TextLog*.log, when you enable this log
cout (the C or C++ output stream) SYSPRINT SYSPRINT
cerr (the C or C++ error stream) SYSOUT SYSOUT
Native trace SYSPRINT
Eviter les incidents Eviter les incidents: Trace information, which includes events at the Fine, Finer and Finest levels, is written only to this output. If you do not enable diagnostic trace, setting the log detail level to Fine, Finer, or Finest does not affect the logged data.gotcha
SYSPRINT
Eviter les incidents Eviter les incidents: Trace information, which includes events at the Fine, Finer and Finest levels, is written only to this output. If you do not enable diagnostic trace, setting the log detail level to Fine, Finer, or Finest does not affect the logged data.gotcha
Native Message logs SYSOUT or your configured error stream SYSOUT or your configured error stream
Note: Cette rubrique fait référence à un ou plusieurs des fichiers journaux de serveur d'applications. Il est recommandé de configurer le serveur de telle sorte qu'il utilise l'infrastructure de journalisation et de trace HPEL (High Performance Extensible Logging) à la place des fichiers SystemOut.log, SystemErr.log, trace.log et activity.log sur les systèmes distribués et IBM i. Vous pouvez également utiliser HPEL conjointement avec vos fonctions de journalisation z/OS natives. Si vous utilisez l'infrastructure HPEL, vous pouvez accéder à toutes les informations de journalisation et de trace en utilisant l'outil de ligne de commande LogViewer à partir de votre répertoire bin de profil de serveur. Pour plus d'informations sur l'utilisation de HPEL, voir les informations sur l'utilisation de HPEL en vue du traitement des incidents liés aux applications.
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 modeGraphical representation of traditional logging on z/OS
Figure 4. z/OS - HPEL log and trace mode. z/OS - HPEL log and trace modeGraphical representation of HPEL logging on z/OS

Icône indiquant le type de rubrique Rubrique de concept



Icône d'horodatage Dernière mise à jour: July 9, 2016 2:27
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=cprf_logging
Nom du fichier : cprf_logging.html