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 Administration Guide.
Reason:
An XCOM server attempted to connect to an XCOMPLEX where the initiating Admin is at a different release of CA XCOM Data Transport. The XCOMPLEX only allows connections by servers running the same release of CA XCOM Data Transport. XXXXXX is the type of CA XCOM Data Transport job, either SERVER or ADMIN. YYYYYYYYYYYYYYYY specifies the name of the XCOMPLEX that the connection is attempted to.
Action:
None required. The XCOM Server continues to run as a stand-alone server.
Reason:
An IBM Signaling Services macro has terminated with a return code indicating that the PLEXQ GROUP has been damaged.
Action:
Terminate all CA XCOM servers and batch utilities that are connected to the PLEXQ group and attempt to restart them. In the event that this condition should occur, the underlying cause of the failure should be investigated. This is a system environmental error and a solution should be pursued through IBM support.
Reason:
This message indicates that this CA XCOM program has connected to the PLEXQ GROUP identified in the message. Variable substitution in the message text is as follows:
yyyyyyyy = the name of the PLEXQ group to which this program connected.
zzzzzzzz = the name by which this program is known in the PLEXQ group.
Action:
None
Reason:
This message indicates that this CA XCOM program has disconnected from the PLEXQ GROUP identified in the message. Variable substitution in the message text is as follows:
yyyyyyyy = the name of the PLEXQ group to which this program connected.
zzzzzzzz = the name by which this program is known in the PLEXQ group.
Action:
None
Reason:
This message indicates that another CA XCOM program has connected to the PLEXQ GROUP identified in the message, and to which the region which issued the message was already connected. Variable substitution in the message text is as follows:
wwwwwwww = the name of the system where the connector is running.
xxxxxxxx = the name of the job or started task which connected.
yyyyyyyy = the name of the PLEXQ group to which the program connected.
vvvv = the version level of the server connecting to the PLEXQ group.
zzzzzzzz = the name by which the program is known in the PLEXQ group.
Action:
None
Reason:
This message indicates that another CA XCOM program has disconnected from the PLEXQ GROUP identified in the message. The region issuing this message is connected to the named PLEXQ GROUP. Variable substitution in the message text is as follows:
xxxxxxxx = the name of the system where the disconnector is running.
yyyyyyyy = the name of the job or started task which disconnected.
zzzzzzzz = the name of the PLEXQ group to which the program connected.
Action:
None
Reason:
An XCOM server attempted to connect to a PLEXQ where the other XCOM servers in the PLEX are at a different release of CA XCOM Data Transport. The PLEXQ only allows connections by servers running the same release of CA XCOM Data Transport. XXXXXX is the type of CA XCOM Data Transport job, SERVER, JOB or, ADMIN. YYYYYYYY specifies the name of the PLEXQ group that the connection is attempted to.
Action:
None required. The XCOM Server continues to run as a stand-alone server.
Reason:
An XCOM server attempted to connect to a PLEXQ where some other XCOM servers in the PLEX are at a different release of CA XCOM Data Transport. xxxxxxxx specifies the name of the PLEXQ group connecting to.
Action:
None required. The XCOM Server can connect to the PLEX group.
Reason:
This XCOM server that is connected to a PLEXQ where other XCOM servers in the PLEX are at a different release of CA XCOM Data Transport. For any requests processed by this server, features added in the newer releases is ignored.
Action:
None required. Transfers continue to function. To eliminate this warning message and have access to all XCOM features, convert all servers to the latest CA XCOM Data Transport release level.
Reason:
An XCOM job attempted connecting to a PLEXQ where other XCOM servers in the PLEX are at lower release levels of CA XCOM Data Transport. Depending on which server the request is assigned to, some features can be ignored.
Action:
None required. Transfers continue to function. To eliminate this warning message and have access to all XCOM features, convert all servers to the latest CA XCOM Data Transport release level.
Reason:
This message indicates that the macro specified in the message has completed with a non-zero return code, indicating that a failure has occurred. Variable substitution in the message text is as follows:
xxxxxxxx = the name of the macro which failed
yyyyyyyy = the return code from the failing macro call
zzzzzzzz = the reason sub-code from the failing macro call
Action:
Locate the RETURN and REASON codes for the appropriate macro in the IBM z/OS documentation and follow the instructions for the specific error code listed there.
Reason:
This message indicates that an expected response to a prior request was not received by the PLEXQ protocol management module within the timeout limit.
Action:
Ensure that the partner region receiving the request is still operational. Increase the TIMEOUT parameter for the local region if the partner region is still functional. If all regions are still operational, gather all output from the requesting CA XCOM server or XCOMJOB batch utility and contact CA XCOM support.
Reason:
A PLEXQ message which was received contains an invalid message type identifier. This message indicates an internal PLEXQ error.
Action:
Gather all output from the failing CA XCOM server or XCOMJOB batch utility and contact CA XCOM support.
Reason:
A PLEXQ request has been received which is missing a critical control block address. This message indicates an internal PLEXQ error.
Action:
Gather all output from the failing CA XCOM server or XCOMJOB batch utility and contact CA XCOM support.
Reason:
A PLEXQ request has been received which has an invalid address for a critical control block. This message indicates an internal PLEXQ error.
Action:
Gather all output from the failing CA XCOM server or XCOMJOB batch utility and contact CA XCOM support.
Reason:
A PLEXQ request has been received which is missing a critical control block address. This message indicates an internal PLEXQ error.
Action:
Gather all output from the failing CA XCOM server or XCOMJOB batch utility and contact CA XCOM support.
Reason:
A PLEXQ request has been received which has an invalid address for a critical control block. This message indicates an internal PLEXQ error.
Action:
Gather all output from the failing CA XCOM server or XCOMJOB batch utility and contact CA XCOM support.
Reason:
A PLEXQ request has been received which is missing a critical control block address. This message indicates an internal PLEXQ error.
Action:
Gather all output from the failing CA XCOM server or XCOMJOB batch utility and contact CA XCOM support.
Reason:
A PLEXQ request has been received which has an invalid address for a critical control block. This message indicates an internal PLEXQ error.
Action:
Gather all output from the failing CA XCOM server or XCOMJOB batch utility and contact CA XCOM support.
Reason:
There is not enough available virtual storage in the CA XCOM region to invoke the transaction program needed to service the request.
Action:
Do one or more of the following:
Reason:
The address of an ECB needed to communicate with another task within the CA XCOM region is not valid. This indicates an internal PLEXQ error.
Action:
Gather all output from the failing CA XCOM server or XCOMJOB batch utility and contact CA XCOM support.
Reason:
A STAT, USTAT, XRSHOW, or XSHOW command was entered but the PLEXQ group is not active.
Action:
None.
Reason:
A STAT, XSHOW, or XRSHOW command was issued for a PLEXQ group to which this CA XCOM Data Transport server is not connected.
Action:
Check the PLEXQ group name that is specified on the command and correct if necessary.
Reason:
A value was specified for the STCPROTOCOL parameter, but the corresponding parameter to define the server to schedule the transfer to was omitted.
Action:
Specify the proper parameter that defines the server to schedule the transfer to, either in the configuration member or as an EXEC parameter.
Reason:
The task within the CA XCOM region which processes PLEXQ messages is being started or is stopping.
Action:
None
Reason:
The command byte in the internal PLEXQ request buffer is not valid.
Action:
Gather all output from the failing CA XCOM server or XCOMJOB batch utility and contact CA XCOM support.
Reason:
An error occurred which caused the request identified by xxxxxxxx to not be completed successfully.
Action:
Review the XCOMLOG and other SYSOUT messages from the CA XCOM invocation looking for other error messages relating to the failed request. If insufficient information was displayed to identify the problem, gather all output from the failing CA XCOM server or XCOMJOB batch utility and contact CA XCOM support.
Reason:
An attempt to acquire storage to use as a buffer for a PLEXQ operation has failed.
Action:
The most common cause of this message is a shortage of virtual storage available within the CA XCOM address space. If possible, increase the REGION JCL parameter for the execution of the program. If there is sufficient storage, check the CA XCOM SYSOUT for other messages relating to errors that may have occurred during the execution of the CA XCOM program.
Reason:
An attempt to join a PLEXQ group has failed because the maximum number of connections are already active.
Action:
Dynamically disconnect from any unneeded or unused PLEXQ groups via the PLEXQ,LEAVE command or remove them from the PLEXQ configuration parameter and restart the server.
Reason:
An attempt to connect to a PLEXQ group has failed because the CA XCOM Data Transport server already has an active connection to the named PLEXQ group.
Action:
If the error occurs during server initialization, remove the duplicate PLEXQ group name from the PLEXQ configuration parameter. If the error occurs as a result of a PLEXQ,JOIN command, the connection already exists, and no further action is required.
Reason:
An attempt to disconnect from a PLEXQ group has failed because the CA XCOM Data Transport server has no active connection to the named PLEXQ group.
Action:
If the PLEXQ group name is correct in the PLEXQ,LEAVE command, no further action is required, as the connection is not active. Otherwise, reissue the PLEXQ,LEAVE command with the correct PLEXQ group name.
Reason:
A PLEXQ,QUERY command was entered on the CA XCOM Data Transport server. This message identifies the subsequent output as being the response to the QUERY command.
Action:
None
Reason:
A PLEXQ command was entered with an invalid SUBCOMMAND. The valid SUBCOMMANDS for PLEXQ are QUERY, JOIN and LEAVE.
Action:
Choose one of the valid SUBCOMMANDS listed and reenter the command with a correct option.
Reason:
An invalid PLEXQ group name was provided as a parameter to the PLEXQ configuration parameter.
Action:
Refer to the CA XCOM Data Transport Administration Guide for the requirements for PLEXQ group names.
Reason:
A PLEXQ JOIN or LEAVE command was issued, but no PLEXQ group name was provided.
Action:
Specify a valid PLEXQ group name as a parameter for the command.
Reason:
Insufficient virtual storage was available to satisfy a request to allocate a buffer to hold an IXCQUERY response.
Action:
Retry the request later, or run the server with a larger storage allocation.
Reason:
The macro call issued to connect to the SYSPLEX Signaling Services Group (named by xxxxxxxx) has received a return code indicating that the connection attempt was unsuccessful.
Action:
Examine the XCOMLOG and SYSOUT from the CA XCOM region to locate any additional messages relating to the PLEXQ connection. Take the action(s) indicated for any such messages.
Reason:
The LSEXPAND macro is used to expand the available stack area for program use within an address space. This macro call has failed with the return code indicated by xxxxxxxx.
Action:
Review the documentation for the LSEXPAND system service and follow the instructions for the return code that was received. This is likely a system environmental error.
Reason:
The XCOMJOB batch utility was invoked specifying a STCPLEXQ parameter of xxxxxxxx, but no servers were found connected to SYSPLEX Signaling Services using that group name.
Action:
Verify that the spelling of the group name on the STCPLEXQ EXEC PARM for the XCOMJOB utility is correct. If the group name is spelled correctly on the STCPLEXQ EXEC PARM, verify that a CA XCOM server (XCOMXFER) has been started, connected and is still active using the specified PLEXQ group name.
Reason:
Informational message indicating that PLEXQ, that does not require an Admin server, replaces the deprecated XCOMPLEX Admin Server.
Action:
None.
Reason:
Informational message indicating where to locate information about using PLEXQ for XCOMPLEX services.
Action:
None.
Reason:
This message identifies the source of the parameters that follow as being the TYPE=CONFIG member read during the XCOM server startup. XXXXXXXX is replaced by the name of the PDS member that was specified on the CONFIG= EXEC parameter.
Action:
None
Reason:
This message identifies the source of the parameters that follow as being the EXEC statement PARM= field.
Action:
None
Reason:
The value specified for the parameter named in this message either has a missing parenthesis or a delimiting “,” was not found as expected.
Action:
Correct the format of the parameter value and restart the CA XCOM Data Transport server.
Reason:
A parameter value was parsed which was expected to be numeric, but non-numeric data was found.
Action:
Correct the parameter value by removing any non-numeric characters and resubmit the job.
Reason:
The numeric value parsed from the parameter is less than the minimum allowed for this numeric parameter.
Action:
Correct the parameter value by changing it to conform to the prescribed limits.
Reason:
The numeric value parsed from the parameter is greater than the maximum allowed for this numeric parameter.
Action:
Correct the parameter value by changing it to conform to the prescribed limits.
Reason:
The length of the value parsed from the parameter is greater than the maximum number of characters allowed for this parameter.
Action:
Correct the parameter value by changing it to conform to the prescribed limits.
Reason:
The length of the value parsed from the parameter is less than the minimum number of characters allowed for this parameter.
Action:
Correct the parameter value by changing it to conform to the prescribed limits.
Reason:
The value parsed from the parameter contains characters that are not allowed for this particular parameter.
Action:
Correct the parameter value by changing it to conform to the prescribed format.
Reason:
The value parsed from the parameter does not match the keywords allowed to be specified for it.
Action:
Correct the parameter value by changing it to be a keyword from the list of possible options for this parameter.
Reason:
The keyword parameter specified in the record is not from the list of supported parameters which can be specified in a TYPE=CONFIG member.
Action:
Check the spelling of the keyword parameter and correct if necessary, or ensure that the parameter is in fact valid for CA XCOM.
Reason:
Severe errors were detected in the parameter records in the TYPE=CONFIG member such that initialization of the CA XCOM program being invoked cannot continue.
Action:
Correct the parameter errors noted prior to this message and resubmit the job.
Reason:
The data set name or prefix specified in the parameter being processed has failed the validation checks implemented by the CA XCOM parameter parsing program. These checks enforce the data set naming conventions established by IBM for z/OS data set names.
Action:
Correct the data set name or prefix specification on the parameter statement and resubmit the job.
Reason:
The prior statement indicated it was being continued to the statement immediately preceding this message. However, the data contained in this parameter statement does not begin in the columns (2 – 16) which are required for second and subsequent continuation statements.
Action:
Check the starting column of this parameter statement and ensure that 1) continuation is desired, and 2) that the data in this statement begins in the correct column range required for continuation. Make any necessary corrections to the parameter statement and resubmit the job.
Reason:
The prior statement indicated it was being continued to the statement immediately preceding this message. However, the data contained in this parameter statement begins in column 1, which is not valid for a continuation statement.
Action:
Check the starting column of this parameter statement and ensure that 1) continuation is desired, and 2) that the data in this statement begins in the correct column range required for continuation. Make any necessary corrections to the parameter statement and resubmit the job.
Reason:
The prior statement indicated it was being continued to the next parameter statement. However, an end-of-file condition was raised before the continuation statement was read.
Action:
Ensure that the previous statement should have been flagged for continuation. If so, add a parameter statement to provide the continuation data that is expected. If not, remove the "+" from the prior parameter statement. Resubmit the job.
Reason:
Some configuration parameters require that the first character be Alphabetic (A-Z) or the characters "@", "#" or "$". The parameter being defined has that requirement, but the value being provided does not conform to it.
Action:
Ensure that the first character of the value (or of each data set name node in the case of a data set name or prefix) conforms to the restriction outlined above.
Reason:
CA XCOM Data Transport uses the first data set in the XCOMCNTL DD concatenation to store and retrieve its CONFIG members. While attempting to process the CONFIG member for this invocation of CA XCOM Data Transport, the XCOMCNTL DD statement was not present in the JCL.
Action:
Add an XCOMCNTL data set to the execution JCL for processing CONFIG members. The absence of the XCOMCNTL data set will cause CONFIG member processing to be skipped.
Reason:
The CA XCOM Data Transport SAVE console command was entered, but no member name was provided as a parameter.
Action:
Specify the name of the CONFIG member which is to be saved or replaced in the first XCOMCNTL data set.
Reason:
The CA XCOM Data Transport SAVE console command was entered along with a member name, but the parameter identified in the message is not recognized as being valid for the command.
Action:
Either enter the console command again without the parameter noted in the message, or correct it to be a valid option for the SAVE command.
Reason:
A CONFIG member with the name specified in the message is being created in the XCOMCNTL data set. The second, optional portion of this message is written if the member is being automatically created from an existing CA XCOM Data Transport Default Options Table, and includes the name and timestamp from when it was assembled.
Action:
None
Reason:
A SAVE command was entered for the module named in the message, but it already exists in the XCOMCNTL dataset. An existing CONFIG member can only be overwritten by adding the REPLACE optional keyword to the command syntax.
Action:
Verify that the member referenced in the message is the correct one, and either specify a different member name, or specify the REPLACE option to cause it to be overwritten.
Reason:
The CONFIG member named in the message is being overwritten with the system parameters currently in effect.
Action:
None
Reason:
Not enough storage is available to process SYSIN01 parameters.
Action:
Run the batch job in a larger region.
Reason:
The identified parameter was specified but the value will be ignored because the parameter has been deprecated.
Action:
Remove the identified deprecated parameter; otherwise the message can be ignored.
Reason:
This message is a diagnostic message that the CA XCOM Data Transport team uses.
Ignore this message.
Action:
None required.
Reason:
This message is a diagnostic message that the CA XCOM Data Transport team uses.
Ignore this message.
Action:
None required.
Reason:
This message is a diagnostic message that the CA XCOM Data Transport team uses.
Ignore this message.
Action:
None required.
Reason:
This message is a diagnostic message that the CA XCOM Data Transport team uses.
Ignore this message.
Action:
None required.
Reason:
This message is a diagnostic message that the CA XCOM Data Transport team uses.
Ignore this message.
Action:
None required.
Reason:
This message is a diagnostic message that the CA XCOM Data Transport team uses.
Ignore this message.
Action:
None required.
Reason:
The CA XCOM Data Transport for z/OS CAIRIM initialization program (FXC0INIT) has started or ended.
Action:
None.
Reason:
The CA XCOM Data Transport for z/OS CAIRIM initialization program (FXC0INIT) requires at least one parameter (INIT, REINIT or DELETE).
Action:
Update the CAIRIM parameter file entry for CA XCOM Data Transport for z/OS with the required action parameter and rerun CAIRIM.
Reason:
The CA XCOM Data Transport for z/OS CAIRIM initialization program (FXC0INIT) requires the CONFIGDSN parameter for action INIT or REINIT. Either the CONFIGDSN parameter was not supplied or the CONFIGDSN is invalid.
Action:
Update the CAIRIM parameter file entry for CA XCOM Data Transport z/OS with the required or correct CONFIGDSN parameter and rerun CAIRIM.
Reason:
The CA XCOM Data Transport for z/OS CAIRIM initialization program (FXC0INIT) successfully deleted the CONFIGDSN value.
Action:
None.
Reason:
The CA XCOM Data Transport for z/OS CAIRIM initialization program (FXC0INIT) attempted symbol call xxxxxxxxxxxx failed with return code nnnnnnnn and reason code nnnnnnnn.
Action:
If the return code is 8 and the action specified was DELETE, CONFIGDSN could not be deleted because it did not exist. For all other cases contact CA XCOM Data Transport technical support.
Reason:
The CA XCOM Data Transport for z/OS CAIRIM initialization program (FXC0INIT) successfully set CONFIGDSN to xxxxxxxx.
Action:
None
Reason:
Used by the CA XCOM Data Transport for z/OS CAIRIM initialization program (FXC0INIT) for debugging messages.
Action:
None
Reason:
CA XCOM Data Transport found the symbol CONFIGDSN with value xxxxxxxx.
Action:
None
Reason:
CA XCOM Data Transport is searching XCOMCNTL or CONFIGDSN for the TYPE=CONFIG member yyyyyyyy.
Action:
None
Reason:
CA XCOM Data Transport could not allocate the CONFIGDSN data set. The dynamic allocation return and reason code is provided.
Action:
Correct the error and retry the batch job.
Reason:
CA XCOM Data Transport is skipping the search for the TYPE=CONFIG member in the CONFIGDSN data set because the CONFIGDSN data set could not be allocated.
Action:
Refer to the 1462E message for the cause of the allocation error.
Reason:
STCAPPL, STCIP, or STCPLEXQ was specified as an EXEC parameter for the job. The value for STCPROTOCOL is determined from the overriding EXEC parameter. If a value is specified for STCPROTOCOL in the configuration member, it is ignored.
Action:
None
Reason:
The call to IBM callable service aaaaaaaa failed with return value xxxxxxxx, return code yyyyyyyy, and reason code zzzzzzzz.
Action:
For the callable service that failed, refer to the IBM z/OS UNIX System Services Programming: Assembler Callable Services Reference for details on the meaning of the return value, return, and reason code.
Reason:
XXXX is the System SSL function that failed. ZZZ is the return value of said function and YYYY is the reason.
Action:
To determine the appropriate action, examine the message. Many errors are the result of the specification of the wrong IPNAME or IPPORT, configuration problems, name resolution, or network problems.
These codes are not CA XCOM Data Transport error codes, but are passed back from System SSL.
Reason:
Specified Section and/or Parameter is missing for the XCOM_CONFIG_SSL config file that is specified for System SSL.
Action:
Add the mentioned section and/or parameter to the config file using the following format:
[PARAMETER]
INITIATE_SIDE = value1
RECEIVE_SIDE= value2
Reason:
One or more of the criteria that is specified in the XCOM_CONFIG_SSL config file did not match the certificate on the corresponding end.
Action:
Verify that the criteria specified in the XCOM_CONFIG_SSL config file matches the information in the corresponding certificate.
Reason:
The system detected that you are using the sample certificates provided.
Action:
The sample certificates can be used for testing purposes, but it is not recommended that they be used in a production environment. New certificates should be created for use in a production system.
Reason:
The CA XCOM Data Transport configuration specifies System SSL (SSL_VERSION=SYSTEM) and the system detected that you are not at z/OS 1.13 or above.
Action:
CA XCOM Data Transport support for IBM System SSL requires z/OS 1.13 or above. Sites running an IBM supported z/OS system below z/OS 1.13 must use OpenSSL for secure socket (SSL) transfers (SSL_VERSION=OPEN).
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|