Previous Topic: Alert Log FilesNext Topic: Diagnostics for Investigator Statistics and Metric Panel


Diagnostics for Times Series

The Time Series Facility (TSF) is used as the backend for the following CA Chorus components:

Collect the JESMSGLG and LOG1 for the TSF Started Task (CHORTSF).

JESMSGLG

Contains all initialization messages for TSF. If TSF fails to initialize properly, you can find details here. Review all ETJTS prefixed messages and confirmation that the region is initialized by seeing the N00503 * TSF INITIALIZATION COMPLETE TSF * message.

The following messages indicate the relevant ports that have been assigned for use by TSF. Ensure that these ports are as expected and match the specifications elsewhere (such as the JBoss ENV and TSF PARM TSFPARMS):

ETJTS802I TSF server QUERY socket registered on port 9317 token "TSF QUERY API: A" servlet=$TFQY00H
ETJTS802I TSF server PDAPI socket registered on port 52393 token "TSF PD API: A " servlet=$TFPD10H
LOG1

Contains all application messages. Of particular interest are messages indicating that TSF data is being received from each of the products. Detector (DBA) and Storage typically send feeds to TSF on an hourly basis. Security sends feeds every 15 seconds or 30 seconds. The absence of recent data causes no data in the queries from Time Series, Investigator Statistics, and Metrics Panel. An example of the messages for a successful data feed follows:

FMTDUMP

TSF data not being available could be due to the CHORTSF task not being active. If the TSF task has abended, obtain the formatted dump.

The CHORTSF LOG1 dd generates messages each time a discipline sends data to TSF. Verify that the data has been received recently for the discipline that you are investigating:

Security
ETJTS212I TSF PDAPI connection established for Security instance CA Security for z/OS (141.202.200.46 9242)
ETJTS214I TSF PDAPI period processed: Security CA Security for z/OS, 2011/05/1220:02:09 to 2011/05/12 20:02:30, metrics 61, recs 4, subrecs 70, elapsed 00:00:01, CPU +00:00:00.0136 (141.202.200.46 9242)ETJTS213I TSF PDAPI connection ended: Security CA Security for z/OS, periods 1, metrics 61, recs 8, subrecs 70, elapsed 00:00:01, CPU 0 00:00:00.0186 (141.202.200.46 9242)
DBA
ETJTS212I TSF PDAPI connection established for Detector instance CA Detector for DB2 for z/OS (141.202.65.31 34984)
ETJTS214I TSF PDAPI period processed: Detector CA Detector for DB2 for z/OS, 2012/03/15 18:00:00 to 2012/03/15 19:00:00, metrics 2785, recs 61, subrecs 11372, elapsed 00:00:19, CPU+00:00:01.5331 (141.202.65.31 34984)
ETJTS213I TSF PDAPI connection ended: Detector CA Detector for DB2 for z/OS, periods 1, metrics 2785, recs 65, subrecs 11372, elapsed 00:00:20, CPU +00:00:01.5375 (141.202.65.31 34984)
Storage
ETJTS213I TSF PDAPI connection ended: Storage Instance Info, periods 1, metrics 833, recs8, subrecs 957, elapsed 00:00:02, CPU +00:00:00.2111 (141.202.65.31 38980)
ETJTS214I TSF PDAPI period processed: Storage Instance Info, 2012/03/15 19:15:00 to 2012/03/15 19:16:00, metrics 1250, recs 6, subrecs 1505, elapsed 00:00:05, CPU +00:00:00.3385 (141.202.65.31 39004)
ETJTS213I TSF PDAPI connection ended: Storage Instance Info, periods 1, metrics 1250, recs10, subrecs 1505, elapsed 00:00:05, CPU +00:00:00.3420 (141.202.65.31 39004)