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

Products

• Jobtrac

Issue/Introduction

What to do when you receive SB37 ABEND on IXX161.

Symptoms include an abend U0203 in the Jobtrac started task:

TRAC179I DB ERROR: CMD=ADDIT,TBL=PST,RET CD=08,INT RC=08                                           

TRAC172E GJTRDSTG DATABASE ERROR.  TERMINATING.                                                                         

*TRAC203C - CA-JOBTRAC SUBTASK ABEND DETECTED.                                                      

IEA995I SYMPTOM DUMP OUTPUT  863                                                                   

        USER COMPLETION CODE=0203       

Environment

Release:
Component: JOBTRC

Cause

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

Resolution

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 CAAXLOAD 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:

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

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 DISP=SHR,DSN=DATACOM.CUSLIB
//         DD DISP=SHR,DSN=DATACOM.CAAXLOAD
//CXX      DD DISP=SHR,DSN=DATACOM.CXX
//PXX      DD DISP=SHR,DSN=DATACOM.PXX
//LXX      DD DISP=SHR,DSN=DATACOM.LXX
//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, it means some Jobtrac instance or TSO user is still connected to the CA Datacom MUF. Identify and suspend or end the instance(s), ask all the Jobtrac users to logoff and then resubmit the DBUTLTY. If the DBUTLTY still fails after verifying all CA Jobtrac  instances are inactive and no one is logged on to CA Jobtrac ISPF session, contact CA Datacom Support for assistance.

Delete IXX161

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

Increase IXX161 Size and perform 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.CAAXLOAD
//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.

Resume CA Jobtrac JM (F JOBTRACn,RESUME).