IBM Support

PI95732: ABEND0SC4 ON MODULE DFSRCP30 AT IMS STARTUP DUE TO A BAD CNTCTBPT POINTER.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ABENDS0C4 RC10 on at offset +X'1006' in module DFSRCP30 into
    routine CNT2LOGR (RCP3-AT-CNT2LOGR).  The problem is due to a
    bad pointer we have loaded into R8 from R15 and that  should
    point to a CTB but it is pointing in the middle of a ESAF
    control block. The CTB address is taken from field CNTCTBPT in
    the CNT we are trying to include in the X'4003' log record for
    the checkpoint we are taking at COLD start.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * IMS V15 with IMS execute parm MSC=Y                          *
    * defined.                                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * IMS restart TCB ABENDS0C4 in DFSRCP30                        *
    * inside routine CNT2LOGR. R8 contains                         *
    * an invalid address.                                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The IMS restart TCB ABENDS0C4 occurs during IMS startup when
    building type 4003 checkpoint records for the system MSC LNB
    control blocks. CTBCTT field of a system CTB/LTB contained an
    invalid address that was loaded into R8. An attempt to access
    the CTT using R8 as pointer resulted in the abend. The system
    MSC LTB's are built during startup in part DFSIINM0. DFSIINM0
    obtains pool space to build the system MSC control blocks but
    does not clear the pool space prior to building the blocks.
    CTBCTT field of the system LTB's is not one of the fields
    populated during the build process which results in data from
    prior use of the pool space to remain in that field.
    
    The reported abend is due to an non-initialized CTBCTT field of
    an MSC system LTB however, depending on content and location
    any non-initialized fields of the system LLB's LNB's and LTB's
    may cause the abend.
    

Problem conclusion

  • Logic has been modified in part DFSIINM0. Logic has been added
    to clear the pool space obtained to build the MSC system control
    blocks prior to building them. Clearing the area before building
    the blocks insures that any fields that are not set during build
    do not contain residual data.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI95732

  • Reported component name

    IMS V15

  • Reported component ID

    5635A0600

  • Reported release

    500

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-03-27

  • Closed date

    2018-04-26

  • Last modified date

    2018-05-01

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

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

    UI55532

Modules/Macros

  • DFSIINM0
    

Fix information

  • Fixed component name

    IMS V15

  • Fixed component ID

    5635A0600

Applicable component levels

  • R500 PSY UI55532

       UP18/04/28 P F804

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":"SSEPH2","label":"IMS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"15","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
23 December 2023