|
|
|
Reason:
A syntax error was detected in the Server IP address. The string was assumed to be an IPv6 address because of the colon (:) in the string. However, CAICCI/PC was unable to parse the string into a valid IPv6 address.
Action:
Correct the IPv6 address specified for the CAICCI Server Identification or use the host name defined to your DNS server.
Reason:
Insufficient memory is available to satisfy a CAICCI/PC request.
Action:
Ensure that the PC meets the memory requirement specification. If there appears to be sufficient memory, contact CA Support.
Reason:
The host has not responded to the last transmission within the expected time.
Action:
Retry the session when the host is less busy or adjust the time-out delay.
Reason:
There was an error at the TCP/IP level. This is not a CAICCI error.
Action:
The specific TCP/IP error name is appended to this message. If necessary, more information may be found in the trace file. To produce a trace file, use the Enable Trace option of the CCIPC configurator.
Reason:
Failed to connect to Secure Sockets Layer. An error message, returned from SSL, is appended to this message. Details will be seen in the trace.
Action:
Enable the trace and re-create the problem. Examine the trace for the cause of the failure to connect.
Reason:
The underlying TCP/IP connection been closed, probably by a network error or by the mainframe server.
Action:
Examine the mainframe server logs to determine the cause of the disconnection.
Reason:
I/O Error encountered by SSL processing, probably originating from an error with the underlying TCP/IP connection.
Action:
Determine the cause of the I/O error from the Detailed Return Code. If its value is zero, an EOF occurred that violates the SSL protocol. Otherwise the Detailed Return Code contains a WinSocket error code. If the cause of the problem cannot be determined, enable trace, attempt to re-create the problem, and contact CA Support.
Reason:
An error in Secure Sockets Layer processing was encountered.
Action:
Enable the trace, attempt to re-create the problem, and contact CA Support.
Reason:
An internal error with CAICCI PC or OpenSSL was encountered.
Action:
Enable the trace, attempt to re-create the problem, and contact CA Support.
Reason:
A Secure Sockets Layer initialization error was encountered.
Action:
Use the Configurator to enable the trace and re-create the problem. Examine the trace for the cause of the failure. If the cause of the problem cannot be determined from the trace, contact CA Support.
Reason:
Certificates on the PC and mainframe do not match.
Action:
Use the Configurator to enable the trace and re-create the problem. Examine the trace for the cause of the failure.
Reason:
No certificate sent from the server.
Action:
If Secure Sockets Layer processing is needed, then a certificate must be supplied on the server side. If the SSL processing is not needed, disable the option with the CAICCI Configurator.
Reason:
Certificate passed from the mainframe server is not a valid CAICCI certificate.
Action:
Adjust the certificates.
Reason:
Certificates on the PC and mainframe do not match.
Action:
Adjust the certificates.
Reason:
Server does not support Secure Sockets Layer. This message was introduced with CAICCI V2.1.
Action:
If you do not need secure data transfer, deactivate this option on the PC through the SSL tab on the Configurator. If you need secure data transfer, you must ensure that the mainframe server is at release R2.1 or greater and SSL is enabled on the mainframe server.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |