Including a V3.1 Performance HDB in the manifest

In CICS PA V3.2 the manifest was introduced to enhance how performance HDB data is exported for viewing in the CICS® PA plug-in for CICS Explorer®. HDB and DB2® tables that were set up for the CICS PA plug-in in V3.1 must be changed before they can be included in the manifest and accessed from the CICS PA plug-in.

About this task

The manifest is a catalog of DB2 tables for HDBs that are associated with the same qualifier and for which the Explorer indicator is set. To include the Performance HDB in the manifest, you must modify the HDB definition to specify a qualifier and select the Explorer indicator. You must also replace the current Template with one of the internal templates that are designed for use with the CICS PA plug-in. These are named EXPLORnn.

The process for migrating the DB2 table depends on whether you REPLACE your DB2 table every time you reload it; or RESUME (that is, append) new data to the existing data in the table. The following procedure covers both methods.

Procedure

  1. Select the performance HDB from the HDB Maintenance panel and make the following changes:
    1. Specify a qualifier. This HDB will be included in the manifest for the corresponding qualifier.
    2. Select the Explorer indicator.
    3. Replace the current template name with EXPLORnn, where nn is the version of CICS TS that you are migrating to.
    4. Press the Exit key (F3) to save the HDB definition.
  2. Update the DB2 table and VIEW as follows:
    • REPLACE users: DROP the existing table and its associated VIEW.

      In the HDB Maintenance panel, enter the T line action next to the performance HDB. This will generate DB2 commands to create the new DB2 table and VIEW. Submit the generated JCL.

    • RESUME users: Rename the existing DB2 table to qqqqqqqq.CPA_CMFPSUM, where qqqqqqqq is the qualifier specified in the HDB definition.

      In the HDB Maintenance panel, use the T line action next to the performance HDB. This will generate DB2 commands to create the DB2 Table and VIEW. Delete the TABLE CREATE command and change the VIEW DROP command to DROP VIEW EXPLORER_SUMMARY. Submit the JCL to DROP and then recreate the VIEW so that it picks up the new table name.