Historical Database Menu

Select option 5 Historical Database from the CICS PA Primary Option Menu to invoke the Historical Database Menu.

Every aspect of the CICS PA Historical Database is controlled via the ISPF dialog. The Historical Database Menu contains the functions to manage the Historical Database environment.
Figure 1. Historical Database (HDB) Menu
  File  Options  Help
---------------------------------------------------------------------
                        Historical Database Menu                  
Option ===> _________________________________________________________
                                                                      
1  Templates         Design HDB Templates                            
2  Define            Define a new HDB                                
3  Load              Load data into the HDBs                         
4  Report            Submit HDB report requests
5  Export            Export HDB data sets to DB2                     
6  Extract           Extract HDB data sets to CSV          
7  Maintenance       Maintain HDB definitions and data sets          
8  Housekeeping      Perform HDB housekeeping                        
                                                                    
Repository . . . . 'CICSPROD.CICSPA.XYX.REPOSTRY'_______________  +

CICS versions (VRM):          
 Transaction Server  . . . 680
 Transaction Gateway . . . 900
 
  F1=Help      F3=Exit      F4=Prompt    F10=Actions    F12=Cancel
The menu provides a pathway to the eight steps for defining and using HDBs:
  1. Template. (Performance HDBs only, not Statistics HDBs)

    Defining an HDB is a two step process: first define a Template and then define an HDB based on that Template. The Template identifies which CMF performance fields are to be kept in the HDB. For more information, see HDB Templates.

  2. Definition.

    After the Template is defined, then define the HDB and its options, such as the characteristics of the HDB data sets and the retention period of the data. For more information, see Define a Performance HDB.

  3. Load.
    Loading data into the HDB is performed by the standard CICS PA batch reporting utility. The command that requests the utility to load an HDB is:
    HDB(LOAD(...
    CICS PA reads the CMF performance class data (and also, for Statistics HDBs, CICS® Transaction Gateway statistics) and builds the HDB data sets. Because the HDB Load process is part of the normal batch reporting process, you can run CICS PA reports and load HDBs together with a single pass of the SMF data. For more information, see Load HDBs.
  4. Report.
    Performance HDB reporting is performed by the standard CICS PA batch reporting utility. The command that requests the utility to report against a Performance HDB is:
    HDB(REPORT(...
    You can tailor Performance HDB reporting by using a Report Form. This allows you to select which fields in the HDB are reported and how they are presented.

    Statistics HDB reporting is done interactively using the CICS PA dialog.

    Statistics Alert reporting, which alerts you when statistics field values meet specified conditions, is performed by the batch reporting utility. The command that requests the utility to generate a Statistics Alert report against a Statistics HDB is:
    HDB(STATSALERT(...

    Before requesting a Statistics Alert report, you must create a Statistics Alert Definition. For details, see Statistics alert reporting.

  5. Export.
    Export allows you to load HDB data into a DB2® table. CICS PA automates this process with two simple steps:
    1. First define the DB2 table to house the data. CICS PA generates JCL to do this for you by creating the necessary DDL to define the table.
    2. Then load the data into the table. CICS PA generates JCL to do this for you by creating the necessary DB2 Load Utility statements to load the data.
    For more information, see HDB Export to DB2 tables
  6. Extract.

    The HDB Extract facility allows you to export data from your HDB data sets to an extract data set in CSV (comma separated values) format, suitable as input into PC-based spreadsheet applications.

  7. Maintain.

    HDB maintenance allows you to change your HDB definition and manage the HDB container data sets. For more information, see HDB Maintenance.

  8. Housekeeping.
    HDB housekeeping should be run periodically to clean up your HDB environment. Housekeeping performs these tasks:
    1. Deletes HDB container data sets that have expired or have delete pending.
    2. Deletes expired DB2 table rows.
    3. Removes definitions from the Repository that are no longer required.
    For more information, see Housekeeping.

Initially, your HDB environment requires a minimal one-time setup. On the Historical Database Menu, specify the name of the Repository. This is a VSAM KSDS where HDB definitions are saved.

You can define as many repositories as required; however only one repository can be used at a time and each repository acts independently. Information cannot be shared between repositories. It is recommended that one global repository is defined and made available to all users. In this way, all Historical Databases are available to users.

The default name is 'CICSPA.HDB.REPOSTRY'. You can change this by overtyping or pressing Prompt (F4) to select from a list of previously used repositories. Normal ISPF data set conventions apply when specifying the name of the data set.

If the Repository data set is not cataloged, CICS PA will prompt you to define it when you attempt to use it.


Information Information

Feedback


Timestamp icon Last updated: Thursday, 7 November 2013


http://pic.dhe.ibm.com/infocenter/cicsts/v5r1/topic//users-guide/cpaug298.htm