MUF abend S0C9 in DBDS2PR at x'000F38' or x'00100C'

Products

• Datacom/DB
• Datacom

Issue/Introduction

Every time a Sysview DCSETS command is issued or a query on SYSADM.DIR_DATASET is executed, MUF abends:

CCSR010E DBMUFPR S0C9 at 217CCF38 LMOD DBDS2PR CSECT DBDS2PR +000F38 N/A N/A N/A
CCSR021I OWNER = CA Datacom/DB R15.1                                            
CCSR022I MODULE = DBDS2PR FMID = CABDF10 RMID = SO15152                         
CCSR060I BREAKING EVENT ADDRESS: 00000000 217CCF10                              
CCSR061I PSW: 07840000 80000000 00000000 217CCF38                               
CCSR062I ILC: 02 INTERRUPT CODE: 09                                             
CCSR067I COMPLETION CODE S0C9 REASON CODE 00000009

When DBDS2PR is at an higher maintenance level, the offset is different, for example with LU10206 applied:

CCSR010E DBMUFPR S0C9 at 1FA7600C LMOD DBDS2PR CSECT DBDS2PR +00100C N/A N/A N/A 
CCSR021I OWNER = CA Datacom/DB R15.1                                             
CCSR022I MODULE = DBDS2PR FMID = CABDF10 RMID = LU10206                          
CCSR060I BREAKING EVENT ADDRESS: 00000000 1FA75FE2                               
CCSR061I PSW: 07842000 80000000 00000000 1FA7600C                                
CCSR062I ILC: 02 INTERRUPT CODE: 09                                              
CCSR067I COMPLETION CODE S0C9 REASON CODE 00000009

Environment

Release : 15.1

Component : DATACOM/DB

Cause

CXX corruption for a user DBID. A CXX report shows that the BLOCK LENGTH and BLOCKS/TRACK information for an area of this DBID is zero. 

Resolution

1. Take a PHYSICAL BACKUP of the database
2. Once you have done a successful BACKUP, recatalog the DBID into the CXX.
3. Run CXX report again to ensure that now the CXX has valid BLOCK LENGTH and BLOCKS/TRACK information.
4. Run DBUTLTY INIT function for the IXX and the data areas and then null load the data areas.
5. LOAD the DBID from the BACKUP.

Updated resolution:

Download and apply Datacom/DB 15.1 PTF LU20209