Explanation: This information message displays the host IP address and TCP/IP communication port number on which IOAGATE is listening. The message indicates that the TCP channel has initialized and is waiting for the partner or client to initiate the connection.
The variables in this message are:
channelId - the identity of the TCP channel that is listening to the specified port
task - the name of the communication task of channelId. Valid values are:
SENDER - the sender side of the dual connection (DC) TCP channel
RECEIVER - the receiver side of the dual connection (DC) TCP channel
LISTENER - the manager task of the multiple connection (MC) TCP channel
taskId - the internal identity of this communication task
type - the internal type of this communication task
port - the number of the TCP/IP communication port that the TCP channel is using to listen for connection
hostIpAdd - the IP address on which IOAGATE is listening for incoming connections, which corresponds with the IP address specified in the BIND parameter in ECAPARM
* (Asterisk) - IOAGATE is listening for incoming connections on all IP address (adapters) of the z/OS. Default.
appl - the application supported by the specified channel
Corrective Action: No action is required.
ECAT01E PROBABLE CTM/EM SET UP ERROR: DATACENTER PLATFORM WRONGLY DEFINED AS 'DISTRIBUTED' INSTEAD OF AS 'Z/OS'
Explanation: IOAGATE received a synchronization message from Control-M/Enterprise Manager that is encoded for non z/OS platforms. The error is probably because the Control-M for z/OS is incorrectly defined in the Control-M Configuration Manager.
Corrective Action: Ensure that in the Platform field of the Control-M Definition dialog box, the Control-M is defined as 'z/OS', not as 'distributed'.
ECAT02I CHANNEL(channelId.TCP) task (taskId.type) ESTABLISHED CONNECTION WITH HOST(hostIpAdd), APPLICATION(appl)
Explanation: This information message indicates that a dual connection (DC) TCP communication channel succeeded in connecting to the specified partner or client.
The variables in this message are:
channelId - the identity of the channel that established connection with a partner or client
task - the communication task of the indicated TCP channel. Valid values are:
SENDER - the sender side of the dual connection TCP channel
RECEIVER - the receiver side of the dual connection TCP channel
taskId - the internal identity of this communication task
type - the internal type of this communication task
hostIpAdd - the IP address of the host of the partner or client
appl - the identity of the application supported by the specified channel
Corrective Action: No action is required.
ECAT03I CHANNEL(channelId.TCP) task (taskId.type) TERMINATED CONNECTION WITH HOST(hostIpAdd)
Explanation: This information message indicates that the communication task of the specified dual connection (DC) TCP communication channel terminated the connection with its partner or client.
The variables in this message are:
channelId - the identity of the channel that terminated connection with a partner or client
task - the name of the terminated communication task of the specified TCP channel that terminated connection. Valid values are:
SENDER - the sender side of the dual connection TCP channel
RECEIVER - the receiver side of the dual connection TCP channel
taskId - the internal identity of this communication task
type - the internal type of this communication task
hostIpAdd - the IP address of the host of the partner or client
Normal processing continues. The dual connection TCP channel will try to re-establish connection to the specified partner or client.
Corrective Action: No action is required.
ECAT04W CHANNEL(channelId.TCP) task (taskId.type) FAILED TO INITIALIZE, WILL RETRY IN A MINUTE
Explanation: This message warns that initialization failed during startup of the specified TCP channel. The ECAT05I or the ECAT09I message may accompany this message and explain the reason for the failure.
The variables in this message are:
channelId - the identity of the channel that failed to initialize
task - the communication task of channelId. Valid values are:
SENDER - the sender side of the dual connection (DC) TCP channel
RECEIVER - the receiver side of the dual connection (DC) TCP channel
LISTENER - the manager task of the multiple connection (MC) TCP channel
COMTASK - the communication task of the multiple connection (MC) TCP channel
taskId - the internal identity of this communication task
type - the internal type of this communication task
Normal processing continues. After one minute, initialization of the indicated TCP channel is attempted again.
Explanation: This message warns that the dual connection (DC) TCP channel detected a TCP/IP internal errno event while trying to connect or during data exchange with a partner or client.
Internal TCP/IP errno events are network activities that are intercepted, identified, and processed by TCP/IP software. A unique name and a standard numeric code identify each event.
Internal TCP/IP events usually reflect normal network activity, including error recovery. Only codes that point to application program interface (API) errors indicate potential software defects.
This message ECAT05W is always followed by the ECAT0EI message, which explains the errno event.
The variables in this message are:
channelId - the identity of the channel that detected the event
task - the name of the communication task of the specified TCP channel that detected the event. Valid values are:
SENDER - the sender side of the dual connection (DC) TCP channel
RECEIVER - the receiver side of the dual connection (DC) TCP channel
taskId - the internal identity of this communication task
type - the internal type of this communication task
errno - the name of the internal TCP/IP eventFor a description of possible values of errno, refer to the ECAT0EI message that always follows this message.
errno_id - the numeric identity of the internal TCP/IP event. For a description of possible values of errno_id, refer to the appropriate TCP/IP vendor documentation.
stage - the internal ID of the processing stage at which the event was detected
api - the TCP/IP socket API function that was active when the event was detected
action - the internal action identity that describes how the dual connection (DC) TCP channel will handle the event. Valid values are:
GO_DOWN - shut down the specified communication task
CLOSE_GO_DOWN - disconnect, and shut down the specified communication task
CLOSE_REINIT - disconnect, reset, and initialize the specified communication task
REINIT - try to initialize the specified communication task again
IGNORE - ignore the event
DISABLE - disable the channel
Normal processing continues, and the specified TCP channel handles the event as described by the value of action.
Corrective Action: For information about the detected errno event, refer to the appropriate TCP/IP vendor documentation. If the problem persists, call your network systems programmer for assistance.
Explanation: This information message indicates that the partner or client disconnected because the dual connection (DC) channel detected an End-Of-File TCP/IP internal errno event.
The variables in this message are:
channelId - the identity of the channel to which the partner was connected
task - the identity of the communication task of channelId. Valid values are:
SENDER - the sender side of the dual connection channel
RECEIVER - the receiver side of the dual connection TCP channel
taskId - the internal identity of this communication task
type - the internal type of this communication task
appl - the identity of the application supported by channelId
Normal processing continues. The TCP channel channelId shuts down, is reset, and is initialized again.
Explanation: This information message indicates that a communication task of the specified multiple connection (MC) TCP channel initialized successfully. This information message is issued during multiple connection (MC) TCP channel initialization.
The variables in this message are:
channelId - the identity of the multiple connection (MC) TCP channel that initialized successfully
task - the communication task of the channelId channel. Valid values are:
LISTENER - the manager task of the multiple connection TCP channel
COMTASK - the communication task of the multiple connection TCP channel
taskId - the internal identity of the task communication task
type - the internal type of the task communication task
appls - list of the applications supported by the channelId channel
Corrective Action: No action is required.
ECAT08W CHANNEL(channelId.TCP) TASK(taskId) CONNECT FROM IP(IPAddress) FORBIDDEN
Explanation: An attempt to connect to IOAGATE has been rejected because the incoming IP address is specified as forbidden in the IP validation list member that is defined for this channel.
The variables in this message are:
channelId - the identity of the channel that received and rejected the connection request
taskId - the internal identity of the channel task that received and rejected the connection request
IPAddress - the IP address from which the connection has been initiated
The connection is closed and normal processing continues.
Explanation: This message warns that the multiple connection (MC) TCP channel detected a TCP/IP errno event while trying to connect or during data exchange with a partner or client.
Internal TCP/IP errno events are network activities that are intercepted, identified and processed by TCP/IP software. A unique name and a standard numeric code identify each event. Internal TCP/IP events usually reflect normal network activity, including error recovery. Only codes that point to application program interface (API) errors indicate potential software problems.
This message ECAT05W is always followed by the ECAT0EI message, which explains the errno event.
The variables in this message are:
channelId - the identity of the channel that detected the event
task - the name of the communication task of channelId. Valid values are:
LISTENER - the manager task of channelId
COMTASK - the communication task of channelId
taskId - the internal identity of the communication task of channelId
type - the internal type of the communication task of channelId
errno - the name of the internal TCP/IP event. For a description of possible errno values, refer to the ECAT0EI message that always follows this message
errno_id - the numeric identifier of the internal TCP/IP event. For a description of possible values of errno_id, see the appropriate TCP/IP vendor documentation
socket - the TCP/IP socket number assigned to this connection within the indicated task
stage - the internal identity of the processing stage at which the event was detected
api - the TCP/IP socket API function that was active when the event was detected
action - the internal action identity that describes how the multiple connection TCP channel will handle the event. Valid values are:
GO_DOWN - Shut down the specified communication task.
REINIT - Try to establish the connection again.
CLEAR - Free resources assigned by the channel to handle this connection.
DISABLE - Disable the channel.
IGNORE - Ignore the event.
hostId - the host IP address of the remote partner or client with which channelId is communicating.
Normal processing continues, and the specified TCP channel handles the event as described by the value of action.
Corrective Action: Refer to the appropriate TCP/IP vendor documentation for information about errno_id. If the problem persists, call your network systems programmer for assistance.
Explanation: This information message indicates that the channelId channel is setting up the TCPaccess subsystem name. This message is issued during startup, when the TCP communication channel is configured with the TCPaccess TCP/IP software of Computers Associates International, Inc.
The message is issued only when both the TCPVENDR=CA and SUBSYSTM parameters are specified in the ECAPARM configuration file.
The variables in this message are:
channelId - the identity of the channel for which the TCPVENDR and SUBSYSTM parameters were specified
task - the communication task assigned to channelId. Valid values are:
RECEIVER - the receiver side of the dual connection (DC) TCP channel
LISTENER - the manager task of the multiple connection (MC) TCP channel
taskId - the internal identity of task
type - the internal type of task
subsystemName - the subsystem name that the TCPaccess software will use in this IOAGATE run
Explanation: The IOAGATE-to-IOAGATE connection has been disrupted.
The variables in this message are:
channelId - the identity of the TCP channel to which the partner IOAGATE was connected
task - the name of the communication task of channelId to which the partner IOAGATE was connected
taskId - the internal identity of task
type - the internal type of task
node - the identity of the node of the partner IOAGATE to which the partner IOAGATE was connected
errno - the reason of the disconnectionFor a description of possible values of errno, see to the appropriate TCP/IP vendor documentation
socket - the TCP/IP socket number assigned to this connection within task
Normal processing continues. IOAGATE tries to reestablish connection.
Corrective Action: No action is required.
ECAT0EI Event(errno : explan)
Explanation: This message always follows the ECAT05W and ECAT09W messages. It displays a short explanation of the errno event that is identified in the preceding ECAT05W or ECAT09W message.
The variables in this message are:
errno - the name of the internal TCP/IP or IOAGATE channel event
explan - short explanation of the errno event specified by the first variable
Corrective Action: No action is required.
ECAT0FS CHANNEL(channelId.TCP) task (taskId.type) BAD IP ADDRESS(ipAdd) SPECIFIED
Explanation: The specified IP address is invalid.
The variables in this message are:
channelId - the identity of the TCP channel that detected the problem
task - the name of the communication task of channelId
taskId - the internal identity of task
type - the internal type of task
ipAdd - the invalid IP address value that caused the problem
The channelId TCP channel goes down.
Corrective Action: Correct the IP address and restart IOAGATE.
Explanation: A severe socket API error occurred while trying to get a socket.
The variables in this message are:
channelId - the identity of the TCP channel that detected the problem
task - the name of the communication task of channelId
taskId - the internal identity of task
type - the internal type of task
IOAGATE shuts down.
Corrective Action: Contact BMC Customer Support.
ECAT0IW CHANNEL(channelId.TCP) task (taskId.type) CONNECT TO PARTNER(node) WILL BE RETRIED IN nn sec
Explanation: An attempt to establish an IOAGATE-to-IOAGATE connection has failed. IOAGATE will retry the attempt after the time interval nn. This message is issued only when the local IOAGATE has CONNECTOR set to LOCAL.
The variables in this message are:
channelId - the identity of the TCP channel that attempted to connect
task - the name of the communication task of channelId
taskId - the internal identity of task
type - the internal type of task
node - the identity of the node of the partner IOAGATE with which connection was attempted
nn - the time interval (in seconds) before another attempt is made to connect
IOAGATE will retry establishing the IOAGATE-to-IOAGATE connection after the time specified (nn seconds).
Corrective Action: No action is required.
ECAT0JE CHANNEL(channelId.TCP) task (taskId.type) HANDSHAKE SENDING TO PARTNER(node) FAILED(errno)
Explanation: An attempt to send a handshake message to a partner IOAGATE failed.
The variables in this message are:
channelId - the identity of the TCP channel that performed a handshaking attempt
task - the name of the communication task of channelId
taskId - the internal identity of task
type - the internal type of task
node - the node identity of the partner with which IOAGATE was atttempting a handshake
errno - the reason for the disconnectionFor a description of possible values of errno, see the appropriate TCP/IP vendor documentation
Corrective Action: Do the following:
Examine the IOAGATE logs to try to determine the cause of the failure.
If possible, correct the problem and restart IOAGATE.
If the problem persists, contact BMC Customer Support.
ECAT0KE CHANNEL(channelId.TCP) task (taskId.type) CONNECT TO PARTNER(node) FAILED, HOST(hostId) UNAVAILABLE
Explanation: IOAGATE is unable to establish IOAGATE-to-IOAGATE connection because the specified Hostname cannot be resolved by TCP/IP.
The variables in this message are:
channelId - the identity of the TCP channel that attempted to connect
task - the name of the communication task of channelId
taskId - the internal identity of task
type - the internal type of task
node - the node identity of the partner to which IOAGATE attempted to connect
hostId - the identity of the Host that caused the problem
IOAGATE disables the indicated channel, and tries to continue processing.
Corrective Action: Try to specify the IP address instead of a Hostname, and restart IOAGATE.
ECAT0LW CHANNEL(channelId.TCP) task (taskId.type) BOTH PARTNER(node) AND IOAGATE ARE CONNECTORs
Explanation: The message warns that both sides of the IOAGATE-to-IOAGATE connection were configured with CONNECTOR set to LOCAL.
The variables in this message are:
channelId - the identity of the TCP channel that detected the error
task - the name of the communication task of channelId
taskId - the internal identity of task
type - the internal type of task
node - the node identity of the partner IOAGATE
IOAGATE continues trying to establish an IOAGATE-to-IOAGATE connection.
Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map, by setting CONNECTOR to LOCAL on one side of the connection and to PARTNER on the other side, then restart the IOAGATEs.
Explanation: This information message displays the socket implementation and client identity information that currently in use by IOAGATE.
The variables in this message are:
channelId - the identity of the TCP channel for which the socket and client ID information is issued
task - the name of the communication task for which the socket and clientid information is issued
taskId - the internal identity of task
type - the internal type of task
socket_typ - the type of socket implementation currently used by IOAGATE. Valid values are:
OE - integrated socket (OpenEdition socket)The value is explicitly specified in the ECAPARM configuration file.
COM - non-integrated socketThe value is explicitly specified in the ECAPARM configuration file.
NONE - no value assigned in the ECAPARM configuration file, default in use
client_id - the internal identity of task assigned by TCP/IP
Corrective Action: No action is required.
ECAT0PS BAD PARAMETERS RECEIVED(REASON:reason) WHEN VALIDATING INCOMING IP ADDRESS
Explanation: An internal error encountered when performing validation of an incoming IP address.
In this message, reason is the hexadecimal error code specifying an exact error case.
Corrective Action: Contact BMC Customer Support.
ECAT0QE PROBABLE CTM/EM SET UP ERROR: CTM/CONFIGURATION MANAGER DISCOVERY PORT WRONGLY SET TO THE CTM/EM PORT
Explanation: IOAGATE received a message from Control-M/Enterprise Manager that was intended for CTMCAS on the port assigned for CTMAS. The error is probably because the Control-M for z/OS is incorrectly defined in the Control-M Configuration Manager.
Corrective Action: Ensure that the Control-M for z/OS Configuration Agent Port is defined in the Control-M Definition dialog box with the value of the port assigned for CTMCAS, not with the value of the port assigned for CTMAS.
ECAT0SI EVENT(event) OCCURRED ON PORT(port)
Explanation: This information message indicates that the event error occurred on port port number. Details about the error are provided in message ECAT09W that precedes message ECAT0SI.
Corrective Action: No action is required.
ECAT0TI IOAGATE(monitorId) RUNNING ON HOST (hostId,hostIpAdd)
Explanation: This information message displays
the STC name of IOAGATE
the name and the IP address of the host on which IOAGATE is currently running
The variables in this message are:
monitorId - the name of the IOAGATE started task
hostId - the identity of the host on which the specified IOAGATE is running
hostIpAdd - the IP address on which the specified IOAGATE is running
Corrective Action: No action is required.
ECAT0XI CHANNEL(channelId.TCP) task (taskId.type) ADDITIONALLY LISTENING FOR CONNECTION ON PORT(port), IP(hostIpAdd)
Explanation: This information message displays the host IP address and the TCP/IP communication port number on which IOAGATE is listening because the SHRDBIND parameter has been specified in the ECAPARM configuration file for the indicated channel. This message is only issued when the SHRDBIND parameter is specified in the ECAPARM configuration file.
The message indicates that the indicated TCP channel has initialized and is waiting for the partner or client to initiate the connection.
The variables in this message are:
channelId - the identity of the TCP channel that is listening to the specified port
task - the name of the communication task of channelId. Valid values are:
SENDER - the sender side of the dual connection (DC) TCP channel
RECEIVER - the receiver side of the dual connection (DC) TCP channel
LISTENER - the manager task of the multiple connection (MC) TCP channel
taskId - the internal ID of this communication task
type - the internal type of this communication task
port - the number of the TCP/IP communication port on which channelId is listening
hostIpAdd - the address to which channelId is listening
Corrective Action: No action is required.
ECAT0YI codename (codeval)
Explanation: This message displays additional diagnostic information when an errno event occurs.
The variables in this message are:
codename - the identity of the code of the problematic macro or service. Valid values are:
"Return Code of the failing service"
"Reason Code of the failing service"
"Information Code of the failing service"
"EVENT(EADDRINUSE) OCCURRED ON PORT"
"EVENT(EADDRNOTAVAIL) OCCURRED ON PORT"
codevalue - the value of the code of the problematic macro or service, or port number
Corrective Action: Keep the DAIGLOG output for possible later analysis.
ECAT0ZI Macro or Service that failed (mserv)
Explanation: This message displays additional diagnostic information when an errno event occurs.
In this message, mserv is the identity of the problematic macro or service.
Corrective Action: Keep the DAIGLOG output for possible later analysis.
Explanation: The SSL handshake with the client failed. The reason for the failure is described in message ECATS1E, which follows this message.
The variables in this message are:
channelId - the identity of the TCP channel that is listening to the specified port
taskId - the internal identity of this communication task
type - the internal type of this communication task
rc - System SSL return code value
Common values for rc are:
rc
Meaning
Most Probable Cause
6
Key label is not found
A bad KEYLAB parameter was specified in the ECAPARM configuration file
406
Error while reading or writing data
A CTM/EM client attempted to communicate using TCP/IP without SSL
For a full explanation of the return codes, please refer to the IBM manual SC24-5901-03 ,z/OS V1R4.0-V1R5.0 System SSL Programming.
The connection is terminated. IOAGATE resumes listening for incoming connections on the DC channel.
Corrective Action: If the return code is 406 and after this failure the SSL handshake succeeds, no action is required. It is normal for CTM/EM to first attempt to connect using TCP/IP without SSL, and if this attempt fails, it retries with SSL.
If the return code is 406 and the error persists, the client side has probably not enabled SSL. Otherwise, refer to message ECATS1E and to the above-mentioned IBM publication.
Explanation: This message is issued after messages ECATS0E, ECATS2E, ECATS4E, and ECATS5E. The message includes more details about the failure reported by the preceding message.
The variables in this message are:
system_ssl_api_call - the internal System SSL API call that failed
rc - the return code that appeared in the preceding message
textual_explanation_of_the_rc - textual explanation of the return code
For a full explanation of the return codes, please refer to the IBM manual SC24-5901-03, z/OS V1R4.0-V1R5.0 System SSL Programming.
Explanation: After connection is established and before the SSL handshake takes place, the SSL initialization fails. The subsequent message (message ECATS1E) includes more details about the failure.
The variables in this message are:
channelId - the identity of the TCP channel that is listening to the specified port
taskId - the internal identity of this communication task
type - the internal type of this communication task
rc - System SSL return code value
A common value for rc is:
rc
Meaning
Most Probable Cause
202
Error detected while opening the key database
A bad KEYRING parameter is specified in the ECAPARM configuration file.
For a full explanation of the return codes, please refer to the IBM manual SC24-5901-03, z/OS V1R4.0-V1R5.0 System SSL Programming.
The connection is terminated. The task resumes listening for new connections on the DC channel.
Corrective Action: Refer to message ECATS1E and to the above-mentioned IBM publication.
Explanation: An internal call to encrypt a message before sending failed. The subsequent message (message ECATS1E) includes more details about the failure.
The variables in this message are:
channelId - the identity of the TCP channel that is listening to the specified port
taskId - the internal identity of this communication task
type - the internal type of this communication task
rc - System SSL return code value
For a full explanation of the return codes, please refer to the IBM manual SC24-5901-03, z/OS V1R4.0-V1R5.0 System SSL Programming.
The connection is terminated. The task resumes listening for new connections on the DC channel.
Corrective Action: Refer to message ECATS1E and to the above-mentioned IBM publication.
ECATS6E CHANNEL(channelID.TCP) TASK(taskID) SSL OPEN FAILED. RC(rc)
Explanation: After an incoming TCP/IP connection was accepted for a channel with SSL=YES, IOAGATE attempted and failed to allocate and initialize a secure socket instance in the SSL subtask. The failure was in one of the following System SSL API calls:
gsk_secure_socket_open()
gsk_attribute_set_buffer()
gsk_attribute_set_numeric_value()
The variables in this message are:
channelID - the identity of the channel that detected the problem
taskID - the internal identity of the channel task that detected the problem
rc - the return code of the API call
The connection is closed.
Corrective Action: If the problem persists, contact BMC Customer Support.
ECATS7E CHANNEL(channelID.TCP) TASK(taskID) SSL CLOSE FAILED. RC(rc)
Explanation: After an incoming TCP/IP connection was closed for a channel with SSL=YES, IOAGATE attempted and failed to close the corresponding secure socket instance in the SSL subtask. The failure was in the gsk_secure_socket_close() System SSL API call.
The variables in this message are:
channelID - the identity of the channel that detected the problem
taskID - the internal identity of the channel task that detected the problem
rc - the return code of the API call
IOAGATE operations continue.
Corrective Action: If the problem persists, contact BMC Customer Support.
ECATS8E CHANNEL(channelID.TCP) TASK(taskID) INTERNAL ERROR IN ECAGCCB. RC(rc)
Explanation: An internal error occurred when an IOAGATE communications subtask attempted to get an internal message from the SSL subtask.
The variables in this message are:
channelID - the identity of the channel that detected the problem
taskID - the internal identity of the channel task that detected the problem
rc - the return code of the API call
IOAGATE disables the channel, and goes down if there is no other active channel.
Corrective Action: Contact BMC Customer Support.
ECATS9E CHANNEL(channelID.TCP) TASK(taskID) INTERNAL ERROR IN ECAPCCB. RC(rc)
Explanation: An internal error occurred when an IOAGATE communications subtask attempted to put an internal message to the SSL subtask.
The variables in this message are:
channelID - the identity of the channel that detected the problem
taskID - the internal identity of the channel task that detected the problem
rc - the return code of the API call
IOAGATE disables the channel, and goes down if there is no other active channel.
Explanation: An internal error occurred when an IOAGATE communications subtask attempted to free an internal buffer for an SSL connection.
The variables in this message are:
channelID - the identity of the channel that detected the problem
taskID - the internal identity of the channel task that detected the problem
socket - the socket for which the error occurred
IOAGATE disables the channel, and goes down if there is no other active channel.
Corrective Action: Contact BMC Customer Support.
ECATSCE CHANNEL(channelID.TCP) TASK(taskID) INVALID REPLY(reply) FROM SSL SUBTASK. REQ(request)
Explanation: An internal error occurred when an IOAGATE communications subtask read an invalid internal reply from the SSL subtask.
The variables in this message are:
channelID - the identity of the channel that detected the problem
taskID - the internal identity of the channel task that detected the problem
reply - the invalid reply
request - the request for which the invalid reply was received
IOAGATE disables the channel, and goes down if there is no other active channel.
Corrective Action: Contact BMC Customer Support.
ECATSDE CHANNEL(channelID.TCP) TASK(taskID) INVALID REQUEST(request) IN CCB AFTER GET
Explanation: An internal error occurred when an IOAGATE communications subtask read an invalid internal request from the SSL subtask.
The variables in this message are:
channelID - the identity of the channel that detected the problem
taskID - the internal identity of the channel task that detected the problem
request - the invalid request
IOAGATE disables the channel, and goes down if there is no other active channel.
Corrective Action: Contact BMC Customer Support.
ECATSEW CHANNEL(channelID.TCP) TASK(taskID) SSLPUT CALL WHILE SSLPUT IN PROCESS. SOCK(socket)
Explanation: An internal error (a previous internal put did not end) occurred when an IOAGATE communications subtask attempted to put an internal message to the SSL subtask.
The variables in this message are:
channelID - the identity of the channel that detected the problem
taskID - the internal identity of the channel task that detected the problem
socket - the socket for which the error occurred
IOAGATE disables the channel, and goes down if there is no other active channel.
