IBM Support

PM08448: BAD MRCB OR MBCB ADDRESS. ABEND0C4 IN DFHTDB OR DFHTDRM . MRCABCN1 HOLDS A BAD MRCB ADDRESS .

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • Various errors relating to bad MRCB or MBCB control blocks.
    MRCBPTR or MBCBPTR is bad in the stacks of either DFHTDB or
    DFHTDRM .
       Symptoms include:
    DFHTD0001 reporting abend0C4 in DFHTDB ( at base level )
    at offset 58C6 because a bad rpl_p because of a bad
    MRCB_RPL_P because of a bad MRCB .
    .
    Abend0C4 in DFHTDRM ( at level UK44630 ) at offset 53C6 in
    routing BCBCHN because of a bad MBCB .
    .
    Abend0C4 in DFHTDRM at offset 3BE .
    .
    These problem happen if the aftermath of an abend within
    DFHTDRM which drives TDRM's recovery routing TDRMREC .  There
    can be an abend0C4 within control of TDRMREC because MRCBPTR
    and MBCBPTR weren't initially cleared and can therefore contain
    residual values .
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All.                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: MRCABCN1 chain gets corrupted if        *
    *                      EXEC CICS SYNCPOINT is issued with an   *
    *                      invalid TDRM work token.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If DFHTDRM is called due to an EXEC CICS SYNCPOINT call with an
    invalid TDRM work token then TDRM may program check. This
    will lead to TDRMREC being called and may result in residual
    data being placed on the unallocated MRCB and MBCB chains.
    
    Additional Keywords: MRCAFCN1 MRCBBCHN MRCBFCHN MBCAFCN2
                         MBCAFCN2 MBCABCN2 MBCAFCN1 MBCABCN1
                         MBCBFCHN MBCBBCHN
    

Problem conclusion

Temporary fix

Comments

  • This APAR is being closed FIN with concurrence from the
    submitting customer.  This means that a fix to this APAR is
    expected to be delivered from IBM in a release which is being
    developed at the time that the APAR was closed.
    The latest release of the product to exit development at the
    time this APAR was closed was:
      CICS Transaction Server for z/OS V4.1.
    PEG12244  PEG 12244
    

APAR Information

  • APAR number

    PM08448

  • Reported component name

    CICSTS V3 Z/OS

  • Reported component ID

    5655M1500

  • Reported release

    500

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-02-24

  • Closed date

    2010-03-05

  • Last modified date

    2010-03-05

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

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

Fix information

Applicable component levels

  • RZ66 PSN

       UP

  • R500 PSN

       UP

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

Document Information

Modified date:
05 March 2010