This section lists new or changed messages for this release.
Reason:
CA XCOM Data Transport has successfully opened the XCOMRRDS Restart File but the record length that is defined for the file is xxxx bytes. CA XCOM is expecting a record length of yyyy bytes. The CA XCOM Data Transport Server terminates with RC=8.
Action:
The XCOMRRDS Restart file RECSIZE has changed with this release. Use the Request Queue Migration Utility (XCOMMIGR) to convert your previous r11.5 or r11.6 XCOMRRDS, or create a new XCOMRRDS using the sample DEFRRDS JCL supplied with this release of the product. Ensure that the procedures for defining the XCOMRRDS Restart File are followed correctly.
Reason:
This message is displayed as the result of a CA XCOM Data Transport SHOW or RSHOW command that is entered with a specific request number.
Action:
None
Reason:
This message is displayed as the result of a CA XCOM Data Transport SHOW or RSHOW command that is entered with a specific request number.
Action:
None
Reason:
This message is displayed as the result of a CA XCOM Data Transport SHOW or RSHOW command that is entered with a specific request number.
Action:
None
Reason:
This message is displayed as the result of a CA XCOM Data Transport SHOW or RSHOW command that is entered with a request number. This message is displayed when transmitting or receiving a report. The following fields are displayed:
Action:
None
Reason:
CA XCOM Data Transport has successfully opened the XCOMHIST History File but the record length that is defined for the file is not yyyy bytes. The actual record length of the file is xxxx. CA XCOM Data Transport will not log any data to the History File, but initiates local requests and accepts remote initiates from the conversation partner.
Action:
The VSAM history file RECSIZE has changed with this release. Use the History Migration Utility (XCOMUTIL) to convert your previous r11.5 or r11.6 VSAM History File or create a new VSAM History File using the DEFHIST JCL supplied with this release of the product. Ensure that installation procedure for XCOMHIST was followed properly.
Reason:
The CA XCOM Data Transport address space in which this message appears has been configured with SNA=NO which disables all SNA transfer activity within the address space.
Action:
Verify that the transfer is being attempted on the correct CA XCOM Data Transport server. If it is the correct server, change the configuration option to SNA=YES (or allow it to default), recycle the server and try the transfer again.
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 multiple 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.
Reason:
One or more of the XCOM modules that were loaded during the initialization does not match the release of the primary program. This message most likely indicates an error with the STEPLIB, LINK LIST, or LPA configuration.
Action:
To use a library structure that is comprised of a single release of XCOM, correct the STEPLIB, LINK LIST, or LPA configuration.
Reason:
A problem was detected with the XCOMHIST data set during server initialization (such as an incorrect record length or a non-KSDS type). The startup value for the HISTORY= parameter is VSAMREQ, which means that a valid XCOMHIST data set MUST be available in order for the server to start.
Action:
To point to an XCOMHIST data set with the appropriate characteristics, either change the server JCL or change the HISTORY= parameter to a value that allows execution without an XCOMHIST data set.
Reason:
The value that is provided for the COMPRESS= parameter specifies a compression method which has been excluded from use by the COMPRESS_ALLOWED parameter.
If the COMPRESS= parameter occurs in a DEST member, the DEST member ENABLE operation fails and the member cannot be used.
If the COMPRESS= parameter was used in SYSIN01, CA XCOM attempts to negotiate to an acceptable compression method based on the COMPNEG parameter value.
Action:
Change the COMPRESS= parameter value to a compression method that is allowed in the CA XCOM environment.
Reason:
The value that is provided for the COMPRESS= parameter for a locally initiated transfer specified a compression method which has been excluded from use by the COMPRESS_ALLOWED parameter. If the compression negotiation is allowed (COMPNEG set to a value other than NO), the compression method has been changed to the COMPNEG setting.
Action:
If the new compression method is acceptable as configured, no further action is required.
Reason:
This is either the first write to the XCOMLOG after server initialization, or the first write since the system clock changed to a new date.
Action:
None
Reason:
The XCOMINQ dataset being processed for an XCOMJOB TYPE=INQUIRE operation contains records that a different release of CA XCOM Data Transport created. Records from a different release level cannot be processed.
xx.x represents the release level in the XCOMINQ records. yy.y represents the release level of XCOMJOB.
Action:
Using the DEFINQ sample JCL supplied with the yy.y release of XCOM, create a new XCOMINQ dataset or invoke a version of XCOMJOB that matches the release indicated in the XCOMINQ records.
Reason:
The value that is provided for the COMPNEG= parameter in either the startup configuration or a DEST member has been excluded from use by way of the COMPRESS_ALLOWED parameter.
Action:
To be a compression method that is allowed in the CA XCOM region and retry the operation, change the value of the COMPNEG parameter.
Reason:
A transfer request was submitted to a server which currently is 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 that is 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
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:
Action:
None
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 connects 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 are 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:
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:
To define the server to schedule the transfer to, either in the configuration member or as an EXEC parameter, specify the proper parameter.
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 using 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 PLEXQ SUBCOMMANDS 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:
See 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 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:
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 valid 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 please 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, a 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 code, 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 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).
Reason:
When XCOMUTIL or XCOMMIGR attempted to open the data set, the call failed.
Action:
Correct the DD name and rerun XCOMUTIL/XCOMMIGR.
Reason:
The only valid SYSIN statements for XCOMUTIL are DATE=, AGE=, PROCESS= and RELEASE=.
The only valid SYSIN statements for XCOMMIGR are RELEASE=.
Action:
Remove the incorrect SYSIN statement and rerun XCOMUTIL/XCOMMIGR.
Reason:
XCOMUTIL or XCOMMIGR did not run successfully.
Action:
To determine the reason it was not successful, check the return code from XCOMUTIL or XCOMMIGR:
Reason:
XCOMUTIL or XCOMMIGR ran successfully.
Action:
Check the other informational messages for details.
Reason:
XCOMUTIL read xxxxxxxx records from the history file (HSTIN).
XCOMMIGR read xxxxxxxx records from the request queue file (RRDSIN)
Action:
Informational message. No action required.
Reason:
XCOMUTIL wrote xxxxxxxx records to the HISTOUT file. These are the records that were kept.
XCOMMIGR wrote xxxxxxxx records to the RRDSOUT file.
Action:
None
Reason:
When running a history or request queue migration, the RELEASE= parameter does not contain a valid release to migrate the history file cluster or request file to.
Action:
Correct the RELEASE parameter to be 11.5, 11.6 or 12.0 and rerun XCOMUTIL/XCOMMIGR. Specify 11.5 or 11.6 to perform backward migration of the VSAM History File cluster or request queue file. Specify 12.0 to perform forward migration of an 11.5 or 11.6 VSAM History File cluster or request queue file to the new version 12.0 format. If you do not have release 11.5, 11.6 or 12.0, create a new history or request queue for the target system using the sample DEFHIST or DEFRRDS JCL for that system.
Reason:
When running a history migration, the source history file sequential data set does not contain the proper size history records for the migration selected.
When running a request queue migration, the source request queue file sequential data set does not contain the proper size queue records for the migration selected.
Action:
Correct the LRECL for the history/request queue file sequential data set created by the IDCAMS job to repro the history file cluster/request queue file. The proper size of the record is 2024 for 11.5, 3034 for 11.6 or 8084 for 12.0 and rerun XCOMUTIL/XCOMMIGR. If you do not have release 11.5, 11.6 or 12.0, create a new history or request queue for the target system using the sample DEFHIST or DEFRRDS JCL for that system.
Reason:
Multiple RELEASE parameters were specified for the history/request queue file migration process.
Action:
Remove the extra RELEASE parameters and rerun XCOMUTIL/XCOMMIGR.
Reason:
A request queue file cannot be migrated from version 12.0 to a release 11.5 format, due to changes made in release 11.6 in support of new features.
Action:
You can only migrate back to release 11.6. If you have release 11.5 or lower, you cannot migrate and must create a new request queue for the target system using the sample DEFRRDS JCL for that system.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|