Additional CA Chorus for DB2 Database Management Configuration › CA Detector Statistics Gathering Overview › How to Load CA Detector Collection Data Automatically

How to Load CA Detector Collection Data Automatically

Use the following process to provide CA Detector collection data automatically to the Time Series Facility (TSF) in CA Chorus.

The TPDTFEED started task procedure runs the CA Detector UNLOAD utility for the most recently completed CA Detector collection interval on a DB2 subsystem. This started task also provides that data to the Time Series Facility (TSF) through a TCP/IP connection. The task is executed for each CA Detector collection interval per DB2 subsystem.

When a collection interval ends, message PDT0170 is issued in the Xmanager JOBLOG where the collection is running. Use this message to trigger the start of each TPDTFEED started task.

Note: If CA OPS/MVS is not available, another message processing and scheduling service can be used.

Follow these steps:

1. Edit and submit the TPDTCOPY member in your_db2tools_hlq.CDBASAMP as described in the member.

   Note: Select a CA Detector TSF high-level qualifier (TPDTHLQ) that determines where to create the CA Detector TSF parmlib and unload data sets. TPDTHLQ must not exceed a length of 12 characters to avoid exceeding the 44 character DSN limit.

   The CA Detector TSF parmlib library is created and the TPDTPARM member is copied to the new library.

   Alternatively, use the following definitions to create the CA Detector TSF parmlib data set manually, and then copy the member TPDTPARM from your_db2tools_hlq.CDBASAMP to TPDTHLQ.PDTTSF.PARMLIB:

   DISP=(NEW,CATLG,DELETE),DSNTYPE=LIBRARY,UNIT=SYSDA,
   DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120,DSORG=PO),
   DSN=TPDTHLQ.PDTTSF.PARMLIB,SPACE=(TRK,(100,20))
   

2. Verify that the following required permissions are provided for the z/OS ID used to start the TPDTFEED started task:
   • OMVS segment for TCP/IP
   • READ access to the high-level qualifier of the CA Database Management Solutions for DB2 for z/OS
   • UPDATE access to the chosen CA Detector TSF high-level qualifier (TPDTHLQ)

   The TPDTFEED started task required permissions are defined.

3. Customize the TPDTFEED started task:
   1. Copy the TPDTFEED member in your_db2tools_hlq.CDBASAMP to a PROCLIB.
   2. Edit the TPDTFEED member as described in the member. The PRDTSF step transmit data to TSF.
   3. Ensure that the CA Detector collection interval is set to a valid TSF interval. The TSF interval is restricted to 1, 5, 10, 15, 20, or 30 minutes or to 1, 2, 4, 6, 8, 12, or 24 hours.

      Note: For more information about specifying these collection intervals, see the CA Detector User Guide.

4. Customize the REXX EXEC TPDT0170:
   1. Copy the TPDT0170 REXX EXEC located in your_db2tools_hlq.CDBASAMP into a valid CA OPS/MVS production rule set. This EXEC processes data collector messages from Xmanager and starts the TPDTFEED started task that provides data to TSF. A sample message follows:

      PDT0170 DETECTOR COLLECTION INTERVAL END TIME=08:00 INTERVAL=01:00 DB2=ssid VCAT=PDTDBA.Rnn DATASTORE=datastore-name
      

      Note: If CA OPS/MVS is not available, another message processing and scheduling service can be used.

   2. Edit TPDT0170 as follows:
      • Modify the site-specific variables for active subsystems and Xmanager jobs.
      • Under tsf_jobname<1-3>, set the TPDTFEED STC names and the corresponding release of the CA Database Management Solutions for DB2 for z/OS.

      Note: If multiple releases send data to TSF concurrently, define a separate TPDTFEED STC for each release.

5. (Optional) See Seeding Data to Multiple TSF Regions to send data to TSF regions on multiple CA Chorus installations.