The CICS PA dialog

You use the CICS® PA dialog to create, maintain, and submit your report requests. You can also use it to specify your input data and tailor requests specific to your requirements without needing to understand the CMF data.

The dialog requires no special customization or setup. Reporting can commence immediately.

The following steps explain how to use the dialog for reporting.
  1. Define your CICS (and other related) systems and their SMF files and log streams. After your systems are defined, you can start reporting against them. You can fast-track this process by using the take-up facility. CICS PA extracts information about your CICS systems from your SMF files and makes it available in the dialog. If you define your own CMF user fields, specify your MCT definition. The user fields can then be incorporated into your CICS PA reports. The following example panel shows some CICS systems, a DB2® subsystem, a WebSphere® MQ subsystem, and an MVS™ System Logger defined to CICS PA.
    Figure 1. CICS PA: System Definitions
                                  System Definitions                  Row 1 from 8
     
    Command ===> ________________________________________________ Scroll ===> CSR
     
    Select a System to edit its definition, SMF Files and Groups.
                                                                        SMF Files
    /   System   Type     Image           Description                   System
    _   MVS1     Image             Production MVS system                MVS1
    _   CICSP1   CICS     MVS1     CICS Production System 1             MVS1
    _   CICSPTOR CICS     MVS1     CICS Production TOR                  MVS1
    _   CICSPAOR CICS     MVS2     CICS Production AOR                  CICSPAOR
    _   CICSPFOR CICS     MVS2     CICS Production FOR                  CICSPFOR
    _   DB2P     DB2      MVS3     DB2 Production Subsystem             DB2P
    _   MQSP     MQ       MVS4     MQ Production Subsystem              MQSP
    _   MVS1LOGR Logger   MVS1     System Logger for MVS1               MVS1
     

    Related CICS systems, such as those systems that connect through IRC/MRO or ISC/APPC, can be grouped together for reporting purposes. For example, if you assign the CICS MRO systems (CICSPTOR, CICSPAOR, CICSPFOR, CICSPDOR) to a group, you can report on these systems as a single entity. CICS PA reports can then show a complete end-to-end picture of your MRO transaction activity, incorporating detailed DB2 statistics derived from the DB2 accounting data of subsystem DB2P.

  2. To build, submit and save your report requests, you can define Report Sets. A Report Set contains the set of reports that you want to run in a single job. Simply select the required reports and submit a report request.
    Figure 2 shows a Report Set. The available reports are displayed in a tree structure (folder style) and grouped by category. Report categories can be expanded or collapsed as required. The Active status controls which reports in the Report Set are run when you submit a report request.
    Figure 2. CICS PA: Report Set
     EDIT                      Report Set – DAILY                      Row 1 of 45 
     Command ===> ________________________________________________Scroll ===> CSR
     
     Description  . . . . Daily Reports for our production MRO system
     
     Enter "/" to select action.
     
     ___          ** Reports **                           Active
          -  ___  Options                                   Yes
                  ___  Global                               Yes
          -  ___  Selection Criteria                        Yes
                  ___  Performance                          Yes
                  ___  Exception                            No
          -  ___  Performance Reports                       Yes
                  ___  List                                 Yes
                  ___  List Extended                        Yes
                  ___  Summary                              Yes
                  ___  Totals                               Yes
                  ___  Wait Analysis                        No
                  ___  Transaction Profiling                No
                  ___  Cross-System Work                    No
                  ___  Transaction Group                    Yes
                  ___  BTS                                  No
                  ___  Workload Activity                    No
                  ___  Transaction Tracking List            No
                  ___  Transaction Tracking Summary         No
          -  ___  Exception Reports                         No
                  ___  List                                 No
                  ___  Summary                              No
          -  ___  Transaction Resource Usage Reports        No
                  ___  File Usage Summary                   No
                  ___  Temporary Storage Usage Summary      No
                  ___  DPL Usage Summary                    No
                  ___  Transaction Resource Usage List      No
          -  ___  Statistics Reports                        No
                  ___  Alert                                No
                  ___  CICS Transaction Gateway             No
          -  ___  Subsystem Reports                         No
                  ___  DB2                                  No
                  ___  WebSphere MQ                         No
                  ___  OMEGAMON                             No
          -  ___  Performance Graphs                        No
                  ___  Transaction Rate                     No
                  ___  Transaction Response Time            No
          -  ___  Extracts                                  Yes
                  ___  Cross-System Work                    Yes
                  ___  Performance                          No
                  ___  Record Selection                     No
                  ___  HDB Load                             No
                  ___  System Logger                        No
                  ___  Statistics                           No
                  ** End of Reports **   
    Report Sets can contain selection criteria, which are used to filter CMF records. This enables you to tailor your reporting to include only the information that you are interested in. For example, you can specify selection criteria to restrict reporting to:
    • A particular date/time range
    • A group of related transaction IDs
    • Transaction response times that exceed your thresholds
  3. To tailor the format and content of your reports, you can define Report Forms. You can use an editor to design your own report by selecting the required CMF fields. You can select most CMF fields for reporting, and detailed explanations of each CMF field is available from the dialog. Report Forms can contain selection criteria. When a report specifies a Report Form and both have selection criteria specified, records must match both sets of selection criteria to be included in the report.
    Figure 3 shows a Report Form tailored to show File Control statistics.
    Figure 3. CICS PA: Report Form
                         EDIT LIST Report Form - FCLIST        Row 1 of 16 More: >
    Command ===> ________________________________________________ Scroll ===> CSR
     
    Description . . . .  File Control List Form            Version (VRM): 710
     
    Selection Criteria:
     _  Performance  *                                     Page width . . 132 
      
       Field 
    /  Name +       Type     Description
    __ TRAN                  Transaction identifier
    __ USERID                User ID
    __ STOP         TIMET    Task stop time
    __ RESPONSE              Transaction response time
    __ DISPATCH     TIME     Dispatch time
    __ CPU          TIME     CPU time
    __ FCWAIT       TIME     File I/O wait time
    __ FCAMCT                File access-method requests
    __ FCADD                 File ADD requests
    __ FCBROWSE              File Browse requests
    __ FCDELETE              File DELETE requests
    __ FCGET                 File GET requests
    __ FCPUT                 File PUT requests
    __ FCTOTAL               File Control requests
    __ EOR                   ---------------- End of Report ----------------
    __ EOX                   ---------------- End of Extract ---------------
     
  4. Define and maintain Historical Databases (HDBs) as repositories of performance data. Generate reports against your HDBs or export HDB data to DB2 tables for further analysis.


dfht3zk.html | Timestamp icon Last updated: Monday, 5 June 2017