IBM Support

PM33652: RUNNING AN ACBGEN BUILD PSB=NAME ABENDS WITH AN S0C4

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • I ran an BUILD PSB=ALL and while I did not get to member
    PSBNAME which references DBD DBDNAME. It executes ok.
    DFS0940I DBD DBDNAME  HAS BEEN ADDED    IN LIBRARY.     DMB SIZE
             = 00001536  BYTES
    DFS0940I PSB PSBNAME  HAS BEEN ADDED    IN LIBRARY.     PSB SIZE
             = 00038528  BYTES
    
    but if I run an ACBGEN with BUILD PSB=PSBNAME I get an S0C4.
    Additional keywords:
    ABENDS00C4
    ABEND0C4
    S0C4
    DFSDLBL80
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS V12 users running ACBGEN with        *
    *                 DEDB and secondary index.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Abend0c4 in DFSDLB00 when attempting to *
    *                      issue message DFS0962I.                 *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    There are many flavors to this abend0c4.
    1. Bad secondary index DBD source with LCHILD statement pointing
       to a primary DEDB that has no association to secondary index.
    2. Bad primary database source (either DEDB or Full Function)
       with LCHILD statement pointing to a DEDB as a secondary
       index.
    Acbgen attempted to issue message DFS2431I DBD1 REFERENCES DBD2
    AS INDEX INVALIDLY. However, the pointer to the index
    database name was zero. As of this result, ACBGEN terminated
    with an abends0c4.
    

Problem conclusion

  • GEN:
    KEYWORDS:
    
    *** END IMS KEYWORDS ***
    DLBLCOM
    Modify this macro at label ERROR992 to either issue message
    DFS2431I DBD1 references DBD2 as an index invalidly or to
    issue message DFS0909I DBD1 is an invalid DBD. Message DFS0909I
    is issued in the case of the address to the index database being
    null. However, in the second case described in the problem
    description, the address to the ddir extension to the index
    database may not be null if the XDFLD statement of the LCHILD
    statement with PTR=INDX contains SEARCH and or SUBSEQ fields.
    As the result of this definition, a key length equal to the sum
    of the search fields and subsequent fields is saved on to the
    high order byte of the address to the ddir extension to the
    index database. Because of this variation, only the 3-byte
    address is checked for a null value. Also, add logic to convert
    to relative branching instructions.
    
    DFSDLB10
    Modify this module to recognize the case where the primary DEDB
    contains no secondary index and to issue message DFS0909I for
    the mismatch between the primary DEDB and the secondary index.
    Also, add logic to convert to relative branching instructions.
    
    DFSDLB00, DFSDLB20 thru DFSDLB80, DBFDLB00.
    Modify the modules to convert to relative branching
    instructions.
    
    DLBLPOP, UERR macros.
    Modify both macros to support relative branching instructions.
    
    *********************
    *  Document change  *
    *********************
    Modify the Messages and Codes manual (ZES1290904) under message
    DFS0909I to add the following text.
    Explanation
    There are cases when the DBD by itself is a valid DBD but it is
    invalidly referenced as a secondary index by another database.
    Programmer Response
    Go through each DBPCB of the involved PSB, pick up the data
    name and search its DBD source for the LCHILD statement with
    PTR=INDX and with reference to the database name specified on
    the error message DFS0909I. Correct the error.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PM33652

  • Reported component name

    IMS V12

  • Reported component ID

    5635A0300

  • Reported release

    200

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2011-02-25

  • Closed date

    2011-03-25

  • Last modified date

    2013-04-04

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

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

    UK66123 PM86134

Modules/Macros

  •    DBFDLB00 DFSDLB00 DFSDLB10 DFSDLB20 DFSDLB30
    DFSDLB40 DFSDLB50 DFSDLB60 DFSDLB70 DFSDLB80 DLBLCOM  DLBLPOP
    UERR
    

Fix information

  • Fixed component name

    IMS V12

  • Fixed component ID

    5635A0300

Applicable component levels

  • R200 PSY UK66123

       UP11/03/31 P F103 Ž

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z Systems"}],"Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 December 2020