What to do when you receive SB37 ABEND on IXX601
Article ID: 54792
Updated On:
Products
Issue/Introduction
If the MANT task is not run on a regular basis or the IXX for Database 601 is not sized appropriately, the database index area (IXX601) for CA 11 could fill up. This can result in an Abend SB37 on the IXX601 file and affect batch processing. The actions to take should the IXX601 file fills up are as follows:
- Suspend or shut down CA 11 on all LPARs that share the same DB 601 (see note below);
- Turn off access to the database and close it in the Multi-User Facility (called MUF) using PGM=DBUTLTY;
- Delete or rename the current IXX601 file;
- Allocate a new IXX601 with a larger size;
- Recreate the index with DBUTLTY RETIX;
- Turn on access to the database with DBUTLTY;
- Resume or restart CA 11.
NOTE: If TRKRMS=NO is specified in the CA 11 config file, CA 11 will have to be shut down down instead of performing a SUSPEND.
Environment
Component: 11
Resolution
Before the IXX601 file can be allocated larger, DB 601 must be made unavailable to CA 11. Use the CA Datacom/AD DBUTLTY program with this input:
//SYSIN DD *
ACCESS DBID=601,STATUS=OFF,USERS=FAIL
COMM DBID=601,OPTION=CLOSE
/*
If the DBUTLTY step does not complete with a COND CODE 0000, at least one instance of CA 11 is still connected to the CA Datacom MUF. Identify and Suspend or end the instances and then resubmit the DBUTLTY. If the DBUTLTY still fails after verifying all CA 11 instances are inactive, contact CA Datacom Support for assistance.
Once this is done you may now delete or rename the IXX601. After the IXX601 has been deleted or renamed, you can allocate a larger IXX601 dataset, rebuild its index entries and make DB 601 available for access by CA11 again. Below is a sample to do all this. Please see information in the NOTE that follows the JCL prior to running this job.
//INITDB EXEC PGM=DBUTLTY,REGION=0M
//STEPLIB DD DISP=SHR,DSN=DATACOM.CUSLIB
// DD DISP=SHR,DSN=DATACOM.CAAXLOAD
//IXX601 DD DISP=(,CATLG),DSN=&CA11..IXX601,
// SPACE=(CYL,(nnn,nn)),UNIT=&UNIT
//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
/*
NOTE: As a rule of thumb, the IXX601 should be as large as the larger of your JHF601 or DSN601, and the secondary extent should be about 20% of the primary. You can use DSNTYPE=LARGE or multiple volumes if desired. To rebuild the index, the CA Datacom/AD MUF stays up and all CA 11 started tasks must be Suspended or shut down (if TRKRMS=NO in the config file). Be certain that the STEPLIB references for the DATACOM CUSLIB and CAAXLOAD are the same as the ones referenced in your CA Datacom/AD started task.
If the DBUTLTY completes with a COND CODE 0000, either Resume or start CA 11.
If the DBUTLTY does not complete with a COND CODE 0000, contact CA Datacom Support for assistance.
Additional Information
One way to ensure that your IXX601 optimizes its space is to use the CA Datacom/AD DBUTLTY function called DEFRAG. The DBUTLTY DEFRAG function defragments or compresses the partial blocks used by the index so that space is reclaimed, and this function runs while the databases are open and in use. Because it runs in the background, users will not be affected.
To run the DEFRAG function, execute the DBUTLTY program with this input:
//SYSIN DD *
DEFRAG DBID=601
/*
You should run the DEFRAG function once a month or more frequently, following the CA 11 MANT process. For additional information on this function, please see the documentation for DEFRAG (Defragment Index) in CA Datacom/AD version 15.0 or 15.1.
Feedback
