PK10292: IMPROVED MSC TRANSACTION TRANSIT REPORTING

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• MSC transactions on the front-end system are reported as
  Message Switches because they do not execute on this
  system, but are routed to another system for processing.
  The transaction name and performance characteristics are
  not reported.
  Note that when the MSC transaction is processed on the
  back-end, it is reported as a normal transaction for the
  back-end system when the INCLUDE(MSC) transit option is
  specified.
  Additional symptoms fixed:
  1) The Dashboard Report is reporting all region types
  for the APPC and OTMA sub-types, instead of just
  MPP regions.  This is causing higher then expected
  values for "In Q" and "Exec" under the APPC and OTMA sub-types.
  
  2) The OSAM Buffer Pool Statistic's "Locates" and "In Pool"
  counts are not reporting high values correctly.
  Smaller volume IMS's are reporting okay.
  One example: The ALL row does not add up to the individual
  subpools for the "Locates" and the "In Pool" columns.
  
  3) A large transaction count discrepancy exists between the
  Transaction Exception Report and the Internal Resource Usage
  Report.  Originally this was to be fixed by PQ99916, however
  it has been found that this was not completely fixed by that
  APAR. The problem is due to IRUR not handling APPC transactions
  correctly. Keywords: TRANEXC IRUR
  
  4) ABEND0C9 IPIPIR91 around x'4166'.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IMS Performance Analyzer V3R3.  *
  ****************************************************************
  * PROBLEM DESCRIPTION: IMPROVED MSC TRANSACTION TRANSIT        *
  *                      REPORTING                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Transit reports show MSC front-end transactions
  as "*MESSAGE SWITCH**" because the input message
  is switched to the remote IMS system for processing,
  and is not processed on the local system.
  The transaction name and performance characteristics
  are not reported.
  Note that when the MSC transaction is processed on the
  back-end, it is reported as a normal transaction for the
  back-end system when the INCLUDE(MSC) transit option is
  specified.
  

Problem conclusion

Temporary fix

Comments

• The INCLUDE(MSGSW) transit option has changed to report
  front-end MSC transactions as normal transactions with
  the standard transit time breakdown.
  Previously, FE MSC transactions were reported as
  "*MESSAGE SWITCH**" with no processing or total transit
  times.
  Additional resolved problems:
   1. Connect Extensions Trace supports V6 IP addresses.
   2. DBUPDATE KSDS update counts incorrect.
   3. DC Tracker incorrectly reports userid when APPC/OTMA.
   4. DC Tracker "connects" FE MSC transactions with their
      associated response.
   5. Transit LOG handles MSGSW Output Queue times.
   6. IRUR Report updates include:
      Scheduling Statistics -
       Programs Scheduled count incorrect
      PSB Pool Get Statistics -
       Elapsed times corrected, increased precision to msec
      Dispatcher Statistics
       TCB times corrected, increased precision to msec
      Program Isolation Enq/Deq -
       Max Bytes Used count incorrect
       Current Bytes used count included
      DL/I Call Statistics -
       Transactions processed count incorrect for APPC
   7. DASHBOARD enhanced:
       New standard (STD) transaction count.
       Complete MSC transit times.
       APPC/OTMA subtypes incorrectly reported under MPP.
   8. AVAIL report MSGIPI0014E incorrectly issued.
   9. DEADLOCK enhanced to support new fields in DFSTRAE0.
  

APAR Information

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

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

  UK08804

Modules/Macros

• IPICPROC IPICTRAC IPIPAV71 IPIPAV81 IPIPAV91
  IPIPDA71 IPIPDA81 IPIPDA91 IPIPDL71 IPIPDL81 IPIPDL91 IPIPET71
  IPIPET81 IPIPET91 IPIPE271 IPIPE281 IPIPE291 IPIPIR71 IPIPIR81
  IPIPIR91 IPIPRT71 IPIPRT81 IPIPRT91 IPIPR271 IPIPR281 IPIPR291
  IPIPUT71 IPIPUT81 IPIPUT91 IPISLCMP IPISLM71 IPISLM81 IPISLM91
  IPISLOGD IPISLS71 IPISLS81 IPISLS91 IPISLT71 IPISLT81 IPISLT91
  

Fix information

• Fixed component name

  IMS PERF ANALYZ

• Fixed component ID

  5655E1500

Applicable component levels

• R330 PSY UK08804

     UP05/11/11 P F511

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.