SOC4-3B and the Job Hangs during Initialization with XCOM for z/OS
search cancel

SOC4-3B and the Job Hangs during Initialization with XCOM for z/OS

book

Article ID: 4276

calendar_today

Updated On:

Products

XCOM Data Transport XCOM Data Transport - z/OS

Issue/Introduction

Over the last week several Jobs with XCOM steps fail at the same point. We see the following :

SYSTEM COMPLETION CODE=0C4 REASON CODE=0000003B
TIME=04.30.32 SEQ=39751 CPU=0000 ASID=0169
PSW AT TIME OF ERROR 078D0001 A6209574 ILC 4 INTC 3B
NO ACTIVE MODULE FOUND
NAME=UNKNOWN

The XCOM Initialization step shows the following:

CA XCOM(tm) Data Transport(r) v12.0 for z/OS I N I T I A L I Z A T I O N
16105 04:30:32.3 XCOMM1401I Parameters from EXEC PARM
16105 04:30:32.3
16105 04:30:32.3 TYPE=SCHEDULE
16105 04:30:32.3 GROUP=XGROUP
16105 04:30:32.3
16105 04:30:32.3

This is where it stops - seems unable to read in the XCOM Defaults  

Environment

Common Services 14.1

Resolution

RO78180 CAMASTER SERVICES S0C4 should be applied, which has this apar as a prerequisite: RO53746 CAMASTER - S0C4-3B ABEND DURING INITIALIZATION, resolves this problem.  This is a CA Common Services fix. The fix allows XCOM to use Symbol Substitution Service correctly.