IBM Support

PL56754: ABEND04F DSNVSR RC00E50054 RC00E50079 AFTER CANCEL OF TSO USER END OF ABSTRACT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A TSO USER WAS CANCELLED AND DB2 CAME DOWN IMMEDIATELY WITH AN
    ABEND04F RC00E50054. USER ALSO SAW SUBSEQUENT ERRORS: ABEND04F
    RC00E50079, ABEND0D6 RC22. HE ALSO RECEIVED MSGIEA912I WHICH
    INDICATED THAT RECOVERY/TERMINATION HAD FAILED. AN ATTEMPT TO
    LOCATE THE ROB FOR THE ACTIVE EB WAS UNSUCCESSFUL. CUSTOMER HAS
    APPLIED UL63943, SO DOES NOT HAVE THE PROBLEM INTRODUCED BY
    UL48068.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: ALL USERS OF DB2.                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: ABEND04E RC00E50079 FOLLOWED BY         *
    *                      ABEND04F RC00E50054.  DB2TERM           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    AN INVALID ROB WAS PASSED TO DSNVSR ON A SUSPEND/RESUME
    REQUEST. DB2 WAS UNABLE TO RECOVER FROM THIS ERROR SO THE
    SUBSYSTEM WAS BROUGHT DOWN WITH RC00E50054.
    

Problem conclusion

  • CODE HAS BEEN ADDED TO THE LATCH MANAGER COMPONENT TO HELP
    PREVENT DUPLICATE ROB'S FROM BEING PLACED ON THE LATCH WAIT
    CHAIN. EXTENSIVE SERVICEABILITY AND ERROR-CHECKING HAS BEEN
    ADDED THROUGHOUT THE AGENT SERVICES COMPONENT TO PREVENT
    IMPROPER OR INVALID USE OF THE ROB FOR SUSPEND AND RESUME
    PROCESSING. THE ROB'S AND EB'S WILL NOW CONTAIN ADDITIONAL
    TRACKING AND DIAGNOSTIC INFORMATION RELATING TO THEIR USE.
    ALSO, EARLIER DETECTION OF AN INVALID ROB MAY ASSIST RECOVERY
    IN KEEPING THE DB2 SUBSYSTEM UP.  DEVCHNG
    THE DB2 MESSAGES AND CODES MANUAL WILL BE UPDATED WITH
    THE FOLLOWING NEW REASON CODES:
    RC00E50005, RC00E50006, RC00E50007, RC00E50008, RC00E50009,
    RC00E50042, RC00E50073, RC00E50096, AND RC00E50097.
    FOLLOWING ARE THEIR DESCRIPTIONS:
    *
    REASON CODE    : 00E50005
    EXPLANATION: A RESOURCE OPTIONS BLOCK (ROB) WHICH WAS TO BE
    ADDED TO A LATCH WAITER CHAIN WAS DISCOVERED TO BE ON THE
    CHAIN ALREADY. THE SAME ROB CANNOT BE ON THE SAME LATCH WAITER
    CHAIN TWICE. THIS IS PROBABLY A DB2 SUBSYSTEM ERROR.
    THIS ABEND REASON CODE IS ISSUED BY THE FOLLOWING CSECT(S):
    DSNVSLT0, DSNVSUL0, DSNVXLT0
    SYSTEM ACTION: THE REQUESTING EXECUTION UNIT IS ABENDED.
    OPERATOR RESPONSE: NOTIFY THE SYSTEM PROGRAMMER.
    SYSTEM PROGRAMMER RESPONSE: COLLECT THE NECESSARY DIAGNOSTIC
    MATERIALS. REFER TO SECTION 5 OF "DIAGNOSIS GUIDE AND
    REFERENCE" FOR FAILURE ANALYSIS PROCEDURES AND FOR INFORMATION
    ABOUT DUMP ANALYSIS AND SERVICE AIDS.
    PROBLEM DETERMINATION: AT THE TIME OF THE ABEND, GENERAL
    REGISTER THREE CONTAINS THE ADDRESS OF THE ROB WHICH WOULD
    HAVE BEEN ADDED TO THE LATCH WAITER CHAIN.
    A RECORD IS WRITTEN TO SYS1.LOGREC AND A DB2 SVC DUMP IS
    REQUESTED.
    COLLECT THE FOLLOWING DIAGNOSTIC ITEMS:
    - CONSOLE OUTPUT FROM THE SYSTEM ON WHICH THE JOB WAS RUN, AND
      A LISTING OF SYSLOG DATA SET FOR THE PERIOD OF TIME SPANNING
      THE FAILURE.
    - DYNAMIC DUMP TAKEN TO SYS1.DUMPXX DATA SET BY DB2.
    - LISTING OF SYS1.LOGREC DATA SET, OBTAINED BY EXECUTING
      IFCEREP1.
    *
    REASON CODE    : 00E50006
    EXPLANATION: AN EXECUTION UNIT WHICH, ACCORDING TO TRACKING
    INFORMATION, IS CURRENTLY SUSPENDED ON A LATCH WAITER CHAIN
    ISSUED A REQUEST TO ACQUIRE A LATCH. A SINGLE EXECUTION UNIT
    CANNOT BE DOING BOTH AT THE SAME TIME. THIS IS PROBABLY A DB2
    SUBSYSTEM ERROR.
    THIS ABEND REASON CODE IS ISSUED BY THE FOLLOWING CSECT(S):
    DSNVSLT0, DSNVXLT0, AND ANY CSECT WHICH ISSUES THE DSNVLTHS OR
    DSNVLTHX LATCH ACQUISITION MACROS.
    SYSTEM ACTION: THE REQUESTING EXECUTION UNIT IS ABENDED.
    OPERATOR RESPONSE: NOTIFY THE SYSTEM PROGRAMMER.
    SYSTEM PROGRAMMER RESPONSE: COLLECT THE NECESSARY DIAGNOSTIC
    MATERIALS. REFER TO SECTION 5 OF "DIAGNOSIS GUIDE AND
    REFERENCE" FOR FAILURE ANALYSIS PROCEDURES AND FOR INFORMATION
    ABOUT DUMP ANALYSIS AND SERVICE AIDS.
    PROBLEM DETERMINATION: AT THE TIME OF THE ABEND, GENERAL
    REGISTER ZERO CONTAINS THE ADDRESS OF THE LATCH UPON WHICH THE
    EXECUTION UNIT IS SUPPOSEDLY WAITING AND GENERAL REGISTER TWO
    CONTAINS THE ADDRESS OF THE RESOURCE OPTIONS BLOCK (ROB) WHICH
    WAS PUT ON THE LATCH WAITER CHAIN.
    A RECORD IS WRITTEN TO SYS1.LOGREC AND A DB2 SVC DUMP IS
    REQUESTED.
    COLLECT THE FOLLOWING DIAGNOSTIC ITEMS:
    - CONSOLE OUTPUT FROM THE SYSTEM ON WHICH THE JOB WAS RUN, AND
      A LISTING OF SYSLOG DATA SET FOR THE PERIOD OF TIME SPANNING
      THE FAILURE.
    - DYNAMIC DUMP TAKEN TO SYS1.DUMPXX DATA SET BY DB2.
    - LISTING OF SYS1.LOGREC DATA SET, OBTAINED BY EXECUTING
      IFCEREP1.
    *
    REASON CODE    : 00E50007
    EXPLANATION: AN EXECUTION UNIT WHICH, ACCORDING TO TRACKING
    INFORMATION, IS CURRENTLY SUSPENDED ON A LATCH WAITER CHAIN
    ISSUED A REQUEST TO TEST OR TO RELEASE A LATCH. A SINGLE
    EXECUTION UNIT CANNOT BE DOING BOTH AT THE SAME TIME. THIS IS
    PROBABLY A DB2 SUBSYSTEM ERROR.
    THIS ABEND REASON CODE IS ISSUED BY THE FOLLOWING CSECT(S):
    DSNVLTT0, DSNVSUL0, DSNVXUL0, AND ANY CSECT WHICH ISSUES THE
    DSNVUNLS OR DSNVUNLX LATCH RELEASE MACROS.
    SYSTEM ACTION: THE REQUESTING EXECUTION UNIT IS ABENDED.
    OPERATOR RESPONSE: NOTIFY THE SYSTEM PROGRAMMER.
    SYSTEM PROGRAMMER RESPONSE: COLLECT THE NECESSARY DIAGNOSTIC
    MATERIALS. REFER TO SECTION 5 OF "DIAGNOSIS GUIDE AND
    REFERENCE" FOR FAILURE ANALYSIS PROCEDURES AND FOR INFORMATION
    ABOUT DUMP ANALYSIS AND SERVICE AIDS.
    PROBLEM DETERMINATION: AT THE TIME OF THE ABEND, GENERAL
    REGISTER ZERO CONTAINS THE ADDRESS OF THE LATCH UPON WHICH THE
    EXECUTION UNIT IS SUPPOSEDLY WAITING AND GENERAL REGISTER TWO
    CONTAINS THE ADDRESS OF THE RESOURCE OPTIONS BLOCK (ROB) WHICH
    WAS PUT ON THE LATCH WAITER CHAIN.
    A RECORD IS WRITTEN TO SYS1.LOGREC AND A DB2 SVC DUMP IS
    REQUESTED.
    COLLECT THE FOLLOWING DIAGNOSTIC ITEMS:
    - CONSOLE OUTPUT FROM THE SYSTEM ON WHICH THE JOB WAS RUN, AND
      A LISTING OF SYSLOG DATA SET FOR THE PERIOD OF TIME SPANNING
      THE FAILURE.
    - DYNAMIC DUMP TAKEN TO SYS1.DUMPXX DATA SET BY DB2.
    - LISTING OF SYS1.LOGREC DATA SET, OBTAINED BY EXECUTING
      IFCEREP1.
    *
    REASON CODE    : 00E50008
    EXPLANATION: A LATCH MANAGER MODULE DETECTED THAT AN EXECUTION
    UNIT REQUESTING LATCH MANAGER SERVICE POINTED TO AN INVALID
    EXECUTION BLOCK (EB). THIS IS PROBABLY A DB2 SUBSYSTEM ERROR.
    THIS ABEND REASON CODE IS ISSUED BY THE FOLLOWING CSECT(S):
    DSNVLTT0, DSNVSLT0, DSNVSUL0, DSNVXLT0, DSNVXUL0
    SYSTEM ACTION: THE REQUESTING EXECUTION UNIT IS ABENDED.
    OPERATOR RESPONSE: NOTIFY THE SYSTEM PROGRAMMER.
    SYSTEM PROGRAMMER RESPONSE: COLLECT THE NECESSARY DIAGNOSTIC
    MATERIALS. REFER TO SECTION 5 OF "DIAGNOSIS GUIDE AND
    REFERENCE" FOR FAILURE ANALYSIS PROCEDURES AND FOR INFORMATION
    ABOUT DUMP ANALYSIS AND SERVICE AIDS.
    PROBLEM DETERMINATION: A RECORD IS WRITTEN TO SYS1.LOGREC AND
    A DB2 SVC DUMP IS REQUESTED.
    COLLECT THE FOLLOWING DIAGNOSTIC ITEMS:
    - CONSOLE OUTPUT FROM THE SYSTEM ON WHICH THE JOB WAS RUN, AND
      A LISTING OF SYSLOG DATA SET FOR THE PERIOD OF TIME SPANNING
      THE FAILURE.
    - DYNAMIC DUMP TAKEN TO SYS1.DUMPXX DATA SET BY DB2.
    - LISTING OF SYS1.LOGREC DATA SET, OBTAINED BY EXECUTING
      IFCEREP1.
    *
    REASON CODE    : 00E50009
    EXPLANATION: A LATCH MANAGER MODULE DETECTED AN INVALID
    RESOURCE OPTIONS BLOCK (ROB) WHILE PROCESSING A REQUEST FOR
    SERVICE. THIS IS PROBABLY A DB2 SUBSYSTEM ERROR.
    THIS MAY BE EITHER AN ABEND REASON CODE OR A DB2 SUBSYSTEM
    TERMINATION CODE.
    THIS REASON CODE IS ISSUED BY THE FOLLOWING CSECT(S):
    DSNVLFRR, DSNVLTT0, DSNVSLT0, DSNVSUL0, DSNVXLT0, DSNVXUL0
    SYSTEM ACTION: THE REQUESTING EXECUTION UNIT IS ABENDED.
    OPERATOR RESPONSE: NOTIFY THE SYSTEM PROGRAMMER.
    SYSTEM PROGRAMMER RESPONSE: COLLECT THE NECESSARY DIAGNOSTIC
    MATERIALS. REFER TO SECTION 5 OF "DIAGNOSIS GUIDE AND
    REFERENCE" FOR FAILURE ANALYSIS PROCEDURES AND FOR INFORMATION
    ABOUT DUMP ANALYSIS AND SERVICE AIDS.
    PROBLEM DETERMINATION: A RECORD IS WRITTEN TO SYS1.LOGREC AND
    A DB2 SVC DUMP IS REQUESTED.
    COLLECT THE FOLLOWING DIAGNOSTIC ITEMS:
    - CONSOLE OUTPUT FROM THE SYSTEM ON WHICH THE JOB WAS RUN, AND
      A LISTING OF SYSLOG DATA SET FOR THE PERIOD OF TIME SPANNING
      THE FAILURE.
    - DYNAMIC DUMP TAKEN TO SYS1.DUMPXX DATA SET BY DB2.
    - LISTING OF SYS1.LOGREC DATA SET, OBTAINED BY EXECUTING
      IFCEREP1.
    *
    REASON CODE    : 00E50042
    EXPLANATION: AN EXECUTION UNIT WHICH, ACCORDING TO TRACKING
    INFORMATION, IS CURRENTLY SUSPENDED ON A LATCH WAITER CHAIN IS
    IN THE AGENT TERMINATION PROCESS. THIS MAY INDICATE THAT A
    LATCH MANAGER REQUEST IS STILL INCOMPLETE OR HAS NOT BEEN
    SERVICED PROPERLY. THIS IS PROBABLY A DB2 SUBSYSTEM ERROR.
    THIS ABEND REASON CODE IS ISSUED BY THE FOLLOWING CSECT(S):
    DSNVFACE, DSNVTEB
    SYSTEM ACTION: THE CURRENT EXECUTION UNIT IS ABENDED.
    OPERATOR RESPONSE: NOTIFY THE SYSTEM PROGRAMMER.
    SYSTEM PROGRAMMER RESPONSE: COLLECT THE NECESSARY DIAGNOSTIC
    MATERIALS. REFER TO SECTION 5 OF "DIAGNOSIS GUIDE AND
    REFERENCE" FOR FAILURE ANALYSIS PROCEDURES AND FOR INFORMATION
    ABOUT DUMP ANALYSIS AND SERVICE AIDS.
    PROBLEM DETERMINATION: AT THE TIME OF THE ABEND, GENERAL
    REGISTER ZERO CONTAINS THE ADDRESS OF THE LATCH UPON WHICH THE
    EXECUTION UNIT IS SUPPOSEDLY WAITING AND GENERAL REGISTER TWO
    CONTAINS THE ADDRESS OF THE RESOURCE OPTIONS BLOCK (ROB) WHICH
    WAS PUT ON THE LATCH WAITER CHAIN.
    A RECORD IS WRITTEN TO SYS1.LOGREC AND A DB2 SVC DUMP IS
    REQUESTED.
    COLLECT THE FOLLOWING DIAGNOSTIC ITEMS:
    - CONSOLE OUTPUT FROM THE SYSTEM ON WHICH THE JOB WAS RUN, AND
      A LISTING OF SYSLOG DATA SET FOR THE PERIOD OF TIME SPANNING
      THE FAILURE.
    - DYNAMIC DUMP TAKEN TO SYS1.DUMPXX DATA SET BY DB2.
    - LISTING OF SYS1.LOGREC DATA SET, OBTAINED BY EXECUTING
      IFCEREP1.
    *
    REASON CODE    : 00E50073
    EXPLANATION: EXECUTION UNIT SWITCH PROCESSING DETECTED AN
    INVALID EXECUTION BLOCK (EB) OR AN INVALID RESOURCE OPTIONS
    BLOCK (ROB). THIS IS PROBABLY A DB2 SUBSYSTEM ERROR.
    THIS ABEND REASON CODE IS ISSUED BY THE FOLLOWING CSECT(S):
    DSNVEUS2, DSNVEUS3, DSNVTEB
    SYSTEM ACTION: THE CURRENT EXECUTION UNIT IS ABENDED.
    OPERATOR RESPONSE: NOTIFY THE SYSTEM PROGRAMMER.
    SYSTEM PROGRAMMER RESPONSE: COLLECT THE NECESSARY DIAGNOSTIC
    MATERIALS. REFER TO SECTION 5 OF "DIAGNOSIS GUIDE AND
    REFERENCE" FOR FAILURE ANALYSIS PROCEDURES AND FOR INFORMATION
    ABOUT DUMP ANALYSIS AND SERVICE AIDS.
    PROBLEM DETERMINATION: AT THE TIME OF THE ABEND, GENERAL
    REGISTER ZERO CONTAINS THE ADDRESS WHICH SHOULD HAVE POINTED
    TO A VALID CONTROL BLOCK BUT DID NOT.
    COLLECT THE FOLLOWING DIAGNOSTIC ITEMS:
    - CONSOLE OUTPUT FROM THE SYSTEM ON WHICH THE JOB WAS RUN, AND
      A LISTING OF SYSLOG DATA SET FOR THE PERIOD OF TIME SPANNING
      THE FAILURE.
    - DYNAMIC DUMP TAKEN TO SYS1.DUMPXX DATA SET BY DB2.
    - LISTING OF SYS1.LOGREC DATA SET, OBTAINED BY EXECUTING
      IFCEREP1.
    *
    REASON CODE    : 00E50096
    EXPLANATION: A REQUEST WAS MADE TO SUSPEND AN EXECUTION UNIT
    BUT THE RESOURCE OPTIONS BLOCK (ROB) WHICH IS REQUIRED FOR
    THIS REQUEST IS INVALID. THIS IS PROBABLY A DB2 SUBSYSTEM
    ERROR.
    THIS ABEND REASON CODE IS ISSUED BY THE FOLLOWING CSECT(S):
    ANY CSECT WHICH REQUESTS SUSPENSION IS SUBJECT TO THIS ABEND
    SINCE IT IS ISSUED BY THE IN-LINE EXPANSION OF THE MACRO USED
    TO MAKE THE REQUEST.
    SYSTEM ACTION: THE REQUESTING EXECUTION UNIT IS ABENDED.
    OPERATOR RESPONSE: NOTIFY THE SYSTEM PROGRAMMER.
    SYSTEM PROGRAMMER RESPONSE: COLLECT THE NECESSARY DIAGNOSTIC
    MATERIALS. REFER TO SECTION 5 OF "DIAGNOSIS GUIDE AND
    REFERENCE" FOR FAILURE ANALYSIS PROCEDURES AND FOR INFORMATION
    ABOUT DUMP ANALYSIS AND SERVICE AIDS.
    PROBLEM DETERMINATION: AT THE TIME OF THE ABEND, GENERAL
    REGISTER ZERO CONTAINS THE ADDRESS WHICH SHOULD HAVE POINTED
    TO A VALID ROB BUT DID NOT.
    COLLECT THE FOLLOWING DIAGNOSTIC ITEMS:
    - CONSOLE OUTPUT FROM THE SYSTEM ON WHICH THE JOB WAS RUN, AND
      A LISTING OF SYSLOG DATA SET FOR THE PERIOD OF TIME SPANNING
      THE FAILURE.
    - DYNAMIC DUMP TAKEN TO SYS1.DUMPXX DATA SET BY DB2.
    - LISTING OF SYS1.LOGREC DATA SET, OBTAINED BY EXECUTING
      IFCEREP1.
    *
    REASON CODE    : 00E50097
    EXPLANATION: A REQUEST WAS MADE TO RESUME AN EXECUTION UNIT
    BUT THE RESOURCE OPTIONS BLOCK (ROB) WHICH IS REQUIRED FOR
    THIS REQUEST IS INVALID. THIS IS PROBABLY A DB2 SUBSYSTEM
    ERROR.
    THIS ABEND REASON CODE IS ISSUED BY THE FOLLOWING CSECT(S):
    ANY CSECT WHICH REQUESTS THE RESUME SERVICE IS SUBJECT TO THIS
    ABEND SINCE IT IS ISSUED BY THE IN-LINE EXPANSION OF THE MACRO
    USED TO MAKE THE REQUEST.
    SYSTEM ACTION: THE REQUESTING EXECUTION UNIT IS ABENDED.
    OPERATOR RESPONSE: NOTIFY THE SYSTEM PROGRAMMER.
    SYSTEM PROGRAMMER RESPONSE: COLLECT THE NECESSARY DIAGNOSTIC
    MATERIALS. REFER TO SECTION 5 OF "DIAGNOSIS GUIDE AND
    REFERENCE" FOR FAILURE ANALYSIS PROCEDURES AND FOR INFORMATION
    ABOUT DUMP ANALYSIS AND SERVICE AIDS.
    PROBLEM DETERMINATION: AT THE TIME OF THE ABEND, GENERAL
    REGISTER ZERO CONTAINS THE ADDRESS WHICH SHOULD HAVE POINTED
    TO A VALID ROB BUT DID NOT.
    COLLECT THE FOLLOWING DIAGNOSTIC ITEMS:
    - CONSOLE OUTPUT FROM THE SYSTEM ON WHICH THE JOB WAS RUN, AND
      A LISTING OF SYSLOG DATA SET FOR THE PERIOD OF TIME SPANNING
      THE FAILURE.
    - DYNAMIC DUMP TAKEN TO SYS1.DUMPXX DATA SET BY DB2.
    - LISTING OF SYS1.LOGREC DATA SET, OBTAINED BY EXECUTING
      IFCEREP1.
    *
    ALSO, THE DESCRIPTION FOR REASON CODE 00E50705 WILL BE
    MODIFIED AS FOLLOWS:
    *
     REASON CODE    : 00E50705
    |EXPLANATION: A SUBSYSTEM TERMINATION WAS REQUESTED BECAUSE
    |EITHER 1) AN AGENT WAS FLAGGED AS EXECUTING IN 'MUST COMPLETE'
    |MODE, OR 2) AN EXECUTION UNIT HOLDS A LATCH, OR 3) AN AGENT IS
    |MARKED AS BEING ON A LATCH WAITER QUEUE, WHEN NONE OF THESE
    |CONDITIONS SHOULD BE TRUE. ADDITIONALLY, THE SUBSYSTEM
    |TERMINATION MAY HAVE BEEN PRECEDED BY AN ABEND WITH THIS
    |REASON CODE. INTERNAL DB2 INFORMATION
     THIS TERMINATION REASON CODE IS ISSUED BY THE FOLLOWING
     CSECT(S): DSNVEUS2, DSNVEUS3, DSNVEOT1
     SYSTEM ACTION: THE DB2 SUBSYSTEM IS ABENDED.
     OPERATOR RESPONSE: NOTIFY THE SYSTEM PROGRAMMER, AND RESTART
     DB2.
     SYSTEM PROGRAMMER RESPONSE: SCAN THE SYS1.LOGREC ENTRIES
     LOOKING FOR ONE OR MORE DB2 ABENDS IMMEDIATELY PRIOR TO THE
     SUBSYSTEM TERMINATION. REFER TO SECTION 5 OF DIAGNOSIS GUIDE
     AND REFERENCE FOR FAILURE ANALYSIS PROCEDURES.
     THE RECOVERY ROUTINE FOR THE CSECT ISSUING THIS REASON CODE
     RECORDS INFORMATION IN THE VARIABLE RECORDING AREA (VRA).
     REFER TO SECTION 5 OF DIAGNOSIS GUIDE AND REFERENCE FOR MORE
     INFORMATION ABOUT THE VRA, DUMP ANALYSIS, AND SERVICE AIDS.
     PROBLEM DETERMINATION: DB2 DIAGNOSTIC INFORMATION MAY BE
     OBTAINED THROUGH SYS1.LOGREC AND SVC DUMP MATERIALS GENERATED
     AT THE TIME OF THE ORIGINAL ERROR. REFER TO THE ACCOMPANYING
     ABEND CODE TO DETERMINE THE FAILURE WHILE IN 'MUST COMPLETE'
     STATE. REFER TO "DB2 ABEND COMPLETION CODES (X'04E' AND
    |X'04F')" ON PAGE 1-6 FOR INFORMATION ABOUT X'04F' AND X'04E'
    |ABEND COMPLETION CODES.
     IF SUBSYSTEM TERMINATION WAS REQUESTED BY MODULE DSNVEUS2, A
     STANDARD MVS SVC DUMP WILL BE GENERATED.
     THE 'MUST COMPLETE' INDICATOR IS BIT ACEMC. LATCH-HELD
    |INDICATORS ARE IN FIELD EBLTCHLD. LATCH WAITER STATUS
    |INFORMATION IS IN FIELD EBLWSI.
    |USUALLY THESE CONDITIONS OCCUR AS THE RESULT OF A PRIOR
    |FAILURE WHERE THE ASSOCIATED RECOVERY ROUTINE DID NOT PERFORM
    |CORRECT RESOURCE CLEANUP. THE CONDITION MAY ALSO OCCUR IF A
    |RESOURCE MANAGER FUNCTION DOES NOT RELEASE ALL LATCHES AND/OR
    |RESET THE 'MUST COMPLETE' BIT BEFORE RETURNING CONTROL TO
    |EITHER DSNVEUS2 OR DSNVEUS3.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PL56754

  • 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

    1990-02-01

  • Closed date

    1991-03-22

  • Last modified date

    1991-08-18

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

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

    UL94604 UL94605

Modules/Macros

  •    DSNDEB   DSNDF002 DSNDROB  DSNVEUS1 DSNVEUS2
    DSNVEUS3 DSNVFACE DSNVLFRR DSNVLTHS DSNVLTHX DSNVLTT0 DSNVRESM
    DSNVSLT0 DSNVSR   DSNVSRR  DSNVSRT  DSNVSUL0 DSNVSUSP DSNVTEB
    DSNVUNLS DSNVUNLX DSNVXLT0 DSNVXUL0 DSN3EOM0 DSN3EOT0
    

Publications Referenced
SC26437901    

Fix information

  • Fixed component name

    5740 IBM DATABA

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R210 PSY UL94604

       UP91/05/02 P DLL5 F104

  • R220 PSY UL94605

       UP91/05/02 P DLL5 F104

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.

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

Document Information

Modified date:
05 March 2021