When determining the root cause of an issue, we may ask for log files to review the performance history of CA Chorus for DB2 Database Management. The following list provides a high-level introduction to the types of logs and their locations:
Note: For log details and locations for common CA Chorus functionality, see the CA Chorus Administration Guide.
Includes CA SYSVIEW for DB2 performance data. Each CA SYSVIEW for DB2 data collector started task is continuously monitoring the performance indicators for one DB2 subsystem. CA SYSVIEW for DB2 logs operational status information to the joblog and SYSOUT data sets. This logging reflects local z/OS system time.
Log Location: Spool data sets in the z/OS job output for the started task.
CA Chorus for DB2 Database Management Responsibilities: CA SYSVIEW for DB2 provides data for several Application Performance and Subsystem Performance displays. CA SYSVIEW for DB2 also sends DB2 Alert data to Xmanager, which feeds it into the CA Chorus server.
(Optional) Directs output to a data set instead of SYSOUT (the default). Add the following DD statements for the sequential log data sets to the OFAPROC started task JCL:
//LOGGER1 DD DISP=SHR,DSN=hlq.LOGGER1 //LOGGER2 DD DISP=SHR,DSN=hlq.LOGGER2
Allocate the sequential log data sets manually with the following attributes:
Note: To turn off the logging capability for OFAPROC, set the Log Level as 0 in hlq.CDBAPARM(OFA). You can edit this member during post-installation tailoring using the Setup option (1) – Create/edit global and product parmlib members. You can also edit this member after installation using the EP (Edit Parmlib) option on the CA Database Management Solutions for DB2 for z/OS Main Menu.
Includes performance information for Xmanager, which unifies each installation of CA Database Management Solutions for DB2 for z/OS into a functional group and provides the execution base for CA Detector and CA Subsystem Analyzer. Xmanager also includes CA Chorus Alert processing services for CA Insight instances that are part of its functional group. Xmanager logs operational status information to the joblog and SYSOUT data sets. Xmanager’s logging reflects local z/OS system time.
Log Location: Spool data sets in the z/OS job output for the started task
CA Chorus for DB2 Database Management Responsibilities: Xmanager provides data for several subsystem performance and application performance displays. It also feeds Alert data to the CA Chorus server for the DB2 Alerts feature.
Includes performance information regarding this subsystem that is shared by all CA Database Management Solutions for DB2 for z/OS products. Xnet provides communications services for the CA Database Management Solutions for DB2 for z/OS products in its functional group. Xnet also provides real-time configuration information to CA Chorus. Xnet logs operational status information to the joblog data sets and the Xnet log file data sets (normally there are two log file data sets). Every CA Chorus request to a CA Database Management Solutions for DB2 for z/OS product in its functional group is logged in the Xnet log file data sets. The logging for each transaction identifies the user ID making the request and the product agent that is processing the request. Timestamps in the Xnet log files reflect the local z/OS system time where Xnet is running. The Xnet log files are plain text, and you can upload them to a PC for viewing or inclusion in an email.
Log Location: Spool data sets in the z/OS job output for the task and the db2tools-hilevel.XNETLOG1 and db2tools-hilevel.XNETLOG2 data sets.
CA Chorus for DB2 Database Management Responsibilities: Xnet provides data for system configuration. It also provides routing information to the CA Chorus server and manages the requests between the CA Chorus server and the CA Database Management Solutions for DB2 for z/OS products in its functional group.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|