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.
Reason:
An SQL function failed.
Examples:
XCOMM0859E History Connect FAILED, rc = -922, CONNECT.00D31024
XCOMM0859E History Insert FAILED, rc = -204, MALMX11.XCOM_HISTORY_TBL
Action:
Check the SQLCODE, return code, or SQLERRMC in the IBM manual DB2 V9R1 for z/OS Codes.
Reason:
Module DSNAOCLI, the ODBC interface module for DB2, failed to load. ODBC functions will abend if this module cannot be loaded.
Action:
Add DSN=DB2.SDSNLOAD to your STEPLIB DD statement.
Reason:
Something has failed during the attempt to insert a row to the history table. CA XCOM Data Transport makes every attempt to save the insert statement so that you can manually insert the row when the database is once again operational.
Action:
Add the following statement to the CA XCOM Data Transport started procedure:
//XCOMHOVR DD dsn=xxxx,DISP=SHR
Allocate the file as a sequential, variable blocked file with LRECL=20000.
If a connect to ODBC fails, or the insert fails then the insert statement is written to this file. The contents of this file can be transferred to a file suitable for use by SPUFI, for example, by issuing the CA XCOM Data Transport modify command COPYHIST,dsn (explained later).
If the write to the XCOMHOUT DD fails for some reason, then the insert statement is dumped in 72-byte chunks to stderr (//SYSOUT DD). CA XCOM Data Transport makes every attempt to ensure that all records get written to the history data set.
Reason:
(a) When CA XCOM Data Transport is started, a check is made to determine how many records exist in the data set pointed to by XCOMHOVR. Unless there are no records, this message is issued once at startup.
(b) Whenever a failure occurs and CA XCOM Data Transport writes the insert statement to XCOMHOVR, a counter is incremented. Whenever that counter is evenly divisible by 10, this message is issued.
Action:
None
Reason:
The COPYHIST command has the following format:
f xcom,copyhist,dsn
The dsn specified must not already exist. CA XCOM Data Transport creates the file as 80-byte records. The data in XCOMHOVR is copied to this dataset as 72-byte records padded with spaces. This format is compatible with IBM’s SPUFI.
Action:
Specify a valid data set name that does not already exist.
Reason:
When the HISTORY INSERT modify command is issued, CA XCOM Data Transport copies the data from XCOMHOVR to the specified data set and this message is issued to let you know how many records were copied.
Action:
None
Reason:
CA XCOM Data Transport was not able to associate itself with the generic resource name specified by the VTAMGNAM parameter in the XCOMDFLT table. An accompanying message, normally message 0186E, provides more detailed information on the actual cause of the error.
Action:
CA XCOM Data Transport continues to run with no specific generic resource name set. See the accompanying message for information on how to prevent the error.
Reason:
An error occurred when transferring an entire PDS program library to a PDSE program library. This type of transaction is not supported.
Action:
None
Reason:
A Ping request has been issued to a remote XCOM server to determine availability of the server. When an SNA LU name is specified for the server, the port number will be displayed as ‘(SNA)’.
Action:
None.
Reason:
A Ping request to the remote XCOM server has completed. Status of the Ping command will be displayed as ‘COMPLETED’ or ‘FAILED’.
Action:
None.
Reason:
Display following a Ping request to a remote XCOM server. Information about the remote XCOM server is provided. This message is displayed only if the Ping request was successful.
Text to be displayed:
PING INFO FOR xxxxxxxxxxxxxxxxxxx [PORT yyyyy]
This message will provide indication of the system that was pinged.
RELEASE= xxxxx SPxx GEN LEVEL xxxx SYSTEM NAME=xxxxxxxx SYSTEM ID=xxxx
This message provides the detail information for the pinged system:
Release, service pack and gen level
History system name and ID
Action:
None.
Reason:
The server being pinged does not support the PING command. The server must be running CA XCOM Data Transport release 11.6 or higher.
Action:
None.
Reason:
An invalid port number was specified for the ping command. The port number must be in the range of 1-65535, or SNA if pinging an ACB name.
An invalid protocol was specified for the ping command. The protocol options are IPV4, IPV6, SSL, and SSLIPV6.
Action:
Correct the port number or protocol and retry the command.
Reason:
The PING command was invoked without specifying the LU name or TCP address of the XCOM server. .
Action:
Reissue the command specifying an LU name or TCP address of an XCOM server.
Reason:
The XCOM Server or XCOMJOB TYPE=EXECUTE has started and is providing an indication of the state of zIIP processing. The state will be either ENABLED or DISABLED.
Action:
None. This message is displayed for informational purposes only.
Reason:
Status of the CPUs for the LPAR is being provided, either as a result of the XCOM Server starting, XCOMJOB TYPE=EXECUTE or the ZIIP STATUS command. The message will display the number of standard and zIIP CPUs, along with the number of CPUs that are available.
Action:
None. This message is displayed for informational purposes only.
Reason:
The ZIIP STATUS command has failed to retrieve CPU status information. The API call to zIIP Enablement Services to retrieve CPU information has returned an error which is given as the return code. CA XCOM Data Transport will continue to operate, but will not attempt to move processing to a zIIP.
Action:
Keep the CA XCOM Data Transport log and SYSLOG and contact CA Technical Support.
Reason:
An attempt was made to initialize zIIP Enablement Services to allow for CA XCOM Data Transport to offload processing to a zIIP. The return and reason codes are from the zIIP Enablement Service API. CA XCOM Data Transport will continue to operate, but will not attempt to move processing to a zIIP.
Action:
Keep the CA XCOM Data Transport log and SYSLOG and contact CA Technical Support.
Reason:
An attempt was made to load the zIIP Enablement Service module, which is part of the CA Common Services library has failed. CA XCOM Data Transport will continue to operate, but will not attempt to move processing to a zIIP
Action:
If you are running r11 of CA Common Services, please insure APAR RO27636 is applied.
Reason:
A process that was running on a zIIP has abended. The reason code is returned from the zIIP Enablement Service. zIIP processing is disabled, and the transfer will be restarted from the point of failure and will not use zIIP,
Action:
Keep the CA XCOM Data Transport log and SYSLOG and contact CA Technical Support.
Reason:
Issued as a result of the ZIIP command, status of each feature which can utilize zIIP processing is displayed.
Action:
None. This message is displayed for informational purposes only.
Reason:
Issued as a result of a ZIIP STATUS command, termination of the XCOM Server or termination of XCOMJOB TYPE=EXECUTE, provides statistical information as to the amount of processing time that was both eligible to be run on a zIIP and actually took place on a zIIP.
Action:
None. This message is displayed for informational purposes only.
Reason:
When performing character set conversion, data in the source file could not be converted.
When UNCONVERTABLE CHARACTERS is displayed, the source data contains one of the following issues: a character that does not have an equivalent character in the target code page or the substitution character that is defined for the conversion table.
The source data contains byte strings that do not represent a valid character in the source code page when MALFORMED CHARACTERS is displayed.
Action:
No action is required.
If MBCS_INPUTERROR is specified as FAIL, when UNCONVERTABLE CHARACTERS is displayed the transfer is terminated. Otherwise the replacement character defined in the conversion table IBM Unicode Services uses is used to replace the character in the target data.
If MBCS_CONVERROR is specified as FAIL, when MALFORMED CHARACTERS is displayed the transfer is terminated. Otherwise the replacement character defined in the conversion table IBM Unicode Services uses is used to replace the malformed character in the target data.
Reason:
An error condition occurred in IBM Unicode Services performing character conversion.
Action:
Determine the cause of the problem by using the return code and reason code. These codes are documented in the IBM z/OS Unicode Services User Guide and Reference manual.
Reason:
When processing a transfer for data in Unicode format (CODE=UTF8 or CODE=UTF16), PACK=LENGTH is forced to improve CPU performance for character set conversion processing.
Action:
No action is required.
Reason:
A valid delimiter for the end of a record was not specified for the USS file, preventing the Unicode transfer from completing.
Action:
Rerun the transfer specifying a valid delimiter.
Reason:
The specified BPX function for a Unicode(CODE=UTF8 or CODE=UTF16) transfer has failed processing a USS file. The file cannot be processed.
Action:
No action is required.
Reason:
A Unicode transfer was submitted but the remote partner does not support Unicode. The transfer request is terminated.
Action:
Rerun the transfer specifying a partner that supports Unicode or change the code type of the transfer to ASCII, EBCDIC, or BINARY.
Reason:
The delimiter options for either the LOCAL_DELIM or REMOTE_DELIM parameters specify options which are mutually exclusive.
Action:
Modify the delimiter options to remove any mutually exclusive options, which are defined in the CA XCOM Data Transport Users Guide under the LOCAL_DELIM and REMOTE_DELIM SYSIN01 parameters.
Reason:
The specified BPX function for a Unicode(CODE=UTF8 or CODE=UTF16) transfer has failed processing a USS file. The file cannot be processed.
Action:
No action is required.
Reason:
An XCOM Server was initiated and the startup member specified in the configuration member or PARM statement was not found in the XCOMCNTL dataset.
Action:
No action is required.
Reason:
A TYPE=EXECUTE transfer utilizing SNA protocol has been attempted but SNA protocol is not enabled by the configuration member.
Action:
To initiate a TYPE=EXECUTE transfer using SNA protocol, specify a configuration member which allows SNA protocol transfers.
Reason:
Using truncation for Unicode data can result in data loss or corruption if truncation occurs in the middle of an MBCS character.
Action:
Initiate the transfer without using truncation. Insure that a large enough logical record length (LRECL) is specified that can hold Unicode data which may have a larger LRECL than the source data.
Reason:
A transfer request was submitted to a server which is currently not allowing the request to be processed. The xxxxxx value indicates the type of transfer, which is either LOCAL or REMOTE depending on how the transfer was initiated. The yyyyyyyy value is the ACBNAME of the server processing the request.
Action:
If the failure is a locally initiated transfer, it is marked as inactive and retries are attempted based on configuration values in place for the server or job. If the failure is a remotely initiated transfer, it is marked in remote suspend status and retries are attempted on the locally initiated server based on configuration values in place for the server or job. Once all retries are exhausted, the transfer is terminated.
Reason:
An informational message preceding the individual configured options of the XCOM server.
Action:
None.
Reason:
An informational message preceding the configured options of the XCOM server.
Action:
None.
Reason:
An informational message indicating the “*” symbol preceding an XCOMM099I message is the XCOM CONFIG parameter default value.
Action:
None.
Reason:
An informational message indicating the “+” symbol preceding an XCOMM099I message is the XCOM CONFIG parameter value which the EXEC parameter changed.
Action:
None.
Reason:
An informational message indicating the “#” symbol preceding an XCOMM099I message is the XCOM CONFIG parameter value which the DFLT modify command changed.
Action:
None.
Reason:
An informational message indicating the XCOM CONFIG parameter and its value, as well as where the value was obtained.
Action:
None.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|