|
|
|
The following pages list CA XCOM Data Transport for z/OS CICS‑specific system messages. Each message is accompanied by a reason explaining the circumstances under which it might be encountered, plus an indication of the action to take when and if that happens. The prefix XCOMK has been deleted from the messages, leaving the numeric designation and the type designations I or E.
Reason:
The user has selected an Operator Control TYPE=DISPLAY function. The selection criteria passed to XCICCAPI and subsequently to the CA XCOM Data Transport server has resulted in zero transfer requests being returned to CICS.
Action:
Review the selection criteria specified and change if necessary.
Reason:
This message indicates that CICS error condition xxxxxxxx was received when XCICCAPI was trying to execute CICS verb yyyyyyyy. This message is normally caused by improper definitions or if the remote system is not available at the time.
Action:
Make sure that the CICS TCT is defined properly and that the remote system is available. Contact CA Technical Support if the above are true and this message continues to appear.
Reason:
XCICCAPI was in a conversation with the CA XCOM Data Transport server and received sense code xxxxxxxx when executing CICS verb yyyyyyyy. The sense data can be found in the SNA Formats manual.
Action:
Make sure that the CICS TCT is defined properly and that the remote system is available. Contact CA Technical Support if the above are true and this message continues to appear.
Reason:
XCOMCAPI has attempted to allocate a session with the CA XCOM Data Transport server, but is waiting for another user to release the session. The PCT entry defines the amount of time that the transaction will wait before ending with errors.
Action:
Retry the failing transaction. If this message continues to appear, check the status of the CICS connection to see if there is a problem with the CICS connection.
Reason:
The user has entered a parameter in the parameter queue (APIPARMQ in the APIDSECT), but this parameter is not valid. See the chapter “The Programming Interface” to see the list of parameters this interface allows.
Action:
Correct the invalid parameter.
Reason:
A parameter was entered that is too long or was started by a quote (' or "), but was not ended by a quote.
Action:
Correct the invalid parameter.
Reason:
Field xxxxxxxx is required, but was not present in the TS Parameter Queue.
Action:
Add parameter xxxxxxxx to the TS Parameter Queue.
Reason:
Field xxxxxxxx was entered in the TS Parameter Queue, but the values entered were incorrect. See the CA XCOM Data Transport for z/OS User Guide for the proper format of the fields that you can enter in the TS Parameter Queue for schedule operations. For operator control operations, see the chapter “The Programming Interface” for the proper format of parameters you can enter in the TS Parameter Queue.
Action:
Fix the parameter in error.
Reason:
Two parameters, xxxxxxxx and yyyyyyyy, are conflicting and are mutually exclusive. For example, if you specify a TYPE=RECEIVE, you cannot specify FILETYPE=REPORT.
Action:
Fix the parameter in error.
Reason:
No local data set name was entered for a file transfer request, even though the unit and block size were entered.
Action:
Enter the correct local data set name.
Reason:
The parameter FILETYPE=CREATE was created, but the BLKSIZE specified was invalid. This normally means that the BLKSIZE was 4 or 32760.
Action:
Fix the BLKSIZE parameter.
Reason:
The parameter FILETYPE=CREATE was created, but the LRECL specified was invalid. This normally means that the LRECL was invalid for the RECFM specified.
Action:
Fix the LRECL parameter.
Reason:
DCB operands were specified, but were conflicting. Two reasons that this message could appear are:
RECFM=FB and BLKSIZE is not a multiple of LRECL.
RECFM=VB and BLKSIZE is not at least a quantity of 4 greater than LRECL.
Action:
Fix the LRECL, BLKSIZE, or RECFM operand.
Reason:
The RECFM parameter was incorrectly specified. See the CA XCOM Data Transport for z/OS User Guide for the allowable RECFM parameters.
Action:
Fix the RECFM operand.
Reason:
Either GROUP or LU must be defined during a transfer schedule request. Neither was defined in the TS Parameter Queue.
Action:
Specify either the GROUP or LU parameter in the TS Parameter Queue.
Reason:
Parameter xxxxxxxxxxxxx was specified, but the XTCNET parameter was not specified in the TS Parameter Queue. XTCNET must be specified to use the CA XCOM Data Transport XTC facility.
Action:
Specify the XTCNET parameter in the TS Parameter Queue.
Reason:
More than eight XTC jobs have been entered in the TS Parameter Queue, while there is a limit of eight jobs to be entered. See the CA XCOM Data Transport for z/OS User Guide for the proper format of the XTC parameters.
Action:
Specify the correct number of XTC jobs in the TS Parameter Queue.
Reason:
XTC parameter xxxxxxxxxxxxx has exceeded its maximum length when defined in the TS Parameter Queue. See the CA XCOM Data Transport for z/OS User Guide for the proper format of the CA XCOM Data Transport XTC parameters.
Action:
Correct the XTC parameter in error in the TS Parameter Queue.
Reason:
The user specified TS Parameters PACK=CRLF, but did not specify RECSEP=YES. PACK=CRLF is valid only when RECSEP=YES.
Action:
Specify RECSEP=YES in the TS Parameter Queue if you want to use CRLF record packing. Otherwise, remove the PACK=CRLF parameter from the TS Parameter Queue.
Reason:
The APPLID of the CA XCOM Data Transport server passed in the COMMAREA (field APISTCAP in DSECT APIDSECT) is not in the CICS TCT or was not defined to CICS through the RDO file. Make sure that the APPLID specified is correct and that the APPLID is defined to CICS.
Action:
Set APISTCAP to a valid APPLID defined to CICS.
Reason:
One of the fields defined in the COMMAREA was not correct. Field APITYPER of APIDSECT must be either S for a schedule or O for operator control functions.
Action:
Specify the correct value for field APITYPER.
Reason:
The CA XCOM Data Transport server APPLID defined in the COMMAREA (field APISTCAP in DSECT APIDSECT) was either nulls or spaces. That field must define the APPLID of the CA XCOM Data Transport server.
Action:
Set APISTCAP to a valid APPLID defined to CICS.
Reason:
The TS Parameter Queue specified in the COMMAREA (field APIPARMQ of DSECT APIDSECT) was specified as spaces or nulls. This field must define the TS Parameter Queue, where the parameters describing the transfer to be performed must be supplied.
Action:
Set APIPARMQ to the TS Parameter Queue name.
Reason:
The user has specified a TYPE=DISPLAY operator control function, but has not specified which CA XCOM Data Transport queues to check. The user must specify YES for at least one of the parameters: INACTIVE, ACTIVE, and COMPLETED.
Action:
Set one of the above parameters to YES.
Reason:
XCOMCICI has attempted to open DD statement xxxxxxxx, but was unable to. The most likely reason for this message is that the DD statement xxxxxxxx was not defined. xxxxxxxx will point to either XCOMIN or XCOMOUT.
Action:
Define the DD statement correctly and rerun the job.
Reason:
Two parameters are valid as input to XCOMIN: SERVER‑APPLID and OPER‑TRAN. A parameter other than these two was read.
Action:
Fix the parameter entered incorrectly and rerun the job.
Reason:
This message is displayed along with another error message that fully describes the actual error. This message indicated that the program did not complete successfully. As a result, the file needed by the install procedure was not created.
Action:
Fix the error and rerun the job.
Reason:
This message is for information purposes only and shows the entered or default STC‑APPLID parameter.
Action:
None
Reason:
This message is for information purposes only and shows the entered or default OPER‑TRAN parameter.
Action:
None
Reason:
This message indicates that the XCOMCICI program has executed successfully and has created the necessary files needed by the CA XCOM Data Transport for z/OS CICS installation procedure.
Action:
None
| Copyright © 2012 CA. All rights reserved. |
|