PM20894: IMS PA TRANSACTION EXCEPTION, TRANSIT ANALYSIS AND MANAGEMENT EXCEPTION REPORTS HAVE SOME INTER-REPORT INCONSISTENCIES

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• IMS PA Transaction Exception, Transit Analysis and Management
  Exception reports have some inter-report inconsistencies,
  especially in Peak and Total (Transit) time calculations.
  There are also inconsistencies between them and form-based
  reports.
  1. Transaction Exception report - DC Calls individual
  calculations are being rounded, causing inflated values in
  report. Peak times should be consistent with Transit Analysis
  report (inconsistency since introduction of report in 2000).
  2. Transit Analysis report -
     a. Total (Transit) time inconsistent; it needs to revert to
     the IMSPA V4.1 formula.
     b. *MSC* and *MESSAGE SWITCH* text is missing from Transact
     Code / PSB columns.
     c. Output responses which were "APPC/NO ENQ" were being
     counted as transactions because the x'31' record was a
     DLI GU.
     d. Input queue time 0 in shared queues environment when ENQ
     (x'35') on front-end system but front-end log does not
     contain the ENQ.
  3. Management Exception report - Total CPU and Call/Wait counts
  are being under-reported in schedules with more than one
  transaction.
  
  Additional issues being addressed via this APAR:
  - Log reports (single system, SHQ and GPARFMT) include
    secondary responses for excluded transactions when INCL by
    TRANCODE specified.
  - Transaction indexes created from IMS V9 DBCTL logs may have
    incorrect Start Time, completion code and input log DDname
    is missing, and missing DBUpdate sections.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of IMS Performance Analyzer V4.2       *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1. IMS PA Transaction Exception,        *
  *                      Transit Analysis and Management         *
  *                      Exception reports have some inter-      *
  *                      report inconsistencies, especially      *
  *                      in Peak and Total (Transit) time        *
  *                      calculations. There are also            *
  *                      inconsistencies between fixed-format    *
  *                      and form-based reports.                 *
  *                      2. Log reports include secondary        *
  *                      responses for excluded transactions     *
  *                      when INCL by TRANCODE specified.        *
  *                      3. Transaction index for DBCTL log has  *
  *                      incorrect start time and completion     *
  *                      code, and input log DDname is missing.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  1. Transaction Exception report - DC Calls individual
  calculations are being rounded, causing inflated values
  in report. Peak times should be consistent with Transit
  Analysis report (inconsistency since introduction of
  report in 2000).
  2. Transit Analysis report -
   A. Total (Transit) time inconsistent; it needs to revert
      to the IMSPA V4.1 formula.
   B. *MSC* and *MESSAGE SWITCH* text is missing from Transact
      Code / PSB columns.
   C. Output responses which were "APPC/NO ENQ" were being
      counted as transactions because the x'31' record
      was a DLI GU.
   D. Input queue time 0 in shared queues environment when
      ENQ (x'35') on front-end system but front-end log does
      not contain the ENQ.
  3. Management Exception report - Total CPU and Call/Wait
  counts are being under-reported in schedules with more
  than one transaction.
  4. Log reports (single system, SHQ and GPARFMT) include
  secondary responses for excluded transactions when INCL
  by TRANCODE specified.
  5. Transaction indexes created from IMS V9 DBCTL logs may
  have incorrect Start Time, completion code and input
  DDname, and missing DBUpdate sections.
  

Problem conclusion

• 1. Update IPISANAL, DASH, LOGx, MATH, MGRX and RESP modules
  to correct inconsistencies.
  2. Produce doc update to explain Transit and Total Time in
  fixed-format reports and how they relate to form fields
  in form-based reports.
  3. Update IPIIPROC to refine filtering of x'31' records and
  to use timestamp from BE x'31' to determine input queue
  times in the absence of a FE x'35'.
  4. Correct filtering of secondary responses in IPISLOGx
  modules.
  5. Update IPIIPROC to correctly set fields from DBCTL logs.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UK61440

Modules/Macros

• IPIFPROC IPIGGET  IPIIPROC IPIPMPA1 IPIPMPB1
  IPIPMP71 IPIPMP81 IPIPMP91 IPISAPAR IPISDASH IPISGRPH IPISLOG
  IPISLOGD IPISLOGM IPISLOGP IPISLOGS IPISLOGT IPISMATH IPISMERG
  IPISMGRX IPISRESP IPI4PROC
  

Fix information

• Fixed component name

  IMS PERF ANALYZ

• Fixed component ID

  5655E1500

Applicable component levels

• R420 PSY UK61440

     UP10/10/21 P F010

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.