With CA Jobtrac Job Management r11, what do should you do when receiving a SB37 ABEND on IXX161?

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

Description:

What to do when you receive SB37 ABEND on IXX161.

Solution:

If IXX for database 161 is not sized appropriately, this could result in the IXX161 file for CA Jobtrac JM filling up. The IXX161 filling up can result in a SB37 abend on the IXX161 file and affect batch job processing.

To rebuild the index, the CA DATACOM/AD MUF stays up and all CA Jobtrac JM started task must be down before you can run this job. Be certain that the STEPLIB references for the CA 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.

The actions to take should the IXX161 file fills up are as follows:

  1. Suspend CA Jobtrac JM on all LPARs that share the same 161 Database (F JOBTRACn,SUSPEND).

  2. Set Access Off and execute a COMM CLOSE on DBID 161 (Using DBUTLTY). Before the IXX161 file can be expanded, database 161 must be made unavailable to CA Jobtrac JM. This is accomplished by using CA Datacom's DBUTLTY with SYSIN control cards of:
    //DBOFF    EXEC PGM=DBUTLTY,REGION=4M                 //STEPLIB  DD DSN=DATACOM.R1102.CUSLIB,DISP=SHR //             DD DSN=DATACOM.R1102.CAILIB,DISP=SHR //CXX        DD DSN=DATACOM.R1102.CXX,DISP=SHR   //PXX        DD DSN=DATACOM.R1102.PXX,DISP=SHR   //LXX        DD DSN=DATACOM.R1102.LXX,DISP=SHR   //DDSNAP   DD SYSOUT=*                                //SNAPER   DD SYSOUT=*                                //SYSOUT   DD SYSOUT=*                                //SYSPRINT DD SYSOUT=*                                //SYSPUNCH DD DUMMY                                   //SYSUDUMP DD SYSOUT=*                                //SYSIN    DD *                                         ACCESS STATUS=OFF,DBID=161,USERS=FAIL                  COMM OPTION=CLOSE,DBID=161 //
    If the DBUTLTY does not complete with a COND CODE 0000, at least one instance of CA Jobtrac JM 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 Jobtrac JM instances are inactive and no one is logged on to CA Jobtrac JM ISPF session, contact CA Datacom Support for assistance.

  3. Delete IXX161
    Once this has been done you may now delete or rename the IXX161.

  4. Increase IXX161 Size and p erform DBUTLTY RETIX.
    After the IXX161 has been deleted or renamed, you can increase the size of the IXX161 dataset, rebuild its index entries and make database 161 available for access by CA Jobtrac JM again. Sample JCL to accomplish this is shown below.
    //INITDB   EXEC PGM=DBUTLTY,REGION=4M //STEPLIB DD DISP=SHR,DSN=DATACOM.CUSLIB //            DD DISP=SHR,DSN=DATACOM.CAILIB //CXX      DD DISP=SHR,DSN=DATACOM.CXX //IXX161  DD DISP=(,CATLG),DSN=your.JOBTRAC.IXX161, //           SPACE=(CYL,(nnn,nn)),UNIT=UNIT,VOL=SER=volser //SYSIN    DD *   RESET AREA=CXX,DBID=0161                   INIT AREA=IXX,DBID=0161                    RETIX DBID=0161,SORT=300000,OPTION1='(I)'   ACCESS STATUS=WRITE,DBID=0161            // 
    If the DBUTLTY completes with a COND CODE 0000, either Resume or start CA Jobtrac.
    If the DBUTLTY does not complete with a COND CODE 0000, contact CA Datacom Support for assistance.

  5. Resume CA Jobtrac JM (F JOBTRACn,RESUME).