MUF restart S0C4 DBMFSPR ***DBRST WAIT DB MISC
Article ID: 103941
Updated On:
Products
CA Datacom - DB
CA Datacom
CA Datacom - AD
CA Datacom - Server
CA CIS
CA Common Services for z/OS
CA 90s Services
CA Database Management Solutions for DB2 for z/OS
CA Common Product Services Component
CA Common Services
CA Datacom/AD
CA ecoMeter Server Component FOC
CA Easytrieve Report Generator for Common Services
CA Infocai Maintenance
CA IPC
Unicenter CA-JCLCheck Common Component
CA Mainframe VM Product Manager
CA Chorus Software Manager
CA On Demand Portal
CA Service Desk Manager - Unified Self Service
CA PAM Client for Linux for zSeries
CA Mainframe Connector for Linux on System z
CA Graphical Management Interface
CA Web Administrator for Top Secret
CA CA- Xpertware
Issue/Introduction
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?
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?
Environment
z/OS
Resolution
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
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
Additional Information
Refer to CA Datacom Core - 15.1 section on "COMM EOJ - EOJ_OK" subsection "MUF EOJ Report Logging"
https://docops.ca.com/ca-datacom/15-1/en/reference/dbutlty-reference/utility-function-summary/comm-communicate-with-muf/comm-eoj-eoj_ok-end-muf-processing#COMMEOJ-EOJ_OK(EndMUFProcessing)-MUFEOJReportLoggingSectionChanges
https://docops.ca.com/ca-datacom/15-1/en/reference/dbutlty-reference/utility-function-summary/comm-communicate-with-muf/comm-eoj-eoj_ok-end-muf-processing#COMMEOJ-EOJ_OK(EndMUFProcessing)-MUFEOJReportLoggingSectionChanges
Task Information
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:
- B-RF
Displays the current buffer references. - LOGR
Displays the number of log records executed by the task since the last close or commit occurred.
Feedback
Powered by
