search cancel

CA 7 Unexpected Datacom Return Code

book

Article ID: 185696

calendar_today

Updated On:

Products

CA 7 Workload Automation

Issue/Introduction

Unexpected Datacom return code within the CA7 started task:

CAL2D044I Dump for DBTSK 02 unexpected condition captured *IEA794I SVC DUMP HAS CAPTURED: 384 DUMPID=002 REQUESTED BY JOB (CA7ONLQ ) DUMP TITLE=CA 7 Unexpected Datacom Return Code L2PDR01E DBTSK002 SCTNAME=SASSCMP2 Error: Len=E6D3َOff=(C8D2,F401) Constraint=WLHK4

Cause


Unexpected Datacom return code within the CA7 started task

Environment

Release : 12.0/12.1

Component : CA-7

Resolution

This issue happens when the database index is out of sync.

To verify if you have an index issue, please review what table has the constraint in the message within the output. Once you have the table name, run a DBUTLTY  with the following SYSIN. In this case it is WLH:

//SYSIN    DD *
VERINDEX DBID=770,OPTION=DATAINDEX,TABLE=WLH
VERINDEX DBID=770,OPTION=INDEXDATA,TABLE=WLH

Within the output of VERINDEX, you should see the following output which shows the the errors:

FINAL STATISTICS:
   INDEX MATCHES           219
   INDEX ERRORS              3
   I/O OPERATIONS            0

Once you have verified that there is an error in the index, run another DBUTLTY with the following SYSIN to address the index issue:

//SYSIN    DD *
ACCESS STATUS=UTLTY,DBID=00770,USERS=FAIL                    
COMM OPTION=CLOSE,DBID=00770                                 
INIT AREA=IXX,DBID=770                                       
RETIX DBID=770,OPTIMIZE=YES,OPTION1='(I)',SORT=99999999999,  
SORTWK=10                                                    
ACCESS STATUS=WRITE,DBID=770

Note:   CA 7 must be shutdown when running the RETIX


After running the DBUTLTY with the RETIX, you should no longer have these errors.