IBM Support

PL48834: IN DSNWDSDM, ABEND001 CAUSES UNNESSASARY DUMP, WHEN DBRMLIB DATASET IS INCORRECT AND HAVE RECFM=U

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • IF A USER MISTAKENLY SPECIFIES A LOADLIB (RECFM=U) AS DBRMLIB
    IN A DB2 COMPILE/BIND JOB, HE RECEIVES ABEND001 IN DSNWDSDM,
    AND SYSTEM GIVES UNNECESSARY SVCDUMP, CAUSING DB2 TO STOP WHILE
    A DUMP IS WRITTEN OUT TO THE DUMP DATASET.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: ALL DB2 USERS                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: MSGIEC020I NO ERROR HANDLING, (SYNAD)   *
    *                      EXIT ABEND001 ABENDS001 ON BIND         *
    *                      SUBCOMMAND WITH INCORRECT DBRM          *
    *                      LIBRARY                                 *
    ****************************************************************
    * RECOMMENDATION: APPLY APPLICABLE PTF                         *
    ****************************************************************
    AN UNNECESSARY DUMP AND JOB TERMINATION OCCURS WHEN THE BIND
    SUBCOMMAND HAS AN INCORRECT OR INVALID DBRM LIBRARY
    PARTITIONED DATA SET SPECIFIED, RESULTING IN AN I/O ERROR.
    

Problem conclusion

  • BIND IS CHANGED TO ADD A SYNAD EXIT SO THAT ANY I/O ERROR
    OCCURING WHEN READING THE DBRM IS INTERECEPTED AND APPROPRIATE
    ERROR MESSAGES ISSUED AND THE BIND TERMINATED. A NEW MESSAGE,
    MSGDSNT214I IS ADDED TO THE DB2 MESSAGES AND CODES TO INDICATE
    THE I/O ERROR:
    |MESSAGE        : DSNT214I
    |
    |MESSAGE TEXT   : I/O ERROR ON DBRM LIBRARY DBRM MEMBER=
    |DBRM-NAME DBRM LIBRARY= DBRM-PDS-NAME XXXXXX
    |
    |EXPLANATION: AN I/O ERROR WAS ENCOUNTERED ATTEMPTING TO READ A
    |DATABASE REQUEST MODULE (DBRM) DURING A BIND SUBCOMMAND.
    |'XXXXXX' IS A PORTION OF THE MESSAGE TEXT GENERATED BY THE
    |SYNADAF MACRO INSTRUCTION TO DESCRIBE THE PERMANENT I/O ERROR.
    | THIS TEXT MAY CONTAIN INFORMATION SUCH AS JOBNAME, STEPNAME,
    |UNIT ADDRESS, DEVICE TYPE, DDNAME, OPERATION ATTEMPTED, AND
    |ERROR DESCRIPTION.
    |
    |DBRM-NAME     NAME OF THE DBRM ASSOCIATED WITH THE ERROR.
    |
    |DBRM-PDS-NAME PARTITIONED DATA SET ASSOCIATED WITH THE ERROR.
    |
    |THIS MESSAGE IS ISSUED BY THE FOLLOWING CSECT(S): DSNTBAP1
    |
    |SYSTEM ACTION: NO APPLICATION PLAN IS CREATED.
    |
    |SYSTEM PROGRAMMER RESPONSE: DETERMINE IF AN INCORRECT
    |DBRM-PDS-NAME WAS SPECIFIED IN THE LIBRARY PARAMETER OF THE
    |BIND SUBCOMMAND, OR AN INCORRECT DATA SET NAME WAS SPECIFIED
    |FOR THE DBRMLIB DD STATEMENT. CHECK CORRECTLY SPECIFIED DATA
    |SETS FOR I/O ERRORS OR MODIFIED DCB ATTRIBUTES.
    |
    

Temporary fix

Comments

APAR Information

  • APAR number

    PL48834

  • Reported component name

    5740 IBM DATABA

  • Reported component ID

    5740XYR00

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1989-08-25

  • Closed date

    1989-10-03

  • Last modified date

    1992-01-09

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

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

    UL60480 UL60481

Modules/Macros

  •    DSNFMDIR DSNFTDIR DSNFTDTA DSNTBAP1
    

Publications Referenced
SC26437900    

Fix information

  • Fixed component name

    5740 IBM DATABA

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R210 PSY UL60481

       UP89/10/13 P F908

  • R220 PSY UL60480

       UP89/10/13 P F908

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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 August 2023