Use UNIX System Services (USS) to retrieve logs according to your site-specific practices.
Note: For information about changing parameters, see the Administration Guide.
Server, boot, chorus, and discipline-specific log files are available in the following location:
/cai/cetjr4m0/logs
The following list provides a high-level introduction to the types of USS logs.
Note: Some of the following log files are in ASCII (code page ISO8859-1) format. When you send the files through FTP to a PC, transfer them in binary mode. To look at the files in z/OS, use the View ASCII data option for browse or the EA line command from the directory list.
Includes all generated logging from the CA Chorus Teiid thread. You can change the value of the priority element to DEBUG, INFO, WARN, ERROR, and FATAL depending on the log requirement. Messages include a standard prefix with timestamp, time zone, and thread ID. End-user information is provided in chorus-status.log, JESMSGLG, or WTO.
Name: chorus-investigator.tmp and server-ebcdic.log
Location: $CHORUS_HOME/logs
Settings: CA Chorus Application Server environment file -Djboss.server.log.threshold=DEBUG
Includes the EBCDIC version of all generated logging from the CA Chorus Teiid thread.
Name: ebcdic log
Location: $CHORUS_HOME/logs
Includes all application trace and user activity for the Storage Management Interface. Access this interface through the Quick Links module. You can view the logging information that is pertaining to the interaction between the Storage Management Interface and the mainframe storage products here. You can view all errors that are occurred with the Storage Management Interface and reported back from the mainframe storage products here.
Name: Storage Management Interface application log
Location: $CHORUS_HOME/logs
Includes the details that are generated whenever the code is invoked and the CA_AXIS2C_LOG_LEVEL variable is set to anything other than NONE. The Data Source API JNI code produces this log file. The USS thread ID is included in the file name. So, each thread writes to a separate log file.
Name: CoptDsService log
Location: $CHORUS_HOME/logs
Settings: CA Chorus Application Server ENVETJ file CA_AXIS2C_LOG_LEVEL=INFO|DEBUG|ERROR|FATAL
The following log files are written during the operation of the CA Chorus Application Server:
Includes details about threads that execute a web service request. One file is created for every unique thread that executes a web service request.
Identifies the name of the service (the subdirectory of axis2/services) that is being executed.
Indicates the POSIX thread ID of the thread executing the web service request.
Includes summary and accounting information for web service operations. This file is written from the CoptDsService code. When the first web service request comes in, the data source API initializes and writes startup information to this file. The following list shows example startup information:
Name: Copt ds log
Location: $CHORUS_HOME/logs
Includes watchdog thread data, which watches for sessions that are not active. If the idle time threshold is exceeded, the threads are removed. Messages appear when the thread wakes up and when it terminates any sessions. This file is written from the data source API service watchdog thread.
Name: Copt thread log
Location: $CHORUS_HOME/logs
Settings: CA Chorus Application server ENVETJ file CA_AXIS2C_LOG_LEVEL=INFO|DEBUG|ERROR|FATAL
Includes the generated logging information from the Policy Admin UI. The logging information is based on the settings in the log4j.properties file. Based on the log requirement, one of the following values can be the logging information:
Messages include a standard prefix with timestamp, log level, java file name, and message location.
Name: Policy admin log
Location: $CHORUS_HOME/logs
Includes the output that is written from the DSI (Distributed Security Interface) server that is spawned during the CA Chorus Application Server initialization. These files contain meaningful data if the debug setting is set to a value other than zero. Sensitive information can be written to these files when the debug is enabled. So, enable this log only when necessary.
Name: DSI output
Location: $CHORUS_HOME/logs
Settings: Debug setting in dsi.conf (65535 is maximum detail).
Includes CA Chorus status, including error messages that indicate the following details:
Additionally, the log includes messages that indicate when the product starts and when it is available.
Name: status log
Location: $CHORUS_HOME/logs
Includes the generated logging information from the Security Admin UI. The logging information is based on the settings in the log4j.properties file. Based on the log requirement, one of the following values can be the logging information:
Messages include a standard prefix with timestamp, log level, java file name, and message location.
Name: Sec admin log
Location: chorus/logs
Includes multiple system output files. End-user information is provided in chorus-status.log, JESMSGLG, or WTO.
Location: Spool data sets in the z/OS job output for the task.
Includes the CA Chorus Application Server messages that are produced during the bootstrap phase.
Name: boot.log
Location: $CHORUS_HOME/logs
Includes Teiid queries and error messages.
Note: This log is disabled by default. Enable it only if CA Support requests that you do so.
Name: chorus-query.log
Includes database information. CA Chorus uses a database that is installed into the CA Datacom/AD environment.
Location: Spool data sets in the z/OS job output for the task.
Note: For the logs associated with a specific discipline, see the applicable User Guide.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|