Batch job generated for trace results in abend code SOC1 when executing.
Same batch job generated without trace executes normally.
Environment
Release : 8.6
Component : Gen Host Encyclopedia
Resolution
Run the application in TSO and use the test facility or possibly run it using DTF if targeting CICS.
In dump the DebugChk routine is located in the TIRCRUNC runtime DLL. This DLL is only intended to be used in CICS environments. This version of DebugChk is making CICS calls, which would explain why a S0C1 abend was received. For Batch applications, the DebugChk routine should be located in the TIRTRCTZ runtime DLL.
If the generated application or an Action Block that is generated with TP Monitor set to CICS, then search for TIRTRCE which is being pulled in from Installation Control dataset or Binder Control Cards dataset, <tsoid>.IEF.LKPRT.LINK dataset.
Check for below right syntax in batch
IMPORT CODE,'TIRTRCTZ','TIRTRCE'
Sometimes having wrong syntax like below in load modules or common Action Blocks may result in abend . IMPORT CODE,'TIRCRUNC','TIRTRCE'