IBM Support

PM66914: CORRUPTED SMF110 RECORDS DUE TO TRANSACTION MONITOR AREA OVERLAYED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Sometimes, the SMF110 record contains wrong value on fields
    related to ODR origin destination ( Ostart , Ouserid , Otran and
    so on). The problem is the ORIGIN data taken from the TMA .
    This happens when a  X'93' value in found in the
    3rd byte after the end of the data in the TIOA.
    This X'93' is the value in field FMHCARGN for an FMH which
    signifies the presence of an ODR.
    The problem is that the code is looking beyond the end of the
    request in the TIOA and and encounters random characters .
    The code should not be past the data encompassed by the TIOATDL
    (the terminal data lenght field ).
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: Bad data in CICS monitoring records for *
    *                      CRSR transaction.                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Bad data appears intermittently in CICS performance monitoring
    records for the CRSR transaction. The bad fields are origin data
    record fields. These fields should contain information about the
    original task which spawned the new task. CRSR is an internal
    CICS transaction and has no origin data so the monitoring fields
    for origin data should be empty.
    DFHZATT processes the request to run the CRSR transaction.
    It parses the request in the TIOA owned by the MRO session.
    Code in DFHZATT steps over an FMH43 and starts looking for
    a X'93' value in field FMHCARGN which signifies the presence
    of origin data in the TIOA. However, the code fails to
    test if it has reached the end of the request before checking
    for a X'93' value.
    It encounters a X'93' which is part of residual data from a
    previous request processed using the same TIOA.
    DFHZATT references this residual data as ORIGIN_DATA when it
    issues the DFHXMAT ATTACH for transaction CRSR.
    

Problem conclusion

  • DFHZATT has been changed to ensure it has not run past the end
    of the request in the TIOA before checking for the presence of
    the origin data record id, x'93' , in field FMHCARGN.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PM66914

  • Reported component name

    CICS TS Z/OS V4

  • Reported component ID

    5655S9700

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-15

  • Closed date

    2012-06-28

  • Last modified date

    2012-08-08

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

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

    UK79947

Modules/Macros

  •    DFHZATT
    

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R700 PSY UK79947

       UP12/07/11 P F207

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":"4.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":"4.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
08 August 2012