CA XCOM Job Abended with XCOMM0007E 08 5A XXXXXX ACB OPEN ERROR

Products

• XCOM Data Transport
• XCOM Data Transport - z/OS
• XCOM - SUPPORT

Issue/Introduction

Getting these error message connecting to the remote XCOM
XCOMM0007E 08 5A T@XCOM00 ACB OPEN ERROR
XCOMM0007E 08 5A T@XCOM01 ACB OPEN ERROR
XCOMM0007E 08 5A T@XCOM02 ACB OPEN ERROR

 

Environment

Release : 12.0

Component : CA XCOM Data Transport for z/OS

Cause

08/5A means that the ACBs are not defined to the local VTAM where the job is being run.

Resolution

The OPEN errors reported for ACBs T@XCOM00, T@XCOM01, and T@XCOM02 are 08/5A. These codes can be found in IBM VTAM documentation for ACB OPEN errors. The explanations found there are usually enough for users to be able to diagnose the underlying problem.

The names used for minor ACBs are derived from
1) the ACBNAME EXEC parm of XCOMJOB
2) the JOBACB CONFIG member parm.
You have T@XCOM specified for BOTH which is what is causing XCOMJOB to try to open minor ACBs prefixed with that name. XCOMJOB appends 2 digit numeric suffixes for individual minor ACB names (i.e. 00 through 99).

If you intended to specify the APPL name of the target server, you should use the STCAPPL EXEC parm (i.e. STCAPPL=T@XCOM). That will cause XCOMJOB to connect to the server with that APPL name.

However, it will still require minor ACBs T@XCOM* in orer to make that connection. Those ACBs must be defined and ACTIV to VTAM.