CA Datacom Version 15.0 MUF abended at startup with
DBMUFPR S0C4 at 28E4A686 LMOD DBMFSPR CSECT DBMFSPR +006686
The TASK INFORMATION portion of the resultant MUF EOJ report showed an entry with "WAIT DB MISC":
***DBRST 274 :04 OPEN WAIT DB MISC
What caused MUF restart S0C4 DBMFSPR with EOJ report showing ***DBRST WAIT DB MISC?
CA Datacom Version 15.0 HIPER RO92484 will address this problem as well as the RESTART hang "WAIT DB MISC" problem as documented that is seen when issue the STATUS console command. For example:
DB01311I - STATUS
DB01327I - MULTI-USER ENABLING, TASKS - ATTACHED-----0, AVAILABLE-----0
DB01328I - TIME I/O JOBNAME R-UNIT TASK CMD-DBID-TBL SEQ STATUS
DB01329I - 29:40 ***DBRST 124 OPEN 571150 WAIT DB MISC
Refer to CA Datacom Core - 15.1 section on "COMM EOJ - EOJ_OK" subsection "MUF EOJ Report Logging"
If the MUF fails with an abnormal EOJ, a page showing task information follows the previously shown other information report. The task information contains status information similar to other status displays, but the task information report is specifically targeted at helping to debug the abnormal failure. Fields unique to the task information report are described after the report example that follows.
TASK INFORMATION JOBNAME RUNIT TASK TIME I/O B-RF CMD-DBID-TBL STATUS TSN LOGR OWNR/Y VALUE/RID JOB0040 79588 1 :04 UPDAT 997C02 PENDING JOB0040 79588 2 :04 1 RDUNX 997F01 WAIT BFR LOCK D DBDB0771 83 JOB0040 79588 3 :04 1 2 RDUKG 997F02 WAIT BFR LOCK D DBDB076C101 JOB0040 4 :04 RDUNX 997F03 PENDING
This page of the report provides the following information: