IBM Support

PP44047: MSGDSNT376I PLAN=BINDCT TIMEOUT DUE TO LOCK HELD. MSGIAT6809 END OF MEMORY AFTER CREATE INDEX WITH NO PRI. OR SEC. QUANTITY.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as returned (APAR cannot be resolved without additional info from IBM or customer.)

Error description

  • USER ATTEMPTED TO CREATE 13 INDEXS ON A TABLE JUST LOADED WITH
    NO PRIMARY OR SECONDARY QUANTITIES SUPPLIED. THAT HUNG HIM UP.
    TO GET FREE, HE TRIED TO DO A SIMPLE SELECT FROM
    SYSIBM.SYSDBAUTH AND HUNG UP FOR AROUND TEN MINUTES. THE USER
    THEN HIT THE ATTENTION KEY AND NOTHING HAPPENED AGAIN. HE TRIED
    ANOTHER SIMPLE SELECT, NOTHING AGAIN. HE CALLED TO HAVE HIS ID
    CANCELLED, BUT OPERATIONS HAD TO TAKE DB2 DOWN TO FREE UP THE
    SYSTEM.
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • THE ABEND073 AND ABEND0D5 ARE THE CONSEQUENCE OF A LOCKOUT
    PROBLEM AND A CANCEL COMMAND ON THE CONSOLE. THE SEQUENCE OF
    EVENTS ARE AS FOLLOWS:-
    1. DSNT376I - PLAN=BINDCT WITH CORRELATION-ID=ED11001 AND
       CONNECTION-ID=TSO IS TIME OUT DUE TO A LOCK HELD BY
       PLAN=DWNA WITH CORRELATION-ID=DW00453 AND CONNECTION-ID=TSO
    2. OPERATOR ENTERED A 'CANCEL U=DR54435' COMMAND ON THE CONSOLE
    3. IAT6809  DB11DBM1 (ADMF ADDR SPACE) - TERMINATED BY END OF
       MEMORY.
    4. ABEND073 - DUE TO THE LOCKOUT PROBLEM (EVENT 1), THE CML
       LOCK (LOCAL LOCK OF DSCF) WAS HELD. AT THE SAME TIME THE
       CANCEL COMMAND WAS ISSUED ON THE CONSOLE (EVENT 3). DSNVSR
       TRIED TO OBTAIN THE LOCAL LOCK OF DSCF. THEREFORE, MVS
       LOCK MANAGER ISSUED ABEND073-08 SAYING THAT 'ANOTHER LOCK
       OF THE SAME TYPE WAS ALREADY HELD.
    5. ABEND0D5 - JUST BECAUSE THE ADDR SPACE THAT A PROGRAM
       REFERRED TO WAS SWAP OUT (NON-DISPATCHABLE). THERE IS NO
       RELATIONSHIP BETWEEN ABEND0D5 AND ABEND073.
    
    THEREFORE, IF THERE WERE PROBLEM, IT WAS THE LOCKOUT PROBLEM.
    HOWEVER, IN ORDER TO SOLVE THE LOCKOUT PROBLEM, WE NEED THE
    DOCUMENTATION AND DETAIL DESCRIPTION OF THE PROBLEM (E.G. SQL
    APPLICATION PROGRAMS AND QMF USERS THAT WERE INVOLVED).
    

APAR Information

  • APAR number

    PP44047

  • Reported component name

    5740 IBM DATABA

  • Reported component ID

    5740XYR00

  • Reported release

    102

  • Status

    CLOSED RET

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1985-05-30

  • Closed date

    1985-06-11

  • Last modified date

    1985-06-11

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

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

Fix information

  • Fixed component name

    5740 IBM DATABA

  • Fixed component ID

    5740XYR00

Applicable component levels

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

Document Information

Modified date:
15 March 2024