Sample output from the CICS Component


This is sample output from the CICS Component. Not all of the report is produced, simply because a lot of findings were made at this site and it did not seem reasonable to bore you with the entire report. Consequently, only example parts of the report are shown.

More comprehensive output can be viewed by following the SAS Output Delivery System sample output thread.

Please note that the output is narrative. The software analyzes data in your performance data base, and produces a narrative report much as would a performance analyst.

The CICS Component User Manual could be consulted for a detailed description of each finding produced by the software. A sample "rule" description from the CICS Component User Manual can be reviewed to appreciate the level of documentation provided with the CICS Component.



   CICS PERFORMANCE CONSTRAINTS BEGINNING ON 03OCT1996 - APPLID: ALLCICS
               Analyzed by Version 7.1.0 of CPExpert(tm)
         (C) Copyright 1997, Computer Management Sciences, Inc.
                               PAGE:   2


RULE CIC112:  THE NUMBER OF GETMAINS IS HIGH

   The number of GETMAINs issued by tasks is higher than should normally
   occur.  This finding is a "rule of thumb" based upon guidance in IBM's
   CICS Performance Guide.  However, CPExpert suggests that you identify
   the tasks issuing the abnormal number of GETMAINs, and determine
   whether the number of storage acquisitions can be reduced. Please refer
   to Rule CIC111 for a discussion of this finding.
   This finding applies to the following CICS statistics intervals:

   STATISTICS                     TOTAL       TOTAL   AVG GETMAINS
   COLLECTION TIME   APPLID     GETMAINS      TASKS     PER TASK       POOL
    0:00,03OCT1996   CICSCD02    184,972      2,819          66        ECDSA
    0:00,03OCT1996   CICSCD03    432,953      3,643         119        ECDSA
    0:00,03OCT1996   CICSCD04     51,897      1,754          30        ECDSA
    0:00,03OCT1996   CICSCD05     30,810        852          36        ECDSA
    0:00,03OCT1996   CICSCP01    233,436     10,036          23        ECDSA
    0:00,03OCT1996   CICSCP02  2,276,580     37,693          60        UDSA
    0:00,03OCT1996   CICSCP02  3,251,427     37,693          86        ECDSA
    0:00,03OCT1996   CICSCP05     12,181        419          29        EUDSA
    0:00,03OCT1996   CICSCP05     61,401        419         147        ECDSA
    0:00,03OCT1996   CICSCP06    644,465      7,517          86        ECDSA
    0:00,03OCT1996   CICSCP07     68,093      2,526          27        EUDSA
    0:00,03OCT1996   CICSCP07    215,880      2,526          85        ECDSA
    0:00,03OCT1996   CICSCP08  1,769,354     50,970          35        EUDSA
    0:00,03OCT1996   CICSCP08  8,892,335     50,970         174        ECDSA
    0:00,03OCT1996   CICSCS05    153,363      4,446          34        EUDSA
    0:00,03OCT1996   CICSCS05    740,806      4,446         167        ECDSA


RULE CIC120:  A STORAGE VIOLATION OCCURRED IN A PRODUCTION CICS REGION

   The CICS statistics revealed that storage violations occurred in a
   production CICS region.  Storage violations should never occur in
   a production CICS region, since they could cause the region to be
   terminated and result in severe performance problems.
   This finding applies to the following CICS statistics intervals:

   STATISTICS                           NUMBER OF              STORAGE
   COLLECTION TIME      APPLID      STORAGE VIOLATIONS           POOL
    0:00,03OCT1996      CICSCD03               1                 EUDSA



RULE CIC121:  TRANSACTIONS EXPERIENCING A STORAGE VIOLATION

   The below transaction(s) experienced a storage violation.  The
   transaction(s) should be reviewed and the cause of the storage violation
   corrected.  If the cause cannot be quickly eliminated, perhaps the
   transaction(s) can be moved to a test CICS region until the storage
   violation can be resolved.

   STATISTICS
   COLLECTION TIME      APPLID          TRANSACTION           PROGRAM
    0:00,03OCT1996      CICSCD03            GF03              TRN29131



CICS PERFORMANCE CONSTRAINTS BEGINNING ON 03OCT1996 - APPLID: ALLCICS Analyzed by Version 7.1.0 of CPExpert(tm) (C) Copyright 1997, Computer Management Sciences, Inc. PAGE: 3 RULE CIC130: THE NUMBER OF STORAGE DUMPS IS HIGH The CICS statistics revealed that storage dumps were taken for a production CICS region. In a heavily-loaded system, the impact of these dumps may be significant. This is because CICS tasks get backlogged and CICS could become stressed recovering from the backlog. This finding applies to the following CICS statistics intervals: STATISTICS COLLECTION TIME APPLID NUMBER OF STORAGE DUMPS POOL 0:00,03OCT1996 CICSCD03 17 ERDSA RULE CIC165: THE "LOOK-ASIDE HIT" RATIO WAS LOW FOR VSAM LSR POOL The ratio of "look-aside hits" to total I/O operations was low for Local Shared Resources (LSR) pools. Please refer to the CICS Component User Manual for a discussion of the implications of this low read hit ratio and for suggestions of ways to improve the ratio of "look aside hits" to the total I/O EXCP operations for this LSR pool. This finding applies to the following CICS statistics intervals: STATISTICS LSR BUFFERS BUFFERS PERCENT COLLECTION TIME APPLID POOL SIZE ASSIGNED READ HITS 0:00,03OCT1996 CICSCD02 1 512 3 INDX:12.5 RULE CIC166: VSAM LSR FILE USED BUFFERS OF SAME SIZE OF DATA AND INDEX CPExpert noticed that a Local Shared Resources (LSR) pool has files assigned with index control intervals the same size as files with data control intervals. Please refer to the CICS Component User Manual for a discussion of the potential performance implications of using the same buffer size for both data and index buffers. This finding applies to the following CICS statistics intervals: STATISTICS BUFFER ---CONFLICTING FILES--- COLLECTION TIME APPLID LSR POOL SIZE VSAM FILE VSAM FILE 0:00,03OCT1996 CICSCP02 1 2,048 M20001 FILEQ1 0:00,03OCT1996 CICSCP02 1 2,048 M20002 FILEQ1 0:00,03OCT1996 CICSCP02 1 2,048 M2271I FILEQ1 0:00,03OCT1996 CICSCP02 1 2,048 M2273U FILEQ1 0:00,03OCT1996 CICSCP02 1 2,048 AR2001 FILEQ1 0:00,03OCT1996 CICSCP02 1 2,048 AR2004 FILEQ1
CICS PERFORMANCE CONSTRAINTS BEGINNING ON 03OCT1996 - APPLID: ALLCICS Analyzed by Version 7.1.0 of CPExpert(tm) (C) Copyright 1997, Computer Management Sciences, Inc. PAGE: 12 RULE CIC167: THERE MAY BE TOO FEW VSAM FILES ASSIGNED TO LSR POOLS CPExpert analyzed the I/O activity of VSAM files assigned to Local Shared Resources (LSR) pools versus the I/O activity of VSAM files which are not assigned to LSR pools. Based upon this analysis, CPExpert believes that you should consider assigning more VSAM files to LSR pools. Please refer to the CICS Component User Manual for a discussion of the potential performance benefits of assigning VSAM files to LSR pools. This finding applies to the following CICS statistics intervals: STATISTICS VSAM FILES VSAM FILES PCT I/O TO PERCENT COLLECTION TIME APPLID IN LSR POOLS NON-SHARED LSR POOLS READ HITS 0:00,03OCT1996 CICSCD05 4 12 7 77 0:00,03OCT1996 CICSCP01 12 15 15 84 0:00,03OCT1996 CICSCP02 24 5 16 88 0:00,03OCT1996 CICSCP08 3 1 16 81 RULE CIC250: THE ICV VALUE MAY BE INAPPROPRIATE The Region Exit Interval (ICV) value in the System Initialization Table (SIT) may be inappropriate. The MROBTCH keyword was specified as MROBTCH=1 in the SIT, and the ICV value was specified as ICV=1000. The correct ICV value depends upon whether the CICS region is a Production or Test region, and whether MRO requests are batched. Please refer to the discussion for Rule CIC250 in the CICS User Manual for CPExpert's suggestions as to whether the ICV value should be increased or decreased. RULE CIC260: INSUFFICIENT SESSIONS MAY HAVE BEEN DEFINED CPExpert believes that an insufficient number of sessions may have been defined for the CICS CP02 connection. A large number of ALLOCATE requests were queued by CICS when a session could not be allocated. CPExpert suggests you consider increasing the number of sessions defined for the connection, or you should increase the ALLOCQ guidance variable in USOURCE(CICGUIDE) to cause CPExpert to signal a potential problem only when you view the problem as serious. This finding applies to the following CICS statistics intervals: STATISTICS PEAK OUTSTANDING COLLECTION TIME APPLID ALLOCATE REQUESTS 0:00,03OCT1996 CICSCP04 4

Return to main page

Last updated by Don Deese on 10/27/03.