IBM Support

PM11472: LOAD ABEND0C4 IN DISCARD PHASE WHEN INCORRECT SYSREC FILE WAS SPECIFIED AS INPUT. DB2OVRLAY/K SMCOVERLAY

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A BLOBF PDS file was accidentally specified as the SYSREC to a
    LOAD.  The LOAD abended in the DISCARD phase with an 0C4.
    Storage areas were overlaid that then caused other DB2 processes
    to abend.  DB2 had to be re-cycled to correct the problem.
    DB2OVRLAY/K
    

Local fix

  • Avoid specifying incorrect SYSREC input files.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 for z/OS V8 and DB2 9 for z/OS       *
    *                 utilities                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: LOAD INTO TABLE specifying a            *
    *                      Partitioned Data Set (PDS) as the input *
    *                      data set results in ABENDS0C4 at        *
    *                      DSNSVSGM +x'08D8'                       *
    ****************************************************************
    * RECOMMENDATION: Apply corrective PTF when available          *
    ****************************************************************
    LOAD INTO TABLE specifying a PDS without a member name as the
    input data set resulted in an ABEND0C4 at DSNSVSGM+x'08D8'.
    Because the input data set was specified only as a PDS without a
    member name, LOAD attempted to read and process the entire data
    set as a sequential file.  This caused all of the 'rows' to be
    discarded.
    
    While processing a discarded 'row', the length of the row was
    interpreted to be greater than 32K which, when copied from one
    buffer to another, overlayed into storage not allocated for the
    receiving buffer resulting in the ABENDS0C4.
    
    
    Additional keywords: SYSREC TEMPLATE INDDN
    

Problem conclusion

  • Code has been modified such that a Partitioned Data Set (PDS)
    without a member name is not allowed as the input data set.  If
    this occurs, MSGDSNU034I - "DATA SET TYPE INVALID FOR DDNAME
    ddname" and the utility will abend with ABEND04E RC00E40070.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM11472

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-04-02

  • Closed date

    2010-06-24

  • Last modified date

    2011-02-19

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

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

    UK58228 UK58229

Modules/Macros

  • DSNUGSDA
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R810 PSY UK58228

       UP10/07/10 P F007

  • R910 PSY UK58229

       UP10/07/10 P F007

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"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":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
19 February 2011