IBM Support

PI14954: IMS PA INCORRECTLY REPORTS DBCTL/ODBM TRANSACTIONS THAT HAVE MULTIPLE UNITS OF RECOVERY (UORS) PER SCHEDULE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • For DBCTL / ODBM transactions IMS PA expects that the Rectoken
    in the IMS x'08' and IMS x'07' records will match, i.e. only a
    single UOR per schedule. If this is not the case then IMS PA
    does not associate the x'07' record to the transaction,
    consequently no Accounting Information is assigned and no
    Transit times are calculated for the transaction.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IMS Performance Analyzer V4.3       *
    ****************************************************************
    * PROBLEM DESCRIPTION: IMS PA incorrectly reports DBCTL/ODBM   *
    *                      transactions that have multiple Units   *
    *                      of Recovery (UORs) per schedule.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    For DBCTL/ODBM transactions IMS PA expects that the Rectoken in
    the IMS x'08' and IMS x'07' records will match, i.e. only a
    single UOR per schedule.  If this is not the case then IMS
    PA does not associate the x'07' record to the transaction,
    consequently no Accounting Information is assigned or Transit
    times are calculated for the transaction.
    

Problem conclusion

  • DBCTL and ODBM threads should be treated as a single transaction
    from x'08' - x'07' irrespective of how many syncpoints they
    issue.
    NOTE: BMPSYNC(YES) has no impact on DBCTL/ODBM processing, a
    single transaction will always be reported regardless of the
    number of syncpoints issued.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI14954

  • Reported component name

    IMS PERF ANALYZ

  • Reported component ID

    5655E1500

  • Reported release

    430

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-04-01

  • Closed date

    2014-05-01

  • Last modified date

    2014-06-03

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

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

    UI17589

Modules/Macros

  • IPI#RSLV IPIGGET  IPIIPROC IPILCA01 IPISAPAR IPI4DMGR IPI4PROC
    

Fix information

  • Fixed component name

    IMS PERF ANALYZ

  • Fixed component ID

    5655E1500

Applicable component levels

  • R430 PSY UI17589

       UP14/05/06 P F405

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.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.3.0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX8A2","label":"IMS Performance Analyzer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.3.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 June 2014