APAR status
Closed as returned (APAR cannot be resolved without additional info from IBM or customer.)
Error description
DB2 ABEND04F MSGDSNV086E RC00E50715 FOLLOWING ABEND0C4 DSNWTRAC + X'06CC'. A TSO USER HAD SELECTED THE QMF OPTION ON THE ISPF MENU PANEL AND WAS WAITING FOR QMF TO INITIALIZE WHEN THE ERROR OCCURRED.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
IN TWO INCIDENTS IN QUICK SUCCESSION, DB2 WAS BROUGHT UP AND THE FIRST USER TO SIGN ON GOT AN ABEND0C4 IN DSNWTRAC BECAUSE OF A GARBAGE PHB POINTER BEING PASSED ON A FREE STORAGE REQUEST. IN BOTH CASES, THE PHB POINTER WAS DERIVED FROM THE CURSOR TABLE, AND BEFORE THAT CAME FROM ACOMPH12. ACOM WAS OVERLAID FOR FORTY BYTES WITH EBCDIC DATA AND GARBAGE. IT WAS NOT POSSIBLE TO DETERMINE WHAT THE OVERLAY WAS WITHOUT A PRINT OUT OF THE PRIVATE AREA. IT APPEARS THAT SOME TRANSIENT STORAGE MANAGEMENT PROBLEM MAY BE THE CULPRIT, SINCE THE DATA IN THE ACOM DID NOT LOOK AT ALL FAMILIAR.
APAR Information
APAR number
PP40244
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-02-07
Closed date
1985-02-15
Last modified date
1985-02-15
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
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