A rapid and abnormal increase in IXX601 utilization occurs, leading to an Abend SB37 on the index file.
This typically happens in environments supporting CA 11 where the index area fills despite organic growth predictions.
Additional indicators found in the MUF joblog may include:
Rapid jumps in extent allocation (e.g., reaching the 16-extent limit within minutes.
This issue is caused by one or more of the following:
Recovering the IXX601
Suspend or shut down the CA 11 application and make DB 601 unavailable to CA 11 using DBUTLTY:
ACCESS DBID=601,STATUS=OFF,USERS=FAIL
COMM DBID=601,OPTION=CLOSEIf the MUF is down (e.g., during a RESTART error), add the following to the beginning of your JCL SYSIN and omit the ACCESS and COMM commands:
SET OPTION1=MUF_NOT_ENABLEDAllocation and Rebuild
1. Delete or rename the existing IXX601 dataset.
2. Allocate a larger IXX601 dataset. Note: As a rule of thumb, the IXX601 should be at least as large as the larger of your JHF601 or DSN601 datasets.
3. Rebuild the index entries using the sample JCL below:
//INITDB EXEC PGM=DBUTLTY,REGION=0M
//STEPLIB DD DISP=SHR,DSN=DATACOM.CUSLIB
// DD DISP=SHR,DSN=DATACOM.CAAXLOAD
//IXX601 DD DISP=(,CATLG),DSN=<HLQ>..IXX601,
// SPACE=(CYL,(nnn,nn)),UNIT=3390
//SYSIN DD *
INIT DBID=601,AREA=IXX
RETIX DBID=601,OPTIMIZE=YES,SORT=999,SORTDFLT=YES,OPTION1='(I)'
COMM DBID=601,OPTION=STATS
REPORT DBID=601,AREA=CXX,TYPE=A
ACCESS DBID=601,STATUS=WRITE
/*
Preventative Maintenance
Apply Required PTFs
Apply the following PTFs to resolve the index loop defect:
• LU00265 and LU00589 (Fixes for LU00112)
• Latest level set recommended.
Implement Regular DEFRAG
Run the DBUTLTY DEFRAG function monthly or more frequently following the CA 11 MANT process. This reclaims space while the database remains active:
DEFRAG DBID=601
To speak with a customer representative or a Support Engineer, see Contact Support or refer to KB 206567.