Below is a description of the types of tools and controls you can use for diagnosing and managing problems in the product environment.
The console displays configuration errors that cause the termination of the product address spaces. Whatever goes to the console also goes to SYSLOG.
SYSLOG is the repository for all messages that have appeared on the operator console. It also contains warning and informational messages that might be helpful after a failure has occurred.
The job log contains errors and warnings (non-termination) that are related to configuration. Anything that goes to the console and SYSLOG automatically goes to the job log.
SYSOUT is a batch log that usually contains diagnostic data from the Java Virtual Machine (JVM) that runs in the servant. Any messages written to stderr will end up in SYSOUT. In addition, SYSOUT might contain error messages that usually appear in the log stream, but were redirected to SYSOUT, because the log stream was not available.
The error log contains messages issued through Java logging and JRas support, if any. In addition, the error log usually contains messages that are only intended for IBM use. These messages support actions, problems, or issues that are usually externalized through additional messages that are issued by other functions. When you work with IBM Support personnel, you might be asked to supply the error log so that service personnel can use these support messages to help diagnose the problem.
SYSPRINT contains component trace (CTRACE) output for clients, and for servants when the product is configured to use SYSPRINT instead of CTRACE buffers and data sets.
CTRACE data sets contain diagnostic trace entries for various processes, depending on the trace options configured for the product.
When an error occurs, the system records information about the error in the logrec data set or the logrec log stream. The information provides you with a history of all hardware failures, selected software errors, and selected system conditions.
This log is used for recovery of XA resources. When an application accesses XA resources, the product stores information about the resource to enable XA transaction recovery. For instructions on how to use the Profile Management Tool or the zpmt command to configure the Transaction XA Partner Log see the "Customization variables: Stand-alone application server cell" topic in the installing your application serving environment section. For instructions on how to change the location of the Transaction XA Partner Log, see the transaction service settings information.
Use the SDSF DA panel to see how many application server address spaces are active, and observe at the CPU%, ECPU% and SIO rate. Use the "ENC" panel to see the enclaves running and what service classes they are running under.
See Using RMF for instructions on starting and using RMF to monitor your transactions.
See the getting help for the modify command example documentation for instructions on using the z/OS modify command to display information about the product servers or servants.