CA XCOM Data Transport for z/OS Message

CA XCOM

™

Data Transport

®

for z/OS

Message Reference Guide

r11.5

This documentation and any related computer software help programs (hereinafter referred to as the

―Documentation‖) is for the end user‘s informational purposes only and is subject to change or withdrawal by CA at any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties.

Notwithstanding the foregoing, licensed users may print a reasonable number of copies of the documentation for their own internal use, and may make one copy of the related software as reasonably required for back-up and disaster recovery purposes, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the provisions of the license for the product are permitted to have access to such copies.

The right to print copies of the documentation and to make a copy of the related software is limited to the period during which the applicable license for the Product remains in full force and effect. Should the license terminate for any reason, it shall be the user‘s responsibility to certify in writing to CA that all copies and partial copies of the

Documentation have been returned to CA or destroyed.

EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY

APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION ―AS IS‖ WITHOUT WARRANTY OF ANY KIND, INCLUDING

WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE

OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS

OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION,

LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF

SUCH LOSS OR DAMAGE.

The use of any product referenced in the Documentation is governed by the end user‘s applicable license agreement.

The manufacturer of this Documentation is CA.

Provided with ―Restricted Rights.‖ Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section

252.227-7014(b)(3), as applicable, or their successors.

All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Copyright © 2010 CA. All rights reserved.

CA Product References

■ CA 7

®

Workload Automation Smart Console Option (CA 7)

■ CA ACF2

®

(CA ACF2)

■ CA NetMaster

®

File Transfer Management (CA NetMaster FTM)

■ CA Roscoe

®

(CA Roscoe)

■ CA Top Secret

®

(CA Top Secret)

■ CA XCOM™ Data Transport

®

(CA XCOM Data Transport)

Contact CA

Contact Technical Support

For your convenience, CA provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA products. At

http://ca.com/support

, you can access the following:

■ Online and telephone contact information for technical assistance and customer services

■ Information about user communities and forums

■ Product and documentation downloads

■ CA Support policies and guidelines

■ Other helpful resources appropriate for your product

Provide Feedback

If you have comments or questions about CA product documentation, you can send a message to

[email protected]

.

If you would like to provide feedback about CA product documentation, complete our short

customer survey

, which is also available on the CA Support website, found at

http://ca.com/docs

.

New Messages

The following regular messages have been added for this release:

XCOMM0055E

APF AUTHORIZATION IS REQUIRED TO TRANSFER USS FILES OR USE

SECURITY=SAF

XCOMM0463E

ERROR SETTING REMOTE USER ID: TRUSTED ACCESS DENIED

XCOMM0464E

PASSWORD MISSING. REQUIRED FOR SAF PROCESSING

XCOMM0480I

PERFORMING FAILOVER PROCESSING TO SERVER XXXXXXXX

RRDS=rrds.data.set.name

XCOMM0481E

INVALID SESSION PARMS FOR TYPE=RECOVER - MUST BE LU 6.2

XCOMM0482I

FAILOVER PROCESSING COMPLETED

XCOMM0483E

UNABLE TO PERFORM FAILOVER REQUEST. XCOMRRDS IS IN USE BY

ANOTHER TASK

XCOMM0484E

ERROR OCCURRED DURING XCOMRRDS ERASE OPERATION

XCOMM0485E

ERRORS OCCURRED PROCESSING THE XCOMRRDS DATASET

XCOMM0486I

NO ELIGIBLE TRANSFERS FOUND IN XCOMRRDS TO RECOVER

XCOMM0487E

SLOT 1 IS NOT VALID - DATASET MAY NOT BE AN XCOM RRDS -

PROCESSING TERMINATED

XCOMM0488E

REMOTE PARTNER DID NOT START THE RECOVERY TRANSACTION

PROGRAM

XCOMM0489I

REQUEST # XXXXXX REROUTED TO SERVER XXXXXXXX

XCOMM0490E

RRDS DATASET IS IN USE BY ANOTHER TASK. RRDS=xx...xx

XCOMM0491E

XXXXXXXX MACRO RECEIVED RC=XX FDBK2=XX DDNAME=

XCOMM0492E

XCOMRRDS DD STATEMENT MISSING - NO RECOVERY POSSIBLE

XCOMM0493E

XCOMRRDS DD STATEMENT DOES NOT REFERENCE A VALID VSAM RRDS

DSN=xx...xx

XCOMM0494E

NO WORKER(S) AVAILABLE TO RECEIVE REQUEST

XCOMM0495E

RRDS DATASET RELEASE=xx DOES NOT MATCH XCOMJOB RELEASE=yy

XCOMM0496E

REQUEST # XXXXXX DELETED FROM XCOM RRDS DATA SET

XCOMM0497E

XCOMJOB RELEASE=xx DOES NOT MATCH SERVER RELEASE=yy

XCOMM0498E

REMOTELY INITIATED REQUEST # XXXXXX NOT PROCESSED BY

TYPE=RECOVER

XCOMM0831E

XCOMCNTL MEMBER XXXXXXXX CONTAINS A LIST NAME LONGER THAN 8

CHARACTERS

XCOMM0832E

XCOMCNTL SUPERLIST XXXXXXXX CONTAINS DUPLICATE LIST NAME

XXXXXXXX

XCOMM0833E

INVALID LENGTH FOR UMASK= PARAMETER

XCOMM0834E

UMASK CONTAINS INVALID CHARACTERS (NOT 0-7)

XCOMM0835E

DSNTYPE= NOT BLANK AND NOT USS

XCOMM0836E

UMASK/FILEDATA/LFILEDATA IS ONLY VALID FOR USS FILES

XCOMM0837E

PARAMETER XXXXXXXXXXXXXXXX IS INVALID FOR USS FILES

XCOMM0838E

CANNOT CREATE PATH, PATHNAME EXISTS, PATH=xxxxxxx

XCOMM0839E

INVALID PATHNAME SPECIFIED – MAX OF 255 CHARACTERS EXCEEDED,

PATH=xxxxxx

XCOMM0840E

UNABLE TO GETMAIN STORAGE FOR NETWORK WORK AREA

XCOMM0841E

CANNOT CREATE USS DIRECTORY, CRUSSDIR=N SPECIFIED IN DEFAULT

OPTIONS TABLE

XCOMM0842E

CANNOT OPEN OUTPUT FILE, FILE IS NOT A REGULAR FILE, PATH=xxxxxx

XCOMM0843E

DEFAULT OPTIONS TABLE DID NOT SPECIFY THAT IBM APAR OA23740 HAS

BEEN APPLIED. THERE WILL BE NO USS SUPPORT

XCOMM0844E

NO FILES FOUND THAT MATCHED PATTERN xxxxx

XCOMM0845E

FOR MEMBER XXXXXXXX, FIRST STATEMENT NOT TYPE=LIST OR

TYPE=SUPERLIST

XCOMM0846E

INVALID 3RD PARAMETER USED ON ENABLE COMMAND

XCOMM0847E

INVALID KEYWORD PARAMETER ON DISABLE LIST COMMAND, VALID

KEYWORDS ARE ALL/FORCE/FORCEALL

XCOMM0848E

INVALID KEYWORD PARAMETER ON LIST COMMAND, VALID KEYWORD IS

ALL

XCOMM0849E

LIST XXXXXXXX CANNOT BE DISABLED, XXXXXXXX NEEDS TO BE

DISABLED, OR USE ALL/FORCE

XCOMM0850E

LIST XXXXXXXX CANNOT BE DISABLED, IS PART OF SUPERLIST XXXXXXXX,

OR USE FORCE OPERAND

XCOMM0851E

LIST XXXXXXXX CONTAINS A CIRCULAR POINTER TO XXXXXXXX

XCOMM0852E

ENABLE FAILED DUE TO PREVIOUS FAILURE

XCOMM0853E

ALLOCATION FAILED, MAXMOUNTWAIT EXCEEDED, DSN=xx

XCOMM0854E

SAF SECURITY FAILED

SAF SECURITY FAILED, USERID IS BLANK

SAF SECURITY FAILED, PERMISSION IS DENIED

SAF SECURITY FAILED, RV=xxxxxxxx, RC=xxxxxxxx, REAS=xxxxxxxx

XCOMM0855W

USS DIRTREE TRANSFER TO MVS PDS WOULD RESULT IN A DUPLICATE

MEMBER NAME, xxxxxxx

XCOMM0858E

CLOSE FAILED FOR USS FILE, CHECK ASSOCIATED MESSAGES IN THE

JOBLOG

The following Health Check messages have been added for this release:

XCMH201I

XCOM Default Table indicates that IBM APAR OA23740 has been applied.

USS transfers will be permitted.

XCMH202W

XCOM Default Table indicates that IBM APAR OA23740 has not been applied.

No USS transfers will be permitted.

XCMH501I

XCOM [Below-the-Line | Above-the-Line] Storage Summary:

XCMH502I

Currently CA XCOM Data Transport is not experiencing any shortage of

[below-the-line | above-the-line] storage.

Storage shortages within a CA XCOM Data Transport region can cause unpredictable results including, but not limited to, miscellaneous abends, file

I/O errors, and network communication errors resulting in failed data transmissions or abnormal termination of the region itself.

XCMH503W

Available storage [below-the-line | above-the-line] is less than nnn% of the total amount.

Storage utilization has exceeded nnn% of the amount available to the CA

XCOM Data Transport region. Storage shortages within a CA XCOM Data

Transport region can cause unpredictable results including, but not limited to, miscellaneous abends, file I/O errors, and network communication errors resulting in failed data transmissions or abnormal termination of the region itself.

XCMH511I

XCOM Task Summary

XCMH512I

Currently the number of active tasks in the CA XCOM Data Transport region is at nnn% of the maximum allowed by the MAXTASK parameter. This is considered normal and is providing adequate throughput.

The MAXTASK configuration parameter limits the number of active tasks that are allowed in the CA XCOM region at any given time. An exception condition is recognized when the active task level reaches the threshold defined for this health check.

When a CA XCOM Data Transport region reaches the MAXTASK limit, additional file transfer requests are delayed and retried at a later time. This may result in unacceptable processing delays for new file transfer requests.

The overhead required to manage this exception condition may degrade the overall performance of the CA XCOM Data Transport region and adversely affect its ability to complete existing file transfer requests.

XCMH513W

The total number of active tasks within the CA XCOM Data Transport region has exceeded nnn% of the configured limit as specified on the MAXTASK parameter.

The MAXTASK configuration parameter limits the number of active tasks that are allowed in the CA XCOM Data Transport region at any given time. An exception condition is recognized when the active task level reaches a certain threshold percentage of that limit. The default threshold percentage is 80%. This threshold can be modified by specifying a different percentage via the "THRESHOLD(nnn)" parameter for this particular health check.



XCMH521I

XCOM Locally Initiated Task Summary

XCMH522I

Currently the number of locally initiated active tasks in the CA XCOM Data

Transport region is at nnn% of the maximum allowed by the MAXLOC parameter. This is considered normal and is providing adequate throughput.

The MAXLOC configuration parameter limits the number of locally initiated active tasks that are allowed in the CA XCOM Data Transport region at any given time. An exception condition is recognized when the locally initiated active task level reaches the threshold defined for this health check.

When a CA XCOM Data Transport region reaches the MAXLOC limit, additional locally initiated file transfer requests are delayed and retried at a later time. This may result in unacceptable processing delays for new file transfer requests. The overhead required to manage this exception condition may degrade the overall performance of the CA XCOM Data Transport region and adversely affect its ability to complete existing File transfer requests.

XCMH523W

The total number of locally initiated active tasks within the CA XCOM Data

Transport region has exceeded nnn% of the configured limit as specified on the MAXLOC parameter.

The MAXLOC configuration parameter limits the number of locally initiated active tasks that are allowed in the CA XCOM Data Transport region at any given time. An exception condition is recognized when the locally initiated active task level reaches a certain threshold percentage of that limit. The default threshold percentage is 80%. This threshold can be modified by specifying a different percentage via the THRESHOLD(nnn) parameter for this particular health check.

When a CA XCOM Data Transport region reaches the MAXLOC limit, additional locally initiated file transfer requests are delayed and retried at a later time. This may result in unacceptable processing delays for new file transfer requests. The overhead required to manage this exception condition may degrade the overall performance of the CA XCOM Data Transport region and adversely affect its ability to complete existing file transfer requests.

XCMH531I

XCOM Remotely Initiated Task Summary

XCMH532I

Currently the number of remotely initiated active tasks in the CA XCOM Data

Transport region is at nnn% of the maximum allowed by the MAXREM parameter. This is considered normal and is providing adequate throughput.

The MAXREM configuration parameter limits the number of remotely initiated active tasks that are allowed in the CA XCOM region at any given time. An exception condition is recognized when the remotely initiated active task level reaches the threshold defined for this health check.

When a CA XCOM Data Transport region reaches the MAXREM limit, additional remotely initiated file transfer requests are delayed and retried at a later time. This may result in unacceptable processing delays for new file transfer requests. The overhead required to manage this exception condition may degrade the overall performance of the CA XCOM Data Transport region and adversely affect its ability to complete existing File transfer requests.

XCMH533W

The total number of active tasks within the CA XCOM Data Transport region has exceeded nnn% of the configured limit as specified on the MAXTASK parameter.

The MAXTASK configuration parameter limits the number of active tasks that are allowed in the CA XCOM Data Transport region at any given time. An exception condition is recognized when the active task level reaches a certain threshold percentage of that limit. The default threshold percentage is 80%. This threshold can be modified by specifying a different percentage via the THRESHOLD(nnn) parameter for this particular health check.



For more information about these messages, see the CA XCOM Data Transport

for z/OS Message Reference Guide.

Changed Messages

The following messages have been changed for this release:

0021I

DEFAULT OPTIONS TABLE SHOULD BE RE-ASSEMBLED.

GEN-LEVEL/VERSION (xxxx-xxx) DOES NOT MATCH XCOMFER (yyyy-yyy)

0040E

INVALID SECURITY PARM—XCOM TERMINATING

0053E

WWWWWWWW ABEND XXXX IN MODULE(YYYYYYYY),

OFFSET(+ZZZZZZZZ)

0132E

INVALID DATASET NAME

INVALID DATASET NAME, MULTIPLE WILDCARDS (*) NOT ALLOWED,

PATH=xxxxx

INVALID DATASET NAME, WILDCARD MUST BE IMMEDIATELY AFTER LAST /

IN PATH=xxxxx

INVALID DATASET NAME, PATH NAME TOO LONG, PATH=xxxxx

0139E

ERROR ON zzzzz FILE REQUEST

ERROR ON zzzzz FILE REQUEST, RV=xxxxxxxx, RC=xxxxxxxx,

REAS=xxxxxxxx,

DIRECTORY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

0219E

INVALID LRECL/BLKSIZE FOR XCOMREST S/B 2020 RECFM=F

0241E

ERROR OPENING FILE

ERROR OPENING FILE, RV=xxxxxxxx, RC=xxxxxxxx, REAS=xxxxxxxx,

DIRECTORY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

0288E

XCOMRRDS RECLEN INVALID—S/B xxxx BYTES

0398I

MEMBER xxxxxxxx BEING RECEIVED

FILE BEING RECEIVED = xxxxxx

0400I

xxxxxx MEMBERS RECEIVED SUCCESSFULLY

xxxxxx FILES RECEIVED SUCCESSFULLY

0460E

SUBSCRIPT CONTAINS INVALID CHARACTERS

0463E

ERROR SETTING REMOTE USER ID: TRUSTED ACCESS DENIED

0793I

TCP/IP REMOTE CONNECTION ESTABLISHED FROM IP=zzzz

0812I

SECURE TCP/IP REMOTE CONNECTION REQUESTED FROM IP=ipaddress

0813E

SECURE TCP/IP CONNECTION REQUESTED WITH DEST=**NONE**,

PORT=08045, IP=ipaddress

0814E

SECURE SOCKET HANDSHAKE COMPLETED SUCCESSFULLY IP=ipaddress

0817E

STCIP= PARAMETER MISSING—CANNOT CONNECT TO SERVER

0839E

INVALID PATHNAME SPECIFIED – MAX OF 255 CHARACTERS EXCEEDED,

PATH=xxxxxx

For more information about these messages, see the CA XCOM Data Transport

for z/OS Message Reference Guide.

Contents

Chapter 1: Introduction 17

Message Storage

...............................................................................

17

Location of the Log File

.........................................................................

18

Message Syntax

................................................................................

18

Parts of the Message

........................................................................

19

Sample Message

............................................................................

20

Conventions

................................................................................

20

Chapter 2: Messages

Chapter 3: Health Check Messages

21

301

Contents 15

Chapter 1: Introduction

This guide provides information about the messages produced by CA XCOM Data

Transport for z/OS.

This section contains the following topics:

Message Storage

(see page 17)


(see page 18)

Message Syntax

(see page 18)

Message Storage

CA XCOM Data Transport includes a comprehensive set of error messages. These messages are written to a log file. The log file serves as an audit trail of CA XCOM

Data Transport status and activity. Some messages are also displayed in the following places:

■ The user's terminal

■ The z/OS operator console

■ The session partner remote computer

Chapter 1: Introduction 17


Location of the Log File

CA XCOM Data Transport parameters that control the disposition of the log file include the following:

■ LOG

■ LOGCL (in CA XCOM Data Transport Default Options Table)

■ LOGCLASS (in XCOMJOB PARM parameters)

■ LOGDEST

For a description of each of these parameters, see the following:

■ For more information about setting installation-wide parameters, see the section CA XCOM Data Transport Default Options Table Parameters in the chapter ―Configuration Parameters‖ in the CA XCOM Data Transport for z/OS

Administration Guide.

■ For more information about single transfer overrides, see the section PARM

Parameters in the chapter ―The Batch Interface‖ in the CA XCOM Data

Transport for z/OS User Guide.

■

By default, the XCOMXFER and XCOMJOB modules write a log to SYSOUT A.

For file transfers using the Menu Interface or a TSO CLIST, no log is written, because all messages are written to the user's terminal.

Message Syntax

The following shows the CA XCOM Data Transport message syntax:

XCOM<system identifier><message no><message type> <message text>

18 Message Reference Guide

Message Syntax

Parts of the Message

The parts of a CA XCOM Data Transport message are as follows:

# (position 0)

If the message number is preceded by #, the transfer can be retried.

XCOM (positions 1 to 4; alphabetic)

Displays the first four characters of a CA XCOM Data Transport message.

system identifier (position 5; alphabetic)

Specifies the CA XCOM Data Transport system that generated the message.

Valid values include the following:

■

C—Microsoft PC-DOS and MS-DOS, and IBM OS/2

■

D—Digital Equipment Corp. VAX/VMS, OpenVMS Alpha, and OpenVMS

VAX

■

E—IBM z/VSE

■

G—Data General AOS/VS

■

K—IBM CICS

■

M—IBM z/OS

■

N—Windows NT

■

R—Netware

■

S—IBM iSeries

■

T—Tandem

■

U—UNIX

■

V—IBM zVM

■

W—Windows

■

8—Stratus Computer and IBM System/88

message no (positions 6 to 9; numeric)

Specifies the message number.

message type (position 10; alphabetic)

Indicates the message type, as follows:

■

I—An informational message. No action is required on the part of the user.

■

E—An error message. Usually some action is necessary to correct the problem or to determine the cause.

message text (position 11; alphanumeric)

Displays the message text.

Chapter 1: Introduction 19

Message Syntax

Sample Message

The following is a sample CA XCOM Data Transport message:

XCOMM0001I XCOMXFER PROGRAM NOW ENDING

Conventions

The chapter ―Messages‖ lists messages that CA XCOM Data Transport for z/OS can return in response to transfer requests, with reasons and recommended user actions, where appropriate. The list of messages uses the following conventions:

■ The prefix XCOMM has been deleted from each message ID, and the type identifier (I or E) has been appended to each ID (for example, error message

XCOMM0413 is listed as 0413E).

■

The messages are listed in numerical order.


Chapter 2: Messages

This chapter contains CA XCOM Data Transport messages.

0000E

MESSAGE TABLE NOT LOADED xxxxxxxx PROGRAM LOAD ERROR yyyyyyyy zzzzzzzz ON MESSAGE

TABLE—XCOM TERMINATING

Reason:

CA XCOM Data Transport could not load a required module. In the first message,

CA XCOM Data Transport could not load or find XCOMMSGT, the message table.

In the second message, CA XCOM Data Transport could not load the module

xxxxxxxx.

Action:

Check that the CA XCOM Data Transport loadlib is in the STEPLIB, JOBLIB, or

LINKLIST libraries. See the chapter ―Installing Your Product‖ in the Installation

Guide. If you are using multiple CA XCOM Data Transport libraries, make sure they all have the same level of APF authorization.

If the later format of the message is displayed, make sure the module xxxxxxxx is in one of the libraries stated above with the same level of authorization, if you are using a combination of STEPLIB, JOBLIB, and LINKLIST.

0001I

XCOM SERVER NOW TERMINATING

Reason:

The CA XCOM Data Transport server has ended.

Action:

None

Chapter 2: Messages 21

Message Syntax

0002I

PARM FIELD MISSING OR NULL—TAKING ALL VALUES FROM DEFAULT

OPTIONS TABLE

Reason:

Either no PARM field or a null values PARM field was specified on the EXEC statement. Default parameter values will be taken from the Default Options

Table.

Action:

None

0004I

xxxxxxxx

Reason:

Displays one of the parameters specified in the PARM field of the EXEC statement.

Action:

None

0005E

PARM LENGTH GREATER THAN 63 BYTES

Reason:

The maximum length of all parameters that can be specified in the EXEC statement PARM field is 63 bytes. The PARM field has exceeded this length.

Action:

Shorten the specified PARM field and rerun the job.

0006E

INVALID KEYWORD PARAMETER

Reason:

The keyword parameter identified by this message is incorrectly specified; for example, it might have been misspelled.

Action:

Correct the specification of the erroneous parameter.


0007E

0008I

Message Syntax

xx yy zzzzzzzz ACB OPEN ERROR

Reason:

Before a program can begin communicating with other systems, it must first issue an OPEN macro, using a VTAM control block called an ACB. The ACB identifies which VTAM Application ID you will use. The APPLID is displayed in the

zzzzzzzz operand of this message. The xx operand is the return code from the

OPEN macro; yy is the ACB error flag (field ACBERFLG in the ACB).

Action:

Contact your systems programming staff to resolve this problem. Check that you are using the correct APPLID ensuring that it has been spelled correctly. Also, check that its major node has been activated and the status of the APPLID prior to running this job is connectable. The IBM documentation describes the error codes provided by the xx and yy operands of the message in the text describing the OPEN macro.

xxxxxxxx ACB OPENED SUCCESSFULLY

Reason:

CA XCOM Data Transport issued an OPEN macro for the VTAM ACB identified by message operand xxxxxxxx. All return codes indicate the normal completion of this task.

Action:

None


Message Syntax

0009I

COMPILED UNDER VTAM Vx Rx Mx—EXECUTING VTAM UNDER Vy Ry My

TO COMPONENT_ID

Reason:

This message identifies the ACF/VTAM version (Vx), release (Rx), and modification (Mx) numbers under which the copy of CA XCOM Data Transport you are using was compiled. It provides the same information (Vy Ry My) about the level of ACF/VTAM under which CA XCOM Data Transport is currently executing. COMPONENT_ID may be displayed on some systems. This contains internal identifiers for the ACF/VTAM product under which CA XCOM Data

Transport is executing.

Action:

None

0010I

COMPILED UNDER VTAM Vx Rx Mx—EXECUTING UNDER UNKNOWN TO

COMPONENT_ID

Reason:

This message identifies the ACF/VTAM version (Vx), release (Rx), and modification (Mx) numbers under which the copy of CA XCOM Data Transport you are using was compiled. CA XCOM Data Transport was unable to determine the level of ACF/VTAM under which it is currently executing.

Action:

None

0011E

VTAM SHOWCB ERROR—XCOM ABENDING

Reason:

An error occurred on a SHOWCB macro required for CA XCOM Data Transport execution. This may indicate an incompatible release of VTAM. CA XCOM Data

Transport requests a dump and terminates with a U111 completion code.

Action:

Contact CA Technical Support.


0012I

00131

0014E

Message Syntax

xxxxxxxx COMMAND PROCESSING FAILED/SUCCESSFUL

Reason:

This message is issued at the end of processing for an operator console command. It indicates whether command processing failed or was successful.

xxxxxxxx is the name of the operator command.

Action:

If command processing has failed, this message will be preceded by one or more messages indicating the cause of the failure. Examine these messages and take appropriate Action.

xxxxxxxxxxxxx

Reason:

A console operator entered a z/OS MODIFY command, such as F XCOM. The command is identified by the message operand xxxxxxxxxxxxx.

Action:

None

xx yy zzzzzzzz ACB CLOSE ERROR

Reason:

During shutdown CA XCOM Data Transport unsuccessfully attempted to close its

ACB. The message operand zzzzzzzz identifies the APPLID that was to be closed.

The operand xx is the CLOSE return code; yy is the ACB error flag (field

ACBERFLG in the ACB). The IBM documentation provides the meanings of these codes.

Note: The ACB will be closed automatically when the job ends.

Action:

None


Message Syntax

0015I

xxxxxxxx ACB CLOSED SUCCESSFULLY

Reason:

During shutdown CA XCOM Data Transport successfully closed its ACB. The message operand xxxxxxxx identifies the APPLID that was closed.

Action:

None

0016I

NO SESSIONS TO DISPLAY

Reason:

The console operator entered a DISPLAY command, requesting that all active

LU-to-LU sessions (even if currently idle) be displayed (see the chapter

―Operation and Control‖ in the CA XCOM Data Transport for z/OS User Guide).

There were no active sessions or the user/console was not authorized to display information about those sessions that were active.

Action:

None

0017I

xxxxxxxx nnnnnnnn yyyyyyyy zzzzzzzz cccccccc

Reason:

This message is displayed in response to a DISPLAY command (see the chapter

―Operation and Control‖ in the CA XCOM Data Transport for z/OS User Guide).

The message operand xxxxxxxx indicates the local LU name or IPNAME or IP address. nnnnnnnn indicates node name (that is, XCOMMODE). yyyyyyyy indicates PARALLEL/SINGLE SESSIONS. zzzzzzzz indicates WINNER/LOSER (if parallel session). cccccccc indicates the status of the session. The status can be

INACTIVE, SEND, RECEIVE, ATTACH-L, or ATTACH-R. ATTACH indicates whether the conversation was initiated locally (-L) or remotely (-R). If the status is SEND or RECEIVE, a second line indicates the request number and byte count that CA

XCOM Data Transport is currently processing.

Action:

None


0018E

0019E

0020E

Message Syntax

DEFAULT OPTIONS TABLE CREATED WITH DIFFERENT VERSION OF

XCOM

Reason:

CA XCOM Data Transport issues this message at initialization when it finds that the Default Options Table was created with a different version of CA XCOM Data

Transport. CA XCOM Data Transport terminates execution.

Action:

Recreate the Default Options Table before restarting CA XCOM Data Transport.

xxxxxxxx PROGRAM LOAD ERROR yyyyyyyy zzzzzzzz

Reason:

An error occurred loading program xxxxxxxx. Return codes yyyyyyyy and

zzzzzzzz are, respectively, the LOAD Abend code and the LOAD Abend reason code.

Action:

Check that the CA XCOM Data Transport load library is in the STEPLIB, JOBLIB, or LINKLIST libraries (see the chapter ―Installing Your Product‖ in the CA XCOM

Data Transport for z/OS Installation Guide) and ensure that you have allocated enough storage for CA XCOM Data Transport.

REQUIRED PROGRAM NOT LOADED—XCOM TERMINATING

Reason:

A program that was required by CA XCOM Data Transport was not loaded; execution terminates. Message 0019E will describe the error codes encountered loading the program.

Action:

Resolve the errors associated with loading the program and rerun the job.


Message Syntax

0021I

DEFAULT OPTIONS TABLE SHOULD BE RE-ASSEMBLED.

GEN-LEVEL/VERSION (xxxx-xxx) DOES NOT MATCH XCOMFER

(yyyy-yyy)

Reason:

The default options table and the version of CA XCOM Data Transport do not match. xxxx-xxx represents the version of CA XCOM Data Transport macro libraries used to assemble the default table. yyyy-yyy is the version of the CA

XCOM Data Transport server. Both xxxx-xxx and yyyy-yyy indicate the service pack sequence number within the service pack.

Action:

Reassemble the default options table with the correct macro libraries. For more information, see the CA XCOM Data Transport for z/OS Administration Guide.

Note: This is an informational message and should be ignored if it is reporting a service pack mismatch.

0023E

UNABLE TO ALLOCATE SNAP DATASET, RETURN CODE=xxxxxxxx

Reason:

The user issued a SNAP or DUMP command. In attempting to satisfy the request,

CA XCOM Data Transport was unable to allocate a SNAP data set. xxxxxxxx contains the error and information codes from dynamic allocation.

Action:

Check the DUMPCL parameter specified either in the PARM field of the EXEC statement or the CA XCOM Data Transport Default Options Table (see the chapter ―The Batch Interface‖ in the CA XCOM Data Transport for z/OS User

Guide or the chapter ―Configuration Parameters‖ in the CA XCOM Data Transport

for z/OS Administration Guide).


0024E

0025I

0026I

Message Syntax

UNABLE TO OPEN SNAP DATASET

Reason:

The user issued a SNAP or DUMP command. In attempting to satisfy the request,

CA XCOM Data Transport encountered an error attempting to open the SNAP data set.

Action:


xxxxxxxx SNAP DUMP PRODUCED

Reason:

A snap dump was produced as the result of a DUMP command (see the chapter

―Operation and Control‖ in the CA XCOM Data Transport for z/OS User Guide).

The dump will be written to the class specified in the DUMPCL operand of the

Default Table. xxxxxxxx is the LU name requested in the DUMP command.

Action:

None

REGION SNAP DUMP PRODUCED

Reason:

A region snap dump was produced as a result of a SNAP command (see the chapter ―Operation and Control‖ in the CA XCOM Data Transport for z/OS User

Guide). The dump will be written to the class specified in the DUMPCL operand of the Default Options Table.

Action:

None


Message Syntax

0027I

ESTAE ROUTINE HAS BEEN ESTABLISHED

Reason:

CA XCOM Data Transport has asked the operating system to protect it from abnormal termination (that is, abending) unless a catastrophic error occurs. The operating system has consented.

Action:

None

0028E

xxxxxxxx ABEND yyy DETECTED—XCOM RECOVERING

Reason:

A file transfer task associated with LU xxxxxxxx has abended with abend code

yyy. The task will subsequently end, but CA XCOM Data Transport will remain active.

Action:

Look up the code yyy in the IBM documentation.

0029E

ABEND xxx DETECTED—XCOM UNABLE TO RECOVER

Reason:

An unrecoverable abend whose code is given by xxx was detected.

Action:

Obtain the SYSLOG and XCOM log and contact CA Technical Support.

0030E

ABEND xxx W/O SDWA—XCOM UNABLE TO RECOVER

Reason:

The ESTAE abend exit whose code is indicated by xxx was invoked without an

SDWA. CA XCOM Data Transport will not recover from this error.

Action:

Obtain the SYSLOG and XCOM log and contact CA Technical Support.


0031E

0032I

0033E

0034E

Message Syntax

INVALID RETURN CODE xx FROM ESTAE—XCOM ABENDING

Reason:

The ESTAE routine was invoked but z/OS returned an error code xx. CA XCOM

Data Transport will not run without the ESTAE exit. CA XCOM Data Transport requests a dump and terminates with a U111 completion code.

Action:


yyyyyyyy COMMAND EXECUTED for xxxxxxxx

Reason:

Command yyyyyyyy was executed for LU xxxxxxxx.

Action:

None

yyyyyyyy FAILED—COULD NOT FIND xxxxxxxx

Reason:

Command yyyyyyyy was issued for LU xxxxxxxx, but LU xxxxxxxx could not be found.

Action:

Determine the correct LU name and re-enter the command.

xxxxxxxx ACTIVATE FAILED—LU ALREADY ACTIVE

Reason:

A console operator entered an ACTIVATE command, requesting CA XCOM Data

Transport to bind a session to a particular LU. However, there was a session already bound.

Action:

None


Message Syntax

0035I

xxxxxxxx ACTIVATE PROCEDURE STARTED

Reason:

A console operator an ACTIVATE command requesting that CA XCOM Data

Transport bind a session to a particular LU. CA XCOM Data Transport is about to make a VTAM SIMLOGON request to obtain that LU-to-LU session.

Action:

None

0036E

ERROR ATTACHING PSO SUBTASK

Reason:

CA XCOM Data Transport was using the z/OS ATTACH macro to attach a subtask for Process SYSOUT (PSO) requests (see the chapter ―The Remote Spooling

Feature (Process SYSOUT)‖ in the CA XCOM Data Transport for z/OS User

Guide). An error occurred while attaching the PSO task. Therefore, CA XCOM

Data Transport will run without PSO support.

Action:


0037I

PSO SUBTASK ATTACHED SUCCESSFULLY

Reason:

This message indicates that the CA XCOM Data Transport PSO subtask was successfully attached.

Action:

None


0038I

0039E

0040E

Message Syntax

PSO SUBTASK DETACHED SUCCESSFULLY

Reason:

This message indicates that the CA XCOM Data Transport PSO subtask was detached successfully. This message is displayed when CA XCOM Data Transport is brought down.

Action:

None

UNABLE TO ATTACH PSO SUBTASK

Reason:

CA XCOM Data Transport was unable to attach the PSO interface subtask because the program XCOMPSOI was not found.

Action:

Ensure that program XCOMPSOI is in the CA XCOM Data Transport STEPLIB or

JOBLIB, or in a LINKLIST library (see the chapter ―Installing Your Product‖ in the

CA XCOM Data Transport for z/OS Installation Guide).

INVALID SECURITY PARM—XCOM TERMINATING

Reason:

A SECURITY parameter value other than ACF2, TOPS, RACF, or SAF was specified. To ensure security, CA XCOM Data Transport will not come up when an invalid SECURITY parameter is specified.

Action:

Correct the SECURITY parameter and rerun the job.


Message Syntax

0041E

INVALID OPERATOR COMMAND RECEIVED

Reason:

A console operator entered a z/OS MODIFY command for CA XCOM Data

Transport but did not specify a valid CA XCOM Data Transport command.

Action:

Check the syntax and the spelling of the operator command (see the chapter

―Operation and Control‖ in the CA XCOM Data Transport for z/OS User Guide) and re-enter the command.

0042E

SECURITY MODULE NOT FOUND—XCOM TERMINATING

Reason:

CA XCOM Data Transport external security support was requested, but the required security module was not loaded properly. CA XCOM Data Transport processing will end.

Action:

Check that the proper CA XCOM Data Transport library is in the STEPLIB, JOBLIB, or LINKLIB libraries, and ensure that adequate virtual storage has been allocated.

0043E

xxxxxxxx LU NOTIFY NOT SUPPORTED FOR TYPE=EXECUTE

Reason:

LU notify is not supported for TYPE=EXECUTE transfers.

Action:

Schedule the request to a CA XCOM Data Transport server.


0044E

0046E

0047E

Message Syntax

xxxxxxxx CICS NOTIFY NOT SUPPORTED FOR TYPE=EXECUTE

Reason:

CICS notify is not supported for TYPE=EXECUTE transfers.

Action:

Schedule the request to a CA XCOM Data Transport server.

XTC PARAMETERS NOT SUPPORTED FOR TYPE=EXECUTE

Reason:

XTC parameters are not supported for TYPE=EXECUTE transfers.

Action:

Schedule the request to a CA XCOM Data Transport server if you want to use XTC parameters.

xxxxxxxx PARM IN ERROR—USING VALUE FROM DEFAULT OPTIONS

TABLE

Reason:

Parameter xxxxxxxx defined in the PARM field of the EXEC statement for

XCOMJOB or the CA XCOM Data Transport server is invalid. Execution continues with CA XCOM Data Transport using the parameter value specified in the Default

Options Table.

Action:

Review the description of parameter xxxxxxxx, which can be found in the chapter ―The Batch Interface‖ in the CA XCOM Data Transport for z/OS User

Guide.


Message Syntax

0048I

PREVIOUS MESSAGE NOT LOGGED—LOG IN USE

Reason:

Only a single request can be logged at any one time. Because CA XCOM Data

Transport can multi-task, sometimes a message will not be logged because the log file is busy.

Action:

None

0049E

XCOM IS NOT APF AUTHORIZED—SOME FUNCTIONS WILL NOT BE

AVAILABLE

Reason:

The CA XCOM Data Transport address space is not authorized. While this does not mean that CA XCOM Data Transport cannot be used, some functions will be unavailable (see the chapter ―Installing Your Product‖ in the CA XCOM Data

Transport for z/OS Installation Guide).

Action:

If you require any of these functions, CA XCOM Data Transport must be authorized.

0050E

xxxxxxxx NOT NOTIFIED—XCOM IS NOT APF AUTHORIZED

Reason:

The TSO user xxxxxxxx could not be sent a message that a file transfer completed because the CA XCOM Data Transport address space is not authorized

(see the chapter ―Installing Your Product‖ in the CA XCOM Data Transport for

z/OS Installation Guide).

Note: This situation will not abort the file transfer.

Action:

CA XCOM Data Transport must be authorized if you require this function.


0051E

0052E

0053E

Message Syntax

XCF FACILITY NOT STARTED—XCOM IS NOT APF AUTHORIZED

Reason:

All libraries must be APF authorized in order to use the IBM Coupling Facility. The

XCOMPLEX requires the IBM Coupling Facility. XCOMPLEX servers will be started but without XCF facility.

Action:

Make sure all libraries are APF authorized.

APF AUTHORIZATION REQUIRED FOR SECURITY—XCOM TERMINATING

Reason:

Because the CA XCOM Data Transport address space is not authorized, the CA

XCOM Data Transport security interface to the host computer was not available.

For this reason, CA XCOM Data Transport ended.

Action:

If you require the use of its security interface, CA XCOM Data Transport must be authorized.

WWWWWWWW ABEND XXXX IN MODULE(YYYYYYYY),

OFFSET(+ZZZZZZZZ)

Reason:

A task in the CA XCOM Data Transport address space has terminated abnormally. This message identifies the affected task, the abnormal termination code, and the module and location where the termination occurred.

Action:

Obtain the SYSLOG and XCOMLOG, and the system dump (if available), and contact CA Technical Support.


Message Syntax

0055E

APF AUTHORIZATION IS REQUIRED TO TRANSFER USS FILES OR USE

SECURITY=SAF

Reason:

Security calls to validate access to USS data sets must be made using SAF.

Making SAF interface calls in these cases requires APF authorization.

Action:

Make the necessary changes to the processing environment so that the

XCOMJOB program will run with APF authorization.

0056I

CA XCOM(R) r.r (GEN LEVEL mmmm SP9) IS UP AND ACCEPTING

LOGONS ON CPU nnnn SERIAL # yyyyyy IN zz-BIT MODE MVS SPx.x.x

Reason:

The CA XCOM Data Transport address space has been successfully initialized and is able to accept session requests. In addition to the CA XCOM Data Transport version, generation level, and service pack numbers (r.r, mmmm, and 9 respectively), the message provides a CPU ID (nnnn), CPU serial number

(yyyyyy), addressing mode (zz), and the version (SPx.x.x) of the z/OS operating system.

Action:

None

0057E

ABEND yyy DETECTED IN PSO SUBTASK—XCOM RECOVERING

Reason:

The CA XCOM Data Transport Process SYSOUT subtask has abended with abend code yyy. It has recovered from this abend and will continue processing. The JES destination or writer for which this error was received will be retried at the next error interval.

Action:



0058E

0059E

0060I

Message Syntax

ABEND yyy DETECTED IN PSO SUBTASK—XCOM UNABLE TO RECOVER

Reason:

The CA XCOM Data Transport Process SYSOUT subtask has abended with abend code yyy. It is unable to recover from this abend and will end. The CA XCOM Data

Transport server will continue working without the Process SYSOUT Interface.

Action:


ABEND yyy W/O SDWA DETECTED IN PSO SUBTASK—XCOM UNABLE TO

RECOVER

Reason:

The CA XCOM Data Transport Process SYSOUT subtask has abended with abend code yyy and was unable to recover from the abend because z/OS did not pass an SDWA in the abend exit routine. The CA XCOM Data Transport server will continue operating without the Process SYSOUT interface.

Action:


CURRENT RELEASE IS k.k—GENERATION LEVEL mmmm

Reason:

k.k and mmmm indicate the release and generation levels, respectively, of the

CA XCOM Data Transport software that is currently running. This message is issued in response to the VER command.

Action:

None


Message Syntax

0061E

CANNOT OVERRIDE SECURITY TO SECURITY= NONE

Reason:

If the SECUR parameter from the Default Options Table has a value other than

NONE, then it cannot be overridden to denote NONE for a specific file transfer.

Action:

Eliminate the invalid SECUR override and resubmit the file transfer request.

0062E

xxxxxxxx TRANSFER REQUEST NOT ACTIVE

Reason:

A TERMINATE command was issued, but LU xxxxxxxx had no currently active file transfer.

Action:

The TERMINATE command only applies to active transfers. Verify that the correct

LU was specified. If the transfer request is pending, use the DELETE command to purge it (see the chapter "Operation and Control" in the CA XCOM Data Transport

for z/OS User Guide‖).

0063E

UNABLE TO ALLOCATE TRACE DATA SET, RETURN CODE=xxxxxxxx

Reason:

The user has attempted to turn on the CA XCOM Data Transport trace function.

However, the SVC99 request to dynamically allocate the trace SYSOUT data set has failed with an error/information code combination of xxxxxxxx.

Action:

See the IBM documentation for a description of the SVC99 reason code. Ensure that the SYSOUT file's class defined through the DUMPCL parameter of the

Default Options Table is valid (see the chapter ―Configuring and Customizing

Your Product‖ in the CA XCOM Data Transport for z/OS Administration Guide).


0064E

0065E

0066I

Message Syntax

UNABLE TO OPEN TRACE DATA SET

Reason:

CA XCOM Data Transport has attempted to open a trace SYSOUT data set to process a trace request, but the OPEN failed. The trace request is denied.

Action:


xxxxxxxx TRACE ALREADY ACTIVE FOR LU

Reason:

A TRACE command has been entered for LU xxxxxxxx, but this LU is neither currently in session, nor defined in the Destination Table (see the chapter

―Configuring and Customizing Your Product‖ in the CA XCOM Data Transport for

z/OS Administration Guide). The trace request is denied.

Action:

If the specified LU is not in the Destination Table, a trace can only be started for it after a session has been initiated.

xxxxxxxx TRACE COMPLETED SUCCESSFULLY

Reason:

The TRACE command entered for LU xxxxxxxx has been successfully processed.

To complete the trace request, enter a NOTRACE command.

Action:

None


Message Syntax

0067E

TRACE FACILITY NOT CURRENTLY ACTIVE

Reason:

A NOTRACE command has been entered, but a trace is not currently active in the system.

Action:

No action is required if a trace is not in progress. If a trace is in progress, reissue the command, specifying the correct LU.

0068I

TRACE DATASET CLOSED SUCCESSFULLY

Reason:

As a result of a NOTRACE command, a trace function has been successfully terminated. The trace will be sent to the SYSOUT class defined by the DUMPCL parameter.

Action:

None

0069E

MAXIMUM NUMBER OF LUs ALREADY BEING TRACED

Reason:

CA XCOM Data Transport supports a maximum of 8 concurrently active TRACE requests. This number was exceeded.

Action:

Wait until one of the currently active requests has been processed and stopped by a NOTRACE command, then enter the new trace request. Or you can use the

* option (see the chapter ―Operation and Control‖ in the CA XCOM Data

Transport for z/OS User Guide) to trace all LUs currently communicating with this computer unless 8 TRACE requests are already active.


0070E

0071I

0072E

Message Syntax

xxxxxxxx TRACE NOT ACTIVE FOR LU

Reason:

The user entered a NOTRACE command but CA XCOM Data Transport determined that a trace request was not active for LU xxxxxxxx.

Action:

If you want to stop all TRACE requests, enter the NOTRACE command without specifying an LU name.

XCOMJOB NOW TERMINATING

Reason:

The program that invoked a file transfer is terminating.

Action:

None

xxxxxxxx MAXIMUM NUMBER OF ACBs IN USE—XCOMJOB

TERMINATING

Reason:

The XCOMJOB program can use a maximum of 99 APPLIDs concurrently. CA

XCOM Data Transport has determined that the maximum number is currently in use.

Action:

Try again after some jobs have completed, or change the transfer to a

TYPE=SCHEDULE request.


Message Syntax

0073E

xxxxxxxx ERROR RECEIVED DURING PROGRAM DELETE

Reason:

The XCOMJOB program deletes all programs before ending. An error occurred deleting program xxxxxxxx.

Action:

If this causes other problems, contact CA Technical Support.

0075E

xxxxxxxx LU NAME NOT FOUND IN XCOMDEST TABLE

Reason:

A request was made for a transmission that requires that the partner LU be associated with a DEST parameter in the Destination Table (see the chapter


z/OS Administration Guide).

Action:

Add a DEST parameter for this LU to the Destination Table.

0076E

xxxxxxxx PARAMETER INVALID-USING VALUE FROM DEFAULT

OPTIONS TABLE

Reason:

An invalid parameter, xxxxxxxx, was specified on the EXEC statement PARM field for XCOMJOB or the CA XCOM Data Transport server.

Action:

See the chapter ―The Batch Interface‖ in the CA XCOM Data Transport for z/OS

User Guide for a description of the PARM keyword parameters.


0077E

0078E

Message Syntax

INVALID TIMEOUT PARM—USING 30-SECOND DEFAULT

Reason:

For a Batch Interface, TYPE=EXECUTE (see the chapter ―The Batch Interface‖ in the CA XCOM Data Transport for z/OS User Guide), or a TSO Execute immediately file transfer request (see the chapter ―The Menu Interface

(TSO/ISPF Panels)‖ in the CA XCOM Data Transport for z/OS User Guide), a timeout value was specified that was not in the legal range of 0-99999 seconds.

Therefore, CA XCOM Data Transport will ignore the value you specified and substitute the default value defined by the TIMEOUT parameter of the Default

Options Table (see the chapter ―Configuring and Customizing Your Product‖ in the CA XCOM Data Transport for z/OS Administration Guide).

Action:

If the default value is not acceptable, respecify a legal value. Be careful not to specify the letter ―l‖ instead of the number 1 or the letter ―O‖ for the number 0.

llllllll ----> rrrrrrrr TIMER EXPIRED—TRANSFER TERMINATED

Reason:

CA XCOM Data Transport issued a VTAM command (for example, SIMLOGON,

RECEIVE, SEND). However, before the command could complete, the prevailing

TIMEOUT parameter value had already been exceeded. CA XCOM Data Transport times out and the transfer terminates. llllllll represents the name of a local LU and rrrrrrrr represents the name of a remote LU. This message is issued only for

TYPE=EXECUTE transfers.

Action:

You have three options: (1) queue this file transfer and rerun the operation;

(2) determine why the partner LU is unavailable and take appropriate measures;

(3) increase the timeout value and rerun the operation.


Message Syntax

0081E

TYPE PARM INVALID—MUST BE EXECUTE, SCHEDULE, OR INQUIRE

Reason:

In your EXEC PARM statement you have specified a value for the TYPE parameter that is neither EXECUTE, SCHEDULE, nor INQUIRE (see the chapter ―The Batch

Interface‖ in the CA XCOM Data Transport for z/OS User Guide).

Action:

Specify a valid value and rerun the operation.

0082E

INVALID LU6.2 COMMAND—INTERNAL ERROR

Reason:

The CA XCOM Data Transport LU6.2 interface has detected an invalid LU6.2 command.

Action:

If this problem is reproducible, take a CA XCOM Data Transport trace and contact

CA Technical Support.

0083E

BIND ERROR IN CINIT—SESSION NOT ESTABLISHED

Reason:

CA XCOM Data Transport has detected an error in the BIND passed by VTAM in the CINIT. CA XCOM Data Transport terminates the pending session.

Action:

Take a CA XCOM Data Transport or VTAM trace to determine the BIND parameters of the session and ensure that the MODETAB/LOGMODE entries are valid for both CA XCOM Data Transport and its partner LU.


0084E

0085I

0086I

Message Syntax

BAD BIND RECEIVED FROM SLU—SESSION NOT ESTABLISHED

Reason:

CA XCOM Data Transport has detected an invalid BIND received from its partner

(secondary) logical unit. The session is terminated.

Action:

Ensure that the MODETAB/DLOGMOD parameters are defined properly for CA

XCOM Data Transport and the partner LU. If necessary, take a VTAM trace to determine the BIND parameters used.

SEND RUSIZE < 256 OR > 65536—DEFAULTING TO 512

Reason:

While negotiating a BIND, CA XCOM Data Transport has detected that the send

RUSIZE is either less than 256 or greater than 65536. CA XCOM Data Transport changes the RUSIZE to its default value of 512. The session is then established with the default value of 512.

Action:

None

RECEIVE RUSIZE < 256 OR > 65536—DEFAULTING TO 512

Reason:

While negotiating a BIND, CA XCOM Data Transport has detected that the receive RUSIZE is either less than 256 or greater than 65536. CA XCOM Data

Transport changes the RUSIZE to its default value of 512. The session is then established with the default value of 512.

Action:

None


Message Syntax

0091E

INVALID BIND RECEIVED FROM PLU—SESSION NOT ESTABLISHED

Reason:

CA XCOM Data Transport, acting as a Secondary Logical Unit (SLU), has received a BIND request from the Primary Logical Unit (PLU), but the data in the BIND is invalid. The pending session will be terminated.

Action:

Ensure that the LU definition has the proper MODETAB/DLOGMOD definitions.

Take a CA XCOM Data Transport trace and contact CA Technical Support.

0092E

BIND RECEIVED FROM PLU NOT LU6—SESSION NOT ESTABLISHED

Reason:

CA XCOM Data Transport, acting as a Secondary Logical Unit (SLU) has received a BIND request from the Primary Logical Unit (PLU), but the BIND is not an LU6

BIND. Because only LU6 BINDs are accepted when operating as an SLU, the pending session is terminated.

Action:

Ensure that all CA XCOM Data Transport APPL definitions are defined with the proper MODETAB/DLOGMOD definitions. If this error persists, take a CA XCOM

Data Transport trace and contact CA Technical Support.

0093E

ERROR ACTIVATING SESSION—SESSION NOT ESTABLISHED

Reason:

An error has occurred while establishing a session.

Action:

Another message is normally displayed with this message. Check this message to determine the actual cause of the failure.


0094E

0095E

0096E

Message Syntax

INVALID STATE FOR xxxxxxxx COMMAND

Reason:

CA XCOM Data Transport has detected a program state check while processing a request. The logical unit is put into an error state until the next error interval expires.

Action:

If this problem can be reproduced, take a CA XCOM Data Transport trace and contact CA Technical Support.

INVALID DATA RECEIVED ON ALLOCATE—REQUEST TERMINATED

Reason:

CA XCOM Data Transport has attempted to allocate a conversation with its session partner and is expecting its session partner to confirm the request. CA

XCOM Data Transport, however, has received unexpected data in response to its allocate request. The logical unit is put into an error state until the next error interval expires. The session is ended.

Action:


xxxxxxxx REQUEST ENDED DUE TO VTAM ERROR

Reason:

A VTAM request (such as ALLOCATE, CNOS, SEND or RECEIVE) has failed due to an error. xxxxxxxx defines the type of request that failed. The session is ended and the request is put into an error state. An accompanying message, normally

Message 0186E, provides more detailed information on the actual cause of the error.

Action:

Correct VTAM error and re-attempt transfer.


Message Syntax

0097E

INVALID DATA RECEIVED ON SEND REQUEST

Reason:

CA XCOM Data Transport has detected invalid incoming data prior to executing a

SEND request. The session will be terminated and the request marked as in error.

Action:


0098E

INVALID DATA RECEIVED—EXPECTING FMH7

Reason:

CA XCOM Data Transport has received a VTAM return code 04 with sense code

0846. The LU protocol has defined that only an FMH7 can follow, but the partner

LU sent something other than an FMH7. The session will be terminated and the request marked as in error.

Action:


0099E

SEND DATA LENGTH > 32768

Reason:

A CA XCOM Data Transport interface program has detected a logical record length greater than 32768 bytes on a SEND operation. Although the LU protocol supports this, CA XCOM Data Transport does not. The session will be terminated and the request marked as in error.

Action:



0100E

0101E

0105E

Message Syntax

LU6 RECORD RECEIVED DOES NOT CONFORM TO GDS STANDARDS

Reason:

A CA XCOM Data Transport interface program has detected incoming data that does not conform to LU6 specifications. The session will be terminated and the request marked as in error.

Action:


LU6 RECORD LENGTH < 4 OR > 32768 BYTES

Reason:

CA XCOM Data Transport has detected an LU record length of less than 4 bytes or greater than 32768 bytes. Record lengths of less than 4 bytes violate the LU protocol, because the logical LU 6 record must be at least 4 bytes. Although it is valid to send records longer than 32768 bytes, CA XCOM Data Transport does not support this.

Action:


xxxxxxxx DATA INVALID

Reason:

The CA XCOM Data Transport program that validates the SYSIN01 Batch

Interface input parameters has detected an invalid parameter xxxxxxxx.

Action:

To determine why the parameter was in error, see the chapter ―The Batch

Interface‖ in the CA XCOM Data Transport for z/OS User Guide.


Message Syntax

0106E

xxxxxxxx END QUOTE MISSING OR INVALID LENGTH

Reason:

This error is caused by an error within the SYSIN01 parameters. It is caused by either one of two problems: (1) the parameter entered is longer than the maximum parameter length allowed; or (2) the user attempted to place the parameter within quotes but did not include an end quote.

Action:



.

0107E

xxxxxxxx FIELD REQUIRED BUT MISSING OR INVALID

Reason:

CA XCOM Data Transport has detected an error within the SYSIN01 Batch

Interface parameter file. Parameter xxxxxxxx is a required parameter but was not entered.

Action:



0108E

xxxxxxxx FIELD HAS INVALID DATA

Reason:

CA XCOM Data Transport has detected an error within the SYSIN01 Batch

Interface parameter file. Parameter xxxxxxxx was defined but the value entered was invalid. If possible, the default value will be used. Otherwise, the file transfer will abend.

Action:




0109E

0110E

0111E

Message Syntax

xxxxxxxx yyyyyyyy PARAMETER CONFLICT

Reason:

CA XCOM Data Transport has detected a conflict between parameters xxxxxxxx and yyyyyyyy of the SYSIN01 Batch Interface parameter file.

Action:



NEITHER LCLDS01 OR LFILE DEFINED

Reason:

The user has attempted to initiate a file transfer but has not defined the local file to be transmitted or received. The file can be defined in one of two ways: (1) via the LCLDS01 DD statement; or (2) via the LFILE parameter of the SYSIN01 parameter file.

Action:

Define the local file and rerun the job.

INVALID DSN DEFINED IN LFILE PARAMETER

Reason:

An invalid data set name has been found in the LFILE parameter that does not conform to z/OS data set naming conventions. The file transfer request is abended.

Action:

Replace the invalid data set name specified in the LFILE parameter with the valid name and resubmit the request.


Message Syntax

0112E

MEMBER NAME NOT ALLOWED WITH PROGLIB=YES

Reason:

SYSIN01 specifies both PROGLIB=YES and a member name for the FILE= or

LFILE= parameter. PROGLIB=YES indicates a PDSE program library transfer, which is valid only for entire library transfers.

Action:

Remove the member specification to transfer an entire PDSE program library or remove PROGLIB=YES if the transfer is not for a PDSE program library. To transfer select members of a PDSE program library, use IEBCOPY to copy the desired members to a staging or temporary PDSE program library. Then transfer the entire staging or temporary PDSE program library using PROGLIB=YES.

0113E

xxxxxxxx ABEND nnn ON zzzzz REQ.—PROG ENDING

Reason:

An abend has occurred on a file control request for LU xxxxxxxx. This kind of error usually indicates an error opening a data set. The abend code is specified by the message operand nnn and the file control request command by zzzzz.

Action:

See the IBM documentation for more information on this abend code.

0114E

ERROR CREATING TEMP DATA SET FOR PROG

LIBRARY=xxxxxxxxxxxxxxxxxxxxx

Reason:

An error occurred when CA XCOM Data Transport tried to create a temporary file for use in transferring a PDSE program library (xxxxxxxxxxx is the name of the program library).

Action:

Review the JESMSGLG of the CA XCOM Data Transport server and look for IBM error messages related to the allocation of the temporary data set. See the IBM documentation for more information on the error messages.


0115E

0116E

0117E

Message Syntax

ERROR UNLOADING TO TEMPFILE FOR PROG


ERROR LOADING FROM TEMPFILE FOR PROG


Reason:

An error occurred when CA XCOM Data Transport tried to unload to or to load from a PDSE program library to a temporary file (xxxxxxxxxxx is the name of the program library).

Action:

Review the output in XCOMPRNT SYSOUT file of the CA XCOM Data Transport server and look for IBM error messages related to the IEBCOPY of the temporary data set. See the IBM documentation for more information on the error messages.

REQUEST FAILED DUE TO ERRORS

Reason:

An error has been detected in the SYSIN01 Batch Interface parameter file, which has caused the file transfer request to abend.

Action:

Additional messages accompany this one. Review the accompanying messages to determine the exact cause of the failure.

INVALID BLKSIZE SPECIFIED FOR FILE CREATE

Reason:

The user instructed CA XCOM Data Transport to create a file on a remote system but specified an illegal BLKSIZE parameter value.

Action:

Enter a legal value in the range of 4 to 32764 bytes.


Message Syntax

0118E

INVALID LRECL SPECIFIED FOR FILE CREATE

Reason:

The user instructed CA XCOM Data Transport to create a file on a remote system but specified an illegal LRECL parameter value.

Action:

Enter a legal value in the range of 4 to 32764 bytes.

0119E

CONFLICTING DCB OPERANDS

Reason:

Inconsistent data control block operands were specified for a file transfer in the

SYSIN01 data input stream, for example, LRECL=100, RECFM=FB, but

BLKSIZE=350.

Action:

Correct the DCB parameters and repeat the request.

0120E

INVALID RECFM SPECIFIED FOR FILE CREATE

Reason:

The user instructed CA XCOM Data Transport to create a file on a remote system but specified an unsupported RECFM parameter value.

Action:

For more information, see the description of the RECFM parameter in SYSIN01

DCB Parameters in the chapter ―The Batch Interface‖ of the CA XCOM Data

Transport for z/OS User Guide .


0121E

0122E

0123E

Message Syntax

ERROR IN BYTE xx OF THE BIND

Reason:

CA XCOM Data Transport has detected an error in the session parameters passed to it by the CINIT or the incoming BIND. Byte xx of the BIND is in error. xx is a hex number relative to byte 0 of the BIND.

Action:

Take a CA XCOM Data Transport trace and determine which byte of the BIND is in error and ensure that the MODETAB/DLOGMOD parameters are defined correctly.

UNRECOVERABLE ERROR CREATING SESSION

Reason:

An error has occurred while attempting to establish a session in which CA XCOM

Data Transport functions as a Secondary Logical Unit (SLU), which made it impossible to continue.

Action:

Additional messages accompany this one. Review the accompanying messages for more specific information on the cause of the error.

FOLLOWING ERROR RECEIVED FROM CONVERSATION PARTNER

Reason:

CA XCOM Data Transport has received an error message from its conversation partner after the conversation partner detected an error.

Action:

The actual error message(s) is displayed immediately following this message. CA

XCOM Data Transport either terminates the transfer requests or marks it as suspended, depending on the contents of the message.


Message Syntax

0124E

DATA SET IS NOT A PDSE PROGRAM LIBRARY.

DSN=xxxxxxxxxxxxxxxxxxxxx

Reason:

An error occurred while CA XCOM Data Transport tried to transfer a PDSE program library (xxxxxxxxxxx is the name of the program library). The data set to be transferred is not a PDSE program library.

Action:

Check the data set identified as DSN=xxxxxxxxxxxxxxxxx in this error message and verify that it is a PDSE program library.

0125E

INVALID DATA RECEIVED

Reason:

Unclassified data received from conversation partner (neither FMH7 nor data in date field).

Action:


0126E

FMH7 SENSE yyyyyyyy

Reason:

CA XCOM Data Transport has received a Function Management Header Type 7

(FMH7), which indicates that an error has occurred. Sense data yyyyyyyy, which is included in the FMH7, is described in the IBM documentation. The current request will be purged from the queue.

Action:

See the IBM documentation and take the appropriate action.


0127E

0128I

0129E

Message Syntax

FMH7 SENSE yyyyyyyy—GDS MSG FOLLOWS

Reason:

CA XCOM Data Transport has received an error message from its conversation partner after the conversation partner detected an error.

Action:

The actual error message(s) is displayed immediately following this message. CA

XCOM Data Transport either terminates the transfer request or marks it as suspended, depending on the contents of the message.

FOLLOWING FMH7 SENT TO CONVERSATION PARTNER

Reason:

CA XCOM Data Transport has detected an error and is about to send an error message to its conversation partner. Error messages are sent via an FMH7. CA

XCOM Data Transport terminates the transfer request.

Action:

Additional messages follow this one. Review the additional messages to determine the exact cause of this error.

PREMATURE END OF CONVERSATION RECEIVED

Reason:

CA XCOM Data Transport has detected that the conversation ended before it had been properly completed. This is considered a violation and the current file transfer request is terminated.

Action:

Resubmit the file transfer. Take a CA XCOM Data Transport trace and contact CA

Technical Support.


Message Syntax

0130E

INVALID DATA RECEIVED—EXPECTING HEADER

Reason:

A request for a conversation had been received by CA XCOM Data Transport, and

CA XCOM Data Transport expected to receive data describing the file transfer.

However, the Header Record was not received. This is considered an error and the transfer request is terminated.

Action:


Technical Support.

0131E

INVALID FILE TYPE FOR SEND TRANSFER—MUST BE FILE

Reason:

A request for a conversation has been received by CA XCOM Data Transport. The request was for CA XCOM Data Transport to transmit a file to its conversation partner, but the conversation partner requested a transfer for something other than a z/OS file (such as a report or a job). This message is sent to the remote system and the transfer request is terminated.

Action:


Technical Support.


0132E

0133I

0134I

Message Syntax

INVALID DATASET NAME

INVALID DATASET NAME, MULTIPLE WILDCARDS (*) NOT ALLOWED,

PATH=xxxxx

INVALID DATASET NAME, WILDCARD MUST BE IMMEDIATELY AFTER

LAST / IN PATH=xxxxx

INVALID DATASET NAME, PATH NAME TOO LONG, PATH=xxxxx

Reason:

The data set name specified in the file transfer request does not conform to z/OS standards. This message is displayed on the console and sent to the partner computer. The file transfer is terminated.

Action:

Check that a legal data set name has been specified.

SEND REQUEST INITIATED BY CONVERSATION PARTNER

Reason:

A request for a file transfer has been initiated by the conversation partner of CA

XCOM Data Transport. This message is displayed only on the operator's console and in the CA XCOM Data Transport log.

Action:

None

TRANSFER TERMINATED BY OPERATOR REQUEST

Reason:

An operator on the CA XCOM Data Transport system has terminated the active file transfer with the conversation partner. This message is transmitted to the conversation partner and is displayed on the console of the local system and in its CA XCOM Data Transport log.

Action:

None


Message Syntax

0135I

TRANSFER SUSPENDED BY OPERATOR REQUEST

Reason:

An operator on the CA XCOM Data Transport system has suspended an active file transfer. The message is relayed to the conversation partner. CA XCOM Data

Transport marks this request as ―suspended‖ if it was suspended by an operator on the local system and ―remote suspended‖ if suspended by a remote operator.

Action:

None

0136E

INVALID DATA RECEIVED—EXPECTING CONFIRM

Reason:

CA XCOM Data Transport sent a request to its conversation partner for a

CONFIRM, but the session partner responded with something other than a

CONFIRM or an FMH7. This is considered a protocol violation and the transfer request is terminated.

Action:


0137I

yyyyyyyy RECORDS SENT SUCCESSFULLY

Reason:

A file transfer completed successfully. The number of logical records transmitted was yyyyyyyy.

Action:

None


0138E

0139E

Message Syntax

ABEND xxx ON yyyyy FILE REQUEST

Reason:

CA XCOM Data Transport has received abend code xxx on a file I/O request of type yyyyy (for example, OPEN, GET). This message is displayed on the console and sent to the remote computer. The file transfer request is then terminated.

Action:

Look up this system abend code in the IBM documentation.

ERROR ON zzzzz FILE REQUEST

ERROR ON zzzzz FILE REQUEST, RV=xxxxxxxx, RC=xxxxxxxx,

REAS=xxxxxxxx,

DIRECTORY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Reason:

An unidentified error has occurred on the file transfer request zzzzz (for example, OPEN, PUT). This message is displayed on the console and sent to the remote computer. The file transfer request is then terminated.

The RV, RC, REAS, and DIRECTORY information are displayed only if the file being transferred is a USS file. They provide diagnostic information.

Action:

Check whether the file that you wish to transmit is a valid file type that CA XCOM

Data Transport supports.

Contact CA Technical Support and advise them of the RV, RC, REAS, and

DIRECTORY values.


Message Syntax

0140E

INVALID LU OR DEST ON INDIRECT TRANSFER

Reason:

The remote computer has specified that it wishes to perform an indirect file transfer. (In an indirect file transfer the z/OS host acts as an intermediary node that stores-and-forwards the transmitted file to the final destination computer.)

However, the specified final destination LU name or DEST was not in this system's CA XCOM Data Transport Destination Table (see the chapter,


z/OS Administration Guide). The file transfer is terminated.

Action:

Ensure that the desired LU or DEST is defined in the control library.

0141I

RECEIVE REQUEST INITIATED BY CONVERSATION PARTNER

Reason:

A request for a file transfer (RECEIVE) has been received by CA XCOM Data

Transport. This message is displayed on the operator console and written in the

CA XCOM Data Transport log.

Action:

None

0142E

INVALID DATA RECEIVED—EXPECTING FILE DESCRIPTOR

Reason:

CA XCOM Data Transport is in the process of receiving a file from its conversation partner and is expecting a record that describes the file being transmitted, but something other than that was received. The current file transfer request is terminated.

Action:



0143E

0144E

0145E

Message Syntax

INVALID DATA RECEIVED—EXPECTING DATA RECORD

Reason:

CA XCOM Data Transport was expecting to receive a data record, but some other type of record arrived. This is considered a violation and the transfer request is terminated.

Action:


SENDING RECLEN > MAX TARGET LENGTH OF xxxxx BYTES

Reason:

CA XCOM Data Transport is in the process of receiving a file, but the record that has been received is larger than the maximum record length allowed (xxxxx).

Because TRUNCATE=YES was not specified, the file transfer is terminated and this message is returned to the conversation partner.

Action:

Verify that the logical record size on the sending platform is less than or equal to the maximum record length of the receiving file. If the sending platform record is greater than the receiving file size then the receiving file's LRECL needs to be increased to accommodate the sending file record size. Or, the sending file's logical record size needs to be reduced to a length that will fit into the receiving file's LRECL.

TRAILER RECORD NOT NUMERIC OR LESS THAN 8 BYTES

Reason:

CA XCOM Data Transport is about to read the last record in the conversation

(called the trailer record) that has a count of the number of records transmitted.

However, that record contains non-numeric data or is smaller than the minimum length of 8 bytes. The file transfer is terminated and this message is sent to the conversation partner even though the file has been completely transferred.

Action:

Take a CA XCOM Data Transport trace simultaneously on both partners, and contact CA Technical Support.


Message Syntax

0146E

RECORD COUNTS ON EOF CHECK DO NOT MATCH

Reason:

While a file is being transferred, both the sending and receiving systems accumulate a count of the number of logical records in the file. At the end of the transfer, the record counts are compared. If they are not the same, then a malfunction must be assumed, and this message is sent.

Action:

Take a CA XCOM Data Transport trace simultaneously on both partners, and contact CA Technical Support.

0148E

DECOMPRESSION ERROR ON RECORD nnnnnnnn

Reason:

During decompression CA XCOM Data Transport encountered an invalid data stream on record number nnnnnnnn.

Action:

This problem can be circumvented by specifying that no compression is desired for this file transfer. Take a CA XCOM Data Transport trace and contact CA

Technical Support.

0147I

xxxxxxxx RECORDS RECEIVED SUCCESSFULLY

Reason:

A file transfer request with a remote computer has completed successfully. The total number of records received was xxxxxxxx.

Action:

None


0149E

0150E

0151I

Message Syntax

INVALID HEADER FILE TYPE

Reason:

The first message CA XCOM Data Transport transmits is called the Header

Record. Among other things, it identifies the type of file being sent as standard data, a report, or a job. In this case, the file type field that was received by this system from its session partner was invalid.

Action:

The remote user should verify that a proper file type is being specified. Take a CA

XCOM Data Transport trace and contact CA Technical Support.

INVALID DATA SET NAME

Reason:

A data set name was specified that does not conform to z/OS file naming conventions.

Action:

Correct the data set name.

xxxxxxxx SESSION ENDED

Reason:

The session between CA XCOM Data Transport and the logical unit xxxxxxxx has terminated. This is a normal status message.

Action:

None


Message Syntax

0152E

FMH DATA RECEIVED INVALID—NOT FMH5 OR FMH7

Reason:

CA XCOM Data Transport has received an FMH other than types 5 or 7. Because these are the only types of FMH supported, CA XCOM Data Transport considers this a protocol violation. The session is terminated and the request is marked as in error.

Action:


0153E

INVALID DATA RECEIVED—EXPECTING FMH7 AFTER RC 0846

Reason:

CA XCOM Data Transport has received sense code 0846 from its conversation partner. The only valid data that can follow 0846 is an FMH7, but CA XCOM Data

Transport determined that an FMH7 did not follow. Because this is considered a protocol violation, the session is ended and the current request is marked as in error.

Action:


0154E

ZERO NSA ADDRESS PASSED—XCOM ABENDING

Reason:

An internal error occurred processing a VTAM request. This error should never occur and is included for documentation purposes only.

Action:



0155I

0156I

0157E

Message Syntax

xxxxxxxx-LOGON EXIT ENTERED

Reason:

The VTAM logon exit was entered for LU xxxxxxxx.

Action:

None

TYPE xx-TPEND RECEIVED

Reason:

CA XCOM Data Transport is ending because VTAM is being shut down. This is a normal message if the operator entered a z/OS HALT NET command before stopping CA XCOM Data Transport or if the operator deactivated the CA XCOM

Data Transport ACB (immediately or forced this condition to occur).

Note: You can restart CA XCOM Data Transport after VTAM is restarted or the

ACB is activated.

Action:

See the IBM documentation, which explains TPEND, and take the appropriate action.

LOSTERM EXIT ENTERED FOR UNKNOWN LU

Reason:

The LOSTERM exit for CA XCOM Data Transport was driven for an LU that was not known to CA XCOM Data Transport.

Action:



Message Syntax

0158E

xxxxxxxx-LOSTERM TYPE nn RECEIVED

Reason:

The LOSTERM exit was driven for the session to LU xxxxxxxx. Why this occurred is indicated by code nn. The session with this LU ends immediately.

Action:

Look up code nn in the IBM documentation, and take the appropriate action.

0159E

xxxxxxxx RELREQ EXIT DRIVEN-LU NOT FOUND

Reason:

The RELREQ exit for CA XCOM Data Transport has been driven by VTAM for LU xxxxxxxx. However, CA XCOM Data Transport is unaware of any session with this logical unit.

Action:

Ignore this message unless other related problems are reported. In that case, contact CA Technical Support.

0160I

xxxxxxxx RELREQ EXIT DRIVEN

Reason:

The RELREQ exit for CA XCOM Data Transport has been driven by VTAM for LU xxxxxxxx. Another VTAM application wants to use the same LU. CA XCOM Data

Transport will release it as soon as the LU xxxxxxxx has no outstanding file transfer requests.

Action:

None


0161E

0162E

0163E

Message Syntax

NSEXIT CLEANUP ENTERED FOR UNKNOWN LU

Reason:

The VTAM NSEXIT was driven for an LU that CA XCOM Data Transport could not find. This could happen if CA XCOM Data Transport had removed the logical unit from its network prior to the NSEXIT being driven.

Action:


NSEXIT NOTIFY ENTERED FOR UNKNOWN LU

Reason:

The CA XCOM Data Transport server had one of its VTAM exit routines, the NS exit, driven by VTAM in order to inform this LU that it no longer had a session to a particular LU. However, as far as CA XCOM Data Transport was aware it did not have an active session to this LU. (It probably had already ended this session by issuing a VTAM CLSDST macro. This can happen, for example, if a user at a dial-up node requested CA XCOM Data Transport to end the session, but turned off his or her modem before CA XCOM Data Transport could comply.)

Action:

None

xxxxxxxx-NSEXIT DRIVEN FOR NSPE

Reason:

The NSEXIT was driven by VTAM for LU xxxxxxxx because a Network Services

Procedure Error request was received for this LU. The session with this LU ends immediately.

Action:

See the IBM documentation for an explanation of the NSEXIT NSPE RU.


Message Syntax

0164E

NSEXIT NSPE DRIVEN FOR UNKNOWN LU

Reason:

VTAM invoked the NSEXIT for an LU but CA XCOM Data Transport could not find that LU in the system.

Action:


0165E

NSEXIT UNKNOWN TYPE RECEIVED

Reason:

VTAM invoked an NSEXIT of an undocumented type. Current VTAM releases support only NSPE, NOTIFY, and CLEANUP NSEXIT RUs. The session with the LU ends immediately.

Action:

Obtain a CA XCOM Data Transport trace of the file transfer and contact CA

Technical Support.

0166E

xxxxxxxx yyyyyyyy NSEXIT DRIVEN

Reason:

VTAM invoked the NSEXIT for LU xxxxxxxx. The message operand yyyyyyyy indicates the type of exit driven and should be NSPE, NOTIFY, or CLEANUP. The session with the LU ends immediately.

Action:

None


0167E

0168E

0169I

Message Syntax

SCIP UNBIND RECEIVED FOR UNKNOWN LU

Reason:

CA XCOM Data Transport received an UNBIND for a logical unit, but it was unaware it had a session with this LU. VTAM had driven the SCIP exit for CA

XCOM Data Transport.

Action:


xxxxxxxx SCIP UNBIND TYPE nn yyyyyyyy RECEIVED

Reason:

An UNBIND has been received from LU xxxxxxxx, forcing an end to this LU-LU session. The UNBIND type nn indicates why the UNBIND was sent. VTAM drove the SCIP exit for CA XCOM Data Transport. The message operand yyyyyyyy represents sense data included in the UNBIND. An UNBIND type of 01 is normal and does not indicate a problem.

Action:

None

xxxxxxxx SCIP RQR RECEIVED

Reason:

An SNA Request Recovery request was received during a session with LU

xxxxxxxx. While this is normal for some LU types, it is not valid for the LU protocol.

Action:

If this is an LU session, then a protocol error has occurred. Contact CA Technical

Support. If this is not an LU session, no further action is required.


Message Syntax

0170I

xxxxxxxx SCIP CLEAR RECEIVED

Reason:

A protocol error probably occurred during a session with an LU. This should never happen during an LU session.

If this is an LU session, you might have incorrectly specified the LU name,

xxxxxxxx, and inadvertently established communications with a logical unit not on the CA XCOM Data Transport network.

Action:

Contact your systems programming staff for help. If this is not an LU session, no further action is required.

0171I

xxxxxxxx SCIP SDT RECEIVED

Reason:

An SNA Start Data Traffic request was received during a session with LU

xxxxxxxx. While this is normal for some LU types, it is not valid for the LU protocol.

Action:

If this is an LU session, then a protocol error has occurred. If this is not an LU session, no further action is required. Contact CA Technical Support.

0172I

xxxxxxxx SCIP STSN RECEIVED

Reason:

An SNA Set and Test Sequence Numbers request was received during a session with LU xxxxxxxx. While this is normal for some LU types, it is not valid for the LU protocol.

Action:

If this is an LU session, then a protocol error has occurred. Contact CA Technical

Support. If this is not an LU session, no further action is required.


0173E

0174E

0175E

Message Syntax

xxxxxxxx SCIP INVALID BIND RECEIVED FOR PLU

Reason:

The CA XCOM Data Transport SCIP exit has been driven by VTAM for LU

xxxxxxxx, but CA XCOM Data Transport has determined that the BIND is not valid.

Action:


xxxxxxxx SCIP ZERO LENGTH BIND RECEIVED

Reason:

The VTAM SCIP routine was invoked for LU xxxxxxxx with a BIND RU, but the

BIND received from VTAM was zero bytes long.

Action:


xxxxxxxx SCIP INVALID SCIP TYPE RECEIVED

Reason:

The VTAM SCIP exit was invoked for LU xxxxxxxx, but the SCIP type was not defined by VTAM.

Action:



Message Syntax

0176I

xxxxxxxx RESP EXIT DRIVEN

Reason:

The CA XCOM Data Transport VTAM application has received an SNA response from LU xxxxxxxx. This message is included for documentation purposes only.

CA XCOM Data Transport does not use the VTAM RESP exit.

Action:

None

0177I

xxxxxxxx DFASY SIGNAL DRIVEN AND IGNORED

Reason:

The VTAM DFASY exit was driven for a signal request for LU xxxxxxxx. For more information on the DFASY exit consult the IBM documentation. This message is included for documentation purposes only. CA XCOM Data Transport does not use the VTAM DFASY exit.

Action:

None

0178E

xxxxxxxx DFASY INVALID DATA RECEIVED FOR LU6

Reason:

The VTAM DFASY exit was driven for LU xxxxxxxx, but data documented by

VTAM was detected in the RU.

For more information on the DFASY exit, consult the IBM documentation.

Action:



0179I

0180E

0181E

0182E

Message Syntax

xxxxxxxx DFASY SHUTC RECEIVED FOR LU2

Reason:

The VTAM DFASY exit was driven with a SHUTC RU for LU xxxxxxxx using 3270 emulation.

Action:


xxxxxxxx DFASY INVALID DATA RECEIVED FOR LU2

Reason:

An invalid DFASY data was received for LU xxxxxxxx during a 3270 emulation.

Action:


xxxxxxxx LERAD RC 18 RECEIVED

Reason:

The VTAM LERAD exit was invoked for LU xxxxxxxx with a return code of 18. This indicates that the RPL was corrupted. The file transfer request will be terminated.

Action:

If this error persists, take a CA XCOM Data Transport trace and contact CA

Technical Support.

MODCB ERROR CODE xx yy RECEIVED—XCOM ABENDING

Reason:

A VTAM MODCB macro received code xx yy when trying to modify the VTAM ACB.

Action:

Ensure that the ACF/VTAM release level is at least Version 2. Obtain a dump and contact CA Technical Support.


Message Syntax

0183E

SHOWCB ERROR CODE xx yy RECEIVED—XCOM ABENDING

Reason:

A VTAM SHOWCB macro received code xx yy when trying to display contents of the VTAM ACB.

Action:

Ensure that the ACF/VTAM release level is at least Version 2. Obtain a dump and contact CA Technical Support.

0184E

xxxxxxxx GENCB NIB ERROR RECEIVED—XCOM ABENDING

Reason:

VTAM returned an error on a GENCR macro instruction, which generated an NIB.

Action:

Ensure that the ACF/VTAM release level is at least Version 2. Check that there is adequate virtual storage. If this error persists, obtain a dump and contact CA

Technical Support.

0185E

xxxxxxxx GENCB RPL ERROR RECEIVED—XCOM ABENDING

Reason:

CA XCOM Data Transport was attempting to generate a Request Parameter List control block for LU xxxxxxxx when an error occurred.

Action:



0186E

0187E

0188E

Message Syntax

zzzzzzzz RC xx FDBK2 yy SENSE nnnn nnnn cccccccc

Reason:

The VTAM LERAD/SYNAD routines were entered with return code xx, feedback 2 code yy, and sense data nnnn nnnn. VTAM command cccccccc caused the error.

zzzzzzzz is the LU name.

One of the more common versions of this message is RC 14 FDBK2 4B SENSE

0821 0000 SIMLOGON, which generally indicates that the default mode entry for this APPLID is not in the Logon Mode Table used by this APPLID.

Action:

This is often only an informational message, because many VTAM return codes are normal, for example, indicating a session is not active. Look up the return code and the FDBK2 code in the IBM documentation. If the codes indicate an error condition and this error persists, take a CA XCOM Data Transport trace and contact CA Technical Support.

RANY GENCB ERROR—XCOM ABENDING

Reason:

At CA XCOM Data Transport initialization, CA XCOM Data Transport was attempting to generate an RPL and NIB for its RECEIVE ANY routine, but VTAM returned an error. Because CA XCOM Data Transport can accept no incoming

ALLOCATEs without the RECEIVE ANY routine, it will abend.

Action:

Bring CA XCOM Data Transport up again. If the problem persists, contact CA

Technical Support.

CID NOT FOUND FOR RANY ROUTINE

Reason:

The CA XCOM Data Transport RECEIVE ANY routine was posted, but CA XCOM

Data Transport had no record of the session identifier (CID). Hence, no further processing can take place for this LU.

Action:


Technical Support.


Message Syntax

0189I

xxxxxxxx RANY RPL POSTED WHILE TPN ACTIVE

Reason:

The CA XCOM Data Transport RECEIVE ANY RPL has been posted, but a conversation is currently active with LU xxxxxxxx.

Action:

None

0190E

RECURSIVE ERROR DETECTED WITHIN RANY ROUTINE

Reason:

The CA XCOM Data Transport RECEIVE ANY routine encountered a recursive

VTAM error. Because this routine is required to process incoming requests, CA

XCOM Data Transport will terminate with a dump.

Action:

Bring CA XCOM Data Transport up again. If this error persists, collect the CA

XCOM Data Transport message log and dump, and contact CA Technical Support.

0191E

INVALID FMH5 RECEIVED

Reason:

CA XCOM Data Transport has received an invalid FMH5 from the session partner.

It returns the above message along with an FMH7 to the session partner.

Action:

Repeat the file transfer request. If this error persists, take a CA XCOM Data

Transport trace and contact CA Technical Support.


0192E

0193E

0194E

Message Syntax

INVALID TPN RECEIVED

Reason:

CA XCOM Data Transport has received a request from the remote system for a conversation, but the TPN (Transaction Program Name) was invalid. This message is returned to the partner LU along with an FMH7.

Action:



TPN CURRENTLY UNAVAILABLE

Reason:

CA XCOM Data Transport has received an incoming ALLOCATE request but the

TPN requested was unavailable. This usually occurs because of an error loading the program.

Action:

Ensure that the CA XCOM Data Transport load modules are in a proper STEPLIB,

JOBLIB, or LINKLST library and that enough storage has been allocated for CA

XCOM Data Transport to run.

INVALID DATA RECEIVED—EXPECTING FMH5

Reason:

CA XCOM Data Transport has received a bid for a conversation from the session partner and expected an FMH5 to follow and initiate the conversation. However, if data other than an FMH5 is followed, CA XCOM Data Transport treats this as a protocol violation, terminates the session and marks the current request as in error.

Action:


Technical Support.


Message Syntax

0195E

SESSION ENDING DUE TO VTAM ERROR

Reason:

CA XCOM Data Transport has encountered a VTAM error during a SEND or

RECEIVE request, causing it to end the session.

Action:



0196E

ERROR IN BYTE xx OF ATTACH FMH5

Reason:

CA XCOM Data Transport was processing an incoming ALLOCATE request, but found an error in byte xx of the request. The incoming ALLOCATE request will be terminated, and this message will be sent to the remote LU.

Action:


Technical Support.

0197I

NO SESSIONS MEET DISPLAY SELECTION CRITERIA

Reason:

The console operator entered a DISPLAY command but there was no data available to meet the selection criteria entered by the operator.

Action:

None


0198I

0199I

0200E

Message Syntax

XCOM NORMAL SHUTDOWN STARTED—ENDING SESSIONS

Reason:

The console operator has initiated a normal CA XCOM Data Transport shutdown via the STOP command. CA XCOM Data Transport will terminate all sessions when the current conversation ends, and then end processing.

Action:

None

XCOM IMMEDIATE SHUTDOWN INITIATED

Reason:

The console operator has requested that CA XCOM Data Transport be brought down immediately via the F XCOM,STOP,IMMED command. CA XCOM Data

Transport will terminate after closing all files without ending any sessions. The sessions will end when CA XCOM Data Transport comes down.

Action:

None

RRDS MASTER FILE NOT OPENED—REQUEST DENIED

Reason:

CA XCOM Data Transport has attempted to access the RRDS Restart File, but the file is not open. CA XCOM Data Transport will display this message when a request is being scheduled. There should be a message displayed at CA XCOM

Data Transport initialization that indicates the reason why the RRDS file was not properly opened.

Action:

None


Message Syntax

0201E

INVALID RRDS REQUEST

Reason:

CA XCOM Data Transport has detected an invalid RRDS request to its Restart

File.

Action:

If this error persists, contact CA Technical Support.

0202E

xxxxxxxx RRDS xxxxx REQUEST DENIED DUE TO ACTIVE RPL

Reason:

CA XCOM Data Transport has received a VSAM error accessing its RRDS Restart

File that indicates that the RPL used to process the request is already active.

Action:


0203E

xxxxxxxx RC xx yy ON zzzzzz RRDS VSAM MACRO

Reason:

A VSAM macro such as SHOWCB, TESTCB, or GENCB has ended due to an error.

The LU name involved is identified by xxxxxxxx. The return code is yy, while

zzzzzz is the VSAM macro issued.

Action:


0204E

xxxxxxxx RC xx yy ON zzzzz RRDS VSAM SLOT xxxxxxxx

Reason:

A VSAM macro such as GET, PUT, or ERASE has received return code xx FDBK yy for LU xxxxxxxx.

Action:

See the return codes documented in the IBM documentation and take the appropriate action.


0205E

0206E

0207W

Message Syntax

INVALID xxxxxxxx DEFAULT OPERATOR COMMAND

Reason:

A DFLT command issued to modify the Default Options Table specified an invalid parameter (xxxxxxxx).

Action:

For the valid parameters in the Default Options Table, review the chapter


z/OS Administration Guide.

xxxxxxxx CHANGE INVALID FOR yyyyyyyy PARAMETER

Reason:

A DFLT command issued to change parameter yyyyyyyy in the Default Options

Table specified invalid value xxxxxxxx.

Action:

For information about how to override the parameters in the Default Options

Table, review Overriding the Default Options in the chapter ―Configuring and

Customizing Your Product‖ in the CA XCOM Data Transport for z/OS

Administration Guide.

xxxxxxxx GROUP IS NOT CURRENTLY ENABLED

Reason:

This message is issued when a user attempts to schedule a transfer request with a group name that is undefined or not currently enabled. CA XCOM Data

Transport accepts the request but takes no action. If the requested group name is defined and/or enabled before the request is deleted due to aging, CA XCOM

Data Transport will process the request; otherwise, the request will be deleted when it meets installation aging criteria.

Message XCOMM501I will be issued each time CA XCOM Data Transport attempts to select the transfer for execution.

Action:

Verify that the group name specified is correct. If the transfer request is to be processed, define and/or enable the requested group.


Message Syntax

0208E

REMOTE SYSTEM IDENTIFICATION NOT PROVIDED

Reason:

A user has attempted to perform a file transfer, but did not define the computer with which it is to communicate. This can be done through the GROUP, IPNAME,

LIST, LU, or USER parameters. The file transfer request is terminated.

Action:

Resubmit the request with a GROUP, IPNAME, LIST, LU, or USER parameter.

0209E

NO SYSIN01 CARDS FOUND FOR FILE TRANSFER

Reason:

The user has attempted to perform a file transfer request, but no Batch Interface

SYSIN01 parameter cards were found. This could happen, for example, if two

NEWXFER cards were back-to-back, or if the NEWXFER file was followed immediately by an end-of-file. The CA XCOM Data Transport job step is terminated.

Action:

Rerun with the required parameter statements (see the chapter ―The Batch

Interface‖ in the CA XCOM Data Transport for z/OS User Guide).

0210E

NEWXFER CARD INVALID FOR TYPE=EXECUTE

Reason:

The user has attempted to perform a TYPE=EXECUTE file transfer. However, the user also included the NEWXFER statement within the SYSIN01 parameters that is invalid for such a transfer.

Action:

Do not attempt to use the NEWXFER feature or resubmit the request as a

TYPE=SCHEDULE transfer.


0211I

0212E

0213E

Message Syntax

xxxxxxxx DEFAULT PARAMETER CHANGED TO yyyyyyyy

Reason:

A DFLT command has been issued to change the Default Options Table parameter xxxxxxxx to a new value yyyyyyyy. The change occurs immediately for most options, but requires some operator intervention for options such as

LOGCL and LOGDEST.

Action:

None

xxxxxxxx PARAMETER ERROR—MUST BE 4 HEX BYTES

Reason:

The console operator has issued a DFLT command to change the EDESC, EROUT,

IDESC, or IROUT default values, but an invalid value was specified.

Action:

Enter value as 4 hexadecimal digits, representing the 16 bits of the routing/descriptor codes.

MEMBER NAME NOT SPECIFIED FOR INPUT PDS

Reason:

The user has attempted to transmit a PDS to a remote system, but no member name was specified. The file transfer request is terminated.

Action:

Rerun the file transfer. Note that if you want to transmit all members of a PDS, specify the wildcard value (*) as a member name.


Message Syntax

0214E

MEMBER xxxxxxxx NOT FOUND IN PDS FILE

Reason:

The user has attempted to transmit a specific member of a PDS to a remote system, but member xxxxxxxx was not found in the PDS file. The file transfer request is terminated.

Action:

Determine the correct member name and resubmit.

0215E

INVALID FIXED LRECL VALUE OF nnnnn

Reason:

This message is issued when CA XCOM Data Transport encounters an error deblocking a fixed-block data set. It indicates that the data set may be corrupted. The transfer request is terminated.

Action:

Examine the data set using appropriate debugging tools. It may be necessary to recreate the data set if it is found to be corrupted.

0216E

INVALID BLOCK CRITERIA FOR VARIABLE BLOCKED FILE

Reason:

The CA XCOM Data Transport file deblocking routine has detected a variable blocked file which has an invalid block or record descriptor. The file transfer request ends and this message is sent to the remote system.

Action:

Correct the variable blocked file and resubmit the request.


0217I

0218I

0219E

Message Syntax

xxxxxxxx RACE CONDITION ENTERED—CONTENTION WINNER

Reason:

CA XCOM Data Transport has detected a RACE condition in which it is the contention winner. This message is informational only and is intended to assist in problem determination if the remote system does not handle this condition properly.

Action:

None

xxxxxxxx RACE CONDITION ENTERED—CONTENTION LOSER

Reason:

CA XCOM Data Transport has detected a RACE condition in which it is the contention loser. This message is informational only and is intended to assist in problem determination if the remote system does not handle this condition properly.

Action:

None

INVALID LRECL/BLKSIZE FOR XCOMREST S/B 2020 RECFM=F

Reason:

The user is attempting to initiate a TYPE=EXECUTE file transfer, but the

XCOMREST file has been defined incorrectly. The file transfer will be processed but no checkpoints will be taken and no restart is possible.

Action:

Define the XCOMREST file as follows and allocate one track:

DCB=(RECFM=FB,LRECL=2020,BLKSIZE=2020)


Message Syntax

0220E

INVALID FILE COMMAND RECEIVED BY XCOMFILE

Reason:

An internal error was detected in the CA XCOM Data Transport file access routine.

Action:


0221E

DATA SET OUT OF SPACE

Reason:

A file transfer request was in progress when the output data set (that is, destination file) ran out of space.

Action:

Increase the allocation for the output data set.

0222E

MEMBER xxxxxxxx NOT FOUND

Reason:

A file transfer request was initiated that involved an input data set (that is, the target file) that was a partitioned data set. However, the specified member,

xxxxxxxx, was not found in the PDS.

Action:

Check the PDS member name.

0223E

ABEND xxx yyy RECEIVED ON FILE REQUEST

Reason:

Abend code xxx yyy has been received on a file request.

Action:

See the IBM documentation and take the appropriate Action.


0224E

0225E

0226E

0227E

Message Syntax

GDG +1 VALID ONLY FOR CREATE

Reason:

The remote user initiated a REPLACE or ADD type file transfer request that specified a GDG value of +1. However, a GDG value of +1 is valid only for a

CREATE function.

Action:

Specify a valid GDG value.

MEMBER GIVEN—LIBRARY NOT PDS

Reason:

A file transfer request indicated a member of a PDS as the file that was to be opened by z/OS. However, the specified file was not a PDS.

Action:

Make the appropriate specification and resubmit the request.

MEMBER NAME MISSING OR INVALID

Reason:

A file transfer request indicated a PDS but did not specify the member.

Action:

Specify the member and resubmit the request.

INVALID DATA SET DSORG

Reason:

The user attempted to transfer a data set with an unsupported data set organization. Only partitioned, sequential or VSAM data sets may be transferred.

Action:

If this was a user error, correct and resubmit. Otherwise, contact CA Technical

Support.


Message Syntax

0228E

MEMBER/GDG NUM INVALID FOR NEW FILE

Reason:

The remote user initiated a CREATE file transfer request for a GDG data set that did not specify a positive generation number. Or, a member name was specified for a sequential data set. CA XCOM Data Transport will default to a sequential data set if directory space is not provided.

Action:

If you are creating a member for a PDS, you must specify REPLACE. If not, and the file is a GDG, you must specify a positive generation number for the CREATE request. If the file to be created is a PDS, you must specify SPACE, including the directory subparameter.

0229E

ERROR RECEIVED DURING RDJFCB EXECUTION

Reason:

An error was encountered processing an RDJFCB macro.

Action:

Repeat the file transfer request. If this error persists, contact CA Technical

Support.

0230E

FILE NOT FOUND ON ALLOCATION DSN=xxxxxxxx

Reason:

A file transfer request specified a local file that could not be found. For

TYPE=SCHEDULE file transfer requests, this message is sometimes caused by

JCL that specifies the local file as a SYSIN DD * file. Because a SYSIN DD * file exists only for the life of the job in which it is specified, it no longer exists when

CA XCOM Data Transport executes the scheduled file transfer. xxxxxxxx is the data set name.

Action:

Correct the file name.


0231E

0232E

0233E

0234E

Message Syntax

DUPLICATE FILE ON ALLOCATION DSN=xxxxxxxx

Reason:

A file transfer request involving a CREATE function was initiated, but the file already existed. xxxxxxxx is the data set name.

Action:

Correct the file name or specify a REPLACE or ADD function as appropriate.

UNABLE TO ALLOCATE DATASET DSN=xxxxxxxx

Reason:

There was an error allocating a data set.

Action:

Repeat the request. If this error persists, contact CA Technical Support.

NOT ENOUGH SPACE ON VOLUME

Reason:

A file transfer request involving a CREATE function was initiated, but there was not enough space on the volume to allocate the data set.

Action:

Specify a volume with sufficient space to allow for the allocation of the data set.

CATALOG ERROR—POSSIBLE DUPLICATE FILE DSN= xxxxxxxx

Reason:

A file transfer request involving a CREATE function was initiated, but the dynamic allocation request failed. Usually this results from a duplicate catalog entry.

Action:

Check that the data set is not already cataloged.


Message Syntax

0235E

INVALID UNIT DEVICE ON ALLOCATION

Reason:

Dynamic allocation returned an error indicating that an invalid unit name was specified. Either the user entered an invalid unit name or the UNIT parameter in the Default Options Table specified an invalid unit name.

Action:

Check that a valid unit name was specified, or that the UNIT parameter in the

Default Options Table is valid (see the chapter ―Configuring and Customizing

Your Product‖ in the CA XCOM Data Transport for z/OS Administration Guide).

0236E

DATA SET UNAVAILABLE ON ALLOCATION DSN = xxxxxxxx

Reason:

The local file being transferred is currently in use and unavailable. xxxxxxxx is the data set name, an alphanumeric string.

Action:

Resubmit the request at a later time.

0237E

INVALID VOLUME NAME ON ALLOCATION

Reason:

The volume name specified on a file transfer request involving a CREATE function was invalid. Either the user entered an invalid volume name or the VOL parameter in the Default Options Table specified an invalid unit name.

Action:

Check to determine the correct volume name. If necessary have the proper tape or disk premounted. Then, retry the request. Also, check that the VOL parameter in the Default Options Table is valid (see the chapter ―Configuring and


Administration Guide) and retry.


0238E

0239E

0240E

Message Syntax

INVALID DATASET NAME ON ALLOCATION

Reason:

The data set name specified is syntactically invalid.

Action:

Specify a valid data set name and rerun the transfer.

RC xxxx yyyy ON DYNAMIC ALLOCATION

Reason:

CA XCOM Data Transport attempted unsuccessfully to dynamically allocate a data set. The message operand xxxx provides the dynamic allocation error codes. The message operand yyyy provides the dynamic allocation information code.

Action:

Check the meanings of these codes. The easiest way to do this is to log on to

TSO/ISPF and access the Main Menu of the Program Development facility.

Choose option T for Tutorial. Then access the table of contents (in some cases this is done by typing UP). From the table of contents menu choose A for

Appendix A. This will display the dynamic allocation codes on the two first pages.

Documentation of the reason codes can also be found in the IBM documentation.

INVALID FILE TYPE OR OPEN ERROR FOR INTRDR OR SYSOUT

Reason:

An internal reader or SYSOUT file could not be opened. Additional messages describe the actual cause of the error.

Action:

Review the additional messages.


Message Syntax

0241E

ERROR OPENING FILE

ERROR OPENING FILE, RV=xxxxxxxx, RC=xxxxxxxx, REAS=xxxxxxxx,

DIRECTORY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Reason:

A problem was encountered while attempting to open a file, but further data is not available.

The RV, RC, REAS, and DIRECTORY information are displayed only if the file being transferred is a USS file. They provide diagnostic information.

Action:

Check the parameters that you specified for this file transfer request.

Contact CA Technical Support and advise them of the RV, RC, REAS, and

DIRECTORY values.

0242E

ERROR OPENING PARTITIONED FILE DIRECTORY

Reason:

CA XCOM Data Transport is attempting to open the directory of a partitioned data set but has received an error doing so. Additional messages describe the actual cause of the error.

Action:

Review the additional messages.

0243E

INVALID OR INCOMPLETE DCB CHARACTERISTICS

Reason:

Because there was either invalid or insufficient information in the DCB, an error occurred attempting to open a sequential data set or a PDS member.

Action:

Ensure that the RECFM, LRECL, BLKSIZE, and data set organization are correct and available to CA XCOM Data Transport. Then, retry the request.


0244E

0245E

0246E

Message Syntax

xxxxxxxx VSAM FILE TYPE NOT KSDS, ESDS, OR RRDS

Reason:

A VSAM file was encountered that was neither a KSDS, ESDS, nor RRDS.

Action:

Determine the VSAM file's type using the LISTCAT Access Methods Services command.

xxxxxxxx RC yy zz ON VSAM OPEN DSN=xxxxxxxx

Reason:

A VSAM OPEN macro failed for DD name xxxxxxxx. The major and minor return codes are yy and zz, respectively. xxxxxxxx is the data set name.

Action:

Look up the return codes in the IBM documentation and take the appropriate action.

xxxxxxxxxx ERROR TYPE yy zz

Reason:

An error occurred processing a VSAM SHOWCB, MODCB or TESTCB macro instruction. xxxxxxxxxx is the type of macro which caused the error. The return codes generated are yy zz.

Action:



Message Syntax

0247E

ACB CLOSE ERROR TYPE xx

Reason:

CA XCOM Data Transport was trying to close a VSAM ACB when an error occurred. Return code xx was generated.

Action:


0248E

SENSE xxxx yyyy RECEIVED DE-ALLOCATE SVC 99

Reason:

An error occurred performing a dynamic deallocation of a file. Sense data xxxx

yyyy are the error and informational codes returned from SVC 99.

Action:

Look up the error and informational codes in the IBM documentation and take the appropriate action.

0249E

VSAM MODCB ERROR CODE xx yy

Reason:

A MODCB macro was issued and error code xx yy was returned. The file transfer request is terminated and this message is sent to the partner LU.

Action:

Look up the error code in the IBM documentation under both the return code and feedback fields, and take the appropriate action.


0250E

0251E

0252E

Message Syntax

VSAM GET ERROR CODE xx yy

Reason:

A VSAM GET request returned error code xx yy. The file transfer request is terminated and this message is sent to the partner LU.

Action:

Look up the error code in the IBM documentation under both the return code and feedback fields.

VSAM SHOWCB ERROR CODE xx yy

Reason:

Error code xx yy was encountered processing a VSAM SHOWCB macro instruction. The file transfer request is terminated and this message is sent to the partner LU.

Action:

Look up the error code in the IBM documentation.

DUPLICATE KEY ON VSAM WRITE

Reason:

An attempt was made to transfer a file to a VSAM keyed or relative data set (or to an Entry Sequenced VSAM file being accessed through an alternate index path) that does not allow duplicates. Because the record key being sent was already on the file, CA XCOM Data Transport aborted the file transfer.

Action:

Eliminate the duplicate key and retry the request.


Message Syntax

0253E

VSAM RECORD OUT OF SEQUENCE

Reason:

An attempt was made to send a record to a VSAM file that was organized as indexed or relative (or was entry sequenced but accessed through an alternate index path). However, the records being sent were not in ascending order by key. Because CA XCOM Data Transport accesses VSAM files sequentially, it could not support this situation.

Action:

Sort the file being sent in ascending order by the same key used by the VSAM file. If appropriate, delete the file from the receiving system before retrying the transfer.

0254E

OUT OF SPACE ON VSAM FILE

Reason:

An attempt was made to send data to a VSAM file that did not have sufficient space to process the request.

Action:

Recreate the VSAM file with more space.

Note: There may be sufficient space except that the file requires reorganization as a result of control interval or control area splits. Use the REPRO command to reorganize.

0255E

VSAM PUT ERROR CODE yy zz

Reason:

A VSAM PUT request returned error code yy zz. The file transfer request is terminated and this message is sent to the partner LU.

Action:

Look up the error code in the IBM documentation under both the return code and feedback fields.


0256E

0257E

0258E

Message Syntax

ACCESS DENIED—SECURITY ERROR

Reason:

CA XCOM Data Transport was unable to execute its security interface as the result of a security system error. As a result, access to the data set was denied.

Action:

Ensure that the appropriate security module (XCOMACF2, XCOMRACF,

XCOMTOPS) is in the CA XCOM Data Transport load library.

ACCESS DENIED BY SECURITY INTERFACE

Reason:

This is the basic message issued when the CA XCOM Data Transport security interface denies access to a data set. Sometimes a more descriptive message will be issued.

Action:

Ensure that the user ID under which the transfer request executes has access privileges to the file.

SENSE nnnn RECEIVED INQ SVC99

Reason:

CA XCOM Data Transport returned sense data nnnn nnnn for LU xxxxxxxx on an

SVC99 INQUIRE MACRO. The file transfer request is terminated.

Action:

Look up the return and reason codes in the IBM documentation and take the appropriate action.


Message Syntax

0259E

xxxxxxxx DD NAME NOT FOUND ON SVC99 INQUIRE

Reason:

The CA XCOM Data Transport Batch Interface (XCOMJOB) attempted to do an

SVC99 inquire on the LCLDS01 DD statement, but the DD statement had not been defined. (This message may be displayed if the LFILE parameter is used instead of the LCLDS01 DD statement in which case the message may be ignored.)

Action:

Ensure that the LCLDS01 statement (or the LFILE parameter) is defined in this file transfer request's JCL.

0260E

FILE DSORG INVALID FOR REQUEST

Reason:

An invalid data set organization was encountered for LU xxxxxxx due to one of the following conditions:

■

The DSORG was not PO, PS, or VS.

■

A partitioned data set was processed without a member name.

■

A member name was specified for a sequential or VSAM data set.

Action:

Correct the improper condition and repeat the file transfer request.

0261E

INVALID LRECL SPECIFIED

Reason:

An LRECL was specified that was not within the legal range supported by MVS.

For RECFM F, FB, or U data sets, the maximum size is 32,764. For V and VB data sets, the maximum size is 32,760.

Action:

Correct the illegal specification and retry the request.


0262E

0263E

0264E

Message Syntax

INVALID BLKSIZE SPECIFIED

Reason:

A BLKSIZE was specified that was not within the legal range supported by z/OS.

For FB and VB the maximum size is 32,764. For FB the minimum size is 4, and for

VB it is 5.

Action:

Correct invalid block size specified and resubmit the request.

INVALID LRECL/BLKSIZE COMBINATION

Reason:

The logical record length and block size specified for a data set are contradictory.

If the record format is fixed blocked, then the BLKSIZE must be a multiple of the

LRECL. For Fixed record format, it must equal the LRECL. For Variable or Variable

Blocked, it must be at least four bytes larger than the LRECL. (If the RECFM is undefined, then the LRECL is not relevant.)

Action:

Make the logical record length and block sizes consistent and retry the request.

R15 xx R0 yy ERROR RECEIVED ON PDS MEMBER

Reason:

CA XCOM Data Transport has attempted to perform a FIND on a partitioned data set, but has received return code xx yy. The file transfer is terminated and this message is sent to the conversation partner.

Action:

Verify that you have correctly identified the PDS and that it is a valid and uncorrupted PDS. See the IBM documentation to check the return codes.


Message Syntax

0265E

xxxxxxxx MEMBER NOT FOUND IN PDS DATASET

Reason:

CA XCOM Data Transport issued a FIND macro to position itself to the correct member in a partitioned data set, but a ―not found‖ condition was raised. The file transfer is terminated and this message is sent to the conversation partner. This error normally occurs under two circumstances: if an alias exists for a member but the actual member does not exist, or if the partitioned data set has been corrupted.

Action:

If xxxxxxxx member in above message is that of the START=xxxxxxxx in

XCOMDFLT or in the PARM statement override, you must define a member whose name matches that of the START= member in XCOMDFLT or in the PARM statement, if used. The member may contain a comment statement only if no destinations are to be enabled during initialization of the CA XCOM Data

Transport server. Otherwise, this message displays and no scheduled transfers will be activated.

0266E

I/O ERROR OCCURRED DURING DIRECTORY FIND

Reason:

CA XCOM Data Transport issued a FIND macro to position itself to the correct member in a partitioned data set but an I/O error occurred. The file transfer is terminated and this message is sent to the conversation partner.

Action:

The PDS should be restored from a backup before retrying the transfer request.


0267E

0268E

0269E

Message Syntax

DIRECTORY FIND FAILED DUE TO LACK OF VIRTUAL STORAGE

Reason:

CA XCOM Data Transport issued a FIND macro for a member of a partitioned data set but there was not enough virtual storage to fulfill the request. The file transfer is terminated and this message is sent to the conversation partner.

Action:

Ensure that the region size for CA XCOM Data Transport is large enough. If it is not, increase the address space region size and bring CA XCOM Data Transport down and up again. If the region size is large enough, issue a CA XCOM Data

Transport SNAP command and contact CA Technical Support.

R15 xx R0 yy ERROR RECEIVED ON DIRECTORY STOW

Reason:

CA XCOM Data Transport has issued a STOW macro to create or update a member of a PDS and has received return code xx yy. The file transfer is terminated and this message is sent to the conversation partner.

Action:

See the IBM documentation and take the appropriate action.

xxxxxxxx DUPLICATE MEMBER ON ADD FUNCTION

Reason:

CA XCOM Data Transport has attempted to add a member to a partitioned data set but the member already exists. Because the user has specified a file option of

CREATE or ADD, the file transfer is terminated and this message is sent to the conversation partner.

Action:

If you want to complete the file transfer, change the file option to REPLACE and retry the file transfer.


Message Syntax

0270E

NOT FOUND CONDITION RAISED ON DIRECTORY STOW

Reason:

CA XCOM Data Transport has issued a STOW macro and the not found condition was raised. This normally happens when an alias is being STOWed and the target member does not exist. The file transfer is terminated and this message is sent to the session partner.

Action:

Verify that the target member exists.

0271E

NO SPACE LEFT IN DIRECTORY

Reason:

CA XCOM Data Transport has issued a STOW macro for a partitioned data set, but there is no space left in the partitioned directory. The file transfer is terminated and this message is sent to the conversation partner.

Action:

If necessary, allocate more directory blocks to the PDS.

0272E

I/O ERROR WRITING TO PARTITIONED DIRECTORY

Reason:

CA XCOM Data Transport has issued a STOW macro to update the directory of a

PDS, but a return code indicating an I/O error was returned. The file transfer is terminated and this message is sent to the conversation partner.

Action:

The data set should be restored from a backup copy before trying to transfer it again.


0273E

0274E

0275E

Message Syntax

I/O ERROR WRITING EOF MARK ON DATA FILE

Reason:

CA XCOM Data Transport has issued a STOW macro that puts an EOF mark on the file, but an I/O error was encountered writing the EOF mark. The file transfer is terminated and this message is sent to the conversation partner.

Action:

The file should be restored or reallocated before attempting to transfer to it again.

DCB NOT OPEN ON DIRECTORY STOW

Reason:

CA XCOM Data Transport has issued a STOW macro for a partitioned data set but the DCB was not open. The file transfer is terminated and this message is sent to the conversation partner.

Action:

If this error persists, get a hard copy of the log and contact CA Technical

Support.

NO VIRTUAL STORAGE AVAILABLE FOR DCB STOW

Reason:

CA XCOM Data Transport has issued a STOW macro for a member of a PDS but there is insufficient virtual storage available for the STOW request. The file transfer is terminated and this message is sent to the conversation partner.

Action:

Ensure that sufficient virtual storage is available for the CA XCOM Data Transport address space. If there is enough virtual storage available, take a CA XCOM Data

Transport snap dump and contact CA Technical Support.


Message Syntax

0276E

ERROR ENCOUNTERED DEBLOCKING SPANNED BLOCK

Reason:

CA XCOM Data Transport was deblocking VBS or VS (that is, variable spanned) records and encountered an error in the deblock routine, such as a start of a block without an end of a block. The file transfer is terminated and this message is sent to the session partner.

Action:

Ensure that the spanned file was created properly. If this file can be used successfully by other programs, such as IDCAMS but not by CA XCOM Data

Transport, contact CA Technical Support.

0277E

LENGTH OF SPANNED RECORD GREATER THAN 32764

Reason:

CA XCOM Data Transport was reading a VB or a VBS file and detected a spanned record whose length was greater than 32764 bytes. Because this is the maximum record length that CA XCOM Data Transport supports, the file transfer is terminated and this message is sent to the conversation partner.

Action:

After ensuring that the maximum record length of the spanned record is less than 32764 bytes, retry the transfer request.

0278E

EOF ENCOUNTERED BEFORE SPANNED DEBLOCK COMPLETE

Reason:

CA XCOM Data Transport was attempting to deblock a variable spanned file. It was in the middle of a record but an end of file was encountered before CA XCOM

Data Transport could complete the record. The file transfer is terminated and this message is sent to the remote system.

Action:

Ensure that the spanned file is complete before attempting to transfer this file again.


0279E

0280E

0281I

Message Syntax

XCOM HISTORY FILE NOT OPEN ON UPDATE REQUEST

Reason:

A file transfer has completed either successfully or unsuccessfully and CA XCOM

Data Transport was attempting to write a history record, but the history file was not open. This does not affect a file transfer nor is this message sent to the conversation partner.

Action:

None

HISTORY PUT REQUEST INVALID—RPL ALREADY ACTIVE

Reason:

CA XCOM Data Transport was attempting to write a record to the history file but an error indicating that the RPL was already active was returned. This message is displayed for informational purposes only and is not sent to the remote system.

Action:

None

xxxxxxxx RC xx yy ON yyyyy VSAM HISTORY MACRO

Reason:

VSAM has returned code xx on a VSAM macro such as GENCB or MODCB when

CA XCOM Data Transport attempted to write a record to its history file. This message is displayed for informational purposes only and is not sent to the remote system.

Action:

None


Message Syntax

0282I

RC xx FDBK yy ON HISTORY FILE zzzzz REQUEST

Reason:

VSAM has received RC xx FDBK yy return codes on a PUT or a GET for the history file. This message is displayed for informational purposes only; it does not affect the file transfer and is not sent to the remote system.

Action:

None

0283E

ERROR OCCURRED ON RRQ/ADD/DELETE REQUEST

Reason:

CA XCOM Data Transport was attempting to add or delete an internal control block but an error was detected by the main CA XCOM Data Transport dispatching task.

Action:

If this error persists, take a SNAP dump of the CA XCOM Data Transport address space and contact CA Technical Support.

0284E

ENQ FAILED FOR APPLID xxxxxxxx

Reason:

CA XCOM Data Transport has issued an ENQ for its APPLID but the ENQ request failed. This is used to determine if a request that is to be scheduled is local to this system or is a remote request. CA XCOM Data Transport enqueues on both the

ACBNAME and APPLID. It is possible that two CA XCOM Data Transport installations running on different computers using GRS might designate the same ACBNAME. If this is the case, the ENQ would fail.

Action:

None


0285E

0286E

0287E

Message Syntax

XCOMRRDS DD STATEMENT MISSING—NOT LOGGING REQUESTS

Reason:

CA XCOM Data Transport was about to open the XCOMRRDS Restart File but

VSAM indicated that the DD statement was missing. If the XCOMRRDS Restart

File is not open, CA XCOM Data Transport will not initiate any local file transfers but it will perform file transfers initiated by the conversation partner.

Action:

Ensure that the XCOMRRDS DD statement is included in the CA XCOM Data

Transport server JCL.

XCOMRRDS OPEN ERROR xx yy—NOT LOGGING REQUESTS

Reason:

CA XCOM Data Transport was attempting to open the XCOMRRDS Restart File but VSAM returned an error code of xx yy. This return code is documented in the

IBM documentation. If the XCOMRRDS Restart File is not open, CA XCOM Data

Transport will not initiate any file transfers but it will perform file transfers initiated by the conversation partner.

Action:

None

XCOMRRDS NOT DEFINED AS RRDS—NOT LOGGING REQUESTS

Reason:

CA XCOM Data Transport has successfully opened the XCOMRRDS Restart File but the file was not defined as an RRDS file.

Action:

Ensure that the procedures for defining the RRDS file are followed correctly. If the XCOMRRDS Restart File is not defined properly CA XCOM Data Transport will not initiate any file transfers, but it will perform file transfers initiated by the conversation partner.


Message Syntax

0288E

XCOMRRDS RECLEN INVALID—S/B xxxx BYTES

Reason:

CA XCOM Data Transport has successfully opened the XCOMRRDS Restart File but the record length defined for the RRDS file is not 2020 bytes. If the

XCOMRRDS Restart File is not defined properly, CA XCOM Data Transport will not initiate any file transfers but it will perform file transfers initiated by the conversation partner.

Action:

Ensure that the procedures for defining the XCOMRRDS Restart File are followed correctly.

0289E

XCOMRRDS xxx ERROR CODE yy zz AT RRDS INITIALIZATION

Reason:

CA XCOM Data Transport was reading the XCOMRRDS Restart File at CA XCOM

Data Transport initialization time but error code yy zz was returned from VSAM.

xxx defines the type of request on which the error occurs. CA XCOM Data

Transport will bypass this record and continue to the next record.

Action:

None

0290E

XCOMRRDS ERROR COUNT EXCEEDED AT RRDS INITIALIZATION

Reason:

At initialization time CA XCOM Data Transport has received more than 10 errors reading the XCOMRRDS Restart File. CA XCOM Data Transport will stop reading the RRDS file at this point.

Action:

Additional messages follow this one. Review accompanying messages to determine the actual cause of the error.


0291I

0292I

0293E

Message Syntax

FOLLOWING REQUEST AGED FROM THE SYSTEM AT STARTUP

Reason:

CA XCOM Data Transport has aged (that is, removed) a request from the

XCOMRRDS file based on the age associated with the request or the default AGE values defined in the Default Options Table via the AGE and REMAGE parameters.

Action:

None

ID=xxxxxxxxxx,NAME=yyyyyyyy,REQ=yyyyyy yyyyyy

Reason:

This message describes a transfer request that was aged off the system (see

Message 0291I). The ID, NAME, and REQ are displayed. NAME indicates either the LU name or the Group name, as appropriate. Also displayed is an indication of whether the transfer was locally or remotely initiated.

Action:

None

XCOMHIST DD STATEMENT MISSING—NOT LOGGING HISTORY

Reason:

CA XCOM Data Transport was attempting to open the XCOMHIST History File but

VSAM issued a return code indicating that the DD statement was not defined in the CA XCOM Data Transport start-up JCL. CA XCOM Data Transport will not log any data to the History File, but will initiate local requests and accept remote initiates from the conversation partner.

Action:

If you wish to maintain a History File, then add the necessary DD statement to the CA XCOM Data Transport server JCL (see the chapter ―The Batch Interface‖ in the CA XCOM Data Transport for z/OS User Guide).


Message Syntax

0294E

XCOMHIST OPEN ERROR xx yy—NOT LOGGING HISTORY

Reason:

CA XCOM Data Transport has attempted to open the XCOMHIST History File but

VSAM returned code xx yy. It will initiate file transfer requests and honor incoming requests but no requests will be logged to the History File.

Action:

Look up this code in the IBM documentation and take the appropriate action.

0295E

XCOMHIST NOT DEFINED AS KSDS—NOT LOGGING HISTORY

Reason:

CA XCOM Data Transport has successfully opened the XCOMHIST History File but the file was not defined as a KSDS file. It will initiate file transfer requests and honor incoming requests but no requests will be logged to the History File.

Action:

Ensure that installation procedure for XCOMHIST was followed properly.

0296E

XCOMRRDS SLOTS EXHAUSTED—NOT LOGGING REQUEST#

Reason:

CA XCOM Data Transport has exhausted all of the slots (that is, records) available in the XCOMRRDS Restart File. As a result, CA XCOM Data Transport will not maintain the information required to restart the file transfer request should the server terminate before the request completes.

Action:

Consider deleting and reallocating the XCOMRRDS Restart File with more records to minimize the likelihood that this condition will occur again.


0297I

0298I

0299E

Message Syntax

REQUEST PROCESSED ON LOCAL SYSTEM

Reason:

CA XCOM Data Transport is attempting to schedule a request to the CA XCOM

Data Transport server and has determined that CA XCOM Data Transport is running on the same system.

Action:

None. This message is displayed for informational purposes only.

REQUEST PROCESSED ON REMOTE SYSTEM

Reason:

CA XCOM Data Transport is about to schedule a file transfer with the CA XCOM

Data Transport server and has determined that the server is executing on a remote system.

Action:


INVALID SESSION PARMS FOR XCOM SCHEDULE—MUST BE LU6

Reason:

CA XCOM Data Transport has attempted to allocate a session so that a file transfer can be scheduled but the session created was not an LU session. The schedule request is terminated at this point.

Action:

Ensure that the LOGMODE/MODETAB definitions are correct and that all CA

XCOM Data Transport APPL definitions have the proper DLOGMOD/MODETAB definitions (see the chapter ―Configuring the Network‖ in the CA XCOM Data

Transport for z/OS Administration Guide).


Message Syntax

0300I

REQUEST # xxxxxx PROCESSED SUCCESSFULLY

Reason:

CA XCOM Data Transport has successfully scheduled a file transfer request. The

CA XCOM Data Transport address space on which the request is scheduled displays this message and sends it to the user requesting the schedule operation. xxxxxx is the request number assigned to the file transfer request.

Action:

None

0301E

INVALID DATA POINTER PASSED TO PSO SUBTASK

Reason:

An internal error occurred in attaching the Process SYSOUT task.

Action:


0302E

PSO TABLE POINTER INVALID—PSO SUBTASK TERMINATING

Reason:

An internal error occurred in attaching the Process SYSOUT task.

Action:


0303I

PSO SUBTASK TERMINATING NORMALLY

Reason:

The Process SYSOUT task terminated normally as the result of shutting down CA

XCOM Data Transport through a console P CA XCOM Data Transport or F

XCOM,STOP command.

Action:

None


0304E

0305E

0306E

0307E

Message Syntax

xxxxxxxx DEST ERROR CODE yy ON SYSOUT INQUIRY

Reason:

A Process SYSOUT inquiry received error code yy for destination xxxxxxxx. The destination is put into a temporary error state.

Action:

The error should reset itself at the next CA XCOM Data Transport error reset interval. If this error persists, contact CA Technical Support.

xxxxxxxx JOB NOT FOUND ON SYSOUT INQUIRY

Reason:

An error occurred during a CA XCOM Data Transport destination inquiry for the destination xxxxxxxx.

Action:


xxxxxxxx INVALID SEARCH ARGUMENT ON SYSOUT INQUIRY

Reason:

An invalid search argument was passed to the Process SYSOUT destination inquiry routine for the destination xxxxxxxx.

Action:


xxxxxxxx PSO INTERFACE UNABLE TO PROCESS INQUIRY

Reason:

The Process SYSOUT routine was unable to process an inquiry request for the destination xxxxxxxx. This will happen occasionally due to timing considerations within the JES address space.

Action:



Message Syntax

0308E

xxxxxxxx DUPLICATE JOBNAMES ON PSO INQUIRY

Reason:

An error occurred when the Process SYSOUT routine was attempting to process an inquiry request for the destination xxxxxxxx. JES detected duplicate job names on the JES queue.

Action:


0309E

xxxxxxxx INVALID JOBNAME/JOBID ON PSO INQUIRY

Reason:

An error occurred when the Process SYSOUT routine was attempting to process an inquiry request for the destination xxxxxxxx. An invalid job name and job number combination was encountered.

Action:


0310E

xxxxxxxx DESTINATION INVALID ON PSO INQUIRY

Reason:

An error occurred when the Process SYSOUT routine was attempting to process an inquiry request for the destination xxxxxxxx. This destination was invalid.

This causes the destination to be put into a permanent error state.

Action:

Check that this destination, as defined in the Destination Table (see the chapter

―Configuring and Customizing CA XCOM Data Transport‖ in the CA XCOM Data

Transport for z/OS Administration Guide) is a valid JES destination.


0311E

0312E

0313E

Message Syntax

xxxxxxxx DEST ERROR CODE yy ON SYSOUT INQUIRY

Reason:

An error occurred when the Process SYSOUT routine was attempting to process an inquiry request for the destination xxxxxxxx. An undefined return code yy was encountered. The destination is put into a temporary error state.

Action:


xxxxxxxx DELETE FAILED R15 = yy

Reason:

A Process SYSOUT delete request failed with an R15 return code yy. The destination is put into a temporary error state.

Action:


xxxxxxxx DELETE FAILED RTNCD = yy

Reason:

A Process SYSOUT delete request failed with the process SYSOUT error code yy.

Destination xxxxxxxx is placed into a temporary error state.

Action:



Message Syntax

0314E

xxxxxxxx ERROR nnnn nnnn RECEIVED ON PSO DYNAMIC ALLOCATION

Reason:

Error code nnnn nnnn occurred during dynamic allocation for the JES Process

SYSOUT File or a temporary data set for the destination xxxxxxxx. The destination is placed into a temporary error state.

Action:

If the abend code indicates an out of space condition, ensure that adequate space is defined in the SEC and PRI parameters in the Default Options Table.

Also, ensure that there is sufficient space on the default volume and unit defined in the Default Options Table.

0315E

xxxxxxxx ABEND yyy-zzz RECEIVED

Reason:

The DCB abend exit intercepted abend code yyy-zzz for the destination

xxxxxxxx. The destination is placed into a temporary error state. An abend message should accompany this message.

Action:

Review the recommended action for the abend message.

0316E

xxxxxxxx OPEN FAILED FOR JES FILE—DELETED

Reason:

An OPEN request for a JES Process SYSOUT file failed. The request associated with the destination xxxxxxxx is placed into a temporary error state. An abend message should accompany this message.

Action:

Review the recommended action for the abend message.


0317E

0318E

0319E

Message Syntax

xxxxxxxx OPEN FAILED FOR TEMPORARY FILE

Reason:

The CA XCOM Data Transport Process SYSOUT Interface was attempting to open a temporary work file to hold the Process SYSOUT data, but it failed. The destination is marked as in error and the request is retried at the next error interval.

Action:

None

xxxxxxxx ERROR xxxx xxxx RECEIVED ON PSO DYNAMIC

UNALLOCATION

Reason:

CA XCOM Data Transport has attempted to deallocate a Process SYSOUT or temporary file, but received error code xxxx xxxx from SVC 99.

Action:

For a description of the error, see the IBM documentation.

ESTAE RETURN CODE xx RECEIVED BY PSO SUBTASK

Reason:

The CA XCOM Data Transport Process SYSOUT Interface program received a bad return code after executing the ESTAE macro. CA XCOM Data Transport will continue without the ESTAE exit.

Action:

None


Message Syntax

0320E

INVALID JES INTERVAL DEFINED—DEFAULTING TO 60 SECONDS

Reason:

The CA XCOM Data Transport Process SYSOUT Interface has determined that the

JES interval is invalid (see the description of the JESINTV parameter in the chapter ―Configuring and Customizing Your Product‖ in the CA XCOM Data

Transport for z/OS Administration Guide). It will use the default value of 60 seconds.

Action:

None

0321E

xxxxxxxx RELEASE FAILED R15=yy

Reason:

A Process SYSOUT release function failed with return code yy for the destination

xxxxxxxx. Destination xxxxxxxx is placed into a temporary error state.

Action:


0322E

xxxxxxxx JOB NOT FOUND ON DELETE—IGNORED

Reason:

CA XCOM Data Transport finished processing a file transfer request and, in attempting to delete the job which initiated the request, CA XCOM Data

Transport was unable to find the job. Destination xxxxxxxx is placed into a temporary error state. This error can occur if a job is deleted after CA XCOM Data

Transport queues it but before CA XCOM Data Transport finishes processing it.

Action:



0323E

0324E

0325E

Message Syntax

xxxxxxxx RETURN CODE XX ON DELETE JOB INQUIRY

Reason:

CA XCOM Data Transport tried to delete a PSO data set after a transfer, but the return code was not equal to zero (the data set was probably deleted by some other means).

Action:

None

LOGOFF COMMAND ENTERED EXPECTING DATA—SESSION ENDING

Reason:

CA XCOM Data Transport received a LOGOFF request from its conversation partner. This message is valid for CA XCOM Data Transport for z/OS Version 1 only.

Action:

None

SYNAD ENTERED FOR JES DEST—xxxxxxxx

Reason:

The DCB SYNAD routine has been entered for a Process SYSOUT or a temporary data set. Destination xxxxxxxx is placed into a temporary error state. An accompanying z/OS message should be issued which will describe the error.

Action:

Look up this error in the z/OS log.


Message Syntax

0326I

xxxxxxxx NOW QUEUEING JOB yyyyyyyy zzzzzzzz

Reason:

CA XCOM Data Transport is queueing job name yyyyyyyy, and job number

zzzzzzzz for LU xxxxxxxx. CA XCOM Data Transport will begin the transfer when

LU xxxxxxxx is ready to receive the transfer.

Action:

None

0327E

xxxxxxxx yyyyyyyy EMPTY DATASET—DELETED

Reason:

CA XCOM Data Transport has attempted to queue a file transfer request, but job name xxxxxxxx, and job number yyyyyyyy was empty. The data set is deleted.

Action:

None

0328I

XCOMREST FILE NOT OPEN—RRDS REQUEST ABORTED

Reason:

The XCOMJOB Batch Interface has attempted to perform a request that wrote data to the XCOMREST file (the sequential restart file), but that file was not open.

Action:

None


0329E

0330I

0331E

Message Syntax

DATA SET NOT FOUND ON THE VOLUME SPECIFIED

Reason:

CA XCOM Data Transport could not find the specified data set. Either the data set name is wrong or the volume name is wrong.

Action:

Check that both the data set name and volume name are accurate and retry the operation. Otherwise, contact CA Technical Support.

PRIMARY SUBSYSTEM IS xxxx

Reason:

CA XCOM Data Transport has determined the primary Job Entry Subsystem for the system it is running on.

Action:

None

xxxxxxxx ERROR nnnn nnnn ON PSO DELETE DYNAMIC UNALLOCATION

Reason:

Attempting to delete a JES data set through a dynamic allocation request, CA

XCOM Data Transport received error code nnnn nnnn for the destination

xxxxxxxx. The destination is placed into a temporary error state.

Action:

For an explanation of this return code consult the IBM documentation. If this error persists, contact CA Technical Support.


Message Syntax

0332E

xxxxxxxx ERROR nnnn nnnn ON PSO DELETE DYNAMIC ALLOCATION

Reason:

CA XCOM Data Transport has received error code nnnn nnnn, while attempting to allocate a JES data set for the destination xxxxxxxx. Destination xxxxxxxx is placed into a temporary error state.

Action:

For an explanation of this return code, consult the IBM documentation. If this error persists, contact CA Technical Support.

0333E

INVALID DATA RECEIVED ON RESTART REQUEST

Reason:

Invalid data was received by CA XCOM Data Transport when it attempted to perform a file transfer restart operation with the conversation partner. The file transfer request is cancelled and this message is sent to the conversation partner.

Action:


0334E

MEMBER xxxxxxxx NOT FOUND ON RESTART REQUEST

Reason:

CA XCOM Data Transport was attempting to perform a restart operation on a PDS but could not find the last member (xxxxxxxx) being processed. It is possible that the PDS has changed since CA XCOM Data Transport ran the file transfer.

The file transfer will be terminated and this message will be sent to the session partner.

Action:

If necessary, re-initiate the file transfer from the beginning.


0335E

0336E

0337E

Message Syntax

RESTART NOT SUPPORTED FOR OUTPUT ESDS FILES

Reason:

CA XCOM Data Transport attempted to restart a file transfer for an ESDS file.

However, CA XCOM Data Transport does not support restart for an ESDS file due to the limitations of VSAM. The file transfer will be terminated and this message will be sent to the conversation partner.

Action:


VSAM RESTART SUPPORTED ONLY FOR REPLACE TRANSFERS

Reason:

CA XCOM Data Transport was attempting to restart a file transfer for a VSAM

KSDS or RRDS file. However, CA XCOM Data Transport only supports restarts for

VSAM files with a CA XCOM Data Transport file option of REPLACE, and this has not been specified. The file transfer will be terminated and this message will be sent to the session partner.

Action:


GDG CREATE FUNCTION INVALID->99 NEW GENERATIONS

Reason:

CA XCOM Data Transport was attempting to create a new GDG file, but has already created 99 generations of that data set. CA XCOM Data Transport has a limit of 99 new generations of a GDG for a DSN. This message is sent to the conversation partner and the file transfer is terminated.

Action:

Delete some generations of the GDG file or specify another GDG file.


Message Syntax

0338E

VSAM ENDREQ ERROR CODE yy zz

Reason:

VSAM has returned error code yy zz to the VSAM ENDREQ macro, which forces the buffers to be flushed. The file transfer will be terminated and this message will be sent to the conversation partner.

Action:

Look up the indicated return codes in a VSAM reference manual and take the appropriate action.

0339I

REMOTE RESTART REQUEST STARTED ON xxxxx RECORD yyyyyyy

Reason:

CA XCOM Data Transport has received a request for a file transfer to restart. CA

XCOM Data Transport has determined that it can honor that request and will restart on record number yyyyy. xxxxx will be either ALPHA or BETA.

Action:

None

0340E

INVALID RESTART REQUEST—ALPHA COUNT ZERO

Reason:

CA XCOM Data Transport has received a file transfer restart request from its conversation partner, but its internal tables indicate no checkpoints were taken.

This message will be returned to the session partner and the file transfer will be restarted from the beginning of the file.

Action:

None


0341E

0342E

0343E

Message Syntax

RESTART NOT ALLOWED FOR REMOTELY INITIATED RECEIVE OF A JOB

OR REPORT—REQUEST DELETED

Reason:

CA XCOM Data Transport has received a file transfer restart request for a JOB transfer, but does not support the restart of a JOB and the request is deleted from the queue. This message will be sent to the conversation partner.

Action:

None

DATASET NAMES DO NOT MATCH ON RESTART REQUEST

Reason:

CA XCOM Data Transport has received a file transfer restart request but the data set name on the restart file does not match the data set name provided by the session partner. This message is sent to the conversation partner and file transfer will be restarted from the beginning of the file.

Action:

None

ALPHA/BETA RESTART COUNTS DO NOT MATCH

Reason:

CA XCOM Data Transport has received a restart request from the conversation partner, but the record counts on the restart file do not the match the record counts provided by the conversation partner. This message is sent to the conversation partner and the file transfer will be restarted from the beginning of the file.

Action:

None


Message Syntax

0344E

BETA COUNT 0 ON RESTART REQUEST

Reason:

CA XCOM Data Transport has received a file transfer restart request but the restart record number is zero. This indicates that no records had been received before the file transfer was terminated. This message is sent to the conversation partner and the file transfer is restarted from the beginning.

Action:

None

0345E

RESTART FAILURE—MATCHING REQUEST NOT FOUND

Reason:

CA XCOM Data Transport has received a restart request from the conversation partner but could not find a match to that request in the CA XCOM Data

Transport restart file. This message is transmitted to the conversation partner and the file transfer is restarted from the beginning.

Action:

None

0346E

xxxxxxxxxx ERROR ON TRANSFER REQUEST HEADER

Reason:

CA XCOM Data Transport has detected an error on a field passed to it by the conversation partner when it attempted to start the file transfer. xxxxxxxx describes the field in error. CA XCOM Data Transport terminates the conversation and sends this message to the conversation partner.

Action:

If this message persists, contact CA Technical Support. Be prepared to take a CA

XCOM Data Transport trace if required.


0347I

0348E

0349E

Message Syntax

FILE TRANSFER INITIATED LOCALLY

Reason:

CA XCOM Data Transport has initiated a file transfer to its conversation partner.

This message indicates that the conversation partner has accepted the request and will begin the file transfer.

Action:

None

GENERIC MEMBERS NOT SUPPORTED IN RELEASE 1 MODE

Reason:

CA XCOM Data Transport was performing a file transfer to another CA XCOM

Data Transport system and was running in release 1 mode. A generic file transfer was specified but generic file transfers in release 1 mode are not supported. The file transfer is terminated and this message is sent to the conversation partner if the partner initiated the file transfer.

Action:

If necessary, transfer the files using specific file names.

RESTART INVALID ON JOB TRANSFER

Reason:

CA XCOM Data Transport received a restart request for a job file transfer but does not support the restart on a job. This message is sent to the conversation partner and the file transfer will be restarted from the beginning.

Action:

None


Message Syntax

0350E

MULTIPLE MEMBERS OF A LIBRARY CANNOT BE TRANSFERRED TO A

SEQUENTIAL FILE—TRANSFER TERMINATED

Reason:

CA XCOM Data Transport has received a request for a file transfer but has determined that the source file is a library and the target file is a sequential file.

CA XCOM Data Transport does not support the reading of multiple members of a

PDS into a sequential file. This message may appear after the first member of a library is transferred and CA XCOM Data Transport is ready to transfer a second member, because it is legitimate to send one member of a PDS to a sequential file. This message is sent to the conversation partner and the transfer will be terminated.

Action:

None

0351I

DSN IS xxxxxxxx

Reason:

CA XCOM Data Transport has received a file transfer request that created a new

GDG file. CA XCOM Data Transport will tell the conversation partner the actual name of GDG created. This message is displayed on the system that initiated the file transfer.

Action:

None

0352E

VSAM RPL ERROR ON xxxxxxxx REQUEST

Reason:

VSAM has encountered an error processing a CA XCOM Data Transport request.

This error indicates that the VSAM RPL is already in use. The file transfer is terminated and this message is sent to the conversation partner.

Action:

If this error persists, contact CA Technical Support. Be prepared to take a CA



0353E

0354E

0355E

Message Syntax

xxxxxxxx MEMBER NOT FOUND DURING BLDL PROCESSING

Reason:

One of the following occurred:

1. CA XCOM Data Transport was performing a BLDL to find the member

(xxxxxxxx) that an alias points to but could not find the base member.

2. A PDS was being transferred with PACK=LENGTH specified.

Action:

Do one of the following, depending on which error occurred:

1. Remove invalid alias from data set.

2. Specify PACK=NO when transferring a PDS.

I/O ERROR ENCOUNTERED DURING BLDL PROCESSING

Reason:

CA XCOM Data Transport was performing a BLDL to find the base member of an alias but an I/O error was encountered. The file transfer is terminated and this message is sent to the session partner.

Action:

Restore the file from a recent backup copy if possible.

INSUFFICIENT VIRTUAL STORAGE FOR BLDL COMMAND

Reason:

CA XCOM Data Transport was performing a BLDL to find the base member of an alias, but the BLDL could not be performed due to a lack of internal storage. This message is transmitted to the session partner and the file transfer is terminated.

Action:

Ensure that sufficient virtual storage is allocated to the CA XCOM Data Transport address space.


Message Syntax

0367I

xxxxxxxx BLOCKS yyyyyyyy RECS RECEIVED SUCCESSFULLY

Reason:

CA XCOM Data Transport has successfully completed a receive type file transfer.

xxxxxxxx blocks and yyyyyyyy records were received.

Action:

None

0373I

xxxxxxxx BLOCKS yyyyyyyy RECS SENT SUCCESSFULLY

Reason:

CA XCOM Data Transport has successfully completed a send type file transfer.

xxxxxxxx blocks and yyyyyyyy records were sent.

Action:

None

0380E

xxxxxxxx MEMBER NOT FOUND FOR ALIAS TTR

Reason:

CA XCOM Data Transport is attempting to find the base member for an alias, but is unable to find it. This could happen if the alias exists but the base member does not exist. This message is displayed, the alias record is bypassed, and CA

XCOM Data Transport continues with the file transfer.

Action:

Remove the invalid alias from the data set.


0381E

0382E

0383E

Message Syntax

REQUEST # NOT ENTERED FOR xxxxxxxx REQUEST

Reason:

The CA XCOM Data Transport for z/OS console operator has entered request type xxxxxxxx but the user did not enter the request number.

Action:

Check the chapter ―Operation and Control‖ in the CA XCOM Data Transport for

z/OS User Guide for the proper syntax of the operator console commands.

REQUEST # xxxxxx FOR xxxxxxxx NOT NUMERIC

Reason:

The CA XCOM Data Transport for z/OS console operator has entered an operator command but the request number entered was not numeric.

Action:


z/OS User Guide for the proper syntax of the operator console commands.

REQUEST # xxxxxx FOR xxxxxxxx NOT FOUND

Reason:

The CA XCOM Data Transport for z/OS console operator has entered a request but the request number was not found in the CA XCOM Data Transport address space.

Action:

Use the SHOW and RSHOW commands, respectively, to display the request numbers of all local and remote CA XCOM Data Transport requests.


Message Syntax

0384E

REQUEST # xxxxxx FOR xxxxxxxx NOT HELD

Reason:

The CA XCOM Data Transport for z/OS console operator has attempted to release a file transfer request but this request was not held.

Action:

Check whether or not you specified the correct request number.

0385E

REQUEST # xxxxxx FOR xxxxxxxx STATUS ACTIVE

Reason:

The CA XCOM Data Transport for z/OS console operator has attempted to delete a file transfer but the transfer is active.

Action:

To terminate an active file transfer, use the TERM operator command.

0386E

REQUEST # xxxxxx FOR xxxxxxxx ALREADY HELD

Reason:

The CA XCOM Data Transport for z/OS console operator has attempted to hold a file transfer but the request is already on hold.

Action:

None

0387E

REQUEST # xxxxxx FOR xxxxxxxx NOT SUSPENDED

Reason:

The CA XCOM Data Transport for z/OS console operator has attempted to resume a suspended file transfer request but the request was not suspended.

Action:

Reissue the command, specifying a suspended transfer.


0388I

0389I

0390E

Message Syntax

NO LOCALLY INITIATED REQUESTS FOR SHOW/RSHOW COMMAND

Reason:

The CA XCOM Data Transport for z/OS console operator has entered a SHOW or

RSHOW command but there are no requests on the local (or remote) queue.

Action:

None

REQ#=nnnnnn, STATUS=xxxxxxxx, USER=aaaaaaaaaaaa, NAME= yyyyyyyy

Reason:

This message is displayed for each file transfer request found by the SHOW or

RSHOW processing.

Action:

None

BAD OPERATOR COMMAND RECEIVED IN XCOMCONS

Reason:

The CA XCOM Data Transport for z/OS console operator has entered a console command but CA XCOM Data Transport had an internal error processing the command.

Action:

If this error occurs, retain the CA XCOM Data Transport log and contact CA

Technical Support.


Message Syntax

0391I

xxxxxxxx COMMAND FOR REQ# nnnnn SUCCESSFUL

Reason:

The CA XCOM Data Transport for z/OS console operator has entered a command that has been successfully processed.

Action:

None

0392E

OPERATOR COMMAND ENDED DUE TO RRDS FILE ERRORS

Reason:

The CA XCOM Data Transport for z/OS console operator has entered an operator control command but the command was terminated because of an error processing the RRDS file. The exact error code should be displayed in an accompanying message.

Action:

Review the additional message to determine the exact cause of the error.

0393E

SYSOUT TABLE ENTRY NOT FOUND FOR DELETE REQ nnnnnn

Reason:

The CA XCOM Data Transport for z/OS console operator has attempted to delete a Process SYSOUT request but CA XCOM Data Transport could not find the destination table entry.

Action:

If this error persists, take a CA XCOM Data Transport SNAP dump and contact CA

Technical Support.


0394E

0395E

0396E

Message Syntax

JOB SUBMISSION ABORTED—CANNOT INSERT COMMA

Reason:

CA XCOM Data Transport was brought up with security options of USER, RACF, or

TOP SECRET. A CA XCOM Data Transport user was performing a job submission and the last column of the JOB card ended in position 71. CA XCOM Data

Transport attempts to add a card with the USERID and PASSWORD at the end of the JOB statement, but cannot because column 71 is the last column used for continuation purposes. The file transfer is terminated and this message is sent to the conversation partner.

Action:

If necessary, change the JOB card so that CA XCOM Data Transport can insert a continuation properly.

RECORD LENGTH ERROR FOUND ON DECOMPRESSION >32764

Reason:

CA XCOM Data Transport was in the process of decompressing a record on a receive request. In decompressing the record the length of the record was greater than 32764 bytes, CA XCOM Data Transport terminates the file transfer and sends this message to the session partner.

Action:

Try performing the file transfer without compression to see if the file transfer works. If this error persists, contact CA Technical Support. Be prepared to take a

CA XCOM Data Transport trace if required.

HOLD PARAMETER NOT VALID FOR TYPE=EXECUTE TRANSFER

Reason:

The user has attempted to perform an immediate file transfer using the CA XCOM

Data Transport TYPE=EXECUTE parameter, but the user specified HOLD=YES.

This parameter is invalid with the TYPE=EXECUTE parameter. The file transfer is terminated and this message is displayed on the system that initiated the file transfer.

Action:

Change the transfer to either TYPE=SCHEDULE or HOLD=NO.


Message Syntax

0397I

MEMBER xxxxxxxx TRANSMITTED SUCCESSFULLY

Reason:

CA XCOM Data Transport has begun a library file transfer. Each time a member

(xxxxxxxx) is successfully transmitted, this message is written to the CA XCOM

Data Transport log. It is not displayed on a TSO or operator console.

Action:

None

0398I

MEMBER xxxxxxxx BEING RECEIVED

FILE BEING RECEIVED = xxxxxx

Reason:

CA XCOM Data Transport has begun a library file transfer. Each time a member

(xxxxxxxx) or file (xxxxxx) is being received, this message is written to the CA

XCOM Data Transport log. It is not displayed on a TSO or operator console.

The FILE version of the message applies to USS files only.

Action:

None

0399I

xxxxxx MEMBERS TRANSMITTED SUCCESSFULLY

Reason:

CA XCOM Data Transport has just completed a library file transfer either successfully or unsuccessfully. This message is displayed to show how many members (xxxxxx) have been transmitted successfully.

Action:

None


0400I

0401E

0402I

Message Syntax

xxxxxx MEMBERS RECEIVED SUCCESSFULLY xxxxxx FILES RECEIVED SUCCESSFULLY

Reason:

CA XCOM Data Transport has just completed a library file transfer either successfully or unsuccessfully. This message is displayed to show how many members or files (xxxxxx) have been successfully received.

Action:

None

xxxxxxxx NAME MATCHED XCOM APPLID—ERROR

Reason:

A user is attempting to schedule a file transfer operation but the destination LU

(xxxxxxxx) was the same as the APPLID of the CA XCOM Data Transport server address space. Because CA XCOM Data Transport cannot transfer a file to itself, the file transfer is terminated. The scheduled request is rejected and this message is sent to the system that requested the transfer.

Action:

None

REQUEST NUMBER xxxxxx ASSIGNED TO TRANSFER REQUEST

Reason:

CA XCOM Data Transport has successfully scheduled a file transfer request and has assigned request number xxxxxx to the request. This message is displayed by the server and is sent to the user that initiated the file transfer.

Action:

None


Message Syntax

0403E

EOF ENCOUNTERED ON VSAM RESTART OPERATION

Reason:

CA XCOM Data Transport has attempted to perform a restart operation on a

VSAM file, but the end-of-file condition was encountered. The file transfer is terminated and this message is sent to the conversation partner.

Action:


0404E

SYSIN/SYSOUT DATA SETS CANNOT BE SCHEDULED

Reason:

The CA XCOM Data Transport user has attempted to schedule a file transfer but the LCLDS01 DD statement defines a SYSIN (that is, DD *) or SYSOUT file.

Because CA XCOM Data Transport cannot pass this information to the server, the scheduled operation fails.

Action:

Change the local LCLDS01 DD statement so that it does not specify a SYSIN or

SYSOUT file.

0405E

CONFLICT BETWEEN TRANSFER TYPE AND FILE TYPE

Reason:

A user is attempting to perform a file transfer operation, but a conflict exists between the type of file transfer and the file type. For example, trying to receive a file defined as DD * or sending a file defined as a SYSOUT file would be a conflict.

Action:

Check the chapter ―The Batch Interface‖ in the CA XCOM Data Transport for z/OS

User Guide for the various combinations of file transfers that are permitted.


0406E

0407E

0408E

Message Syntax

INVALID DATA ENTERED ON THE ISPF OPERATOR REQUEST

Reason:

The CA XCOM Data Transport Menu Interface has attempted to perform an

―operator request‖ type function but CA XCOM Data Transport does not recognize the data entered.

Action:

See the chapter ―The Menu Interface (TSO/ISPF Panels)‖ in the CA XCOM Data

Transport for z/OS User Guide to verify that a valid function was entered. If it was correct, print a copy of the screen and contact CA Technical Support.

CONVERSATION FAILED DUE TO ERRORS

Reason:

This message is displayed when an operator control function is terminated due to errors. Often an accompanying message describes the actual error.

Action:

If this message persists, contact CA Technical Support. Be prepared to take a CA


xxxxxxxx DD STATEMENT MISSING—INQUIRY LIMITED

Reason:

At CA XCOM Data Transport start-up CA XCOM Data Transport attempts to open all of the history files. xxxxxxxx indicates the DDNAME of the history file that could not be opened because the DD statement was not defined. CA XCOM Data

Transport will operate but operator inquiry via the TSO/ISPF panels may be limited.

Action:

Add the DD statement for this history file to the CA XCOM Data Transport server

JCL.


Message Syntax

0409E

xxxxxxxx OPEN ERROR xx yy—INQUIRY LIMITED

Reason:

CA XCOM Data Transport has attempted to open history file xxxxxxxx but has received VSAM error code xx yy. CA XCOM Data Transport will continue to operate but operator inquiry via the TSO/ISPF panels may be limited.

Action:

This return code is documented in the IBM documentation. Check this guide for the appropriate action.

0410E

INVALID COMMAND ENTERED ON XCOM OPER CONVERSATION

Reason:

The Menu Interface user has attempted to perform an invalid operator-type (that is, Option 3) control function.

Action:


0411E

xxxxxxxx ERROR—ENTRY NOT AN ACTIVE TASK

Reason:

The CA XCOM Data Transport operator has attempted to perform an operator control function on a request that has ceased to be active.

Action:

Reissue the display command to perform an operator control function on an active request.


0412I

0413E

0414E

0415E

Message Syntax

xxxxxxxx COMMAND COMPLETED SUCCESSFULLY

Reason:

The CA XCOM Data Transport user has executed a command such as HOLD or

SUSPEND and the request has been successfully executed.

Action:

None

REQUEST CORRELATOR NOT PRESENT—REQUEST DENIED

Reason:

The CA XCOM Data Transport user was attempting to perform an operator control function, but the request correlator was not transmitted to the CA XCOM

Data Transport server by the CA XCOM Data Transport ISPF Menu Interface.

Action:


NON NUMERIC DATA ENTERED ON ALTER COMMAND

Reason:

The operator has attempted to perform an ALTER command but has entered non-numeric data. The request is denied.

Action:


z/OS User Guide for the syntax of this command.

REQUEST NOT HELD—CANNOT RELEASE

Reason:

The user has attempted to perform a release request but this file transfer request was not held. This message is displayed on the user's TSO screen.

Action:

Check that you are attempting to release the correct request number.


Message Syntax

0416E

REQUEST NOT SUSPENDED—CANNOT RESUME

Reason:

The user has attempted to perform a resume request, but the file transfer request was not suspended. This message is displayed on the user's TSO screen.

Action:

Check that you are attempting to resume the correct request number.

0417E

RECORD NOT FOUND ON RRDS FILE REQUEST

Reason:

CA XCOM Data Transport has attempted to read the CA XCOM Data Transport

RRDS file to initiate a file transfer request, but CA XCOM Data Transport could not find the record on the RRDS file. This can be caused by a timing error between the time that the request was put onto the file and the time that it was actually written to the RRDS file. The node will be put into an error state, and the request will be retried at the next error interval.

Action:

None

0418E

NO ELIGIBLE SERVER FOUND TO ACCEPT xxxxxxxxx REQUEST

Reason:

xxxxxxxxx is the type of request.

If this message is in response to a SCHEDULE request, no XCOMPLEX Worker

Servers are active. At least one XCOMPLEX Worker Server must be active to successfully schedule a transfer to the XCOMPLEX Admin Server. Or, the only available XCOMPLEX Worker Server is the destination SNA LU.

If this message is in response to an INQUIRE request, the INQUIRE data set contains transfers for more than one XCOMPLEX ADMIN.

Action:

For a SCHEDULE request, make sure at least one XCOMPLEX Worker Server is active and in session with the XCOMPLEX Admin Server and the XCOMPLEX

Worker Server is not the destination SNA LU.

For an INQUIRE request, create a new unique INQUIRE data set and use in only one XCOMPLEX.


0419I

0420I

0421I

Message Syntax

REQ#=nnnnnn ID=XXXXXX STATUS=XXXXXXXX

IPNAME=999.999.999.999 (or LUNAME=)

TYPE= FILETYPE= COUNT=999999999

LCL USER= SDATE=YYYYMMDD STIME=9999

REM USER= SPRTY=99

AGE=999 PSO=

RECSEP=

GROUP=

PACK=

CKPT=9999

TDUDATA= TRUNCATE=

INITIATE=

EPRTY=99

CODE=

COMPRESS=

SYSUDATA=

FILEOPT=

Reason:

This message is displayed as the result of a CA XCOM Data Transport SHOW or

RSHOW command entered with a request number.

Action:

None

LDSN=local_data set_name

Reason:


RSHOW command entered with a specific request number and shows the local data set name.

Action:

None

RDSN=xxxxxx

Reason:


RSHOW command entered with a specific request number and shows the remote data set name.

Action:

None


Message Syntax

0422I

CLASS=x, DEST=xxxxxxxx, FORM=xxxxxxxxxx, FCB=xxxx, HOLD=xxx,

NAME=xxxxxxxx, CTRL=xxxx

Reason:


RSHOW command entered with a request number. It is displayed when transmitting or receiving a report. The following fields are displayed:

■ The Class, Destination, Form, and FCB of the report

■ A hold flag, control flag (that is, ASA, MACHINE or name)

■ The report name which will be printed on the report banner page

Action:

None

0423E

XCOM OPERATOR CONTROL SESSION ENDED DUE TO ERRORS

Reason:

CA XCOM Data Transport was processing a control request through the TSO/ISPF panels when an error occurred from which it could not recover. The Operator

Control session is terminated. An accompanying message describes the actual error that caused the request to end.

Action:

Review the accompanying message.

0424E

TRANSFERS TO XCOM ADMIN NOT ALLOWED

Reason:

A transfer has been directly scheduled to the XCOMPLEX Admin Server.

Action:

The XCOMPLEX Admin Server cannot be used as a remote partner. Do not schedule transfers to it.


0425E

0426E

0427I

Message Syntax

XCOM HISTORY FILE HAS RUN OUT OF SPACE

Reason:

CA XCOM Data Transport has attempted to write a record to the history file, but

VSAM returned an error indicating that there was no more space in the history file.

Action:

Increase the size of the history file or delete/define the history file to enable the

CA XCOM Data Transport history processing to complete successfully.

CANNOT PERFORM OPERATOR FUNCTIONS ON COMPLETED TRANSFERS

Reason:

The TSO operator has attempted to perform an operator control function on a completed file transfer, but CA XCOM Data Transport does not allow this.

Action:

Ensure that the object of the operator control function has not completed processing.

REQUEST CANCELED BY TSO USERID xxxxxxxx

Reason:

The TSO operator has canceled a task. The task is moved to the History File and the TSO user that canceled the task is identified in the History File message field.

xxxxxxxx is the ID of the TSO user that canceled the task.

Action:

None


Message Syntax

0428E

INVALID PARAMETERS ENTERED ON CONSOLE ALTER COMMAND

Reason:

The CA XCOM Data Transport for z/OS console operator has attempted an ALTER command but the data entered on the ALTER command is invalid.

Action:


z/OS User Guide for the correct syntax of CA XCOM Data Transport operator commands.

0429I

xxxxxxxx ALTER COMMAND PROCESSED SUCCESSFULLY

Reason:

The CA XCOM Data Transport for z/OS console operator has entered an ALTER command and CA XCOM Data Transport has successfully processed the command. xxxxxxxx defines the type of alter request such as a Start Time or

Scheduling Priority override.

Action:

None

0430E

START TIME NOT NUMERIC OR IN hhmm FORMAT

Reason:

The CA XCOM Data Transport for z/OS console operator has attempted to enter an ALTER TIME command but the time entered was not in the format of hhmm.

If the operator enters the TIME operand without a value, the time defaults to

00:00. If the time is entered, all four digits of hhmm must be entered as numeric characters without separators.

Action:

See the chapter ―Operation and Control‖ in the CA XCOM Data Transport for z/OS

User Guide for the proper format of the ALTER command.


0431E

0432E

0433E

Message Syntax

START DATE NOT NUMERIC OR IN yyddd FORM

Reason:

The CA XCOM Data Transport for z/OS console operator has attempted to enter an ALTER DATE command but the date entered was not in the format of yyddd.

If operator enters no date, CA XCOM Data Transport will default to use today's date. The operator must enter five numeric digits to define the new date.

Action:



PRIORITY NOT NUMERIC IN ALTER PRIORITY COMMAND

Reason:

The CA XCOM Data Transport for z/OS console operator has entered an ALTER

SPRTY or ALTER PRTY command but the priority entered did not have numeric data in it.

Action:



RECORD NOT FOUND IN XCOMRRDS FOR SHOW/RSHOW COMMAND

Reason:

The CA XCOM Data Transport for z/OS console operator entered a SHOW or

RSHOW command but CA XCOM Data Transport was unable to find a record with the specified request number on the CA XCOM Data Transport RRDS file.

Action:

Re-enter the command to ensure that request number entered was proper.


Message Syntax

0434E

UNABLE TO OPEN DATA SET FOR SHARED ACCESS—FILE UNDER

EXCLUSIVE CONTROL OF ANOTHER USER

Reason:

A file transfer receive request has been received and CA XCOM Data Transport has attempted to open the file for input, but found another task currently updating that file. The file transfer request is terminated and the message displayed and sent to the remote computer.

Action:

The file transfer request can be retried at a later time when the file is not being updated.

0435E

UNABLE TO OPEN DATA SET FOR EXCLUSIVE ACCESS—FILE UNDER

EXCLUSIVE CONTROL OF ANOTHER USER

Reason:

A file transfer receive request has been received and CA XCOM Data Transport has attempted to open the file for output, but found another task currently updating that file. The file transfer request is terminated and the message displayed and sent to the remote computer.

Action:

The file transfer request can be retried at a later time when the file is not being updated.

0437E

LCLDS01 DISP=NEW NOT SUPPORTED FOR PDS WITH MEMBER NAME

SPECIFIED—USE LFILE SYSIN01 PARAMETER

Reason:

Because of the way that z/OS treats a PDS when a member name is specified, CA

XCOM Data Transport does not support the situation where a PDS is created within the LCLDS01 DD statement with a member name specified.

Action:

We recommend that if you want to perform this type of action, that you either allocate the data set in a prior step using the IEFBR14 utility, or use the applicable CA XCOM Data Transport SYSIN01 parameters to create the data set.


0438E

0439I

0443I

Message Syntax

LIST/USER SUBPARAMETERS VALID ONLY FOR TYPE=SCHEDULE

TRANSFERS

Reason:

The user has attempted to initiate an immediate file transfer request (that is,

TYPE=EXECUTE) but has used a list or user name rather than a group or LU. The list function is supported only when scheduling a file transfer request. It cannot be done in a TYPE=EXECUTE transfer.

Action:

If the function must be done via a TYPE=EXECUTE, you must specify each of the

LUs or groups manually. Otherwise, you can also use the LIST or USER parameter with TYPE=SCHEDULE transfers.

DATACLAS= MGMTCLAS= STORCLAS= DSNTYPE=

Reason:

The user entered a SHOW,req# command. This message displays as part of the response to the SHOW command that displays the values of DATACLAS,

MGMTCLAS, STORCLAS, and DSNTYPE (if any).

Action:

None

RESTARTING XCOMJOB TYPE=EXECUTE ON SEQUENCE # xxx

Reason:

A user has executed an XCOMJOB TYPE=EXECUTE transfer. CA XCOM Data

Transport has determined by looking in its restart data set that the prior execution of XCOMJOB has ended abnormally and CA XCOM Data Transport must restart the file transfer request. CA XCOM Data Transport reads the file transfer information off of the XCOMREST data set, and parses through the file transfer requests which have been entered through the SYSIN01 parameters. When a match is made on that SYSIN01 parameter CA XCOM Data Transport will restart on that file transfer request.

Action:

None


Message Syntax

0445I

REQUEST NUMBER xxxxxx ASSIGNED TO yyyyyy zzzzzzzz

Reason:

A user has attempted to initiate a file transfer send request to a list. CA XCOM

Data Transport will create a file transfer request for each entry in that list.

xxxxxx defines the request number assigned to the transfer request. yyyyyy defines the group or LU name, and zzzzzz defines the name of the group or LU name.

Action:

None

0446I

SCHEDULE REQUEST CONFIRMED BUT MESSAGE NOT RECEIVED

Reason:

CA XCOM Data Transport has successfully scheduled a file transfer request, but did not receive a message from the server indicating the request number assigned to the file transfer request.

Action:

Retain the CA XCOM Data Transport log file and contact CA Technical Support.

0447E

xxxxxxxx REQUEST ENDED WITH ERRORS—CONTINUE=YES NOT

SPECIFIED

Reason:

A TYPE=EXECUTE transfer request was initiated, and the user specified that the transfer should end if any transfers receive a VTAM error. Prior messages should show the VTAM error received. This message indicates that the XCOMJOB execution will stop because a VTAM error occurred.

Action:

If you want to continue execution with other transfer requests, regardless of whether a transfer request fails because of a VTAM error, then specify

CONTINUE=YES as a PARM on the EXEC card, or let the parameter default to YES by not specifying the CONTINUE parameter.


0448E

0449I

Message Syntax

xxxxxxxx EXECUTION BYPASSED BECAUSE PREVIOUS TRANSFER FOR

SAME LU ENDED WITH VTAM ERROR

Reason:

TYPE=EXECUTE transfer has been requested with multiple transfers for the same

LU. One of the transfers ended with a VTAM error. If the next transfer request is for the same LU, CA XCOM Data Transport will also bypass that one because it is likely that all additional transfers for that LU will also fail with a VTAM error. This message will only be displayed when CONTINUE=NO is specified.

The same error conditions are possible with a TYPE=SCHEDULE transfer. This indicates that the server where the transfers are being scheduled is down, or unavailable.

Action:

For TYPE=EXECUTE transfers, correct the errors specified in previous messages.

If you want to continue execution of this transfer regardless of whether the previous transfer failed, specify CONTINUE=YES as a parameter on the JCL job card.

For TYPE=SCHEDULE transfers where the server is unreachable, correct the problem.

RRQ DELETE REQUEST INVALID FOR SLOT 1

Reason:

An internal error caused CA XCOM Data Transport to try to delete the first slot from the an internal request table. Slot 1 is saved to act as a control slot and so should not be deleted.

Action:

If this error persists, retain the CA XCOM Data Transport log file and contact CA

Technical Support.


Message Syntax

0451I

xxxxxxxx NOW CONNECTED TO XCOMPLEX ADMIN yyyyyyyy

Reason:

XCOMPLEX Worker Server xxxxxxxx has successfully connected to the

XCOMPLEX Admin Server yyyyyyyy. A CNOS issued from the XCOMPLEX Worker

Server to XCOMPLEX Admin Server was successful.

Action:


0452I

xxxxxxxx NOW DISCONNECTED FROM XCOMPLEX ADMIN yyyyyyyy

Reason:

XCOMPLEX Worker Server xxxxxxxx has successfully disconnected from the

XCOMPLEX Admin Server yyyyyyyy.

Action:

None. This message is displayed for informational purposes only

0453I

AUTO CONNECT TO XCOMPLEX ADMIN xxxxxxxx FAILED. AUTO RETRY

IN 2 MINS

Reason:

XCOMPLEX Admin Server xxxxxxxx was not running or the CNOS issued from the

XCOMPLEX Worker Server to connect to the XCOMPLEX Admin Server was not successful.

Action:

The XCOMPLEX Worker Server will automatically retry every two minutes for up to one hour. Check to see if the XCOMPLEX Admin Server xxxxxxxx is running or if there is an SNA connectivity problem.


0454I

0455E

Message Syntax

OPERLIM EXCEEDS XCF MAX ENTRIES. OPERLIM REDUCED TO VALUE IN

XCOMM1054I

MESSAGE

Reason:

During the XCOMPLEX Admin startup process, the value of OPERLIM in the default options table exceeded the maximum list entries shown.

Action:

If the message is displayed during the XCOMPLEX Admin startup, review the

ISPF inquiry needs and determine if the OPERLIM value in the XCOMDFLT or the

XCF table size should be adjusted.

The OPERLIM value in the XCOMDFLT for the XCOMPLEX Admin should be equal or less than the value of the maximum list entries of the CROSS-COUPLING

FACILITY used by this XCOMPLEX.

To retain the OPERLIM value, increase the storage of the XCF. This increases the maximum list entries to accommodate the desired OPERLIM value.

xxxxxxxx HAS ENCOUNTERED A CRITICAL ERROR ON DATASET yyyyyyyy

Reason:

CA XCOM Data Transport server has encountered a critical file error condition.

xxxxxxxx is the name of the program that has detected the error and yyyyyyyy is the data set that has the file error.

Action:

Review the JESMSGLG, JESYSMSG, and XCOMLOG of the CA XCOM Data

Transport server and see what kind of file error is being encountered. Then correct the file error condition for the data set. For example, if there is an out of space error, delete and redefine the data set with larger space allocation. If this error persists, retain the CA XCOM Data Transport JESMSGLG, JESYSMG, and

XCOMLOG files and contact CA Technical Support.


Message Syntax

0456E

xxxxxxxx CONTINUATION MISSING OR INVALID—MUST BEGIN IN

COLUMNS 2 - 16

Reason:

CA XCOM Data Transport server has encountered an error in the parameter card in the SYSIN01 for the XCOMJOB batch run. The parameter xxxxxxxx statement has incorrect syntax for continuation. The statement must have a non-blank character in column 52 and the next line must begin in columns 2 to 16.

Action:

Correct the syntax of the parameter xxxxxxxx and rerun your XCOMJOB.

0458E

SUBSCRIPT VALUE IS NOT NUMERIC

Reason:

A value provided as a symbolic variable offset or length subscript is not numeric.

Only numeric characters are allowed.

Action:

Enter a valid character—numeric only.

0459E

SUBSCRIPT LENGTH IS NOT VALID

Reason:

The length of a subscript parameter is not valid. A maximum of eight numeric characters is allowed for each of the offset and length subscript values.

Action:

Enter a valid-length value.

0460E

SUBSCRIPT CONTAINS INVALID CHARACTERS

Reason:

A blank character has been entered as a subscript value.

Action:

Enter a valid character—numeric only.


0461E

0462E

0463E

Message Syntax

ZERO SUBSCRIPT VALUE ENTERED

Reason:

Zero subscript values are not allowed. The minimum value that can be entered as an offset or length subscript is 1.

Action:

Enter a non-zero subscript value.

SUBSCRIPT OUT OF RANGE FOR SPECIFIED SYMBOLIC

Reason:

The subscript offset/length pair provided exceeds the total size of the field.

Action:

Correct the subscript value.

ERROR SETTING REMOTE USER ID: TRUSTED ACCESS DENIED

Reason:

The user ID from the remote partner is not on the destination member selected for this transfer. This can also be caused by no destination member matching the

LU or IP address of the remote partner.

Action:

Contact your CA XCOM Data Transport administrator to add the user ID as a

TRUSTID in the destination member; or resend your transfer, not as a TRUSTED transfer, and provide the user ID and password. If there is a destination member for the remote partner, check if it has been enabled.


Message Syntax

0464E

PASSWORD MISSING. REQUIRED FOR SAF PROCESSING

Reason:

When SECURITY=SAF or when USS-forced SAF processing invokes the SAF routines in CA XCOM Data Transport, the USERID or LUSER must be provided with the corresponding PASSWORD or LPASS.

Action:

If you are using USERID, specify a valid PASSWORD; if you are using LUSER, specify a valid LPASS.

0480I

PERFORMING FAILOVER PROCESSING TO SERVER XXXXXXXX

RRDS=rrds.data.set.name

Reason:

Failover processing is being initiated, and transfers will be moved to the named server. The source of the moved transfers is the XCOM queue (XCOM RRDS data set) indicated.

Action:

None

0481I

INVALID SESSION PARMS FOR TYPE=RECOVER - MUST BE LU 6.2

Reason:

An invalid protocol was used to connect to the CA XCOM Data Transport for z/OS server. The connection is refused.

Action:

Ensure that the connection is being made over an SNA session that supports LU

6.2 or using TCP/IP.


0482I

0483E

0484E

Message Syntax

FAILOVER PROCESSING COMPLETED

Reason:

Failover processing has completed normally and successfully.

Action:

None

UNABLE TO PERFORM FAILOVER REQUEST. XCOMRRDS IS IN USE BY

ANOTHER TASK

Reason:

The attempt to acquire an exclusive ENQ on the XCOM RRDS data set has failed.

Action:

Determine which task holds an ENQ on the XCOM RRDS data set and take appropriate action.

ERROR OCCURRED DURING XCOMRRDS ERASE OPERATION

Reason:

An attempt to erase a record from the XCOMRRDS data set has failed. Failover processing is terminated.

Action:

Evaluate the return code and fdbk2 code given in message XCOMM0491E.

Correct the error, and rerun the failover processing job.


Message Syntax

0485E

ERRORS OCCURRED PROCESSING THE XCOMRRDS DATASET

Reason:

During the initial processing of the XCOMRRDS data set, one or more errors occurred.

Action:

Evaluate the additional messages that may accompany this message and take corrective action accordingly.

0486I

NO ELIGIBLE TRANSFERS FOUND IN XCOMRRDS TO RECOVER

Reason:

There are no eligible transfers in the XCOM RRDS data set that need to be rerouted to the target CA XCOM server. This is an informational message.

Action:

If the XCOM RRDS data set contained no eligible transfers at the time the server was terminated, then this is not an error. If the XCOM RRDS data set contained eligible transfers at the time the server was terminated, set the TRACE= parameter to YES on the TYPE=RECOVER job statement. Rerun the job and contact CA XCOM support for further assistance.

0487E

SLOT 1 IS NOT VALID - DATASET MAY NOT BE AN XCOM RRDS -

PROCESSING TERMINATED

Reason:

The XCOM RRDS data set contains certain internal control information. The RRDS data set referenced by the XCOMRRDS DD statement does not contain this information. Either the data set has not been properly initialized as an XCOM

RRRDS data set, or the file content has been damaged.

Action:

Use a utility program to display the contents of the data set and contact CA

XCOM support for further assistance.


0488E

0489I

0490E

Message Syntax

REMOTE PARTNER DID NOT START THE RECOVERY TRANSACTION

PROGRAM

Reason:

The target CA XCOM server did not activate the requested Transaction Program in response to the request from the batch XCOMJOB utility. Possible causes are that the target server is experiencing a resource shortage or does not support failover processing.

Action:

Ensure that failover support has been enabled for the target server. If it has been enabled, verify that sufficient resources are available and that task levels are within the configured limits.

REQUEST # XXXXXX REROUTED TO SERVER XXXXXXXX

Reason:

The transfer identified by the request number in this message has been successfully rerouted to the target CA XCOM server identified in this message.

Action:

None

RRDS DATASET IS IN USE BY ANOTHER TASK. RRDS=xx...xx

Reason:

The attempt to open the XCOMRRDS data set has failed with return code x'08' and fdbk2 code x'A8', which indicates that the data set is already open by another task. The value displayed for RRDS= is the name of the data set that was being opened.

Action:

Ensure that the XCOMRRDS DD statement references the correct data set name, or identify the task that has it open and close it.


Message Syntax

0491E

XXXXXXXX MACRO RECEIVED RC=XX FDBK2=XX DDNAME=

Reason:

A VSAM macro identified in the message has ended with a non-zero return/fdbk2 code combination.

Action:

Consult the appropriate operating system documentation to determine the cause and the resolution for the problem.

0492E

XCOMRRDS DD STATEMENT MISSING - NO RECOVERY POSSIBLE

Reason:

No XCOMRRDS DD statement has been provided in the JCL.

Action:

Add an XCOMRRDS DD statement to the XCOMJOB JCL, pointing to the appropriate XCOM RRDS data set.

0493E

XCOMRRDS DD STATEMENT DOES NOT REFERENCE A VALID VSAM RRDS

DSN=xx...xx

Reason:

The data set referenced on the XCOMRRDS DD statement is not a valid VSAM

RRDS data set.

Action:

Check the XCOMRRDS DD statement and ensure that it refers to a valid XCOM

RRDS data set.


0494E

0495E

Message Syntax

NO WORKER(S) AVAILABLE TO RECEIVE REQUEST

Reason:

An attempt was being made to reroute transfers to one or more CA XCOM

WORKER servers in an XCOMPLEX, but the CA XCOM ADMIN server has no

WORKER servers active.

Action:

Ensure that the CA XCOM WORKER servers are active in the XCOMPLEX and that the XCOMJOB TYPE=RECOVER is connecting to the correct CA XCOM ADMIN server.

RRDS DATASET RELEASE=xx DOES NOT MATCH XCOMJOB

RELEASE=yy

Reason:

The control record in the XCOM RRDS data set that is being processed by a

TYPE=RECOVER utility has a release level that differs from the release level of the XCOMJOB program that is attempting to access it. This condition may also occur if the XCOM RRDS data set was allocated and initialized, but has not been accessed by a CA XCOM Data Transport for z/OS server.

Action:

Verify that the input XCOM RRDS data set name that is referenced by the

XCOMRRDS DD statement in the TYPE=RECOVER job is correct. If not, correct the JCL and resubmit the TYPE=RECOVER job. If it is correct, TYPE=RECOVER processing cannot be performed using this XCOM RRDS data set.


Message Syntax

0496E

REQUEST # XXXXXX DELETED FROM XCOM RRDS DATA SET

Reason:

A remotely initiated transfer found in the XCOM RRDS data set during

TYPE=RECOVER processing is a type of transfer that is not capable of being restarted from a checkpoint. The transfer record has been deleted from the

XCOM RRDS data set without being rerouted to the target server.

Action:

Reason:

None

0497E

XCOMJOB RELEASE=xx DOES NOT MATCH SERVER RELEASE=yy

Reason:

The TYPE=RECOVER job and the server that you are using are set up for different releases of CA XCOM Data Transport.

Action:

Use a server that is set up for the same release of CA XCOM Data Transport as your TYPE=RECOVER job.

0498E

REMOTELY INITIATED REQUEST # XXXXXX NOT PROCESSED BY

TYPE=RECOVER

Reason:

Transfer entries in an XCOM RRDS data set that were initiated by a remote partner are not eligible for TYPE=RECOVER processing.

Action:

None


0500I

0501I

0502E

Message Syntax

RRDS ERASE REQUEST INVALID FOR SLOT 1

Reason:

An internal error caused CA XCOM Data Transport to try to erase the first slot from the RRDS file. Because this is a control record, this is not allowed and it is flagged as an error.

Action:


Technical Support.

xxxxxxxx GROUP IS NOT ENABLED—TRANSFER DELAYED

Reason:

This message is issued when a request has been scheduled to the CA XCOM Data

Transport server for a group that is undefined or not currently enabled. If this condition existed at the time the request was scheduled, an XCOMM0207W message was issued at that time. CA XCOM Data Transport ignores the request and continues looking for other work. If the required group is not defined or enabled before the request matches installation aging criteria, the request is deleted.

Action:

Verify that the group name specified is correct. If the transfer request is to be processed, define and/or enable the requested group.

ERROR CODE xx ON CA7 INTERFACE ATTACH

Reason:

CA XCOM Data Transport was attempting to attach the CA7 interface program but received return code xx from the z/OS ATTACH command. This error code can be found in the IBM documentation.

Action:

Ensure that the CA7 Interface module is in the CA XCOM Data Transport

STEPLIB, and that there is a sufficient region defined for the CA XCOM Data

Transport job.


Message Syntax

0503E

ERROR CODE xx ON EXIT01 ATTACH

Reason:

CA XCOM Data Transport was attempting to attach the CA XCOM Data Transport

EXIT 01 program but received return code xx from the z/OS ATTACH command.

This error code can be found in the IBM documentation.

Action:

Verify that the CA7 interface module is in the CA XCOM Data Transport STEPLIB and that there is a sufficient region defined for the CA XCOM Data Transport job.

0505E

XCOMRRDS RETURN CODE xx yy ON zzz REQUEST

Reason:

CA XCOM Data Transport has received an invalid return code accessing the RRDS file. zzz is the CA XCOM Data Transport request, while xx yy is the return code received. VSAM return codes can be found in the IBM documentation.

Action:


Technical Support.

0506E

DESTINATION FOUND FOR INDIRECT REQUEST BUT DEST/WRITER NOT

SPECIFIED

Reason:

A user has attempted to send an indirect transfer request to another CA XCOM

Data Transport user but a definition error has occurred. The destination LU was defined in the XCOMDEST Table, but there was no destination or writer defined for that LU. The file transfer that initiated the indirect transfer request is terminated and this message is sent to the conversation partner.

Action:

Define a valid destination or writer for the LU specified in the request.


0507I

0508I

0509E

Message Syntax

xxxxxxxx yyyyyyyy ENQ HELD BY zzzzzzzz—NOWAIT SPECIFIED

Reason:

CA XCOM Data Transport internally issued an ENQ request and the CA XCOM

Data Transport program specified that the task should not wait for the ENQ to be freed. xxxxxxxx defines the LU that issued the ENQ request. yyyyyyyy defines the ENQ resource, while zzzzzzzz is the LU that owns the ENQ resource.

Action:

None

xxxxxxxx yyyyyyyy ENQ HELD BY zzzzzzzz—TASK PUT INTO WAIT

Reason:

CA XCOM Data Transport internally issued an ENQ request and the CA XCOM

Data Transport program specified that the task should be placed into a wait state until the ENQ is freed. This message indicates that the task will be placed into a wait state until another transfer request frees up the ENQ. xxxxxxxx defines the

LU that is put into a wait state. yyyyyyyy defines the ENQ resource, while

zzzzzzzz is the LU that owns the ENQ resource.

Action:

None

xxxxxxxx ERROR ON ENQ yyyyyyyy—INVALID PARAMETERS

Reason:

CA XCOM Data Transport internally issued an ENQ request but the parameters supplied in the ENQ request were invalid. xxxxxxxx indicates the LU that issued the ENQ request, while yyyyyyyy is the value of the ENQ request.

Action:


Technical Support.


Message Syntax

0510I

xxxxxxxx yyyyyyyy ENQ FREED BY zzzzzzzz—TASK CONTINUES

Reason:

Task xxxxxxxx has issued an ENQ request for resource yyyyyyyy, but this request was already owned by the LU zzzzzzzz. This message indicates that the

LU zzzzzzzz has freed up the resource, and the LU xxxxxxxx now owns the resource xxxxxxxx and can continue processing.

Action:

None

0511I

INVALID ROSCOE PROC NAME FOR ROSCOE NOTIFY (ROSPROC)

Reason:

A transfer request has requested that CA XCOM Data Transport notify a ROSCOE user with information about a file transfer, but the ROSCOE PROC name defined in the CA XCOM Data Transport Default Table is invalid or missing.

Action:

Correct the CA XCOM Data Transport Default Table with the correct ROSCOE

PROC name.

0512E

LOCATE ERROR CODE xx ON DATA SET yyyyy

Reason:

CA XCOM Data Transport has attempted to use the catalog management services command LOCATE to determine the true name of a GDG data set, but has received return code xx from z/OS. yyyyy is the data set name used in the locate request. The return code is defined in the IBM documentation.

Action:

See the IBM documentation for the appropriate action.


0513E

0514E

0515E

Message Syntax

ADDITIONAL PARAMETERS REQUIRED FOR xxxxxxxx COMMAND

Reason:

A CA XCOM Data Transport console operator has entered a CA XCOM Data

Transport command but there were not enough parameters entered to fulfill the command. For example, an operator could enter an ACT command without entering the LU to be activated. xxxxxxxx defines the operator command entered.

Action:


User Guide for more information on the format of the operator commands.

xxxxxxxx ERROR FINDING XCOMDEST ENTRY FOR PROCESS SYSOUT

REQUEST—DELETED FROM ACTIVE QUEUE

Reason:

CA XCOM Data Transport has received a Process SYSOUT request for LU

xxxxxxxx but cannot locate the proper entry in the XCOMDEST Table. The entry is deleted from the CA XCOM Data Transport RRDS file.

Action:

If this message persists, retain the CA XCOM Data Transport log file and contact

CA Technical Support.

UNABLE TO GETMAIN STORAGE FOR FILE I/O BUFFER—TRANSFER

TERMINATED

Reason:

CA XCOM Data Transport has attempted to issue a GETMAIN request for a file buffer, but there was not enough storage available to fulfill the request. Rather than abending, the transfer request is aborted, and this message is sent to the message partner.

Action:

If this error persists, reevaluate the region size associated with the CA XCOM

Data Transport job, using the Server Storage Usage Worksheet available on http://ca.com/supportconnect or contact CA Technical Support.


Message Syntax

0516E

UNABLE TO GETMAIN STORAGE FOR FILE CONTROL BLOCK

AREA—TRANSFER TERMINATED

Reason:

CA XCOM Data Transport has attempted to issue a GETMAIN request for a file control block, but there was not enough storage available to fulfill the request.

Rather than abending, the transfer request is aborted, and this message is sent to the message partner.

Action:



0517E

UNABLE TO GETMAIN STORAGE FOR FILE DATA AREA—TRANSFER

TERMINATED

Reason:

CA XCOM Data Transport has attempted to issue a GETMAIN request for a file data area, but there was not enough storage available to fulfill the request.


Action:

If this error persists, re-evaluate the region size associated with the CA XCOM



0518E

0519E

0520E

Message Syntax

UNABLE TO GETMAIN STORAGE FOR FILE WORK AREA—TRANSFER

TERMINATED

Reason:

CA XCOM Data Transport has attempted to issue a GETMAIN request for a file work area, but there was not enough storage available to fulfill the request.


Action:



UNABLE TO GETMAIN STORAGE FOR HISTORY WORK AREA

Reason:

CA XCOM Data Transport has attempted to issue a GETMAIN request for a history work area, but there was not enough storage available to fulfill the request.

Rather than abending, the history request is aborted, and this message is displayed in the CA XCOM Data Transport log file and the z/OS console.

Action:



UNABLE TO GETMAIN STORAGE FOR XCOM VTAM CONTROL BLOCKS

Reason:

CA XCOM Data Transport has attempted to issue a GETMAIN request for a VTAM control block, but there was not enough storage available to fulfill the request.

Rather than abending, this is treated as a VTAM error, and the session is immediately ended.

Action:




Message Syntax

0521E

UNABLE TO GETMAIN STORAGE FOR XCOM VTAM WORK AREA

Reason:

CA XCOM Data Transport has attempted to issue a GETMAIN request for a VTAM work area, but there was not enough storage available to fulfill the request.

Rather than abending, this is treated as a VTAM error, and the session is ended immediately.

Action:



0522E

UNABLE TO GETMAIN STORAGE FOR PROCESS SYSOUT CONTROL

BLOCK

Reason:

CA XCOM Data Transport has attempted to issue a GETMAIN request for a

Process SYSOUT control block but there is not enough storage available to fulfill the GETMAIN request. Rather than abending, the Process SYSOUT request is marked as an error and retried at the next error interval.

Action:



0523E

UNABLE TO GETMAIN STORAGE FOR RRDS WORK AREAS

Reason:

CA XCOM Data Transport has tried to issue a GETMAIN request for an RRDS work area, but there is not enough storage available to fulfill the GETMAIN request.

Rather than abending, the RRDS request is denied and this message is displayed in the CA XCOM Data Transport log file and on the z/OS console.

Action:




0524E

0525E

0526E

Message Syntax

UNABLE TO GETMAIN STORAGE FOR LOGICAL UNIT CONTROL BLOCK

Reason:

CA XCOM Data Transport has attempted to GETMAIN storage for a logical unit control block but there is not enough storage available to satisfy that request.

The session request is aborted at this point.

Action:

If this error persists, reevaluate the storage associated with the CA XCOM Data

Transport region.

UNABLE TO GETMAIN STORAGE XCOM REQUEST CONTROL BLOCK

Reason:

CA XCOM Data Transport has attempted to GETMAIN storage for a request control block, but there is not enough storage available to satisfy that request.

The request is aborted at this point.

Action:

If this error persists, reevaluate the storage associated with the CA XCOM Data

Transport region.

UNABLE TO GETMAIN STORAGE FOR SCHEDULE EXIT ROUTINES

Reason:

CA XCOM Data Transport has attempted to GETMAIN storage for the scheduling exit, but there was not enough storage available to satisfy that request. Rather than abending CA XCOM Data Transport, the scheduling exit is not executed.

Action:




Message Syntax

0527E

XCOM EXIT 02 TURNED OFF—MODULE XCOMEX02 NOT FOUND

Reason:

A user specified EXIT02=YES on the CA XCOM Data Transport default table, but the module was not loaded by CA XCOM Data Transport.

Action:

At start-up time, ensure that you really want to use that CA XCOM Data

Transport exit. If so, follow the instructions in the CA XCOM Data Transport for

z/OS User Guide to assemble that module. The CA XCOM Data Transport EXIT02 is a JES2 exit that scans through JES control blocks to obtain additional information on Process SYSOUT reports.

0528E

XCOM EXIT 03 TURNED OFF—MODULE XCOMEX03 NOT FOUND

Reason:

A user-specified EXIT03=YES on the CA XCOM Data Transport default table, but that module was not loaded by CA XCOM Data Transport at start-up time.

Action:

Ensure that you really want to use that CA XCOM Data Transport EXIT. If so follow the instructions in the CA XCOM Data Transport for z/OS User Guide to assemble that module. The CA XCOM Data Transport EXIT03 is a JES3 exit that scans through JES control blocks to obtain additional information on Process

SYSOUT reports.

0529E

XCOM EXIT xx TURNED OFF—INVALID FOR SUBSYSTEM yyyy

Reason:

CA XCOM Data Transport has recognized that EXIT xx has been turned on but that it is Job Entry subsystem specific (that is, JES2 OR JES3). The subsystem that CA XCOM Data Transport is running under is invalid for use with the exit specified. For example, specifying EXIT02=YES for JES3 is invalid, as is specifying EXIT03=YES for JES2.

Action:

Disable the invalid EXIT selection in the CA XCOM Data Transport Default Options

Table.


0530E

0531E

0532I

Message Syntax

NETWORK xxxxxxxx JOB yyyyyyyy NOT FOUND FOR XTC REQUEST

Reason:

A file transfer has just completed which uses the CA XCOM Data Transport transfer control parameters. It specified that job yyyyyyyy in network xxxxxxxx should be processed, but that job was not on the CA XCOM Data Transport locally initiated task queue. This message is displayed for informational purposes only and so does not affect the execution of a transfer request.

Action:

None

RRDS RECORD NOT FOUND ON xxxxxxxx XTC READ REQUEST

Reason:

A file transfer has just completed which uses the CA XCOM Data Transport

Transfer Control Facility. CA XCOM Data Transport was attempting to read the

RRDS file to update a transfer request, but the record was not found on the file.

Action:

Take a snap dump of the CA XCOM Data Transport address space, retain the CA

XCOM Data Transport log file, and contact CA Technical Support.

xxxxxxxx yyyyyyyy REQUEST zzzzzz PURGED BY XTC REQUEST

Reason:


Transfer Control Facility. It specified that job yyyyyyyy in network xxxxxxxx with request number zzzzzz was purged as a result of the completion of this transfer request.

Action:

None


Message Syntax

0533I

xxxxxxxx yyyyyyyy REQUEST zzzzzz UPDATED BY aaaaaaa XTC

REQUEST

Reason:


Transfer Control Facility. It specified that job yyyyyyyy in network xxxxxxxx with request number zzzzzz was updated as a result of the completion of this transfer request. aaaaaaaa defines whether the transfer request was incremented, decremented, or released as a result of the request.

Action:

None

0534I

REQUEST xxxxxx CREATED BY XCOM NOTIFY REQUEST

Reason:

A CA XCOM Data Transport file transfer request has just completed and it specified that CICS or another LU should be notified that the request has been completed. CA XCOM Data Transport then spawns another task with request number xxxxxx to send the notification request to another user.

Action:

None

0535I

XCOM NOTIFY COMPLETED SUCCESSFULLY

Reason:

This message indicates that CA XCOM Data Transport has successfully notified

CICS or another LU of the completion of another file transfer request.

Action:

None


0536E

0537E

0538I

Message Syntax

RRDS RECORD NOT FOUND FOR XCOM NOTIFY SLOT xxxxxx

Reason:

CA XCOM Data Transport has begun processing a file transfer notify request, but when attempting to read the record from the RRDS file, it was unable to find the record. The notify request is purged.

Action:

Retain the CA XCOM Data Transport log file and contact CA Technical Support.

HISTORY RECORD NOT FOUND FOR XCOM NOTIFY REQ# xxxxxx

Reason:

CA XCOM Data Transport tried to process a file transfer notify request, but could not find the record in the history file. The history file might have been purged or there might have been a problem in writing the record to the history file. The notify request is purged.

Action:

Determine if the history file record has been purged. If the history file record has been purged, the operation that generated this message cannot be done. If the history file record has not been purged, contact CA Technical Support.

FOLLOWING MESSAGE RECEIVED ON XCOM NOTIFY FROM LU xxxxxxxx

REQUEST # nnnnnn

Reason:

CA XCOM Data Transport is the recipient of a notify request from another CA

XCOM Data Transport session. It will display the message associated with request number 999999 in an accompanying message.

Action:

Check the accompanying message to determine the exact cause of the error.


Message Syntax

0539E

INVALID SYNTAX OF XCOM NOTIFY MESSAGE

Reason:

CA XCOM Data Transport is the recipient of a notify request from another CA

XCOM Data Transport system. However, the data passed with the notify request in invalid.

Action:

If this problem can be reproduced, contact CA Technical Support. Be prepared to take a CA XCOM Data Transport trace of the notify request if necessary.

0540I

NOTIFY=xxxx NNAME=yyyyyyyy NUSER=zzzzzzzz

XFER REQ#=nnnnnn XFER DATE=

Reason:

A CA XCOM Data Transport operator has issued a SHOW request for a task that is a notify request. This message displays the transfer start date, whether CICS or an LU is notified, the name of the LU or group to be notified, the user ID, and the transfer request number.

Action:

None

0541I

NAME=xxxxxxxx NOTIFY REQ#=999999 NOTIFY DATE=99999

Reason:

A CA XCOM Data Transport operator has issued a SHOW request for a task that is a notify request. This message displays the name of the LU that initiated the notify request, and the request number and end date of the notify task.

Action:

None


0542I

0543I

0544E

Message Syntax

XCOM XTCNET= xxxxxxxx XTCJOB= yyyyyyyy HOLDCT=

Reason:

An operator has issued a SHOW command for a file transfer request. This message displays some pertinent information on the CA XCOM Data Transport transfer control parameters such as the network name, job name, and hold count of a transfer request.

Action:

None

XCOM XTC JOB=xxxxxxxx yyyyyyy IF aaaaaaaaaaa

Reason:

An operator has issued a SHOW command for a file transfer request. This message displays some pertinent information on the CA XCOM Data Transport

Transfer Control parameters such as a job which should be updated based upon the completion of this request. xxxxxxxx defines another job in the same CA

XCOM Data Transport network that controls this job. yyyyyyyy defines whether the request is for an increment, decrement, purge or release. aaaaaaaaaaa defines whether the request will be performed on a successful or unsuccessful request.

Action:

None

xxxxxxxx ERROR COPYING PROCESS SYSOUT FILE—JOB DELETED

Reason:

An internal error has been received copying a Process SYSOUT file. The job causing the error is deleted from the JES queue. The only cause of this is when the CA XCOM Data Transport SYNAD routine is entered when reading data from the JES queue. Generally this data set is corrupted by a JES error, and is not valid. CA XCOM Data Transport therefore deletes it so that it can continue processing valid Process SYSOUT requests.

Action:



Message Syntax

0545E

CALL TO CEEPIPI (xxxxxxxx) FAILED, MOD=yyyyyyyy, RC=nnnnnnnn

Reason:

The CA XCOM Data Transport module yyyyyyyy was unable to invoke the C language subroutines for function xxxxxxxx. RC=nnnnnnnn contains the return code from the IBM Language Environment.

Action:

Verify that the IBM Language Environment runtime libraries (SCEERUNx) are available via either STEPLIB or LINKLIST. If using the TCP/IP protocol, verify that the TCP/IP option of CA XCOM Data Transport has been installed. Otherwise retain the CA XCOM Data Transport log and JESLOG and contact CA Technical

Support.

0546E

RRDS RECORD DELETE FAILED

Reason:

This is a diagnostic message when an ERASE against the RRDS fails.

Action:

Retain the CA XCOM Data Transport log and JESLOG and contact CA Technical

Support.

0547E

xxxxxxxxxxxxx PARAMETER INVALID WITHOUT XTCNET PARM

Reason:

The CA XCOM Data Transport XTC function will work only when specifying the

XTCNET parameter that defines the name of the XTC network in which to run. If you do not specify the XTCNET parameter, CA XCOM Data Transport flags all XTC parameters as errors, and terminates the CA XCOM Data Transport job.

Action:

See the sections SYSIN01 Transfer Control (XTC) Parameters and Coding

Interdependent Transfers in the chapter ―The Batch Interface‖ of the CA XCOM

Data Transport for z/OS User Guide, to construct a valid XTCNET.


0548E

0549E

0550I

Message Syntax

XCOM XTC LIMIT OF 8 JOBS EXCEEDED—TRANSFER NOT SCHEDULED

Reason:

More than 8 jobs have been specified on XTC PURGE, DECR, INCR, or REL XTC parameter cards. A maximum of eight jobs can be specified for any Action to be performed when a transfer ends. Specifying more than eight XTC jobs will cause an error and the transfer request will not be scheduled.

Action:

Wait until some jobs have completed and reissue the command.

xxxxxxxxxxxxx XTCPARM EXCEEDS MAXIMUM JOB LENGTH

Reason:

XTC parameter xxxxxxxxxxxxx was entered but when parsing it, CA XCOM Data

Transport determined that the maximum length of a parameter had been exceeded. The maximum job length is 8 bytes.

Action:

Correct the XTC parameter and resubmit the request.

SESSION ENDING DUE TO XCOM mmmmmmmmmmm REQUEST

Reason:

mmmmmmmmmmm defines the reason for DROPSESS:

■ Returns DROPSESS=YES if DROPSESS= YES is specified in the destination table.

■ Returns DROPSESS=QEMPTY if DROPSESS= QEMPTY is specified in the destination table and there is no locally initiated request in the queue for the

LU.

Action:

None


Message Syntax

0551E

INVALID TAPE LABEL NUMBER OR LABEL TYPE ENTERED

Reason:

CA XCOM Data Transport was parsing the SYSIN01 Label parameter and noticed one of two errors:

■

A non-numeric label number

■

A label type not consistent with the label types supported

Action:

See the CA XCOM Data Transport for z/OS User Guide, correct the parameter values, and resubmit the request.

0552E

ERROR GETMAINING DATA FOR TEXT PACK CONTROL BLOCK

Reason:

CA XCOM Data Transport has attempted to issue a conditional GETMAIN for a record packing function but the GETMAIN has abended. Normally this is because there is not enough storage specified for CA XCOM Data Transport to use. CA

XCOM Data Transport ends the transfer request and break the session.

Action:

To resolve this problem give CA XCOM Data Transport a larger region size. See the Server Storage Usage Worksheet available on http://ca.com/supportconnect or contact CA Technical Support.

0553E

INVALID DATA LENGTH RECEIVED AFTER DECOMPRESSION FOR

UNPACK FUNCTION— > 2048 BYTES

Reason:

CA XCOM Data Transport was decompressing a packed function and found that the data length after decompression was greater than 2048 bytes.

Action:

If this error persists, try running the transfer request without compression. If you require compression, contact CA Technical Support. Be prepared to take a

CA XCOM Data Transport trace if required.


0554E

0555E

0556E

Message Syntax

PACK=CRLF INVALID WHEN RECSEP IS NOT SET TO YES

Reason:

The user has attempted to use the PC record packing function but has specified

RECSEP=NO. The transfer request is terminated with errors.

Action:

Specify RECSEP=YES, or resubmit the request, allowing RECSEP to take the default value.

INTERNAL ERROR AT END OF FILE DURING XCOM RECORD DEPACKING

FUNCTION

Reason:

CA XCOM Data Transport has detected an internal error during its end of file depacking function.

Action:


XCOM Data Transport trace of the transfer.

INVALID LENGTH BYTES ON RECORD DEPACKING FUNCTION

Reason:

CA XCOM Data Transport has detected an internal error during the record depacking function.

Action:




Message Syntax

0557E

ERROR GETMAINING DATA FOR THE XCOM PARAMETER REQUEST

Reason:

There is insufficient virtual storage available for CA XCOM Data Transport to process the control library.

Action:

Change the JCL that brings up the server, increasing the value on the REGION operand, so that CA XCOM Data Transport has enough storage to operate.

0558E

INVALID PARAMETER IN XCOMSTRT STARTUP LIST

Reason:

The master member of CA XCOM Data Transport 's start-up list that points to all the other members has invalid syntax.

Action:

To determine the proper syntax, see the chapter ―Configuring and Customizing

Your Product‖ in the CA XCOM Data Transport for z/OS Administration Guide.

Take the appropriate action.

0559I

xxxxxxxx ENABLE/DISABLED SUCCESSFULLY

Reason:

This message indicates that the member xxxxxxxx was either enabled or disabled successfully. A member can be enabled at CA XCOM Data Transport initialization automatically or through the enable operator command. The

DISABLE operator command disables a member.

Action:

None


0560E

0561E

0562E

Message Syntax

xxxxxxxx FOLLOWING FILE ERROR RECEIVED ON XCOMCNTL

Reason:

An error occurred while processing the CA XCOM Data Transport control library.

Action:

See subsequent messages.

xxxxxxxxxxxxxxxx yyyyyyyyyyyyyyyy CONFLICTING PARAMETERS IN

XCOMCNTL

Reason:

The two operands, xxxxxxxxxxxxxxxx and yyyyyyyyyyyyyyyy are mutually exclusive. The site has made an error coding operands in the member of the CA

XCOM Data Transport Dynamic Control library.

Action:

As fits your requirements, remove one of the conflicting parameters.

xxxxxxxx DUPLICATE PARAMETERS

Reason:

The same operand was specified more than once.

Action:

Delete one of the duplicates, disable, and then re-enable the dynamic definition library member.


Message Syntax

0563E

xxxxxxxx INVALID PARM IN XCOMCNTL MEMBER yyyyyyyy

Reason:

The operand xxxxxxxx is invalid.

Action:

To determine the correct spelling and syntax, see the chapter ―Configuring and

Customizing Your Product‖ in the the CA XCOM Data Transport for z/OS


Note: Earlier releases of CA XCOM Data Transport for z/OS may not support this operand.

0564E

xxxxxxxx TOO MANY PARMS IN XCOMCNTL MEMBER yyyyyyyy

Reason:

There is a limit of 16 logical units per group on one TYPE=DEST table entry, and there is a limit of 1024 LUs or Groups on a single list. This message indicates that one of these limits has been exceeded in a dynamic table definition.

Action:

Change your request to reduce the number of LUs and/or groups in a list.

0565E

xxxxxxxx INVALID VALUE FOR XCOMCNTL MEMBER yyyyyyyy

Reason:

While the Syntax operand specified is correct, the value is either invalid or out of range.

Action:

For the proper setting, see the chapter ―Configuring and Customizing Your

Product‖ in the CA XCOM Data Transport for z/OS Administration Guide.


0566E

0567E

0568E

0569E

Message Syntax

TYPE= PARAMETER NOT FIRST CARD IN XCOMCNTL MEMBER xxxxxxxx

Reason:

Either TYPE=DEST or TYPE=LIST must be the first operand in the first record in members of the CA XCOM Data Transport control library.

Action:

Make TYPE=DEST or TYPE=LIST the first operand in the first record in members of the CA XCOM Data Transport control library.

xxxxxxxx LU PARAMETER NOT DEFINED

Reason:

For TYPE=DEST members in the CA XCOM Data Transport control library, specify the SNA Logical Unit(s) which represent the remote computer(s). The LU name is required to acquire a session with that unit.

Action:

Edit the member, add the LU name, then enable the member.

xxxxxxxx LU/USER PARAMETERS BOTH DEFINED

Reason:

This message is for future use only.

Action:


xxxxxxxx GROUP NAME DEFINED NOT EQUAL TO MEMBER NAME

Reason:

The group name operand must specify a value that is the same as the member name.

Action:

Change the specified group name so that it matches the member name, and enable the CA XCOM Data Transport control library member.


Message Syntax

0570E

xxxxxxxx MULTIPLE LUS DEFINED WHEN PARSESS=YES

Reason:

If parallel sessions is defined, multiple logical units in a single group cannot be specified. These two features are mutually exclusive.

Action:

Select either parallel sessions or multiple LUs in a single group, and enable the

CA XCOM Data Transport control library member.

0571E

xxxxxxxx LOGMODE SNASVCMG NOT ALLOWED

Reason:

The mode name, SNASVCMG cannot be used in the remote node definitions. This mode name is reserved by SNA for a special ―manager‖ between LUs that support parallel sessions.

Action:

You must use another mode name.

0572E

xxxxxxxx WRITER AND DEST BOTH DEFINED

Reason:

An external writer and a destination cannot be defined for a Process SYSOUT request in the same member of the CA XCOM Data Transport control library.

Action:

Either remove one or code a second member with a different Group name (that is different member name).

0573E

xxxxxxxx WINNERS AND LOSERS INVALID WHEN PARSESS=NO

Reason:

WINNERS and LOSERS operands are invalid outside of parallel sessions.

Action:

Delete the WINNERS and LOSERS operands.


0574E

0575E

0576E

0577E

Message Syntax

xxxxxxxx MEMBER ALREADY ENABLED

Reason:

The member has already been enabled. The request is ignored.

Action:

For a recently edited member, disable first then re-enter the enable command.

xxxxxxxx ERROR GETMAINING AREA FOR XCOMCNTL FUNCTION

Reason:

A z/OS GETMAIN macro was issued to obtain storage for I/O to the CA XCOM

Data Transport control library.

Action:

Increase the value of the REGION operand in your JOB or EXEC Job Control

Language Statements. Contact CA Technical Support.

xxxxxxxx REMOTE PARTNER NAMES NOT DEFINED FOR LIST

Reason:

When defining a distribution list, an IPNAME, LU, or GROUP operand is required.

Action:

Define a distribution list with an IPNAME, LU, or GROUP operand.

xxxxxxxx LIST NAME NOT EQUAL TO MEMBER NAME

Reason:

CA XCOM Data Transport cannot define (that is ENABLE) this distribution list successfully. The LIST name must be the same as the member name in which it is defined.

Action:

Make the LIST name the same as the member name in which it is defined.


Message Syntax

0578E

xxxxxxxx LIST NAME ALREADY ENABLED

Reason:

The member has already been enabled. The request is ignored.

Action:

For a recently edited member, disable first then re-enter the enable command.

0579I

xxxxxxxx DISABLED SUCCESSFULLY

Reason:

CA XCOM Data Transport has successfully disabled a member of the CA XCOM

Data Transport control library.

Action:

None

0580E

xxxxxxxx MEMBER ALREADY DISABLED

Reason:

This member has already been disabled. The request is ignored.

Action:

None

0581E

xxxxxxxx NOT FOUND FOR LIST OR DISABLE COMMAND

Reason:

A group could not be found when the LIST or DISABLE operator commands were invoked.

Action:

Check the spelling of the group name in the command line.


0582E

0583E

0584E

Message Syntax

STATUS AND RELATIVE GENERATION NUMBER INVALID

Reason:

While CA XCOM Data Transport was processing a dynamic allocation for a generation data set (GDG), a return code of 0394 was received from SVC99.

When a GDG with a relative number of 0 is created, this problem could occur.

Action:

Supply a valid generation number and resubmit the request.

INVALID GENERATION NAME FOUND BY CATALOG LOCATE DURING

GDG CREATE PROCESSING

Reason:

CA XCOM Data Transport was processing a generation data group file and found a problem with the data set name. This happens if the GDG name received as a result of the LOCATE request points to a data set that does not conform to standard GDG conventions (that is, G0000V00).

Action:

Specify a valid GDG data set name and resubmit the request.

UNABLE TO ALLOCATE STORAGE FOR XCOM STARTUP

FUNCTION—XCOM TERMINATING

Reason:

There was an insufficient amount of virtual storage available for CA XCOM Data

Transport to initialize. The startup attempt was aborted.

Action:

Increase the amount of storage available in your JCL by editing the CA XCOM

Data Transport start-up Job Control Language. Adjust the value of the REGION= operand on the execute statement. Resubmit the JCL or re-enter the console

START CA XCOM Data Transport command.


Message Syntax

0585E

LIST OR GROUP NAME REQUIRED FOR ENABLE AND DISABLE

COMMANDS

Reason:

No LIST or GROUP name was given to enable or disable a member of the CA

XCOM Data Transport control library.

Action:

Re-enter the command with a LIST or GROUP name.

0586I

xxxxxxxx nnnn ACTIVE SESSIONS—DISABLE PENDING

Reason:

A DISABLE command was entered while one or more file transfers were in progress to this Group. The DISABLE command will be processed after all active transfers have completed. It is not necessary to re-enter the command.

Action:

None

0587I

TABLE=LIST,GENERATE=xxxxxxxx, NAME=yyyyyyyy

Reason:

This is an informational message issued in response to the LIST command, in which the group is a name of a dynamic or static list.

Action:

None


0588I

Message Syntax

GROUP=XXXXXXXX MODEL= N/A SETUP=XXX

ERROR STATE=XX PSO STATUS=XXXX

ACCSEC=XX

COMPNEG=XXX*

VERSION=9

PACK=XX RECSEP=XXX

COMPRESS=XXX

CVASCII=XXXX

CVEBCDIC=XXXX

CVBINARY=XXXX

MAXPACK=99999*

LOGNREQ=XX*

WRITER=XXXXXXXX

PSOWAIT=XX

NEWWTR=XXXX

PSOUSER=XXXXX

NEWDEST=XXXX

PSOPREF=XXXX*

GETSESS=XXX

PSODISP=XXXXXX*

DROPSESS=XXX

PSOCKPT=9999*

FERL=999*

TERL=99999*

SERL=999* VERL=999*

SWAIT=99999*

TIMEOUT=99999* LOGMODE=XXXXXXXX

SRUSIZE=99999 RRUSIZE=99999

PSPACE=99

SSPACE=99

PARSESS=XXX -->

PRPACE=99

SRPACE=99

WINNERS=999

NEGOTIATED: -->

WINNERS=999

LOSERS=999

LOSERS=999

ALERTS: CONV=X SESS=X SEC=X FILE=X GEN=X

LU = XXXXXXXX

Reason:

This message is displayed in response to the LIST group command. The parameters are those defined in control library members. The line showing negotiated winners and losers values is issued only for groups with

PARSESS=NO.

An asterisk (*) to the right of a value means that the parameter was not coded in the control member but was taken from the Default Options Table. The asterisk may appear next to the LOGNREQ, GETSESS, DROPSESS, LOGMODE, and VERL parameters.

Action:

None


Message Syntax

0592E

CNOS VARIABLE RECEIVED WHEN MODENAME NOT SNASVCMG

Reason:

The CA XCOM Data Transport server received an invalid LU command from a remote computer. The command ―Change Number Of Sessions‖ (CNOS) is valid only in parallel sessions, and when the mode name for the session is

―SNASVCMG‖. The session on which the command was received had a different mode name so file transfers to the remote computer or logical unit will not work.

Action:

Check the appropriate definitions on the remote system.

0593E

SINGLE SESSION BIND RECEIVED FOR PARALLEL SESSION LU

Reason:

The incoming BIND command specified one session, while the LU was defined for parallel sessions. The BIND is rejected.

Action:

Redefine for either single or parallel sessions.

0594E

PARALLEL SESSION BIND RECEIVED FOR SINGLE SESSION LU

Reason:

The incoming BIND command specified parallel sessions, while the LU was defined as a single session. The BIND is rejected.

Action:

Redefine for either single or parallel sessions.


0595E

0596E

0597E

Message Syntax

PARALLEL SESSION BIND RECEIVED FOR UNDEFINED LU/MODE PAIR

Reason:

A remote LU has not been predefined in the CA XCOM Data Transport control library for the parallel session. It received an incoming BIND that could not be mapped to a predefined node.

Action:

Add a member to the CA XCOM Data Transport Dynamic Control library that defines a node for a parallel session.

ACT COMMAND CANNOT BE USED TO ACTIVATE SESSIONS DEFINED AS

PARSESS=YES

Reason:

The F XCOM,ACT,luname command was used in an attempt to BIND a parallel session to a remote computer. This command is only valid when the remote LU uses a single LU session. The F XCOM,CNOS,luname command is used to send a

BIND to a LU defined for a parallel session.

Action:

Check the definition for your system, and see the chapter ―Operation and

Control‖ in the CA XCOM Data Transport for z/OS User Guide, for the correct syntax of these commands.

xxxxxx TASK LIMIT EXCEEDED ON INCOMING ALLOCATE—TRANSFER

TERMINATED

Reason:

The installation specifies an upper limit to the number of simultaneous file transfers. This limit was exceeded and the transfer terminated. CA XCOM Data

Transport can process many file transfer requests simultaneously. The maximum number of requests can be defined locally or remotely. This number can be changed by using the DFLT console command or by changing the default table limits of MACLOC, MAXREM, or MAXTASK.

Action:

Increase or remove the limit.


Message Syntax

0598E

xxxxxxxx GROUP NOT DEFINED IN XCOMDEST—REQUEST MARKED AS

ERROR

Reason:

The group name or operator command is not defined in the CA XCOM Data

Transport Dynamic Control library.

Action:

Check spelling of the group, and/or properly define the group or member.

0599E

nnnnnn TASK LIMIT EXCEEDED ON LOCAL ALLOCATE—TRANSFER

DELAYED

Reason:

The installation specifies an upper limit to the number of simultaneous file transfers. This limit was exceeded and the transfer has been delayed. CA XCOM

Data Transport can process many file transfer requests simultaneously. The maximum number of requests can be defined locally or remotely. This number can be changed by using the DFLT console command or by changing the default table limits of MACLOC, MAXREM, or MAXTASK.

Action:

Increase or remove the limit file transfers.

0600I

xxxxxx CNOS OPERATOR COMMAND ACCEPTED—WILL BE PROCESSED

ASYNCHRONOUSLY

Reason:

The CNOS command entered is being processed. The message shows that the operator command syntax is correct; CA XCOM Data Transport may still be in the process of establishing or manipulating the parallel sessions request.

Action:

None


0601E

0602E

0603E

Message Syntax

MODE NAME INVALID FOR CNOS GDS—MUST BE SNASVCMG

Reason:

CA XCOM Data Transport received a CNOS request from another logical unit but the request came on a session that was not bound with the mode name

SNASVCMG. This is a violation of SNA protocol.

Action:

Contact CA Technical Support. Be prepared to take a CA XCOM Data Transport trace if required.

INVALID PROGRAM STATE WITHIN XCOMCNOS

Reason:

CA XCOM Data Transport was processing a Change Number Of Sessions (CNOS) request but the program encountered an invalid state.

Action:


INVALID DATA RECEIVED ON CNOS TPN—NOT CNOS GDS

Reason:

CA XCOM Data Transport was processing a Change Number Of Sessions (CNOS) request but some data was encountered that is not a CNOS Generalized Data

Stream variable.

Action:



Message Syntax

0604E

NO DATA RECEIVED ON CNOS CONVERSATION

Reason:

CA XCOM Data Transport was processing a Change Number Of Sessions (CNOS) request and expected to receive a response from the other site but no response was received.

Action:


0605E

xxxxxxxxxxxxxxx—ERROR FOUND ON CNOS CONVERSATION

Reason:

CA XCOM Data Transport was processing a Change Number Of Sessions (CNOS) request and found an error within the CNOS Generalized Data Stream variable.

xxxxxxxxxxxxxxx will describe the data in question.

Action:

Recreate the problem and then contact CA Technical Support.

0606E

CNOS DATA RECEIVED NOT REQUEST DATA

Reason:

CA XCOM Data Transport was processing an incoming CNOS request but the data received was invalid.

Action:



0607E

0608E

0609I

Message Syntax

xxxxxxxx—ABNORMAL REPLY RECEIVED ON CNOS CONVERSATION

REPLY

Reason:

CA XCOM Data Transport was processing a locally initiated CNOS request but received an abnormal reply. xxxxxxxx defines the error.

Action:

Recreate the problem, then contact CA Technical Support.

xxxxxxxx—ABNORMAL REPLY RECEIVED ON CNOS CONVERSATION

REQUEST

Reason:

CA XCOM Data Transport processed a remotely initiated CNOS request but received an abnormal request. xxxxxxxx defines the error.

Action:


NEGOTIATED WINNERS=xxx NEGOTIATED LOSERS=yyy

Reason:

This is output from the operator console's CNOS command for nodes that support parallel sessions. Contention winners are those sessions that this node gets priority to use if both sides want to initiate a transmission simultaneously.

Contention losers are those sessions upon which the partner computer gets first preference.

Action:

None


Message Syntax

0610E

INVALID CNOS COMMAND—GROUP NOT ENTERED

Reason:

The CNOS operator command did not specify the group name, which is a required parameter.

Action:

Enter the command again after specifying the group name.

0611E

INVALID CNOS COMMAND SYNTAX

Reason:

The F XCOM,CNOS command was entered incorrectly.

Action:

Check the spelling of keywords and the out-of-range value. See the chapter

―Operation and Control‖ in the CA XCOM Data Transport for z/OS User Guide to determine the correct setting for this keyword.

0612E

INVALID CNOS COMMAND—WINNERS/LOSERS NOT NUMERIC

Reason:

The WINNERS and LOSERS operands are supposed to be set equal to the number of parallel sessions for contention winner sessions and contention loser sessions respectively. A non-numeric value is incorrect.

Action:

Assign numeric values for WINNERS/LOSERS.


0613E

0614E

0615E

Message Syntax

INVALID CNOS COMMAND—GROUP NOT PARSESS=YES

Reason:

F XCOM,CNOS, luname commands are only valid to parallel session nodes. The

ACTIVATE command will start a session to a single session node.

Action:

For the format of the ACTIVATE command, see the chapter ―Operation and

Control‖ in the CA XCOM Data Transport for z/OS User Guide.

INVALID CNOS COMMAND—GROUP NAME NOT FOUND

Reason:

An F XCOM,CNOS, luname command was entered for a group or LU that was not defined. CA XCOM Data Transport for z/OS requires that parallel sessions nodes be defined in the CA XCOM Data Transport control library.

Action:

Verify that the parallel sessions nodes have been properly defined in the CA

XCOM Data Transport control library.

INVALID CNOS REQUEST—CNOS REQUEST ALREADY ACTIVE

Reason:

A CNOS operator command was entered while CA XCOM Data Transport was already in the process of doing a CNOS operation. The first CNOS command must be complete before entering a second CNOS command.

Action:

Wait for completion of the first CNOS command and resubmit the request.


Message Syntax

0616E

xxxxxxxx yyyyyyyy REQUEST INVALID FOR PARALLEL SESSIONS

GROUP

Reason:

An invalid CANCEL request was entered for an LU (that is a group) defined to use parallel sessions. For parallel sessions nodes, the CNOS command must be used.

Action:

For more information about operator console commands, see the chapter

―Operation and Control‖ in the CA XCOM Data Transport for z/OS User Guide.

0617E

xxxxxxxx COMMAND REQUIRES REQUEST NUMBER FOR TCP/IP OR

PARALLEL SESSION LUs

Reason:

Entering a terminate or suspend command to a network node using parallel sessions requires an exact request number so that CA XCOM Data Transport knows which operation(s) to terminate or suspend.

Action:

Determine the request number through the console commands SHOW and

RSHOW as well as the TSO/ISPF operator control panels.

0618I

xxxxxx CNOS REQUEST PROCESSED SUCCESSFULLY

Reason:

A CNOS request has been successfully processed and an LU CNOS conversation has been processed successfully with the session partner.

Action:

None


0619E

0620E

0621E

Message Syntax

ACCESS DENIED—USER SECURITY LOAD MODULE NOT FOUND

Reason:

The load module that processes user security was not found.

Action:

Install the load module and add it the CA XCOM Data Transport load library.

TRANSFER TERMINATED DUE TO INVALID XCOMCNTL PARAMETER

Reason:

This message is issued only for a TYPE=EXECUTE job. If CA XCOM Data

Transport read the CA XCOM Data Transport control library and found a parameter in the node definition, then CA XCOM Data Transport terminated the file transfer.

Action:

Check the syntax of the control library member that defines the remote system.

For more information about this syntax, see the chapter ―Configuring and

Customizing Your Product‖ the CA XCOM Data Transport for z/OS Administration

Guide.

FOLLOWING ERROR RECEIVED PROCESSING XCOMCNTL FILE

Reason:

This message is issued at either start-up time or as a result of an enable or disable command being issued. The ENABLE or DISABLE operations of this remote node definition will not be processed and the command execution will fail. However, the CA XCOM Data Transport server will stay up.

Action:

See subsequent messages.


Message Syntax

0622E

xxxxxxxx FIELD IN ERROR ON EXIT PROGRAM SCHEDULE REQUEST

Reason:

CA XCOM Data Transport attempted to schedule a transfer request through its fast schedule facility, but found field xxxxxxxx in error.

Action:


0623E

USERID ON JOB CARD MATCHES USERID OF XCOM SERVER—JOB

SUBMISSION ABORTED

Reason:

The CA XCOM Data Transport security interfaces do not allow an operator to use a user ID for a file transfer that has the same access privileges as the CA XCOM

Data Transport server. In some companies, this would be a security risk.

Action:

Select another user ID for authorization purposes.

0624I

MAXTASKS=nnnn,MAXLOC=mmmm,MAXREM=ssss

Reason:

This message indicates the maximum number of concurrent file transfers. There are three limits; one for locally initiated file transfers, one for remotely initiated file transfers, and another for the total number of maximum transfers. The local and remote transfers do not have to add up to the total number of transfers.

Action:

Use the Server Storage Usage Worksheet (available on http://ca.com/supportconnect) to determine appropriate values for these parameters, or contact CA Technical Support.


0625E

0626E

0627E

Message Syntax

INVALID INQ CONSOLE COMMAND—SHOULD BE INQ,MAX

Reason:

An invalid console command INQUIRE was entered.

Action:

Check the syntax in the chapter ―Operation and Control‖ in the CA XCOM Data

Transport for z/OS User Guide, and then re-enter the command.

xxxxxxxx LOGMODE PARAMETER REQUIRED WHEN PARSESS=YES

Reason:

If you are using parallel sessions, it is necessary to define the mode name you will be using in the CA XCOM Data Transport Dynamic Control library member that describes this remote computer.

Action:

Define the mode name.

SUBMITTING ID NOT EQUAL TO USER PARM ON JOB CARD

Reason:

For a CA XCOM Data Transport job submit, USER= on job card was not the same as the user who initiated the transfer.

Action:

Revise the job card indicating a valid user.


Message Syntax

0628I

FUNCTION NOT AUTHORIZED FOR OPERATOR

Reason:

A user of the ISPF dialog interface attempted to perform a function for which he is not authorized.

Action:

Check with the site CA XCOM Data Transport administrator to determine why the function is not authorized. CA XCOM Data Transport provides sites with two ways to control access to these functions: (1) the Administrator Table and (2) Exit 4.

0629E

EXIT xx TURNED OFF—EXIT PROGRAM WAS NOT LOADED

Reason:

Exit xx was requested but was not loaded.

Action:

Check to see if the load module for this exit exists in CA XCOM Data Transport

LINKLIB.


0630I

Message Syntax

TASK: xxxxxxxx y...y

Reason:

The CA XCOM Data Transport console operator issued a START or STOP command for the task indicated by xxxxxxxx and one of the following conditions took effect:

■ ACTIVATED—The task was successfully activated in response to a START command.

■ ALREADY ACTIVE—The task requested via a START command is already active.

■

NOT ENABLED—The task requested via a START or STOP command was not enabled via the Default Table.

■ ACTIV. FAILED—A bad return code was received when an attempt was made to activate the task requested by a START command.

■ NOT DEFINED—A START or STOP command was entered for an inactive task.

■ NOT ACTIVE—A STOP command was entered for a task that is not active.

■ DEACTIVATED—The task requested in a STOP command was deactivated.

Action:

Take one of the following actions:

■

ACTIVATED—None.

■

ALREADY ACTIVE—None. The START command is ignored.

■

NOT ENABLED—Check and, if necessary, enable the task in the Default

Table. Reassemble and relink the table.

■ ACTIV. FAILED—Check the CA XCOM Data Transport and system logs for an accompanying message describing the failure (for example, ―Module Not

Found‖).

■

NOT DEFINED—Check the START or STOP command to ensure that a valid task name was specified. See the CA XCOM Data Transport for z/OS User

Guide for valid task names.

■ NOT ACTIVE—None. The STOP command is ignored.

■ DEACTIVATED—None.


Message Syntax

0637C

WAITING FOR xx uuuuuuuu UNITS

DSN-yyyyyyyyyyyyyyyyy

Where xx is the number of unit(s) needed.

Where uuuuuuuu is the device type (generic or esoteric).

Where yyyyyyyy is the data set name for the device requested.

Reason:

There were no online idle devices for the transfer to use at the time of the request. The request will be retried at a later point.

Action:

None

0637I

WAITING FOR xx uuuuuuuu UNITS

Reason:

A wrong local unit name (uuuuuuuu) was specified. The function responsible for generating this message is retried once the Default Options Table parameter

ERRINTV has been satisfied.

Action:

Check the correct name of the local unit.

0638E

NO MEMBER NAME SPECIFIED

Reason:

There was a non-generic transfer to a PDS member and no member name was specified on either the target or the sending system.

Action:

Specify a member name on either system.


0640E

0641I

0646E

Message Syntax

VTAM ERROR RETRY LIMIT EXCEEDED—TRANSFER TERMINATED

Reason:

In attempting to retry a transfer that was re-queued due to a VTAM error, CA

XCOM Data Transport has exceeded the limit specified by the VERL parameter in the Default Table. The transfer is terminated with a logic error.

Action:

Determine the cause of the VTAM error and submit the transfer again.

RC xxxx yyyy ON DYNAMIC ALLOCATION

Reason:

CA XCOM Data Transport attempted unsuccessfully to use a SVC 99 to dynamically allocate a z/OS data set. The message operand xxxx provides the

Dynamic Allocation Interface Routine (DAIR) codes. The message operand yyyy provides the Dynamic Allocation Return Codes (DARC). These errors will be retried at the CA XCOM Data Transport error interval.

Action:

The return codes in this message are IBM Dynamic Allocation codes (dynalloc errors). Look them up on TSO or in the appropriate IBM documentation.

NO ALIAS IN z/OS MASTER CATALOG—DSN=xxxxxxxx.xxxxxxxx...

Reason:

CA XCOM Data Transport, tried to create a data set, but found no alias name in the system master catalog matching the high level qualifier of the data set name indicated by xxxxxxxx.xxxxxxxx... in the message. CA XCOM Data Transport found the MSTRCATU parameter in the Default Table set to NO, indicating that updates to the master catalog are not allowed. The creation and cataloging of this data set would require an update to the master catalog and is, therefore, suppressed. The transfer is terminated with a file error.

Action:

Determine if the data set name was entered correctly. If so, contact the administrator of the system master catalog to obtain an alias for this data set name.


Message Syntax

0647I

LOGNREQ=xxx, CONVTYPE=yyyyyy

Reason:

This message is displayed only after a CA XCOM Data Transport LIST operator command has been displayed. xxx specifies the LOGNREQ parameter and can be

YES, NO, or blank. A blank field indicates that the parameter was not entered and will use the LOGNREQ parameter in the default table. yyyyyy specifies whether the CONVTYPE parameter was specified as MAPPED or BASIC.

Action:

None

0648I

SUCCESSFUL LOGON/LOGOFF REQUEST FOR USER yyyyyyyy

Reason:

This message is displayed when a user successfully logs on to, or logs off from,

CA XCOM Data Transport. xxx will specify ON for a LOGON, and OFF for a

LOGOFF request. The user that is logging on or off is identified as yyyyyyyy.

Action:

None

0649E

INVALID FIELD LENGTH IN IRMA ERROR MESSAGE BUFFER

Reason:

In parsing a multi-line message from an IRMA remote, CA XCOM Data Transport encountered an invalid length field containing non-numeric characters.

Action:

Contact your CA XCOM Data Transport administrator.


0650E

0651E

0652E

Message Syntax

VALUE xxxxxxxx IS TOO LONG FOR PARAMETER yyyyyyyy

Reason:

The user-specified value of xxxxxxxx is of incorrect length for parameter

yyyyyyyy. During assembly of the XCOMDFLT default options table, the keyword parameter xxxxxxxx has length restrictions.

Action:

For information about the keyword in error, see the chapter ―Configuring and


Administration Guide; then correct the error and rerun the job.

PARAMETER xxxxxxxx VALUE xxxxxxxx INVALID—MUST BE YES, Y, NO

OR N

Reason:

The value must be YES (Y) or NO (N). During assembly of the XCOMDFLT default options table, the keyword parameter xxxxxxxx can only be set to YES (Y) or NO

(N).

Action:

For information about the keyword in error, see the chapter ―Configuring and


Administration Guide; then correct the error and rerun the job.

PARAMETER xxxxxxxx VALUE yyyyyyyy INVALID—OUTSIDE OF

ALLOWABLE VALUES

Reason:

During assembly of the XCOMDFLT (XCOM Default Options Table), the keyword parameter xxxxxxxx was set to an invalid value of yyyyyyyy.

Action:

See the chapter ―Configuring and Customizing Your Product‖ in the CA XCOM

Data Transport for z/OS Administration Guide, to ascertain this keyword's valid values, then correct the error and rerun the job.


Message Syntax

0655I

REQUEST nnnnnn COMPLETED: xxxxxx...

Reason:

XCOMJOB TYPE=INQUIRE issues this message for each completed file transfer.

nnnnnn is the transfer number and xxxxxx... is the completion status.

Action:

None

0656I

NO HISTORY RECORD FOR REQUEST nnnnnn

Reason:

XCOMJOB TYPE=INQUIRE cannot find transfer nnnnnn in the history file for the

CA XCOM Data Transport region named in the STCAPPL= parameter.

Action:

None

0657I

REQUEST nnnnnn NOT COMPLETED: xxxxxx...

Reason:

XCOMJOB TYPE=INQUIRE issues this message for each file transfer that has not completed before the INQWAIT timer expires. nnnnnn is the transfer number and xxxxxx... is the status of the transfer.

Action:

None

0658I

NO TRANSFERS SPECIFIED IN XCOMINQ OR SYSIN01

Reason:

No request numbers were specified in the XCOMINQ file or in the OREQ= parameter for XCOMJOB TYPE=INQUIRE.

Action:

None


0659I

0660E

0661E

Message Syntax

XCOMINQ FILE PROCESSING ERROR

Reason:

An error occurred processing the file with DDNAME XCOMINQ.

Action:

None

REQUESTS IN XCOMINQ FILE EXCEED MAXIMUM OF xxxx—REQ # nnnnnn REMOVED

Reason:

The number of requests in the data set pointed to by DDNAME XCOMINQ exceeds the maximum allowable value of xxxx.

Action:

Reduce the number of transfers to be inquired about in the data set pointed to by the XCOMINQ DD card to a number that is less than the xxxx-specified system maximum.

TYPE=EXECUTE DISALLOWED BY INSTALLATION

Reason:

A TYPE=EXECUTE file transfer was attempted, but this function was disallowed by the installation.

Action:

Notify your CA XCOM Data Transport Systems Administrator or use

TYPE=SCHEDULE. See PARM Parameters in the CA XCOM Data Transport for

z/OS User Guide for explanations of TYPE=EXECUTE and TYPE=SCHEDULE.


Message Syntax

0663I

NNNNNNNN HISTORY RECORDS WRITTEN TO XXXXXXXX

Reason:

Indicates the number of history records that have been written out to the History

Output DD (as specified by the CA XCOM Data Transport default (XCOMDFLT) parameter HISTORY_OUT_DD).

Action:

None

0664X

HISTORY WRITE SKIPPED : reason code

Reason:

Indicates that the history records were not written to the History Output DD for the reason specified in the reason code.

Action:

Correct the error and rerun the history request.

0665I

XXXXXXXXX REQUEST RECEIVED

Reason:

The CA XCOM Data Transport server has received the specified request.

Action:

None


0668E

0669E

0670E

Message Syntax

INCOMPATIBLE COMPRESSION METHOD REQUESTED BY PARTNER

Reason:

One of two conditions has occurred. (A) If this CA XCOM Data Transport is initiating the request, the partner CA XCOM Data Transport has not responded in the negotiation process with the compression code this CA XCOM Data Transport requested at transfer initiation. (B) If the partner CA XCOM Data Transport initiated the transfer, the partner is requesting a compression method not supported on this CA XCOM Data Transport for this type of transfer, that is

VERSION=1.

Action:

For case (A), change the transfer parameter for compression from

COMPRESS=RLE|COMPACT|COMPACTL to one of the older COMPRESS=YES|NO selections. For case (B), change COMPRESS= as in case (A) above, or force the

CA XCOM Data Transport partner, if possible, to switch to a VERSION=2 transfer.

If none of these solutions works, contact CA Technical Support.

DATA SET NOT FOUND IN CATALOG

Reason:

One of two conditions has occurred. (A) The data set to be used as input for a file transfer could not be found in a catalog. (B) The generation data group for a generation data set could not be found in a catalog. In either condition, the transfer request is terminated with a file error.

Action:

For (A), determine if the FILEOPT parameter in the SYSIN01 file is correct. For

(B), make sure that the data set or generation data group has been catalogued.

NO SUPPORT FOR PDSE IN THE CURRENT VERSION

Reason:

The version of CA XCOM Data Transport under which you are running does not support Extended Partitioned Data Sets (PDS/E). The transfer request is terminated with a file error.

Action:

None


Message Syntax

0671E

DSN SPECIFIES VSAM CATALOG CLUSTER OR ALIAS NAME

Reason:

The data set name specified as output of a file transfer is either the name of or the alias of a VSAM catalog. Continuation of the file transfer would result in a corruption of the catalog and a loss of data. The transfer request is terminated with a file error.

Action:

Make sure the data set name is specified correctly.

0672I

CA XCOM(R) DATA TRANSPORT(R) r.r—GENERATION LEVEL nnnn

Reason:

This is an informational message appearing only in a ―batch‖ request of CA XCOM

Data Transport, indicating the release (r.r) and generation level (nnnn) of the CA

XCOM Data Transport you are running

Action:

None

0673E

INVALID CONTROL BLOCK PASSED TO #FREEMAIN ROUTINE

Reason:

This message is issued by the CA XCOM Data Transport storage release processor when it detects a request by CA XCOM Data Transport to release storage that it has not acquired. The request is ignored.

Action:

Report this error to CA Technical Support. Be sure to save supporting documentation such as the CA XCOM Data Transport log and any dumps that may have been taken before or after the error message.


0674E

0675E

0683C

Message Syntax

INVALID LENGTH PARAMETER PASSED TO #FREEMAIN ROUTINE

Reason:

This message is issued by the CA XCOM Data Transport storage release processor when it detects a request by CA XCOM Data Transport to release storage that it has acquired, but not with the requested length. The request is ignored.

Action:

Report this error to CA Technical Support. Be sure to save supporting documentation such as the CA XCOM Data Transport log and any dumps that may have been taken before or after the error message.

WRONG LRECL/RECLEN COMB IN VB DSET—nnnnn/nnnnn

Reason:

The logical record length nnnnn and block size nnnnn specified for a VB data set are contradictory. For Variable Blocked, the BLKSIZE must be at least four bytes larger than the LRECL.

Action:

Make the logical record length and block sizes consistent and retry the request.

JES2 DEPENDENT MODULE NOT FOUND—USING SSOB FIELDS

Reason:

This message is issued by the CA XCOM Data Transport Process SYSOUT subtask when it cannot find a usable copy of module XCOMJ001, the so-called

JES-dependent module. CA XCOM Data Transport attempts to continue execution, but may not process PSO requests correctly without this module.

Action:

JES2 sites should assemble and link-edit this module into the CA XCOM Data

Transport load library using the sample provided in CA XCOM Data

Transport.Rvrm.SAMPLIB(XCOMJ001). It is important that this module be assembled using the JES2 macro library associated with the JES2 running on the same system as CA XCOM Data Transport.


Message Syntax

0688E

GDG BASE NOT FOUND IN CATALOG

Reason:

The GDG data set name specified in a file transfer request did not have a corresponding GDG base record in the appropriate catalog. The transfer request is terminated.

Action:

Verify that the data set name was correctly specified. If so, define the GDG in the appropriate catalog.

0690E

xxxxxxxx NAME PARAMETER WAS NOT DEFINED FOR CONVERT

Reason:

The NAME parameter was not defined in the code page conversion table for the

PDS member xxxxxxxx. This error was encountered while attempting to ENABLE a code page conversion table.

Action:

Define the NAME parameter for the code page conversion table.

0691E

xxxxxxxx ALL CNVVAL00—FF PARAMETERS WERE NOT DEFINED

Reason:

One or more CNVVALxx parameters are missing from the code page conversion table for the PDS member xxxxxxxx. This error was encountered while attempting to ENABLE a code page conversion table.

Action:

Define any missing CNVVALxx parameters.


0692E

0693E

0694E

0695E

Message Syntax

xxxxxxxx UNABLE TO OBTAIN STORAGE FOR ENABLE COMMAND

Reason:

Not enough storage was available to enable a code page conversion table.

Action:

Attempt the translation later, after ensuring there is enough storage available.

xxxxxxxx LINK LIST LOGIC ERROR DURING ENABLE COMMAND

Reason:

An internal link list logic error occurred during ENABLE processing of a code page conversion table.

Action:


xxxxxxxx CONVERSION TABLE IS IN USE BY A DESTINATION

Reason:

The code page conversion table named xxxxxxxx is currently in use by one or more active destination(s).

Action:

To disable the code page conversion table, you must disable the destinations actively using the code page conversion table first.

xxxxxxxx CONVERSION TABLE IS NOT ENABLED, AND IS IGNORED

Reason:

While enabling a destination, a conversion parameter (CVASCII, CVBINARY, or

CVEBCDIC) was found specifying a code page conversion table that is not enabled.

Action:

Enable the code page conversion table from the CA XCOM Data Transport START

PDS member before enabling any destinations.


Message Syntax

0696E

INVALID LOCAL/REMOTE REQUEST INITIATION FLAG—REQUEST

DELETED

Reason:

CA XCOM Data Transport has received a file transfer request with an invalid or no request initiation flag and has deleted the request from the queue.

Action:

None

0697E

REQUEST DELETED DUE TO TASK AGING

Reason:

CA XCOM Data Transport has removed a file transfer that has aged off the queue.

Action:

None

0698E

LU xxxxxxxx SNA PROTOCOL VIOLATION, RU TOO LARGE

Reason:

CA XCOM Data Transport has received an SNA data request unit (RU) that is larger than the largest RU size agreed upon in the BIND for the session with LU

xxxxxxxx.

Action:

Check the LOGMODE being used for the session. If this LOGMODE specifies reasonable RU sizes, contact CA Technical Support.


0699E

0700E

0702E

Message Syntax

xxxxxxxx—ERROR IN MODEL PROCESSING

Reason:

CA XCOM Data Transport Dynamic Destination Processor found an error in the

MODEL while enabling member xxxxxxxx. This may be the result of one of the following:

■ The requested MODEL was not found in CA XCOM Data Transport control library.

■ Errors occurred during the MODEL initialization process.

■ The requested MODEL itself required prototype processing (nested MODELs are not allowed).

■

The requested MODEL is not a TYPE=DEST member.

Action:

Correct the error(s) in the control member and/or the model and enable the member again. See the chapter ―Configuration Parameters‖ in the CA XCOM

Data Transport for z/OS Administration Guide.

MUTUALLY EXCLUSIVE PARAMETERS ENTERED

Reason:

Mutually exclusive parameters were entered in a CA XCOM Data Transport control library member.

Action:

Correct the control library member, then issue the CA XCOM Data Transport

ENABLE command for that member.

CONCATENATED DATASETS ARE NOT ALLOWED FOR LCLDS01 FOR

TYPE=SCHEDULE TRANSFERS

Reason:

A user is attempting to concatenate DDs for the file transfer and

TYPE=SCHEDULE is specified in the PARM field for XCOMJOB.

Action:

Change the JCL to avoid the concatenation or use transfers of type EXECUTE.


Message Syntax

0703E

SWAREQ ERROR—UNABLE TO OBTAIN JFCB ADDRESS

Reason:

Internal error occurred.

Action:

If this persists call CA Technical Support.

0704E

LU xxxxxxxx REQUIRES A USER LOGON PRIOR TO FILE TRANSFER

Reason:

A user logon is required for this LU, but it has not occurred at the time of a file transfer attempt. The LU has the LOGNREQ=YES parameter in effect either from the Dynamic Destination table entry or the Default Options table.

Action:

The user must log on to CA XCOM Data Transport or the LOGNREQ=YES restriction must be removed.

0705E

MORE THAN ONE REMOTE SYSTEM IDENTIFIER SPECIFIED

Reason:

The parameters GROUP, IPNAME, LIST LU, and USER are mutually exclusive and may not be used in conjunction with each other.

Action:

Choose one of the above five methods of specifying the partner(s) you wish to communicate with.

0706E

RETURN CODE xxxxxxxx LOADING CNMNETV MODULE

Reason:

An error occurred loading the NetView interface module CNMNETV.

Action:

Determine the cause of the load error.


0707E

0708E

0709E

0710I

Message Syntax

NETVIEW PPI RC=xx—<REASON xx DESCRIPTION>

Reason:

CA XCOM Data Transport received a non-zero return code from the NetView PPI interface. The specific reason will be listed in the message.

Action:

Take appropriate action based on the message content.

NOT ALL REQUIRED PARMS ENTERED FOR SDSNOTE

Reason:

While performing SDS script processing, SDSNOTE found that one or more of the required parameters were not entered.

Action:

Check the SYSIN data set, add the needed parameters, then try to rerun the script.

WRONG PARM/VALUE/SYNTAX IN SDSNOTE SCRIPT

Reason:

SDSNOTE found an error while processing the SDS script.

Action:

Correct the error and run the script again.

xxxxxxxx PING CONFIRMATION RECEIVED—rrrr

Reason:

CA XCOM Data Transport server received xxxxxxxx (negative|positive) confirmation from the SDS server after sending a SDS note. rrrr-return code received from the SDS server.

Action:

None


Message Syntax

0714E

VTAM COMMAND TIMEOUT, ABORTING SESSION WITH SLU=xxxxxxxx

Reason:

VTAM command time-out interval as specified in the TIMEOUT parameter has been exceeded and the session has been terminated abnormally.

Action:

Review the CA XCOM Data Transport log for additional information and try to determine why the partner LU is unavailable.

0715W

LOAD MODULE xxxxxxxx NOT CREATED DURING XCOM INSTALLATION

Reason:

The specified load module was not created during the CA XCOM Data Transport for z/OS installation procedure.

Action:

Find the installation step that was skipped and perform that step. An example would be updating and running a job to assemble and link-edit nodule xxxxxxxx.

0716I

xxxxxxxx PENDING QUEUED SESSION TERMINATED

Reason:

The session was not completed within the time-out limit. The pending session has been terminated.

Action:

Determine why the partner LU was unavailable. For group transfers, the next LU in the group will be tried.


0717E

0718E

0719I

Message Syntax

XCOM/NETVIEW ALERT INTERFACE DISABLED

Reason:

An unrecoverable error occurred in the CA XCOM Data Transport/NetView interface. The interface is disabled.

Action:

Look for other messages indicating the reason for the unrecoverable error.

ADMINISTRATOR TABLE NOT FOUND—XCOM TERMINATING

Reason:

CA XCOM Data Transport was unable to load the Administrator Table (load module XCOMADMT) and OPERSEC=USER and EXIT=NO were specified in the

Default Options Table, implying that CA XCOM Data Transport should check operator requests against this table. CA XCOM Data Transport terminates execution.

Action:

Verify that the XCOMADMT load module has been created and resides either in a system link list library or one of the libraries accessible via the CA XCOM Data

Transport server's JOBLIB or STEPLIB DD statement. For more information about creating an Administrator Table, see the CA XCOM Data Transport for z/OS

Administration Guide.

SESSION ESTABLISHED WITH SLU=xxxxxxxx, MODE=xxxxxxxx,

CID=xxxxxxxx, DEST=xxxxxxxx

Reason:

This message is issued when CA XCOM Data Transport establishes a session with a partner in which it is serving as the primary logical unit (PLU). The following information is provided in the message:

SLU

MODE

CID

DEST

Logical unit name of the secondary logical unit (that is, the partner)

Name of the logmode entry being used by the partner

VTAM CID identifying this session

Name of the CA XCOM Data Transport destination member associated with this request (**NONE** if there is none)


Message Syntax

Action:

None

0720I

TRANSFER INTERRUPTED BY CANCEL IMMEDIATE OPERATOR REQUEST

Reason:

An active transfer request has been stopped due to the issuance of the console operator command CANCEL to cancel the session with the LU being used for the transfer.

If the CANCEL command was specified with the IMMED option, the transfer will be retried after the error interval; if checkpointing was in effect, the transfer will be restarted from the most recent checkpoint.

If the CANCEL command was specified with the PURGE option, the transfer is terminated immediately and it will not be retried.

If the CANCEL command was specified with the SUSPEND option, the transfer will be retried only after the console operator command RESUME has been issued.

Action:

None

0721I

STOP COMMAND RECEIVED—XCOM ORDERLY SHUTDOWN INITIATED

Reason:

This message is issued when a z/OS STOP command is issued for the CA XCOM

Data Transport server. CA XCOM Data Transport stops processing any new or queued transfer requests, but attempts to let active transfers proceed to completion.

Action:

This is the preferred method of stopping CA XCOM Data Transport (issuing an F

XCOM,STOP command performs the equivalent action). If CA XCOM Data

Transport fails to terminate, a second z/OS STOP command may be issued (the

F XCOM,STOP IMMED command performs the equivalent action for this second command). This will result in the immediate termination of the CA XCOM Data

Transport server (see the description of message 0722I).


0722I

0723E

0724E

Message Syntax

SECOND STOP COMMAND RECEIVED—XCOM IMMEDIATE SHUTDOWN

INITIATED

Reason:

This message is issued when a second z/OS STOP command is issued for the CA

XCOM Data Transport server. CA XCOM Data Transport immediately terminates without attempting to quiesce any active transfers.

Action:

This method of stopping CA XCOM Data Transport should b used only if the first

STOP command fails to terminate the server once any active transfer requests have completed.

dddddddd xxx-yy OP DCB ABEND EXIT ENTERED

Reason:

The PSO interface encountered an xxx-yy abend code while copying data for destination dddddddd.

Action:

Take appropriate action for the specified abend code. If the problem persists, contact CA Technical Support.

PSO ERROR: DEST=dddddddd, JOB=jjjjjjjj, JOBID=iiiiiiii, DD=ssssssss,

DSN=xxxxxxxx.xxxxxxxx.xxxxxxxx.xxxxxxxx.xxxxxxxx

Reason:

The PSO interface encountered an error processing a JES spool data set for destination dddddddd. The spool file causing the error can be identified by the

JOB, JOBID, DD, and DSN parameters. CA XCOM Data Transport will prompt the operator for action.

Action:

See message 0725E.


Message Syntax

0725A

DEST=xxxxxxxx REPLY ―R‖ TO RETRY, ―C‖ TO CANCEL

Reason:

An error has occurred as described in message 0724E. CA XCOM Data Transport is prompting the operator for action.

Action:

A reply of R causes CA XCOM Data Transport to retry the specified destination at the next defined PSO interval. A reply of C disables the PSO interface for this destination. The job causing the error should be held or deleted before replying

R. If a destination is disabled (due to a C reply), it can be activated by disabling or enabling the control library member.

0726E

REPLY INVALID—IGNORED

Reason:

An invalid response was received to a WTOR.

Action:

Enter a valid response.

0727I

JOB=jjjjjjjj, JOBID=iiiiiiii, DD=dddddddd, DEST=ssssssss, COPIED TO xxxxxxxx.xxxxxxxx.xxxxxxxx.xxxxxxxx

Reason:

The PSO interface has successfully copied data identified by the JOB, JOBID, and

DD parameters to the specified data set.

Action:

None


0728E

0729E

0730E

Message Syntax

FILE ERROR xxxxxxxx

Reason:

This message is issued when the CA XCOM Data Transport file access routines experience a physical or logical I/O error. xxxxxxxx is a descriptive error message obtained by invoking the z/OS SYNADAF service routine at the time of the error.

Action:

Examine the description returned from the SYNADAF service routine to determine the cause of the error and take corrective action before retrying the transfer request.

dddddddd REPORT NOT QUEUED, WILL BE RETRIED LATER

Reason:

A PSO transfer could not be queued. The data will be copied again and retried.

Action:

Review XCOMLOG for related messages about the possible causes of this condition. If the problem persists, contact CA Technical Support.

XCOMTASK UNABLE TO FIND DEST ENTRY FOR PSO DATA

Reason:

CA XCOM Data Transport was notified that PSO data was ready to be queued for transfer, but CA XCOM Data Transport could not find the PSO request.

Action:

If the problem persists, contact CA Technical Support.


Message Syntax

0731I

xxxxxxxx IN USE BY PSO TASK, DISABLE PENDING

Reason:

This message is issued when a DISABLE command is issued for a control library member that is in use by the PSO subtask. CA XCOM Data Transport marks the request as pending (that is, it will be processed when the PSO subtask has finished its processing).

Action:

None

0732E

xxxxxxxx COMMAND FAILED—DEST yyyyyyyy IN PROCESS OF BEING

DISABLED

Reason:

Command xxxxxxxx was issued for the control library member yyyyyyyy but could not be processed because a DISABLE command was pending for that member.

Action:

If an ENABLE command was issued, reissue the command once the control library member has been disabled. For any other command, wait for the

DISABLE command to be processed, then issue an ENABLE command for the control library member before reissuing the failing command.

0733E

TYPE=EXECUTE TRANFERS NOT ALLOWED WHEN LOGNREQ=YES IS IN

EFFECT FOR LU

Reason:

A TYPE=EXECUTE transfer cannot take place because a user logon is required for transfers to this LU.

Action:

Specify LOGNREQ=NO in the control library member.


0734E

0735E

Message Syntax

xxxxxxxx DUPLICATE LU NAME PRESENT IN GROUP

Reason:

This message is issued when an LU name is specified more than once in a control library member. It may be issued during CA XCOM Data Transport initialization or when an ENABLE command is processed for the member. CA XCOM Data

Transport continues execution but does not enable the control library member.

Action:

Correct the LU specification for the member, then issue an ENABLE command to enable it for use by CA XCOM Data Transport.

SESSION ERROR RETRY LIMIT EXCEEDED, TRANSFER TERMINATED

Reason:

This message is issued when a transfer exceeds the number of session acquisition failures permitted by the SERL (Session Error Retry Limit) parameter in effect for the partner LU. This may be specified in a control library member for that LU or the Default Options Table. CA XCOM Data Transport terminates the transfer request.

Action:

Other error messages will be issued prior to this indicating the reason for the session acquisition failures. Examine these messages to determine whether an abnormal condition exists. Additionally, the SERL parameter in the control library member (if any) or Default Options Table can be adjusted to meet installation criteria.


Message Syntax

0736E

FILE ERROR RETRY LIMIT EXCEEDED, TRANSFER TERMINATED

Reason:

This message is issued when a transfer exceeds the number of file access errors permitted by the FERL (File Access Error Retry Limit) parameter in effect for the partner LU. This may be specified in a control library member for that LU or the

Default Options Table. CA XCOM Data Transport terminates the transfer request.

Action:

Other error messages will be issued prior to this indicating the reason for the file access errors. Examine these messages to determine whether an abnormal condition exists. Additionally, the FERL parameter in the control library member

(if any) or Default Options Table can be adjusted to meet installation criteria.

0737E

SUM TOTAL ERROR RETRY LIMIT EXCEEDED, TRANSFER TERMINATED

Reason:

This message is issued when a transfer exceeds the total number of errors permitted by the TERL (Total Error Retry Limit) parameter in effect for the partner LU. TERL is the aggregate of errors covered by the FERL, SERL, and VERL parameters. This may be specified in a control library member for that LU or the

Default Options Table. CA XCOM Data Transport terminates the transfer request.

Action:

Other error messages will be issued prior to this indicating the reason for the file access errors. Examine these messages to determine whether an abnormal condition exists. Additionally, the TERL parameter in the control library member

(if any) or Default Options Table can be adjusted to meet installation criteria.


0738E

0739E

0740E

Message Syntax

SESSION CREATION FAILED SECURITY AUTHORIZATION

Reason:

This message is issued when LU access security is in effect for the partner LU involved in the transfer request. CA XCOM Data Transport has determined that the user is not authorized to create a session with that LU and has terminated the request.

Action:

Verify that the correct LU name has been specified. If so, contact your site security administrator to obtain the required access level to use this LU with CA


PARTNER SECURITY CHECK FAILED BY USER EXIT 12

Reason:

This message is issued when LU access security is in effect for the partner LU involved in the transfer request. User Exit 12 has told CA XCOM Data Transport to fail the user's request to use the partner LU. CA XCOM Data Transport terminates the transfer request.

Verify that the correct LU name has been specified. If so, contact your site security administrator to obtain the required access level to use this LU with CA


COMMAND xxxxxxxx FAILED BY SECURITY

Reason:

This message is issued when command security checking is being used to validate authority to use CA XCOM Data Transport operator functions. The user attempted to execute command xxxxxxxx and the request was rejected by the site security package. CA XCOM Data Transport does not execute the requested command.

Action:

Contact the site security administrator to obtain the required access level to execute the command.


Message Syntax

0741I

NEGOTIATING COMPRESSION METHOD FROM COMPRESS=xxxxxx TO

COMPRESS=yyyyyy

Reason:

This message is issued when CA XCOM Data Transport receives a transfer request from a remote system that wishes to use a compression method that this

CA XCOM Data Transport does not support. CA XCOM Data Transport responds by negotiating to a compression type that both can support (or disabling compression in some cases). xxxxxx indicates the original compression method requested by the remote system; yyyyyy indicates the compression method this

CA XCOM Data Transport has negotiated to use.

Action:

Check with CA Technical Support to determine whether there is a more current version of the CA XCOM Data Transport product that supports the requested compression method.

0742E

INSUFFICIENT STORAGE FOR OPERATOR SECURITY

CHECKING—COMMAND REJECTED

Reason:

This message is issued when security checking is in effect for operator commands (that is, OPERSEC=SAF has been specified in the Default Options

Table). CA XCOM Data Transport is unable to acquire storage required to make the requested security check. As a result, the command is not executed.

Action:

Retry the command after a short pause to determine if storage is then available.

If this error occurs frequently, try to raise the region size for the CA XCOM Data

Transport server. If the problem still is not corrected, contact CA Technical

Support.


0743E

0744E

0745E

Message Syntax

COMMAND NOT AUTHORIZED FROM THIS CONSOLE

Reason:

This message is issued when security checking has been requested for operator commands. It indicates that the command cannot be executed from the console from which it was entered. This can occur for one of two reasons:

■ The operator is not authorized to issue the command (in cases where the operator has logged on at the console using a z/OS LOGON command).

■ The console has an insufficient z/OS console authority level for the requested command (in cases where the operator has not logged on or operator logon is not supported by the operating system).

Action:


COMMAND SECURITY CHECK FAILED BY USER EXIT 13

Reason:

This message is issued when security checking has been requested for operator commands and the operator's request has been rejected by User Exit 13. The command is not executed.

Action:


xxxxxxxx yyyyyyyy UNAVAILABLE, DSN=dddddddd

Reason:

CA XCOM Data Transport was unable to obtain exclusive use of the system resource. The file transfer is suspended until the next error interval. xxxxxxxx,

yyyyyyyy, and dddddddd identify the resource.

Action:

None


Message Syntax

0746E

TRANSFER TERMINATED: LIBRARY NEGOTIATION=NO

Reason:

CA XCOM Data Transport has failed a transfer request because the LIBNEG parameter is set to NO.

Action:

None

0747I

TRANSFER END DATE/TIME EXPIRED, TRANSFER DELETED

Reason:

Informational message indicating that the transfer has been deleted from the queue.

Action:

None

0778E

PARTNER DOES NOT SUPPORT LARGE PACKING FEATURE

Reason:

CA XCOM Data Transport on the remote system only supports a packing block size of 2048 bytes.

Action:

Perform one of the following actions:

■ Change the MAXPACK value specified for this destination in the CA XCOM

Data Transport control library to 2048.

■ Change the system default for MAXPACK in the CA XCOM Data Transport

Default Options Table (XCOMDFLT) to 2048.

■ Code PACK=NO in the SYSIN01 for this transfer.


0779E

0780E

0781E

Message Syntax

yyyy ABEND DETECTED—XCOM RECOVERING, IP = zzzz

Reason:

The CA XCOM Data Transport TCP/IP subtask for IP address zzzz has abended with abend code yyy, terminating the transfer request. The CA XCOM Data

Transport server will continue working.

Action:

Examine the abend code to determine the appropriate action.

TXPI nnn xxxxxxxxxxxxxxxx return value = zzz

Reason:

xxxxxxxxxxxxxxxx is the TCPIP function that failed. zzz is the return value from

TCP/IP causing the transfer request to terminate. This message usually indicates a failing socket function and the error return value.

Action:

Examine the message to determine the appropriate action; many errors are the result of the specification of the wrong IPNAME or IPPORT, configuration problems, name resolution, or network problems.

The return values are in the IBM data set CEE.SCEEH.H(ERRNO). The high level qualifier may differ at your site.

These codes are not CA XCOM Data Transport error codes, but are passed back from TCP/IP.

SUBTASK NOT RESPONDING—CANCELLING IP = zzzz

Reason:

The CA XCOM Data Transport TCP/IP subtask for IP address zzzz is being cancelled due to an error condition causing it to be in an invalid state. The transfer request will terminate and the CA XCOM Data Transport server will continue working.

Action:

Re-execute the request.


Message Syntax

0782E

INVALID TCP/IP COMMAND—INTERNAL ERROR

Reason:

Internal logic error. The request will terminate and the CA XCOM Data Transport server will continue working.

Action:

Contact CA XCOM Data Transport client services.

0783E

xxxxxxxx REQUEST ENDED DUE TO TCP/IP ERROR

Reason:

The SEND or RECEIVE request ended due to a TCP/IP error.

Action:

Examine the preceding message 0780E for the cause.

0784E

UNABLE TO GETMAIN STORAGE FOR XCOM TCP/IP BUFFER

Reason:

Insufficient storage for a CA XCOM Data Transport TCP/IP subtask buffer, causing the request to terminate. The CA XCOM Data Transport server will continue working.

Action:

Change the JCL that brings up the server, increasing the value of the REGION operand so that CA XCOM Data Transport has enough storage to operate.

0785I

STARTING TCP/IP CONNECTION TO PORT=yyyyy, IP=zzzz

Reason:

This message indicates that a TCP/IP connection is being started to IP address

zzzz, port yyyyy.

Action:

None


0786I

0787I

0788I

Message Syntax

TCP/IP CONECTION ESTABLISHED WITH DEST=xxxxxxxx,

PORT=yyyyy, IP=zzzz

Reason:

This message indicates that a TCP/IP connection was successfully made to IP address zzzz, port yyyyy, for destination xxxxxxxx.

Action:

None

TCP/IP ERRORS DURING LISTENER ESTABLISHMENT, NO REMOTE

CONNECTIONS AVAILABLE

Reason:

This message indicates that TCP/IP errors occurred during the establishment of the CA XCOM Data Transport server listener subtask, and no TCP/IP remote connections are available due to these errors.

Action:

Examine the preceding message 0780E for the cause. The server must be stopped and started again to retry.

XCOM TCP/IP LISTENER ACTIVE ON PORT yyyyy, IP ADDRESS=zzzz

Reason:

The CA XCOM Data Transport server TCP/IP listener subtask successfully started on port yyyyy at IP address zzzz.

Action:

None


Message Syntax

0789E

INVALID TPNAME RECEIVED FROM TCP/IP CONNECTION

Reason:

A remote TCP/IP partner sent an invalid TPNAME during session establishment.

Action:

None

0790E

TCP/IP TASK LIMIT EXCEEDED ON INCOMING ACCEPT—TRANSFER

TERMINATED

Reason:

The maximum number of incoming TCP/IP tasks for an IP address is exceeded, the remote request is terminated.

Action:

Increase or remove the limit specified by TCPSESS.

0791E

TIMER EXPIRED—TRANSFER TERMINATED, IP=zzzz

Reason:

CA XCOM Data Transport issued a TCP/IP command and before it could complete the prevailing TIMEOUT parameter had already been exceeded. CA XCOM Data

Transport times out and the transfer terminates. zzzz is the IP address of the remote partner. This message is issued only for TYPE=EXECUTE transfers.

Action:

You have three options: (1) queue this file transfer and rerun the operation;

(2) determine why the partner is unavailable and take appropriate measures; and (3) increase the time-out value and rerun the operation.


0792E

0793I

0794E

Message Syntax

TCP/IP SESSION TIMEOUT, ABORTING CONNECTION WITH IP=zzzz

Reason:

The timeout interval as specified in the TIMEOUT parameter has been exceeded and the session has been terminated abnormally.

Action:

Try to determine why the partner is unavailable.

TCP/IP REMOTE CONNECTION ESTABLISHED FROM IP=zzzz

Reason:

A TCP/IP remote connection was successfully established from IP address zzzz.

Action:

None

Note: If a destination member has been selected for this particular transfer, this message is displayed a second time, with DEST=xxxxxxxx on the second line.

RECURSIVE ERROR DETECTED, TCP/IP LISTENER TERMINATED

Reason:

The CA XCOM Data Transport TCP/IP listener subtask encountered a recursive

TCP/IP error.

Action:

Examine the log for 0780E messages indicating the cause. Cycle CA XCOM Data

Transport to start the listener subtask.


Message Syntax

0795I

FOLLOWING FMH7 SENT TO CONVERSATION PARTNER, IP=zzzz

Reason:

XCOM detected an error and is about to send an error message to its conversation partner.

Action:

Additional messages follow this one. Review the additional messages to determine the exact cause of this error.

0796I

SHUTDOWN IN PROGRESS, TCP/IP REMOTE CONNECTIONS NO LONGER

AVAILABLE

Reason:

The STOP command was entered and the CA XCOM Data Transport server is terminating. No new TCP/IP connections will be established by the listener subtask.

Action:

None

0797E

CA90s HAS NOT BEEN INITIALIZED; PRODUCT CHECKING CANNOT BE

PERFORMED ON THIS CPU

Reason:

CA90s has not been initialized on this CPU; product checking for CA XCOM Data

Transport cannot be performed.

Action:

Execute CA90s before starting CA XCOM Data Transport.


0798E

0799I

0800E

Message Syntax

TCP/IP TASK LIMIT EXCEEDED ON LOCAL ALLOCATE—TRANSFER

DELAYED

Reason:

The installation specifies an upper limit on the number of simultaneous file transfers to any one IP address. The limit has been exceeded and the transfer has been delayed.

Action:

Increase or remove the limit specified by TCPSESS.

TCPSESS=nnn

Reason:

This message indicates the maximum number of concurrent file transfers to any one IP address. The range is 0 to 128 (0 indicates the number of concurrent file transfers is unlimited).

Action:

None

ERROR ATTACHING TXPI SUBTASK

Reason:

The attach of the TXPI subtask for TCP/IP failed, due to insufficient storage.

Action:

Use the Server Storage Usage Worksheet (available on http://ca.com/supportconnect ) to determine an appropriate region size and appropriate values for the tuning parameters, or contact CA Technical Support.


Message Syntax

0801E

TCP/IP OPTION SPECIFIED BUT NOT INSTALLED—TCP/IP CANNOT BE

ENABLED

Reason:

Configuration error; the Default Options Table parameter TCPIP=YES was specified, but the TCP/IP option is not installed.

Action:

Install the TCP/IP option.

0802E

TCP/IP OPTION SPECIFIED BUT IS NOT ENABLED—CONNECTION

CANNOT BE ESTABLISHED

Reason:

A TCP/IP transfer was specified, but the TCP/IP option is not enabled.

Action:

Specify the default table parameter TCPIP=YES.

0803I

STARTING XCOM TCP/IP LISTENER

Reason:

The CA XCOM Data Transport server is starting the TCP/IP listener subtask.

Action:

None. Message 0788I or 0787E will follow.

0804E

UNABLE TO GETMAIN STORAGE FOR TCP CONTROL BLOCK

Reason:

Insufficient storage for a CA XCOM Data Transport TCP buffer caused the request to terminate. The CA XCOM Data Transport server continues working.

Action:

Change the JCL that brings up the server, increasing the value of the REGION operand so that CA XCOM Data Transport has enough storage to operate.


0805I

0806I

0807I

0808I

Message Syntax

TCP/IP CONNECTION ENDED WITH IP=ipaddress

Reason:

A TCP/IP connection with IP address ipaddress completed.

Action:

None

STARTING XCOM TCP/IP SSL LISTENER

Reason:

The CA XCOM Data Transport server is starting the secure TCP/IP listener subtask.

Action:


XCOM TCP/IP SSL LISTENER ACTIVE ON PORT port, IP

ADDRESS=ipaddress

Reason:

The CA XCOM Data Transport server secure TCP/IP listener subtask successfully started on port port at IP address ipaddress.

Action:

None

SHUTDOWN IN PROGRESS, TCP/IP SSL REMOTE CONNECTIONS NO

LONGER AVAILABLE

Reason:

The STOP command was entered and the CA XCOM Data Transport server is terminating. No new secure TCP/IP connections will be established by the listener subtask.

Action:

None


Message Syntax

0809E

TARGET SERVER DOES NOT SUPPORT SECURE_SOCKET=YES

Reason:

The schedule request is rejected because the CA XCOM Data Transport server is configured to reject secure TCP/IP.

Action:

Specify SECURE_SOCKET=NO and rerun the schedule request or contact your

CA XCOM Data Transport administrator.

0810E

TARGET SERVER REQUIRES SECURE_SOCKET=YES

Reason:

The schedule request is rejected because the CA XCOM Data Transport server is configured to only accept secure TCP/IP.

Action:

Specify SECURE_SOCKET=YES and rerun the schedule request or contact your

CA XCOM Data Transport administrator.

0811I

STARTING SECURE TCP/IP CONNECTION TO PORT=port, IP=ipaddress

Reason:

A secure TCP/IP connection is being started to IP address ipaddress, port port.

Action:

None


0812I

0813I

0814I

Message Syntax

SECURE TCP/IP REMOTE CONNECTION REQUESTED FROM IP=ipaddress

Reason:

A request for a secure TCP/IP remote connection was received from IP address

ipaddress.

Action:

None

Note: If a destination member has been selected for this particular transfer, this message is displayed a second time, with DEST=xxxxxxxx on the second line.

SECURE TCP/IP CONNECTION REQUESTED WITH DEST=**NONE**,

PORT=08045, IP=ipaddress

Reason:

A request for a secure TCP/IP connection was sent to IP address ipaddress, port

port, for destination destination.

Action:

None

SECURE SOCKET HANDSHAKE COMPLETED SUCCESSFULLY

IP=ipaddress

Reason:

Secure Socket (SSL) negotiation for the connection with IP address ipaddress successfully completed. The connection is now a secure TCP/IP connection.

Action:

None


Message Syntax

0815I

TCP/IP ERRORS DURING SSL LISTENER ESTABLISHMENT, NO REMOTE


Reason:

TCP/IP errors occurred during the establishment of the CA XCOM Data Transport server SSL listener subtask. No secure TCP/IP remote connections are available due to these errors.

Action:


0816I

RECURSIVE ERROR DETECTED, TCP/IP SSL LISTENER TERMINATED

Reason:

CA XCOM Data Transport SSL TCP/IP listener subtask encountered a recursive

TCP/IP error.

Action:

Examine the log for 0780E messages indicating the cause. Cycle CA XCOM Data

Transport to start the listener subtask.

0817E

STCIP= PARAMETER MISSING—CANNOT CONNECT TO SERVER

Reason:

The schedule request over TCP/IP cannot be processed without the STCIP parameter.

Action:

Specify the STCIP parameter and retry the schedule request.

If you want to schedule over SNA instead of TCP/IP, use an XCOMDFLT with SNA set to YES.


0818I

0820I

0821I

0822I

Message Syntax

SECURE TCP/IP CONNECTION ENDED WITH IP=ipaddress

Reason:

A secure TCP/IP connection with IP address ipaddress completed.

Action:

None

STARTING XCOM TCP/IPV6 LISTENER

Reason:

The CA XCOM Data Transport server is starting the TCP/IPv6 listener subtask.

Action:


STARTING XCOM TCP/IPV6 SSL LISTENER

Reason:

The CA XCOM Data Transport server is starting the secure TCP/IPv6 listener subtask.

Action:


XCOM TCP/IPV6 LISTENER ACTIVE ON PORT port, IP

ADDRESS=ipaddress

Reason:

The CA XCOM Data Transport server TCP/IPv6 listener subtask successfully started on PORT port at IP address ipaddress.

Action:

None.


Message Syntax

0823I

XCOM TCP/IPV6 SSL LISTENER ACTIVE ON PORT port, IP

ADDRESS=ipaddress

Reason:

The CA XCOM Data Transport secure server listener for TCP/IPv6 subtask successfully started on PORT port at IP address ipaddress.

Action:

None.

0824E

TCP/IPV6 ERRORS DURING LISTENER ESTABLISHMENT, NO REMOTE


Reason:

This message indicates that TCP/IP errors occurred during the establishment of the CA XCOM Data Transport server listener subtask, and that no TCP/IPv6 remote connections are available due to these errors.

Action:


0825E

TCP/IPV6 ERRORS DURING SSL LISTENER ESTABLISHMENT, NO

REMOTE CONNECTIONS AVAILABLE

Reason:

This message indicates that TCP/IP errors occurred during the establishment of the CA XCOM Data Transport server secure listener subtask, and that no

TCP/IPv6 remote connections are available due to these errors.

Action:



0826E

0827E

0828I

Message Syntax

RECURSIVE ERROR DETECTED, TCP/IPV6 LISTENER TERMINATED

Reason:

The CA XCOM Data Transport TCP/IPv6 listener subtask encountered a recursive

TCP/IP error.

Action:

Examine the log for 0780E messages indicating the cause. Stop and start the CA

XCOM Data Transport to start the listener subtask.

RECURSIVE ERROR DETECTED, TCP/IPV6 SSL LISTENER TERMINATED

Reason:

The CA XCOM Data Transport TCP/IPv6 secure listener subtask encountered a recursive TCP/IP error.

Action:

Examine the log for 0780E messages indicating the cause. Stop and start the CA

XCOM Data Transport to start the secure listener subtask.

SHUTDOWN IN PROGRESS, TCP/IPV6 REMOTE CONNECTIONS NO

LONGER AVAILABLE.

Reason:

The STOP command was entered and the CA XCOM Data Transport server is terminating. No new TCP/IPv6 connections will be established by the listener subtask.

Action:

None.


Message Syntax

0829I

SHUTDOWN IN PROGRESS, TCP/IPV6 SSL REMOTE CONNECTIONS NO

LONGER AVAILABLE.

Reason:

The STOP command was entered and the CA XCOM Data Transport secure server is terminating. No new TCP/IPv6 secure connections will be established by the listener subtask.

Action:

None.

0830W

REQUIRED SSL LOAD MODULE module NOT FOUND, NO SSL LISTENERS

WILL BE STARTED

Reason:

SSL required modules ETPKISSL and/or ETPKICRY were not loaded successfully.

As a result CA XCOM Data Transport will not start any SSL listener subtask.

Action:

Install solution QO90695 and ensure that the above load modules are available to CA XCOM Data Transport.

0831E

XCOMCNTL MEMBER XXXXXXXX CONTAINS A LIST NAME LONGER THAN

8 CHARACTERS

Reason:

You have attempted to enable a superlist. However, one of the list names in the superlist is longer than eight characters. List names can be no more than eight characters, because they specify a member name in the XCOMCNTL data set.

Action:

Correct the statement in error and reissue the ENABLE command.


0832E

0833E

0834E

0835E

Message Syntax

XCOMCNTL SUPERLIST XXXXXXXX CONTAINS DUPLICATE LIST NAME

XXXXXXXX

Reason:

You have attempted to enable a superlist. However, the superlist contains duplicate list names. No list name can be named more than once in any superlist in the definition chain.

Action:


INVALID LENGTH FOR UMASK= PARAMETER

Reason:

The UMASK= parameter must be three characters long

Action:

Correct the UMASK= parameter.

UMASK CONTAINS INVALID CHARACTERS (NOT 0-7)

Reason:

At least one of the characters in UMASK is not in the range 0 to 7.

Action:

Correct the UMASK= parameter, so that each character is in the range 0 to 7.

DSNTYPE= NOT BLANK AND NOT USS

Reason:

The valid values for DSNTYPE for USS files are blanks and USS.

Action:

Correct the DSNTYPE= parameter to either blanks or USS.


Message Syntax

0836E

UMASK/FILEDATA/LFILEDATA IS ONLY VALID FOR USS FILES

Reason:

You have specified UMASK or FILEDATA or LFILEDATA for a non-USS file. These parameters can be specified for USS files only.

Action:

Replace the UMASK=, FILEDATA=, or LFILEDATA= parameter.

0837E

PARAMETER XXXXXXXXXXXXXXXX IS INVALID FOR USS FILES

Reason:

The parameter xxxxxxxxxxxxxxxx that you have specified is not valid for USS files.

Action:

Replace the invalid parameter.

0838E

CANNOT CREATE PATH, PATHNAME EXISTS, PATH=xxxxxxx

Reason:

The path name xxxxxxx that you have specified for a new path already exists.

Action:

Specify a new path name.

0839E

INVALID PATHNAME SPECIFIED – MAX OF 255 CHARACTERS

EXCEEDED, PATH=xxxxxx

Reason:

The path name xxxxxx that you have specified exceeds 255 characters.

Action:

Specify a new path name that is 255 characters or less.


0840E

0841E

0842E

Message Syntax

UNABLE TO GETMAIN STORAGE FOR NETWORK WORK AREA

Reason:

An internal request to acquire working storage has failed. This is most likely due to a temporary shortage of available virtual storage within the CA XCOM Data

Transport region.

Action:

Retry the transfer or session establishment attempt that initiated the request for working storage. If further attempts continue to fail, consider downward adjustments of the values specified for MAXTASK, MAXREM, MAXLOC, and

MAXDEL.

CANNOT CREATE USS DIRECTORY, CRUSSDIR=N SPECIFIED IN

DEFAULT OPTIONS TABLE

Reason:

CA XCOM Data Transport cannot create a USS directory, because CRUSSDIR=N has been specified in your default options table.

Action:

None

CANNOT OPEN OUTPUT FILE, FILE IS NOT A REGULAR FILE,

PATH=xxxxxx

Reason:

CA XCOM Data Transport cannot open the output file, because the path specified

(xxxxxx) is not a regular file.

Action:

Check the output file path that you have specified, and correct it.


Message Syntax

0843E

DEFAULT OPTIONS TABLE DID NOT SPECIFY THAT IBM APAR OA23740

HAS BEEN APPLIED. THERE WILL BE NO USS SUPPORT

Reason:

CA XCOM Data Transport cannot provide USS support, because

IBM_APAR_OA23740=N has been specified in your default options table.

Action:

None

0844E

NO FILES FOUND THAT MATCHED PATTERN xxxxx

Reason:

Your request to send USS files failed because there were no files found that matched the specified pattern (xxxxx).

Action:

Correct the pattern and repeat the SEND request.

0845E

FOR MEMBER XXXXXXXX, FIRST STATEMENT NOT TYPE=LIST OR

TYPE=SUPERLIST

Reason:

You have attempted to enable a superlist. However, the first statement in the superlist definition is not TYPE=LIST OR TYPE=SUPERLIST. Superlists can point to lists and superlists only.

Action:



0846E

0847E

0848E

Message Syntax

INVALID 3RD PARAMETER USED ON ENABLE COMMAND

Reason:

You have issued an ENABLE command and specified more that just the list name.

There is only one argument in the ENABLE command.

Action:


INVALID KEYWORD PARAMETER ON DISABLE LIST COMMAND, VALID

KEYWORDS ARE ALL/FORCE/FORCEALL

Reason:

You have issued a DISABLE LIST command with an additional parameter that was not ALL, FORCE, or FORCEALL.

Action:

Correct the keyword in error and reissue the ENABLE command.

INVALID KEYWORD PARAMETER ON LIST COMMAND, VALID KEYWORD

IS ALL

Reason:

You have issued a LIST, LIST command with an additional parameter that was not ALL.

Action:

Correct the keyword in error and reissue the ENABLE command.


Message Syntax

0849E

LIST XXXXXXXX CANNOT BE DISABLED, XXXXXXXX NEEDS TO BE

DISABLED, OR USE ALL/FORCE

Reason:

You have issued a DISABLE LIST command where LIST is the name of an enabled superlist. However, this superlist refers to one or more enabled lists. To disable this superlist you must include the keyword ALL or FORCE, as follows:

■ DISABLE LIST,ALL will disable the specified superlist and all lists that were enabled by this superlist.

■

DISABLE ALL,FORCE will DISABLE the named superlist but not DISABLE the individual LISTs that are pointed to.

Action:

Add the appropriate parameter and reissue the DISABLE LIST command.

0850E

LIST XXXXXXXX CANNOT BE DISABLED, IS PART OF SUPERLIST

XXXXXXXX, OR USE FORCE OPERAND

Reason:

You have issued DISABLE,LIST where list is also specified in an enabled superlist. To disable this list, you must use the FORCE keyword.

DISABLE ALL,FORCE bypasses the check for inclusion in enabled superlists.

Action:

Add the FORCE parameter and reissue the DISABLE LIST command.

0851E

LIST XXXXXXXX CONTAINS A CIRCULAR POINTER TO XXXXXXXX

Reason:

You have attempted to enable a superlist. One of the LIST= parameters in this list or another superlist names the superlist being enabled.

Action:

Correct the LIST= parameters and reissue the ENABLE command.


0852E

0853E

Message Syntax

ENABLE FAILED DUE TO PREVIOUS FAILURE

Reason:

You tried to enable a superlist. This process causes one or more related lists to get enabled separately.

In this case, at least one of the related lists has failed to enable. Therefore the entire superlist has failed to be enabled.

Action:

Check the superlist and related lists, and then try the enable again.

ALLOCATION FAILED, MAXMOUNTWAIT EXCEEDED, DSN=xx

Reason:

Your request for a device mount (for example, for a tape or disk) failed because

CA XCOM Data Transport has waited longer than the maximum waiting time specified by the MAXMOUNTWAIT parameter.

Action:

Check that the requested media exists onsite and repeat your request later.


Message Syntax

0854E

XCOMM0854E SAF SECURITY FAILED

XCOMM0854E SAF SECURITY FAILED, USERID IS BLANK

XCOMM0854E SAF SECURITY FAILED, PERMISSION IS DENIED

XCOMM0854E SAF SECURITY FAILED, RV=xxxxxxxx, RC=xxxxxxxx,

REAS=xxxxxxxx

Reason:

SAF security has failed for the action you were performing. This can happen for various reasons, as follows:

■ USERID IS BLANK—You have not entered a user ID.

■ PERMISSION IS DENIED—Either the user ID or the password (or both) is invalid.

■ RV=xxxxxxxx, RC=xxxxxxxx, REAS=xxxxxxxx—These values provide diagnostic information (the return value, return code, and reason code) for the security failure.

Action:

The action you need to take varies, depending on the reason for the failure, as follows:

■

USERID IS BLANK—Enter a user ID.

■

PERMISSION IS DENIED—Enter a valid user ID and password.

■

RV=xxxxxxxx, RC=xxxxxxxx, REAS=xxxxxxxx—Check the return code (RC) in ‗SYS1.MACLIB(BPXYERNO)‘ or contact CA Technical Support.


0855W

0858E

Message Syntax

USS DIRTREE TRANSFER TO MVS PDS WOULD RESULT IN A DUPLICATE

MEMBER NAME, xxxxxxx

Reason:

You are attempting to transfer USS files to a z/OS partitioned data set. Member names of z/OS partitioned data sets are limited to eight characters. Because there is no such limit for USS files, names of more than eight characters are truncated to the first eight characters when USS files are transferred to a z/OS partitioned data set.

CA XCOM Data Transport has determined that at least two USS files have the same first eight characters. It will transfer the first of those files, but not the subsequent files, because they would have duplicate member names in the partitioned data set.

Each USS file with unique first eight characters is transferred. Each USS file that violates the unique requirement is identified by XCOMM0855W in the XCOMLOG only. Because of the possible high volume, no WTO is written.

Notes:

■ If you are running XCOMJOB TYPE=EXECUTE, the return code is 4 instead of

0 if this situation is detected.

■

xxxxxxx identifies the complete USS path name, which includes the simple file name.

Action:

Ensure that each USS file that you are transferring is unique in its first eight characters. Then resend the files that failed to transfer.

CLOSE FAILED FOR USS FILE, CHECK ASSOCIATED MESSAGES IN THE

JOBLOG

Reason:

A close failed for a USS file. There may be associated messages with more information about why the close failed.

Action:

Check any associated messages in the log.

Note: If the close failed for an output file, the file is deleted.


Message Syntax

1000I

STARTING CROSS-SYSTEM COUPLING FACILITY SERVICE TASK

Reason:

CA XCOM Data Transport has started the Cross-System Coupling Facility Service

Task.

Action:


1001I

STOPPING CROSS-SYSTEM COUPLING FACILITY SERVICE TASK

Reason:

CA XCOM Data Transport is stopping the Cross-System Coupling Facility Service

Task.

Action:


1002E

XCOMCFTK CALLED WITH INVALID POINTER TO CSA

Reason:

This is an internal error.

Action:

Keep the CA XCOM Data Transport log and SYSLOG and call CA Technical

Support.

1003E

XCOMCFTK CALLED WITH INVALID FUNCTION REQUEST

Reason:


Action:


Support.


1004E

1005I

1006I

1007E

Message Syntax

MUST RUN AUTHORIZED TO USE XCF SERVICES

Reason:

All libraries must be APF authorized in order to use the IBM Coupling Facility. The

XCOMPLEX requires the IBM Coupling Facility.

Action:

Make sure all libraries are APF authorized.

XCOMPLEX SERVICES ENABLED FOR NODE (xxxxxxxx)

Reason:

NODE xxxxxxxx has successfully connected to the coupling facility.

Action:


XCOMPLEX SERVICES DISABLED FOR NODE (xxxxxxxx)

Reason:

NODE xxxxxxxx has disconnected from the coupling facility.

Action:


CONNECTION TO XCF FAILED

Reason:

Connection to the Cross Coupling Facility failed.

Action:

See message 1019I, which is displayed after this one for more information and return codes.


Message Syntax

1008E

XCOMPLEX STRUCTURE NAME MISSING FOR CONNECT

Reason:


Action:


Support.

1009E

XCOMPLEX GROUP NAME ALREADY CONNECTED

Reason:

An attempt was made to start two servers with the same acbname on two separate processors.

Action:

Make sure acbnames are unique throughout the XCOMPLEX.

1010I

SHUTDOWN IN PROGRESS FOR XCOMPLEX SERVICES

Reason:

This is an informational message.

Action:

None

1012E

XCOMCFTK TASK HAS ABENDED WITH SXXX

Reason:

The task has abended with abend code SXXX.

Action:

If the reason for the abend is known, correct the problem (for example, module not found). Otherwise, keep the CA XCOM Data Transport log, SYSLOG, and dump and call CA Technical Support.


1013I

1014E

1015E

1016E

Message Syntax

XCF REQ=xxxxxxxxxxxxxxxx RC=xxxxxxxx REASON=xxxxxxxxx

LIST=xxxx ENTRY=xxxxxxxxxxxxxxxx

Reason:

This message gives return codes for the error message which precedes it.

Action:


Support. See the IBM documentation for reason codes.

DISCONNECT FROM XCF FAILED

Reason:

CA XCOM Data Transport could not disconnect successfully from the Coupling

Facility.

Action:

For more information, see message 1013I .

INVALID TOKEN PASSED FOR XCF DISCONNECT REQUEST

Reason:


Action:


Support.

REGION ALREADY CONNECTED TO XCF

Reason:


Action:


Support.


Message Syntax

1017I

XCF READING MASTER ENTRY FROM LIST #0000

Reason:

This message indicates that CA XCOM Data Transport is checking to see if the structure used by the CA XCOM Data Transport server has already been allocated

Action:


1018I

xxxxxxxx= yyyyyyyy

Reason:

This message follows another error message and gives diagnostic information when CA XCOM Data Transport detects an error in the contents of list 0 for the

Coupling Facility.

Action:


Support.

1019I

XCF CONNECT STR=xxxxxxxxxxxxxxxx, CONN=xxxxxxxx,

RC=xxxxxxxxx, RSN=xxxxxxxx, DISP=xxx

Reason:

This message follows another error message and gives diagnostic information.

Action:


Support. See the IBM documentation for reason codes.


1020I

1021I

1022I

1023E

Message Syntax

MAXIMUM SERVERS SUPPORTED=xxxxxxxx

Reason:

This is an informational message. The XCOMPLEX can have a maximum of

xxxxxxxx servers.

Action:


ALLOCATING MASTER ENTRY IN LIST #0000

Reason:

This is an informational message. CA XCOM Data Transport did not find an existing list structure and is building one.

Action:


LOCATING SERVER ENTRY IN LIST #0000

Reason:

This is an informational message. CA XCOM Data Transport is checking to see if this server has a prior entry in the structure to reuse. If not, it will create new one.

Action:


ERROR LOCATING SERVER ENTRY

Reason:


Action:


Support.


Message Syntax

1024E

DELETE_MULTI FAILED—DISCONNECTING

Reason:

This is an internal error. There was an error clearing the list for a server.

Action:

Retain the CA XCOM Data Transport log and SYSLOG and call CA Technical

Support.

1025E

NO MORE AVAILABLE LIST HEADERS—DISCONNECTING

Reason:

An attempt was made to start more than the maximum number of servers allowed.

Action:

See the description of informational message 1020I for the maximum number of servers that may be started.

1026I

UPDATING MASTER ENTRY IN LIST #0000

Reason:

This is an informational message that is issued when a server starts up. The server updates the master list with its own list number.

Action:


1027E

REWRITE OF MASTER ENTRY FAILED—DISCONNECTING

Reason:


Action:


Support.


1028I

1029E

1030E

Message Syntax

ADDING SERVER ENTRY FOR NODE (xxxxxxxx) WHICH IS USING LIST

#0000

Reason:

This is an informational message that is issued when an XCOMPLEX Worker

Server adds itself to the master list. xxxxxxxx is the ACB name of the server. The list number is the number it assigned itself when initially connecting to coupling facility or reconnecting.

Action:


UPDATE FAILED FOR SERVER LIST #0000

Reason:

This is an internal error. CA XCOM Data Transport was unable to update the master list. This precedes error message 1018I.

Action:

See error message 1018I for return codes.

READ OF MASTER ENTRY FAILED—DISCONNECTING

Reason:


Action:


Support.


Message Syntax

1031I

DISPLAYING CONTENTS OF XCF MASTER ENTRY

Reason:


Action:


1032I

DISPLAYING CONTENTS OF LOCAL MASTER ENTRY

Reason:


Action:


1033E

MASTER ENTRY VERIFICATION FAILED—DISCONNECTING

Reason:


Action:


Support.

1034E

UNABLE TO OBTAIN LOCK—DISCONNECTING

Reason:


Action:


Support.


1035E

1036E

1037I

1038I

Message Syntax

LOCK FAILED—DISCONNECTING

Reason:


Action:


Support.

UNLOCK FAILED—RECOVERY ABANDONED

Reason:


Action:


Support.

XCF DISCONNECT/NORMAL RC=xxxxxxxx RSN=xxxxxxxx

Reason:

This message is issued for when a disconnect from the IBM Coupling Facility is requested under normal circumstances.

Action:

If the RC is non-zero, keep the CA XCOM Data Transport log and SYSLOG and contact CA Technical Support.

XCF DISCONNECT/FAIL RC=xxxxxxxx RSN=xxxxxxxx

Reason:

This is an internal error. This message is issued because of a prior error.

Action:


Support.


Message Syntax

1039I

XCF COMPLETION EXIT DRIVEN RC=xxxxxxxx RSN=xxxxxxxx

Reason:

This is an informational message.

Action:

None

1040E

XCF STRUCTURE OUT OF SPACE

Reason:

The XCOMPLEX structure is full.

Action:

Shut down all the servers in the XCOMPLEX. Increase the size of the structure.

See the sample JCL in CAI.CBXGJCL(POLCFRM). Bring up all servers in the

XCOMPLEX.

1041E

XCF EVENT EXIT ENTERED EC=xxxxxxxx, UNKNOWN SUB=

Reason:


Action:


Support.

1042E

XCF EVENT EXIT xxxxxxxxxxxxxxxx ALREADY CONNECTED TO yyyyyyyy

Reason:


Action:


Support.


1043I

1044E

1045I

1046I

Message Syntax

XCF EVENT EXIT xxxxxxxxxxxxxxxx HAS JUST CONNECTED TO yyyyyyy

Reason:


Action:


Support.

XCF EVENT EXIT xxxxxxxxxxxxxxxx DISC/FAILED, STRUCT yyyyyyyy

Reason:


Action:


Support.

XCF EVENT EXIT LOCATING SERVER ENTRY FOR FAILED SYSTEM

Reason:


Action:


Support.

XCF EVENT EXIT CLEARING SERVER ENTRIES FROM LIST (xxxxxxxxx)

Reason:


Action:


Support.


Message Syntax

1047I

XCF EVENT EXIT xxxxxxxxxxxxxxxx DISC/NORMAL, STRUCT yyyyyyyy

Reason:


Action:


Support.

1048I

XCF EVENT EXIT xxxxxxxxxxxxxxxx CONNECTIVITY LOST, STRUCT yyyyyyyy

Reason:


Action:


Support.

1049E

XCF EVENT EXIT xxxxxxxxxxxxxxxx STRUCTURE FAILED, STRUCT yyyyyyyy

Reason:


Action:


Support.


1050I

1051E

1052E

1053E

Message Syntax

XCF EVENT EXIT xxxxxxxxxxxxxxxx NOW zzzzVOLATILE, STRUCT yyyyyyyy

Reason:


Action:


Support.

GETMAIN FAILED FOR XCFDSECT REQUEST BLOCK

Reason:

The CA XCOM Data Transport region does not have any more storage available.

Action:

Increase the region size and/or tune the MAXTASK parameters so that fewer simultaneous transfers will be processed.

XCOMCFTK SERVICE TASK NOT ACTIVE—REQUEST REJECTED

Reason:


Action:


Support.

ERROR ALLOCATING MASTER LIST #0000

Reason:


Action:


Support.


Message Syntax

1054I

MAXIMUM LIST ENTRIES SUPPORTED=xxxxxxxx

Reason:

This is an informational message. xxxxxxxx is the maximum number of list entries available.

Action:


1055I

CLEARING LIST #0000 FOR USE BY NODE(xxxxxxxx)

Reason:

This is an informational message. CA XCOM Data Transport is clearing the list for server xxxxxxxx.

Action:


1056I

XCF EXTENDED LOGGING ACTIVATED

Reason:

This is an informational message. The XTRACE has been turned on.

Action:

None

1057I

XCF EXTENDED LOGGING TERMINATED

Reason:

This is an informational message. The XTRACE has been turned off.

Action:

None


1058I

1059E

1061I

1062I

Message Syntax

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Reason:

This is an informational trace message. It is free form and has no specific text associated with it.

Action:

None

XCOMRANX—INVALID INTERNAL COMMAND RECEIVED

Reason:


Action:

Keep the CA XCOM Data Transport log and SYSLOG and any other output. A dump may also be produced. Contact CA Technical Support.

zzzzzzzz—REQ#=999999,STATUS=xxxxxxxx,USER=aaaaaaaa,NAME=y

Reason:

This is the response a XSHOW or XRSHOW command. zzzzzzzz is the server name.

Action:


xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Reason:

This is the response from the STAT command. It is free form and has no specific text associated with it.

Action:



Message Syntax

1063E

zzzzzzzz—REQUEST # NOT ENTERED FOR xxxxxxxx REQUEST

Reason:

This is the response to an XSHOW or XRSHOW command. zzzzzzzz is the server name. xxxxxxxx is either XSHOW or XRSHOW. The request number was missing for the command.

Action:

Enter the request number with the command.

1064E

xxxxxxxx—REQUEST # xxxxxx FOR xxxxxxxx NOT NUMERIC

Reason:

This is the response to an XSHOW or XRSHOW command. zzzzzzzz is the server name. xxxxxxxx is either XSHOW or XRSHOW. The request number was not numeric.

Action:

Enter a numeric request number.

1065E

xxxxxxxx—REQUEST # xxxxxx FOR xxxxxxxx NOT FOUND

Reason:

This is the response to an XSHOW or XRSHOW command. zzzzzzzz is the server name. xxxxxxxx is either XSHOW or XRSHOW. The specified request number was not found.

Action:

Enter a valid request number.


1066I

1067E

1068I

Message Syntax

xxxxxxxx—NO zzzzzzzz INITIATED REQUESTS FOR yyyyyy COMMAND

Reason:

This is the response to an XSHOW or XRSHOW command. zzzzzzzz is the server name. xxxxxxxx is either XSHOW or XRSHOW. zzzzzzzz indicates LOCALLY or

REMOTELY. There are no requests in the queue.

Action:


GETMAIN FAILED FOR WORKER REGION STATISTICS TABLE

Reason:

The CA XCOM Data Transport region does not have any more storage available.

Action:

Increase the region size and/or tune the MAXTASK parameters so that fewer simultaneous transfers will be processed.

CROSS-COUPLING FACILITY LISTENER TASK xxxxxxxx

Reason:

This is an informational message issued for the startup and shutdown of the

RANX listener task where xxxxxxxx indicates starting or stopping.

Action:

None


Message Syntax

1069I

zzzzzzzz HAS RECEIVED yyyyyyy COMMAND

Reason:

This is an informational message in response to an XSHOW, XRSHOW, or STAT command. zzzzzzzz is the ACB name of the XCOMPLEX Worker Server. yyyyyyy is the command. Indicates XCOMPLEX WORKER zzzzzzzz is connected to the

XCOMPLEX Admin Server and will respond to the yyyyyyy command.

Action:

None

1070I

zzzzzzzz IS NOT CONNECTED TO THIS XCOMPLEX

Reason:

This is an informational message in response to a STAT, XSHOW, or XRSHOW command. zzzzzzzz is the ACB name of the XCOMPLEX Worker Server. It indicates that the XCOMPLEX Worker Server, zzzzzzzz, is not connected to the

XCOMPLEX Admin Server.

Action:

None required. If desired, the XCOMPLEX Worker Server can be connected to the

XCOMPLEX Admin Server. Verify the XCOMPLEX Worker Server is active. If not active, start the XCOMPLEX Worker Server. If the XCOMPLEX Worker Server is active, ensure the destination member is enabled for the XCOMPLEX Admin

Server and manually issue a CNOS command to start session. See the discussion of the ENABLE and DISABLE commands in the CA XCOM Data Transport for z/OS


5500E

SEC ERR xx yy: RAzzzzz UNKNOWN ERROR

Reason:

The CA XCOM Data Transport IBM RACF security module has received return code xx yy from either a RACINIT or RACCHECK macro request. zzzzz will be INIT for RACINIT and CHECK for RACCHECK. The error was undocumented at the time the module was written. The transfer request is terminated and this message is sent to the session partner.

Action:

See the IBM documentation for a description of return codes which can be returned to a RACINIT or RACCHECK request, and take the appropriate action.


5501E

5502E

5503E

Message Syntax

INIT ERR 04 00: USERID NOT DEFINED

Reason:

The CA XCOM Data Transport RACF security module has received return code 04

00 from the RACINIT macro request, indicating USERID NOT DEFINED. The message is sent to the conversation partner and the transfer request is terminated.

Action:

See the IBM documentation.

INIT ERR 08 00: INVALID PASSWORD

Reason:


00 from the RACINIT macro request, indicating INVALID PASSWORD. This message is sent to the conversation partner and the transfer request is terminated.

Action:


INIT ERR 0C 00: PASSWORD EXPIRED

Reason:

The CA XCOM Data Transport RACF security module has received return code 0C

00 from the RACINIT macro request, indicating PASSWORD EXPIRED. This message is sent to the conversation partner and the transfer request is terminated.

Action:



Message Syntax

5504E

INIT ERR 10 00: NEW PASSWORD INVALID

Reason:


00 from the RACINIT macro request, indicating NEW PASSWORD INVALID. This message is sent to the conversation partner and the transfer request is terminated.

Action:


5505E

INIT ERR 14 00: USERID NOT IN GROUP

Reason:


00 from the RACINIT macro request, indicating USERID NOT IN GROUP. This message is sent to the conversation partner and the transfer request is terminated.

Action:


5506E

INIT ERR 18 00: REJECTED BY RACF EXIT

Reason:


00 from the RACINIT macro request, indicating REJECTED BY RACF EXIT. This message is sent to the conversation partner and the transfer request is terminated.

Action:



5507E

5508E

5509E

Message Syntax

INIT ERR 1C 00: USERID REVOKED

Reason:


00 from the RACINIT macro request, indicating USERID REVOKED. This message is sent to the conversation partner and the transfer request is terminated.

Action:


INIT ERR 20 00: SECURITY SYSTEM DORMANT

Reason:


00 from the RACINIT macro request, indicating SECURITY SYSTEM DORMANT.

This message is sent to the conversation partner and the transfer request is terminated.

Action:


INIT ERR 24 00: ACCESS TO GROUP REVOKED

Reason:


00 from the RACINIT macro request, indicating ACCESS TO GROUP REVOKED.


Action:



Message Syntax

5510E

INIT ERR 28 00: OIDCARD NOT SPECIFIED

Reason:


00 from the RACINIT macro request, indicating OIDCARD NOT SPECIFIED. This message is sent to the conversation partner and the transfer request is terminated.

Action:


5511E

INIT ERR 2C 00: OIDCARD INVALID

Reason:


00 from the RACINIT macro request, indicating OIDCARD INVALID. This message is sent to the conversation partner and the transfer request is terminated.

Action:


5512E

INIT ERR 30 00: UNAUTH FOR TERMINAL

Reason:


00 from the RACINIT macro request, indicating UNAUTH FOR TERMINAL. This message is sent to the conversation partner and the transfer request is terminated.

Action:



5513E

5514E

5515E

Message Syntax

INIT ERR 30 04: UNAUTH FOR SYSTEM NOW

Reason:


04 from the RACINIT macro request, indicating UNAUTH FOR SYSTEM NOW. This message is sent to the conversation partner and the transfer request is terminated.

Action:


INIT ERR 30 08: UNAUTH FOR TERMINAL NOW

Reason:


08 from the RACINIT macro request, indicating UNAUTH FOR TERMINAL NOW.


Action:


INIT ERR 34 00: UNAUTH TO USE XCOM

Reason:


00 from the RACINIT macro request, indicating UNAUTH TO USE CA XCOM Data

Transport. This message is sent to the conversation partner and the transfer request is terminated.

Action:

Ask your CA XCOM Data Transport System Administrator for the necessary authorization.


Message Syntax

5516E

FILE ERR 08 00: ACCESS NOT AUTHORIZED

Reason:


00 from the RACCHECK macro request, indicating ACCESS NOT AUTHORIZED.


Action:


5517E

FILE ERR 08 04: FILE TO BE ERASED

Reason:


04 from the RACCHECK macro request, indicating FILE TO BE ERASED. This message is sent to the conversation partner and the transfer request is terminated.

Action:


5518E

FILE ERR 08: UNAUTH FOR THIS TAPE

Reason:


08 from the RACCHECK macro request, indicating UNAUTH FOR THIS TAPE. This message is sent to the conversation partner and the transfer request is terminated.

Action:



5519E

5520E

5521E

Message Syntax

FILE ERR 08 0C: ACCESS NOT AUTHORIZED

Reason:


0C from the RACCHECK macro request, indicating ACCESS NOT AUTHORIZED.


Action:


FILE ERR 08 10: UNAUTH FOR BLP TAPE

Reason:


10 from the RACCHECK macro request, indicating UNAUTH FOR BLP TAPE. This message is sent to the conversation partner and the transfer request is terminated.

Action:


FILE ERR 0C 00: OLDVOL NOT FOUND

Reason:


00 from the RACCHECK macro request, indicating OLDVOL NOT FOUND. This message is sent to the conversation partner and the transfer request is terminated.

Action:



Message Syntax

5550E

XCOM LOGONID IS NOT A MUSASS

Reason:

The CA XCOM Data Transport CA ACF2 interface requires that the CA XCOM Data

Transport server be defined as a MUSASS (Multiple User Address Space). When

CA XCOM Data Transport made a request to CA ACF2, users were informed that the CA XCOM Data Transport logon ID was not a MUSASS. The transfer is terminated and this message is sent to the conversation partner.

Action:

To resolve this problem, turn on the MUSASS attribute for the CA XCOM Data

Transport address space and bring CA XCOM Data Transport down and then up again.

5551E

$ACFGCVT NOT LINKED INTO XCOMACF2

Reason:

The CA XCOM Data Transport CA ACF2 security interface requires that the user link the $ACFGCVT module into the XCOMACF2 load module. This is because

$ACFGCVT is vendor-supplied and is required by the security interface. The transfer request is terminated and this message is sent to the conversation partner.

Action:

For more information about linking XCOMACF2, see the chapter ―Installing Your

Product‖ in the CA XCOM Data Transport for z/OS Installation Guide.

5552E

NO ACUCB FOR THIS ASCB—ACCESS DENIED

Reason:

The CA XCOM Data Transport CA ACF2 security routine has attempted to find the

ACUCB (an ACF2 Control Block) for this address space but is unable to find one.

This is normally caused by the CA XCOM Data Transport server not being monitored by CA ACF2.

Action:

Ensure that the CA XCOM Data Transport server is being monitored by CA ACF2.

Otherwise, the transfer request is terminated and this message is sent to the conversation partner.


5553E

5560E

Message Syntax

NO ACF2 CVT—ACCESS DENIED

Reason:

The CA XCOM Data Transport CA ACF2 security routine has attempted to find the

ACF2 CVT but was unable to find it. This may be because CA ACF2 is not installed on the CPU that is running CA XCOM Data Transport.

Action:

Check the CA XCOM Data Transport Default Table and if necessary, correct the

SECUR parameter to name the proper CA XCOM Data Transport security interface.

RACxxxxx RC yy zz ACCESS DENIED BY TOP SECRET

Reason:

The CA XCOM Data Transport CA Top Secret security interface received a

RACINIT or RACHECK macro RACxxxxx. The RACF return code and reason codes are indicated by yy and zz, respectively. CA XCOM Data Transport was unable to interpret these fields to provide a descriptive explanation.

Action:

Look up the codes in the appropriate IBM documentation.


Message Syntax

5561E

NEW PASSWORD INVALID OR NOT ALLOWED

Reason:

An attempt to change the current password on the remote system by using the

CA XCOM Data Transport change password feature was rejected by the remote system's security software. There are two common reasons for this rejection:

1. The indicated new password did not conform to the password syntax conventions on that system.

2. For a user ID that possesses a ―multi-password‖ attribute (that is, different passwords for different facilities), there was no current password defined for the CA XCOM Data Transport facility. Hence, it could not be changed.

Action:

For problem type 1, specify a legitimate new password or postpone changing the old password. For problem type 2, define a password for the CA XCOM Data

Transport facility to the remote security software, or remove the multi-password attribute from the user. As an alternative, you might try resubmitting the request without specifying any password.

5562E

XCOM SECURITY GETMAIN FAILURE—ACCESS DENIED

Reason:

CA XCOM Data Transport has issued a conditional GETMAIN request from within the CA XCOM Data Transport security validation module but the request failed due to a lack of storage available.

Action:

Ensure that the region size specified by CA XCOM Data Transport is sufficient.

Otherwise, the transfer request is terminated and this message is sent to the conversation partner.

8001E

UNABLE TO OPEN xxxxxxxx DD—XCOMUTIL TERMINATED

Reason:

When XCOMUTIL attempted to open the data set, the call failed.

Action:

Correct the DD name and rerun XCOMUTIL.


8002E

8003E

8004E

8005E

Message Syntax

INVALID PARAMETER CARD—NOT DATE/AGE OR PROCESS

Reason:

The only valid SYSIN statements for XCOMUTIL are DATE=, AGE= and

PROCESS=.

Action:

Remove the incorrect SYSIN statement and rerun XCOMUTIL.

INVALID AGE PARAMETER ENTERED—NOT NUMERIC, INVALID LENGTH,

OR NOT ENTERED—XCOMUTIL TERMINATED

Reason:

The AGE SYSIN parameter must be numeric and in the range 1 to 999.

Action:

Correct the value for the AGE parameter and rerun XCOMUTIL.

DUPLICATE PROCESS CARD ENTERED—XCOMUTIL TERMINATED

Reason:

The PROCESS= SYSIN parameter was specified more than once.

Action:

Remove the extra parameter(s) and rerun XCOMUTIL.

PROCESS CARD DEFINED BUT OBJECT IS NOT HISTORY

Reason:

The SYSIN parameter PROCESS=HISTORY was not specified correctly.

Action:

Specify PROCESS=HISTORY and rerun XCOMUTIL.


Message Syntax

8006E

DATE PARAMETER ENTERED NOT 5 NUMERIC CHARACTERS

Reason:

The DATE SYSIN parameter was specified incorrectly.

Action:

The DATE SYSIN parameter must be specified as a Julian date in the format

yyddd. Correct the DATE and rerun XCOMUTIL.

8007E

MULTIPLE AGE/DATE PARAMETERS ENTERED—ERROR

Reason:

More than one AGE or DATE SYSIN parameter was entered.

Action:

Only one AGE or DATE parameter may be entered. Remove the extra parameter(s) and rerun XCOMUTIL.

8008E

NEITHER AGE NOR DATE CARDS ENTERED—ERROR

Reason:

No AGE or DATE SYSIN parameter was entered.

Action:

Add an AGE or DATE parameter to the SYSIN parameters and rerun XCOMUTIL.

8009E

DATE ENTERED WAS 6 BYTES LONG—MUST BE YYDDD

Reason:

The DATE SYSIN parameter was specified incorrectly.

Action:

The DATE SYSIN parameter must be specified as a Julian date in the format yyddd. Correct the DATE and rerun XCOMUTIL.


8010E

8011E

8012I

Message Syntax

PROCESS CARD MISSING—XCOMUTIL TERMINATED

Reason:

The SYSIN parameter PROCESS was not specified.

Action:

The SYSIN parameter PROCESS=HISTORY is required. Add the parameter and rerun XCOMUTIL.

XCOMUTIL PROGRAM ENDED WITH ERRORS

Reason:

XCOMUTIL did not run successfully.

Action:

Check the return code from XCOMUTIL to determine the reason it was not successful:

■

4—No history records were written to the output file

■

8—XCOMUTIL could not open one of the files

■

12—One of the SYSIN parameter was in error

XCOMUTIL PROGRAM ENDED SUCCESSFULLY

Reason:

XCOMUTIL ran successfully.

Action:

Check the other informational messages for details.


Message Syntax

8013I

xxxxxxxx RECORDS READ FROM HISTIN FILE

Reason:

XCOMUTIL read xxxxxxxx records from the history file.

Action:

Informational message. No action required.

8014I

xxxxxxxx RECORDS WRITTEN TO HISTOUT FILE

Reason:

XCOMUTIL wrote xxxxxxxx records to the HISTOUT file. These are the records that were kept.

Action:

None

8015I

xxxxxxxx RECORDS PURGED FROM HISTORY FILE

Reason:

XCOMUTIL deleted xxxxxxxx records from the history file.

Action:

None

8016I

RECORDS ON HISTORY FILE ON OR BEFORE yyddd WILL BE DELETED

Reason:

XCOMUTIL will delete all records that were written on or before Julian date

yyddd.

Action:

None


9001E

9002E

9004E

Message Syntax

SVC 99 ERROR DDNAME=dddddddd RC=xxxx REASON=yyyy OPENING

XCOMLOG FILE

Reason:

CA XCOM Data Transport has received return code xxxx with reason code yyyy when attempting to open the CA XCOM Data Transport Log File on DDNAME

dddddddd. This is often caused by specifying an invalid CA XCOM Data Transport

LOGCLASS or LOGDEST parameter.

Action:

Look up the return and reason codes in the IBM documentation and take the appropriate action.

OPEN FAILED FOR XCOMLOG DATA SET\LOGGING STOPPED

Reason:

CA XCOM Data Transport has attempted to open the XCOMLOG data set, but was not successful.

Action:

Check for any accompanying messages to determine the reason for the error.

THE 1ST CHARACTER OF THE TSO USERID IS NOT ALPHANUMERIC OR

NATIONAL STANDARD @, #, $

Reason:

CA XCOM Data Transport has attempted to notify a TSO user, but the specified

TSO user ID does not conform to TSO naming standards. The file transfer itself was unaffected.

Action:

Correct the specified TSO user ID and resubmit the request.


Message Syntax

9005E

TSO USERID SPECIFIED HAS AN INVALID FORMAT MAXIMUM LENGTH

IS 7 CHARACTERS

Reason:


TSO user ID exceeded the seven-character maximum permitted by TSO.

Action:


9006E

TSO USERID SUPPLIED CONTAINS CHARACTERS THAT ARE INVALID

Reason:


TSO user ID does not conform to standard TSO naming conventions.

Action:


9007E

xxxxxxx REPRESENTS THE TSO USERID THAT WAS FOUND IN ERROR

SEND COMMAND WAS NOT ISSUED

Reason:

This message will be displayed together with messages 9004E, 9005E, or 9006E.

It indicates the user ID that CA XCOM Data Transport was requested to notify.

Action:

None


9999E

Message Syntax

GETMAIN FAILED TRYING TO DISPLAY MESSAGE

Reason:

There is not enough memory available.

Action:

Increase the region size for CA XCOM Data Transport or tune the CA XCOM Data

Transport default parameters MAXTASK, MAXLOC, and MAXREM.


Chapter 3: Health Check Messages

CA Health Checker Common Service issues the following messages to report the results (either success or exception) of CA XCOM Data Transport health checks.

This section contains the following topics:

XCMH201I

(see page 301)

XCMH202W

(see page 302)

XCMH501I

(see page 303)

XCMH502I

(see page 304)

XCMH503W

(see page 305)

XCMH511I

(see page 306)

XCMH512I

(see page 306)

XCMH513W

(see page 307)

XCMH521I

(see page 308)

XCMH522I

(see page 309)

XCMH523W

(see page 310)

XCMH531I

(see page 311)

XCMH532I

(see page 312)

XCMH533W

(see page 313)

XCMH201I

XCOM Default Table indicates that IBM APAR OA23740 has been applied.

USS transfers will be permitted.

Reason:

This message indicates that IBM_APAR_OA23740=YES was specified in the CA

XCOM Default Options Table for this CA XCOM Data Transport region. This check only applies to CA XCOM Data Transport regions running on operating system levels below z/OS 1.10. Having this APAR applied and affirming it in the Default

Options Table is a best practice. This parameter and message are irrelevant for

CA XCOM Data Transport servers running on z/OS 1.10 and above.

Action:

No action is required.

Chapter 3: Health Check Messages 301

Message Syntax

XCMH202W

XCOM Default Table indicates that IBM APAR OA23740 has not been applied. No USS transfers will be permitted.

Reason:

IBM_APAR_OA23740=NO was specified or defaulted in #DFLTAB. This exception only applies to CA XCOM Data Transport regions running on operating system levels below z/OS 1.10.

Action:

This message is issued by the CA XCOM Health Check exit, which examines the value of the IBM_APAR_OA23740 in the Default Options Table. The following actions and responses are documented for this check:

System Action:

The system continues processing, but without the ability to transfer USS files.

Operator Response:

None required.

Problem Determination:

Determine if IBM APAR OA23740 has been applied. If so, then change the value in the XCOM Defaults Table (#DFLTAB) to YES.

System Programmer Response:

Determine if IBM APAR OA23740 has been applied. If so, then change the value in the XCOM Defaults Table (#DFLTAB) to YES.

Source:

CA XCOM Data Transport module XCOMXFER

Reference Documentation:

See the following guides:

■

CA XCOM Data Transport for z/OS Administration Guide

■

CA XCOM Data Transport for z/OS Message Reference Guide (message

XCOMM0843E)


XCMH501I

Message Syntax

XCOM [Below-the-Line | Above-the-Line] Storage Summary:

==================================

Current Usage:

----------------------------

Total........ n.nn[M | K]

Allocated.... - n.nn[M | K]

__________

Remaining.... n.nn[M | K]

----------------------------

% Used....... nnn%

==================================

Peak Usage:

----------------------------

Total........ n.nn[M | K]

Allocated.... - n.nn[M | K]

__________

Remaining.... n.nn[M | K]

----------------------------

% Used....... nnn%

==================================

Reason:

This message details the storage allocation levels of the storage area indicated in the text of the message (either above or below the 16MB line).

Action:



Message Syntax

XCMH502I

Currently CA XCOM Data Transport is not experiencing any shortage of

[below-the-line | above-the-line] storage.

Storage shortages within a CA XCOM Data Transport region can cause unpredictable results including, but not limited to, miscellaneous abends, file I/O errors, and network communication errors resulting in failed data transmissions or abnormal termination of the region itself.

Reason:

The storage utilization within the CA XCOM Data Transport region has been analyzed and compared to the defined threshold. The storage utilization level is within the configured threshold value. This is a normal condition.

Action:



Message Syntax

XCMH503W

Available storage [below-the-line | above-the-line] is less than nnn% of the total amount.

Storage utilization has exceeded nnn% of the amount available to the

CA XCOM Data Transport region. Storage shortages within a CA XCOM

Data Transport region can cause unpredictable results including, but not limited to, miscellaneous abends, file I/O errors, and network communication errors resulting in failed data transmissions or abnormal termination of the region itself.

Reason:

The storage utilization within the CA XCOM Data Transport region has been analyzed and compared to the defined threshold. The storage utilization level has exceeded the configured threshold value. This is an exception that can affect the functionality of the CA XCOM Data Transport region as described above.

Action:

This message is issued by the CA XCOM Health Check exit, which provides detailed information about the exception condition and the suggested response.

The following actions and responses are documented for this check:

System Action:

The CA XCOM Data Transport region attempts to continue processing.


Notify the System Programmer responsible for CA XCOM Data Transport.


N/A


Increase the amount of storage available to the region or reduce the maximum number of concurrent tasks allowed via the

MAXTASK/MAXLOC/MAXREM parameters. These values can be changed in the Default Options Table, which is generated using the CA XCOM Data

Transport #DFLTAB macro. The MAXTASK/MAXLOC/MAXREM values can also be immediately (but temporarily) changed using the CA XCOM Data

Transport DFLT console command.

Source:



See the CA XCOM Data Transport for z/OS Administration Guide.


Message Syntax

XCMH511I

XCOM Task Summary

======================================

MAXTASK Setting......... 150

Current # Tasks......... 0

Peak # Tasks............ 1

# Times at MAXTASK...... 0

======================================

Reason:

This message details the overall task level within the CA XCOM Data Transport region.

Action:


XCMH512I

Currently the number of active tasks in the CA XCOM Data Transport region is at nnn% of the maximum allowed by the MAXTASK parameter.

This is considered normal and is providing adequate throughput.

The MAXTASK configuration parameter limits the number of active tasks that are allowed in the CA XCOM Data Transport region at any given time. An exception condition is recognized when the active task level reaches the threshold defined for this health check.

When a CA XCOM Data Transport region reaches the MAXTASK limit, additional file transfer requests are delayed and retried at a later time.

This may result in unacceptable processing delays for new file transfer requests.

The overhead required to manage this exception condition may degrade the overall performance of theCA XCOM Data Transport region and adversely affect its ability to complete existing file transfer requests.

Reason:

The overall task level within the CA XCOM Data Transport region has been analyzed and compared to the defined threshold. The task level is within the configured threshold value. This is a normal condition.

Action:



Message Syntax

XCMH513W

The total number of active tasks within the CA XCOM Data Transport region has exceeded nnn% of the configured limit as specified on the

MAXTASK parameter.

The MAXTASK configuration parameter limits the number of active tasks that are allowed in the CA XCOM Data Transport region at any given time. An exception condition is recognized when the active task level reaches a certain threshold percentage of that limit. The default threshold percentage is 80%. This threshold can be modified by specifying a different percentage via the "THRESHOLD(nnn)" parameter for this particular health check.


This may result in unacceptable processing delays for new file transfer requests. The overhead required to manage this exception condition may degrade the overall performance of the CA XCOM Data Transport region and adversely affect its ability to complete existing file transfer requests.

Reason:

The overall task level within the CA XCOM Data Transport region has been analyzed and compared to the defined threshold. The task level has exceeded the configured threshold value. This is an exception condition that can affect performance as stated above.

Action:



System Action:

The CA XCOM Data Transport region continues processing.


None required.


N/A


Message Syntax


Either externally pace the workflow of transfer requests processed by the CA

XCOM Data Transport server or, if sufficient system resources are available, adjust the maximum number of tasks allowed by increasing the MAXTASK parameter specified on the #DFLTAB macro used to generate the CA XCOM

Default Options Table. The MAXTASK configuration value can also be immediately (but temporarily) changed using the CA XCOM Data Transport

DFLT console command.

Source:




XCMH521I

XCOM Locally Initiated Task Summary

======================================

MAXLOC Setting.......... 75

Current # Local Tasks... 0

Peak # Local Tasks...... 1

# Times at MAXLOC....... 0

======================================

Reason:

This message details the locally-initiated task levels within the CA XCOM Data

Transport region.

Action:



XCMH522I

Message Syntax

Currently the number of locally initiated active tasks in the CA XCOM

Data Transport region is at nnn% of the maximum allowed by the

MAXLOC parameter. This is considered normal and is providing adequate throughput.

The MAXLOC configuration parameter limits the number of locally initiated active tasks that are allowed in the CA XCOM Data Transport region at any given time. An exception condition is recognized when the locally initiated active task level reaches the threshold defined for this health check.

When a CA XCOM Data Transport region reaches the MAXLOC limit, additional locally initiated file transfer requests are delayed and retried at a later time. This may result in unacceptable processing delays for new file transfer requests. The overhead required to manage this exception condition may degrade the overall performance of the CA

XCOM Data Transport region and adversely affect its ability to complete existing file transfer requests.

Reason:

The locally-initiated task level within the CA XCOM Data Transport region has been analyzed and compared to the defined threshold. The task level is within the configured threshold value. This is a normal condition.

Action:



Message Syntax

XCMH523W

The total number of locally initiated active tasks within the CA XCOM

Data Transport region has exceeded nnn% of the configured limit as specified on the MAXLOC parameter.

The MAXLOC configuration parameter limits the number of locally initiated active tasks that are allowed in the CA XCOM Data Transport region at any given time. An exception condition is recognized when the locally initiated active task level reaches a certain threshold percentage of that limit. The default threshold percentage is 80%. This threshold can be modified by specifying a different percentage via the

THRESHOLD(nnn) parameter for this particular health check.

When a CA XCOM Data Transport region reaches the MAXLOC limit, additional locally initiated file transfer requests are delayed and retried at a later time. This may result in unacceptable processing delays for new file transfer requests. The overhead required to manage this exception condition may degrade the overall performance of theCA

XCOM Data Transport region and adversely affect its ability to complete existing file transfer requests.

Reason:

The locally-initiated task level within the CA XCOM Data Transport region has been analyzed and compared to the defined threshold. The locally-initiated task level has exceeded the configured threshold value. This is an exception condition that can affect performance as stated above.

Action:



System Action:

The CA XCOM Data Transport region continues processing.


None required.


N/A


XCMH531I

Message Syntax



XCOM Data Transport server or, if sufficient system resources are available, adjust the maximum number of tasks allowed by increasing the MAXLOC parameter specified on the #DFLTAB macro used to generate the CA XCOM

Default Options Table. The MAXLOC configuration value can also be immediately (but temporarily) changed using the CA XCOM Data Transport


Source:




XCOM Remotely Initiated Task Summary

======================================

MAXREM Setting.......... 75

Current # Remote Tasks.. 0

Peak # Remote Tasks..... 0

# Times at MAXREM....... 0

======================================

Reason:

This message details the remotely-initiated task levels within the CA XCOM Data

Transport region.

Action:



Message Syntax

XCMH532I

Currently the number of remotely initiated active tasks in the CA XCOM

Data Transport region is at nnn% of the maximum allowed by the

MAXREM parameter. This is considered normal and is providing adequate throughput.

The MAXREM configuration parameter limits the number of remotely initiated active tasks that are allowed in the CA XCOM Data Transport region at any given time. An exception condition is recognized when the remotely initiated active task level reaches the threshold defined for this health check.

When a CA XCOM Data Transport region reaches the MAXREM limit, additional remotely initiated file transfer requests are delayed and retried at a later time. This may result in unacceptable processing delays for new file transfer requests. The overhead required to manage this exception condition may degrade the overall performance of the CA

XCOM Data Transport region and adversely affect its ability to complete existing File transfer requests.

Reason:

The remotely-initiated task level within the CA XCOM Data Transport region has been analyzed and compared to the defined threshold. The task level is within the configured threshold value. This is a normal condition.

Action:



Message Syntax

XCMH533W

The total number of active tasks within the CA XCOM Data Transport region has exceeded nnn% of the configured limit as specified on the

MAXTASK parameter.

The MAXTASK configuration parameter limits the number of active tasks that are allowed in the CA XCOM Data Transport region at any given time. An exception condition is recognized when the active task level reaches a certain threshold percentage of that limit. The default threshold percentage is 80%. This threshold can be modified by specifying a different percentage via the THRESHOLD(nnn) parameter for this particular health check.


This may result in unacceptable processing delays for new file transfer requests. The overhead required to manage this exception condition may degrade the overall performance of the CA XCOM Data Transport region and adversely affect its ability to complete existing file transfer requests.

Reason:

The remotely-initiated task level within the CA XCOM Data Transport region has been analyzed and compared to the defined threshold. The remotely-initiated task level has exceeded the configured threshold value. This is an exception condition that can affect performance as stated above.

Action:



System Action:

The CA XCOM Data Transport region attempts to continue processing.


None required.


N/A


Message Syntax



XCOM Data Transport server or, if sufficient system resources are available, adjust the maximum number of tasks allowed by increasing the MAXTASK parameter specified on the #DFLTAB macro used to generate the CA XCOM

Default Options Table. The MAXTASK configuration value can also be immediately (but temporarily) changed using the CA XCOM Data Transport


Source:





CA XCOM Data Transport for z/OS Message

CA XCOM

™

Data Transport

®

for z/OS

Message Reference Guide

CA Product References

Contact CA

http://ca.com/support

[email protected]

customer survey

http://ca.com/docs

New Messages

Changed Messages

Contents

Chapter 1: Introduction 17

Chapter 2: Messages

Chapter 3: Health Check Messages

21

301

Contents 15

Chapter 1: Introduction

Message Storage

Location of the Log File

Message Syntax

Message Storage

Chapter 1: Introduction 17

Location of the Log File

Location of the Log File

Message Syntax

18 Message Reference Guide

Message Syntax

Parts of the Message

Chapter 1: Introduction 19

Message Syntax

Sample Message

Conventions

20 Message Reference Guide

Chapter 2: Messages

0000E

0001I

Chapter 2: Messages 21

Message Syntax

0002I

0004I

0005E

0006E

22 Message Reference Guide

0007E

0008I

Message Syntax

Chapter 2: Messages 23

Message Syntax

0009I

0010I

0011E

24 Message Reference Guide

0012I

00131

0014E

Message Syntax

Chapter 2: Messages 25

Message Syntax

0015I

0016I

0017I

26 Message Reference Guide

0018E

0019E

0020E

Message Syntax

Chapter 2: Messages 27

Message Syntax

0021I

0023E

28 Message Reference Guide

0024E

0025I

0026I