What to do when you receive SB37 ABEND on IXX601

Document ID : KB000054792
Last Modified Date : 14/02/2018
Show Technical Document Details

If the MANT task is not run on a regular basis or the IXX for database 601 is not sized appropriately, this could result in the IXX601 file for CA-11 filling up. The IXX601 filling up can result in a SB37 abend on the IXX601 file and affect batch jobs processing. The actions to take should the IXX601 file fills up are as follows:

  • Suspend CA-11 on all LPARs that share the same 601 Database.
  • Set Access Off and execute a COMM CLOSE on DBID 601 (Using DBUTLTY).
  • Delete IXX601.
  • Increase IXX601 Size.
  • Perform DBUTLTY RETIX.
  • Perform DBUTLTY Access Write.
  • Resume CA-11.

NOTE: If TRKRMS=NO is specified in the config file, CA-11 will have to be shutdown down instead of performing a SUSPEND, followed by a RESUME.

Before the IXX601 file can be expanded, database 601 must be made unavailable to CA-11. This is accomplished by using CA Datacom's DBUTLTY with SYSIN control cards of:


If the DBUTLTY 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 instance(s) 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 has been done you may now delete or rename the IXX601. After the IXX601 has been deleted or renamed, you can increase the size of the IXX601 dataset, rebuild its index entries and make database 601 available for access by CA-11 again. Sample JCL to accomplish this is shown below. Please see information in NOTE that follow JCL below prior to running this job.

//IXX601   DD DISP=(,CATLG),DSN=&CA11..IXX601,
//     SPACE=(CYL,(nnn,nn)),UNIT=&UNIT
//SYSIN    DD *
 RETIX DBID=601,SORT=999999999

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.

As a rule of thumb, the IXX601 should be as large as the larger of your JHF601 or DSN601.
To rebuild the index, the DATACOM/ AD MUF stays up and all CA-11 started task must be down before you can run this job if TRKRMS=NO is specified in your config file. Be certain that the STEPLIB references for the DATACOM CUSLIB and CAILIB and the CXX reference to the CXX dataset are the same as the ones referenced in your DATACOM/AD MUF started task.


Some other considerations to keep in mind in regards to addressing SB37 on the IXX601 are CA-11 PTF QO90849 (which was published in the 3.0 release and is included in r11.0) and the Defrag Function of the DATACOM/AD. PTF QO90849 addressed an earlier issue where DATACOM did not free unused IXX entries in a secondary key until they are referenced again. The MANT task needs to read all JEHF records at the end of the cycle to ensure the index records are freed by DATACOM. The potential IXX freed is only for JEHF records. If you have not done so already it recommended that you put on the latest service pack maintenance for CA-11 as well as this PTF. The DBUTLTY DEFRAG function defragments or compresses the IXX lower level (or DXX) of the index. It compresses the space available to the index so that space is reclaimed. The DEFRAG function can be performed by using the DATACOM DBUTLTY with the control card of DEFRAG DBID=601. It is ideal to perform the DEFRAG function at least once a month. For additional information on this function, please refer to DEFRAG chapter in the DATACOM/AD DBUTLTY Reference Guide.