IBM Support

PI55761: USER CORRELATION DATA POINTER PASSED TO XAPADMGR IS TO UNINITIAL IZED STORAGE, WITH RESIDUAL DATA POPULATING ODR FIELDS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You are running in an environment with DYNATRACE and CA SYSVIEW,
    with XAPADMGR enabled.  DYNATRACE examines Origin Descriptor
    Records (ODR) to determine if User Correlation Data is present,
    before updating with appropriate association data, by following
    the pointer to UCD in the XM_TXN block.  The analysis reveals
    that the field is non-zero, so no update occurs, and DYNATRACE
    outputs a message indicating 'TAG NOT SET'.
    .
    Although XAPADMGR should only be invoked when association
    is not present, inspection of the UCD field is telling a
    different story to DYNATRACE in this scenario.
    .
    CICS does not appear to initialize the data at the pointer
    to UCD, which is passed to the exit XAPADMGR.  This leads
    to incorrect processing in DYNATRACE when residual data is
    discovered.
    Additional Symptoms Search Keywords: KIXREVPAD
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: UEPUCD storage area passed to XAPADMGR  *
    *                      user exit is not initialised.           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The XAPADMGR user exit can be used to add user information to
    the association data of a task, at the point of origin of the
    distributed transaction. A 64-byte storage area is created, and
    the address of this field is passed to the exit in field UEPUCD.
    This 64-byte storage area is not initialised by CICS to zeros.
    .
    On return from the user exit, any data in the UEPUCD storage
    area is copied to the MNADCB (mnodr_user_correlator) and to the
    TMA (TMA_DFHCICS_365). If the area was not updated by the exit,
    this will lead to stale data being copied to these locations
    if it contained non-zero values.
    This is visible in field OUSERCOR in the CICS SMF monitoring
    records.
    Additional Keywords: GLUE
    

Problem conclusion

  • DFHXMTA has been updated so that the 64-byte storage area passed
    to exits in the XAPADMGR global user exit point will be
    initialised to zeros before calling the first exit active in
    this exit point.
    If more than one exit is active in the XAPADMGR global user exit
    point, the area addressed by UEPUCD will not be reset by CICS
    between invoking the exits.
    .
    The CICS Transaction Server for Version 5 Release 2
    Customisation Guide (SC34-7269-00) will be updated
    in the description of the XAPADMGR global user exit:
    Application association data exit in the AP domain (XAPADMGR)
    The description of the UEPUCD parameter will be updated to read:
    Address of a 64-byte output area in which the exit program can
    place the user correlation data.
    This area will be cleared to zeros by CICS before invoking the
    first exit program active in the XAPADMGR user exit point, but
    will not be reset by CICS between programs if multiple exit
    programs are active. The same storage area will be passed to
    subsequent exit programs active in the same exit point.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PI55761

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-01-20

  • Closed date

    2016-02-26

  • Last modified date

    2016-06-21

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

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

    PI57036 UI36046 PI64575

Modules/Macros

  • DFHXMTA
    

Publications Referenced
SC34726900    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R900 PSY UI36046

       UP16/03/18 P F603

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"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":"5.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
21 June 2016