ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

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

book

Article ID: 186436

calendar_today

Updated On:

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 [email protected] ACB OPEN ERROR
XCOMM0007E 08 5A [email protected] ACB OPEN ERROR
XCOMM0007E 08 5A [email protected] ACB OPEN ERROR

 

Cause

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

Environment

Release : 12.0

Component : CA XCOM Data Transport for z/OS

Resolution

The OPEN errors reported for ACBs [email protected], [email protected], and [email protected] 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 [email protected] 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. [email protected]). That will cause XCOMJOB to connect to the server with that APPL name.

However, it will still require minor ACBs [email protected]* in orer to make that connection. Those ACBs must be defined and ACTIV to VTAM.