|
|
|
Reason:
A remote node yyyyyyyy, with IP address nnn.nnn.nnn.nnn, has reconnected to this host.
Action:
No action is required.
Reason:
During remote reconnection to host xxxxxxxx, the IP address has changed from the last connection.
Action:
If a MULT-LAN card is available on this remote host, the host IP address was changed, or if Virtual IP Addressing (VIPA) is used, ignore this message. Otherwise, there may be two or more remote nodes with the same system ID name, which is a configuration problem.
Reason:
A remote connection is about to be closed. The message identifies both the number of data bytes transferred and the number of network packets required.
Action:
No action required.
Reason:
CAICCI has received a data packet from a remote application that appears to be invalid. The message contains information that may be important for CAICCI support personnel in diagnosing the problem. After reporting the error, CAICCI will close the connection to the remote system.
Action:
Retry the failing operation. If the problem persists, contact CAICCI support.
Reason:
CCITCP and CCITCPGW require External Security (CA ACF2, CA Top Secret, or RACF).
Action:
Beginning with IBM TCP/IP Version 3.4, IBM requires OMVS segments to be defined to the external security product installed. See the IBM documentation for details about defining an OMVS segment.
Reason:
A TCP/IP Sockets API error has occurred. The variable portion of the message identifies the specific API invoked and explains the error that occurred. If the error can be associated with a single user, then that user's connection will be broken and other sessions will be unaffected. Otherwise, if the error is global in nature or occurs during initialization, CCITCP will terminate.
Certain errors may indicate a lack of memory within the CCITCP address space. If you receive one of these errors, either increase the size of the CCITCP address space (by increasing the REGION= parameter in the CCITCP started task JCL), or run another copy of the CCITCP address space.
Action:
Correct the problem identified in the error message and retry the failing operation.
Reason:
Multiple messages are associated with this message number. All of them are informational regarding the parameters and commands that were passed to CCITCP, CCITCPGW, CCISSL, and CCISSLGW, their run-time environment, and their resultant mode and status of operation.
Action:
No action required.
Reason:
The CCITCP address space was started before TCP/IP for z/OS. CAICCI will periodically attempt to connect to TCP/IP and will continue operating once TCP/IP starts.
Action:
Start TCP/IP for z/OS, if you have not done so already.
Reason:
The CAIENF SNMP address space has been started.
Action:
No action is required.
Reason:
An error has occurred while executing the CAICSMF or CAICRIM CLISTs. Actual return code from processing is displayed.
Action:
Probable error in locating CAILIB or member CAISMFU/CAIRIMU does not exist. Check the CAILIB symbolic to ensure that the indicated library is correct and that the members CAISMFU and CAIRIMU exist.
Reason:
The CAIENF address space has become unavailable.
Action:
Start the CAIENF address space.
Reason:
MVS system is at pre-ESA level.
Action:
Upgrade the MVS system.
Reason:
CAIENF address space has become available.
Action:
No action is required.
Reason:
CAIENF SNMP event is not active to CAIENF. CAS9DCM4 has probably not been installed.
Action:
Install DCM CAS9DCM4 into the CAIENF database.
Reason:
An attempt has been made to start the CAIENF SNMP address space a second time.
Action:
No action is required.
Reason:
The CAIENF SNMP Monitor has completed its initialization.
Action:
No action is required.
Reason:
The P ENFSNMPM command has been issued and accepted. ENFSNMPM will shutdown.
Action:
No action is required.
Reason:
The CAIENF SNMP Monitor TRACE facility is now turned on to get tracing for diagnosis.
Action:
No action required. This message is informational.
Reason:
The CAIENF SNMP Monitor TRACE facility is now turned off.
Action:
No action required. This message is informational.
Reason:
This command is not valid for the CAIENF SNMP Monitor.
Action:
Check if your command is TRAce, NOtrace, SNAP or NOsnap.
Reason:
The SNAP facility is now turned on to dump hex CAIENF data to diagnose problems with the CAIENF SNMP monitor.
Action:
No action required. This message is informational.
Reason:
The SNAP facility for CAIENF SNMP Monitor is now turned off.
Action:
No action required. This message is informational.
Reason:
Another CAS9 initialization procedure is running on the system. This instance of CAS9 will wait up to 20 minutes for the other CAS9 to end. If the other instance of CAS9 does not end within 20 minutes, this instance of CAS9 will terminate.
Action:
No action is required.
Reason:
One of a group of messages issued in response to an CAIENF/CICS QUERY request.
The status (active or inactive) of the CAIENF/CICS interface.
Action:
No action is required. This message is informational.
Reason:
One of a group of messages issued in response to an CAIENF/CICS QUERY request.
This message displays the product ID, interface name, entry point address, and
status of one or more installed CAIENF/CICS applications.
Action:
No action is required. This message is informational.
Reason:
The purpose of this general information message is to display miscellaneous
CAIENF/CICS status information. This message would be issued, for example, in response
to an CAIENF/CICS QUERY request, to indicate the absence of any installed CAIENF/CICS
applications.
Action:
No action is required. This message is informational.
Reason:
This message is issued in response to a product/region-specific CAIENF/CICS QUERY
request. It confirms that product product is installed in CICS region region and is
currently active.
Action:
No action is required. This message is informational.
Reason:
This message is issued in response to a product/region-specific CAIENF/CICS QUERY
request. It indicates that product product is not installed in CICS region region.
Action:
No action is required. This message is informational.
Reason:
This message is issued in response to a product/region-specific CAIENF/CICS QUERY
request. It indicates that product product is installed in CICS region region, but it
is currently inactive.
Action:
No action is required. This message is informational.
Reason:
A SYSPRINT DD statement could not be found. The job cannot continue without this statement.
Action:
Supply a SYSPRINT DD statement in the execution JCL.
Reason:
A DCMLIB DD statement could not be found. The job cannot continue without the statement.
Action:
Supply a DCMLIB DD statement in the execution JCL.
Reason:
An input control statement was found that was not a comment or a DCM( statement.
Action:
Correct the control statement that is in error.
Reason:
An input DCM control statement was found that contained a blank before the closing parenthesis was found. The statement is considered to be terminated at the blank and the data following the blank is ignored.
Action:
Correct the control statement that is in error.
Reason:
A DCM load module must contain an eyecatcher of EDCM as the first characters. The DCM named in the message was found and loaded into storage, but the eyecatcher was not EDCM. Mapping of the named DCM is bypassed.
A DCM load module must also contain a version number of 1 or 2. If the version is not 1 or 2, then the DCM will not be mapped.
Action:
Research the named DCM to determine if the name was specified incorrectly or if the named member is not really a DCM.
For version 1 or 2 incompatibility, contact CA Support.
Reason:
The DCM named in the message was not found in the DCMLIB. Mapping of the named DCM is bypassed.
Action:
Research the named DCM to determine if the name was specified incorrectly or if the DCM is in a library other than the one named on the DCMLIB DD statement.
Reason:
An I/O error occurred while loading the named DCM from the DCM library. Mapping of the named DCM is bypassed.
Action:
Review the job log to determine if z/OS reported any errors. check the DCM library for errors and retry the job.
Reason:
The operating system reported an unknown type of error while loading the named DCM. Mapping of that DCM is bypassed.
Action:
Review the job log to determine if z/OS reported any errors. Check the DCM library for errors and retry the job.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |