IBM Support

PH22187: IMS DLS S0C4 ABEND FOLLOWING DFS0730I UNABLE TO OPEN DATA SET WITH DDNAME XXXXXXXX FOR REASON I,10

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The s0c4 is occurring at the first instruction in
    DFSDVSM0-JRNAD.  A 31-bit parmlist (R1) is being passed to our
    JRNAD routine but DFSDVSM0 is currently in amode24.  Looking at
    R14 address in SAVEAREA at time of Abend,
    it points back into DFSDVSM0, which is running AMODE31 at that
    time.  Registers at time of dump do not make a whole lot of
    sense.
    
    Just prior to the abends0c4, we see the following message:
    
    DFS0730I UNABLE TO OPEN DATA SET WITH DDNAME halpartx FOR REASON
    I,10,  DATABASE halpart TRN tran1 IMSP
    DFS629I IMS DYD TCB ABEND - SYS 0C4 -DLS     IMSP
    
    The DFS0730I I,10 indicates that this HALDB PHIDAM primary index
    is already in the IMS "Open table", DFSOPTBL.  However,
    looking at the ACB associated with the vsam index, it is closed
    and should not be in this table.  Shortly after this, another
    PST's
    SAVEAREA Flow has DFSDVSM0 processing a "VSAM VERIFY"
    (PSTFNCTN=xDF) on this same ACB.  DFSDVSM0 VERVV00 Routine
    does a BALR to VSAM Interface module (IDA019R0), getting address
    to IDA019R0 from ACB + 8 (ACBINRTN).  Because this ACB
    is closed (ACBOFLGS = x42), ACBINRTN = zeroes.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * IMS V14 Full Function DB users                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * JRNAD exit got ABENDS0C4 because parameter list was not      *
    * accessible.                                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * INSTALL CORRECTIVE SERVICE FOR APAR/PTF                      *
    ****************************************************************
    ACB which was associated to RPL which was in parameter list was
    not open. JRNAD exit is not supposed to be scheduled.
    

Problem conclusion

  • DFSDVSM0
    
    Check ACBOPEN. If ACBOPEN is not ON, skip calling VERVV00
    
    DFSDOC40, DFSDOC50, DFSDOC60
    
    Added check ACB is open or not just before issuing DFS0730I I10.
    If ACB is not open, skip writing DFS0730I I10 and keep on OPEN
    process
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH22187

  • Reported component name

    IMS V14

  • Reported component ID

    5635A0500

  • Reported release

    400

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-02-13

  • Closed date

    2020-02-24

  • Last modified date

    2020-03-02

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

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

    PH22194 UI68056

Modules/Macros

  • DFSDVSM0 DFSDOC60 DFSDOC40 DFSDOC50
    

Fix information

  • Fixed component name

    IMS V14

  • Fixed component ID

    5635A0500

Applicable component levels

  • R400 PSY UI68056

       UP20/02/26 P F002

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":"14.1","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
30 November 2023