Messages ECAC00 through ECACxx

This group includes messages for the IOA (infrastructure) product.

ECAC60E CHANNEL(channelId.protocol) TASK(taskId.type) SIB ALLOCATION FAILED FOR msgType.reqType MESSAGE

Explanation: IOAGATE encountered an internal problem when trying to allocate a SIB (Service Instance Block) control block for the current transaction (message).

The variables in this message are:

• channelId - the identity of the channel that detected the problem
• protocol - the current channel uses this communication protocol. Valid values are:
  • TCP -TCP/IP communication protocol
  • SNA - SNA communication protocol
• taskId - the internal identity of the channel task that detected the problem
• type - the internal type of the channel task that detected the problem
• msgType - the type of the messageValid values are:
  • INCOMING
  • OUTGOING
  • INTERNAL
• reqType - the type of the requestThis variable may not appear.Valid values are:
  • NOTIFY
  • STOP
  • CANCEL
  • MODIFY
  • INIT
  • ATTTACH

Corrective Action: If the message persists, contact BMC Customer Support.

ECAC61E CHANNEL(channelId.protocol) TASK(taskId.type) SIB LOCK FAILED FOR msgType.reqType MESSAGE

Explanation: IOAGATE encountered an internal problem when processing the SIB (Service Instance Block) control block of the current transaction (message).

The variables in this message are:

• channelId - the identity of the channel that detected the problem
• protocol - the current channel uses this communication protocol Valid values are:
  • TCP - TCP/IP communication protocol
  • SNA - SNA communication protocol
• taskId - the internal identity of the channel task that detected the problem
• type - the internal type of the channel task that detected the problem
• msgType - the type of the messageValid values are:
  • INCOMING
  • OUTGOING
  • INTERNAL
• reqType - the type of the requestThis variable may not appear.Valid values are:
  • NOTIFY
  • STOP
  • CANCEL
  • MODIFY
  • INIT
  • ATTTACH

Corrective Action: Contact BMC Customer Support if the message persists.

ECAC62E CHANNEL(channelId.protocol) TASK(taskId.type) msgType MESSAGE FAILED DUE TO DISCONNECTION, PORT(port) /APPLID(applId)

Explanation: IOAGATE failed to process the specified message due to disconnection on the indicated port (TCP protocol) port or the VTAM application ID (SNA protocol) applId.

The variables in this message are:

• channelId - the identity of the channel that detected the problem
• protocol - the current channel uses this communication protocol Valid values are:
  • TCP - TCP/IP communication protocol
  • SNA - SNA communication protocol
• taskId - the internal identity of the channel task that detected the problem
• type - the internal type of the channel task that detected the problem
• msgType - the type of the messageValid values are:
  • INCOMING
  • OUTGOING
  • INTERNAL
• port - the port number for TCP disconnection
• applId - the VTAM application identity for SNA disconnection

Corrective Action: Contact BMC Customer Support if the message persists.

ECAC63I CHANNEL(channelId. SNA) DEALLOCATE SENT TO PARTNER LU(luName) OUT_CONVID(out_conversation_id) IN-CONVID(in_conversation_id)

Explanation: This information message indicates that a DEALLOCATE command was sent to the partner IOAGATE, because either the partner or the local IOAGATE terminated.

The variables in this message are:

• channelId - the identity of the channel with which the specified partner was communicating
• luName - VTAM LU 6.2 (APPC) LU name of the partner IOAGATE
• out_conversation_id - VTAM LU 6.2 (APPC) outgoing conversation identity
• in_conversation_id - VTAM LU 6.2 (APPC) incoming conversation identity

If the partner IOAGATE is terminating, the local IOAGATE sends a termination message to the partner IOAGATE. If the local IOAGATE is terminating, it sends termination messages to its partner IOAGATEs.

Corrective Action: No action is required.

ECAC64E CHANNEL(channelId.protocol) TASK(taskId.type) msgType MESSAGE REJECTED, NO APPL SERVER IS AVAILABLE

Explanation: IOAGATE rejected the specified message because no Application server was available.

The variables in this message are:

• channelId - the identity of the channel that rejected the message
• protocol - the current channel uses this communication protocol Valid values are:
  • TCP - TCP/IP communication protocol
  • SNA - SNA communication protocol
• taskId - the internal identity of the channel task that rejected the message
• type - the internal type of the channel task that rejected the message
• msgType - the type of the messageValid values are:
  • INCOMING
  • OUTGOING
  • INTERNAL

Corrective Action: Contact BMC Customer Support if the message persists.

ECAC65E CHANNEL(channelId.protocol) TASK(taskId.type) msgType MESSAGE REJECTED, REQUIRED ADDR. SPACE(addrSpaceId) IS DOWN

Explanation: IOAGATE rejected the specified message because the required Application server was down.

The variables in this message are:

• channelId - the identity of the channel that rejected the message
• protocol - the current channel uses this communication protocol. Valid values are:
  • TCP - TCP/IP communication protocol
  • SNA - SNA communication protocol
• taskId - the internal identity of the channel task that rejected the message
• type - the internal type of the channel task that rejected the message
• msgType - the type of the message. Valid values are:
  • INCOMING
  • OUTGOING
  • INTERNAL
• addrSpaceId - the internal identity of the address space of the Application

Corrective Action: Contact BMC Customer Support if the message persists.

ECAC66E CHANNEL(channelId.protocol) TASK(taskId.type) msgType MESSAGE REJECTED, CHANNEL DOES NOT SUPPORT APPLICATION(applCode)

Explanation: IOAGATE rejected the specified message because an invalid application was specified in the message.

The variables in this message are:

• channelId - the identity of the channel that rejected the message
• protocol - the current channel uses this protocolValid values are:
  • TCP - TCP/IP communication protocol
  • SNA - SNA communication protocol
• taskId - the internal identity of the channel task that rejected the message
• type - the internal type of the channel task that rejected the message
• msgType - the type of the messageValid values are:
  • INCOMING
  • OUTGOING
  • INTERNAL
• applCode - the application code

Corrective Action: Contact BMC Customer Support if the message persists.

ECAC67E CHANNEL(channelId.protocol) TASK(taskId.type) msgType MESSAGE REJECTED, APPL. SERVER(applServer) IS UNAVAILABLE

Explanation: IOAGATE rejected the specified message because the required application server was unavailable.

The variables in this message are:

• channelId - the identity of the channel that rejected the message
• protocol - the current channel uses this communication protocolValid values are:
  • TCP - TCP/IP communication protocol
  • SNA - SNA communication protocol
• taskId - the internal identity of the channel task that rejected the message
• type - the internal type of the channel task that rejected the message
• msgType - the type of the messageValid values are:
  • INCOMING
  • OUTGOING
  • INTERNAL
• applServer - the name of the unavailable application server

Corrective Action: Contact BMC Customer Support if the message persists.

ECAC68E CHANNEL(channelId.protocol) TASK(taskId.type) hshakeType HANDSHAKE(FROM=local_node_id TO=target_node_id) action

Explanation: IOAGATE is about to ignore or reject the specified handshake message for the reason indicated in the message that accompanies this ECAC68E message.

The variables in this message are:

• channelId - the identity of the channel that rejected the handshake
• protocol - the current channel uses this communication protocolValid values are:
  • TCP - TCP/IP communication protocol
  • SNA - SNA communication protocol
• taskId - the internal identity of the channel task that detected the problem
• type - the internal type of the channel task that detected the problem
• hshakeType - the type of the handshakeValid values are:
  • CONNECT
  • CONFIRM
  • REJECT
  • INFORM
  • UNKNOWN
• local_node_id - the identity of the local node in which the local IOAGATE is running
• target_node_id - the identity of the partner node in which the partner IOAGATE is running
• action - the action that IOAGATE is about to perform to the received handshake Valid values are:
  • TO BE REJECTED
  • RECEIVED
  • TO BE PRINTED

IOAGATE disconnects from the IOAGATE that sent this handshake message.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map. For more information on configuring the network map, see the INCONTROL for z/OS Installation Guide.

ECAC69I REASON: NO PARTNER NODE IN MAP(mapId) MATCHES SENDER NODE(node_id) IN HANDSHAKE

Explanation: This message follows the ECAC68E message, and specifies the exact reason for the handshake rejection, which is that the network map does not contain the node name obtained in the handshake message.

The variables in this message are:

• mapId - the identity of the network map
• node_id - the identity of the partner node in which the partner IOAGATE is running

IOAGATE disconnects from the IOAGATE that sent this handshake message.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map. For more information on configuring the network map, refer to the INCONTROL for z/OS Installation Guide.

ECAC6AI LOCAL NODE(local_node_id) OF CHANNEL(channel) DOES NOT MATCH TARGET NODE(target_node_id) OF HANDSHAKE

Explanation: The message follows the ECAC68E message, and specifies an exact reason for the handshake rejection, that is, the local node name does not match the target node name obtained in the handshake message.

The variables in this message are:

• local_node_id - the identity of the local node in which the local IOAGATE is running
• channel - the identity of the channel that detected the problem
• target_node_id - the identity of the partner node in which the partner IOAGATE is running

IOAGATE disconnects from the partner IOAGATE that sent this handshake message.

Corrective Action: Correct IOAGATE-to-IOAGATE connection configuration in the network map. For more information on configuring the network map, see the INCONTROL for z/OS Installation Guide.

ECAC6BI REASON: INVALID HANDSHAKE RECEIVED: rsn

Explanation: This message follows the ECAC68E message, and specifies an exact reason for the handshake rejection, which is that the handshake message has an illegal format.

In this message, rsn is the reason for the identification of the handshake as invalid. Valid values are:

• Bad HANDSHAKE ID
• Bad Type-Message
• Bad Type-Record
• Bad Product-ID
• Bad Software-Lvl

IOAGATE disconnects from the IOAGATE that sent the handshake message.

Corrective Action: Contact BMC Customer Support.

ECAC6CE CHANNEL(channelId.protocol) TASK(taskId.type) msgType MESSAGE REJECTED, INVALID SEQUENCE NUMBER(seqNumber)

Explanation: IOAGATE rejected the specified message due to an invalid sequence number in the message.

The variables in this message are:

• channelId - the identity of the channel that rejected the message
• protocol - the current channel uses this communication protocolValid values are:
  • TCP - TCP/IP communication protocol
  • SNA - SNA communication protocol
• taskId - the internal identity of the channel task that rejected the message
• type - the internal type of the channel task that rejected the message
• msgType - the type of the messageValid values are:
  • INCOMING
  • OUTGOING
  • INTERNAL
• seqNumber - the invalid sequence number that appears in the message

Corrective Action: If the message persists, contact BMC Customer Support.

ECAC6DE CHANNEL(channelId.protocol) TASK(taskId.type) ALLOCATED SIB NOT FOUND FOR msgType.reqType MESSAGE

Explanation: IOAGATE encountered an internal problem. It was unable to find the SIB (Service Instance Block) control block for the current transaction although this SIB must exist.

The variables in this message are:

• channelId - the identity of the channel that detected the problem
• protocol - the current channel uses this communication protocol. Valid values are:
  • TCP - TCP/IP communication protocol
  • SNA - SNA communication protocol
• taskId - the internal identity of the channel task that detected the problem
• type - the internal type of the channel task that detected the problem
• msgType - the type of the message. Valid values are:
  • INCOMING
  • OUTGOING
  • INTERNAL
• reqType - the type of the request This variable may not appear.Valid values are:
  • NOTIFY
  • STOP
  • CANCEL
  • MODIFY
  • INIT
  • ATTACH

Corrective Action: If the message persists, contact BMC Customer Support.

ECAC6EE CHANNEL(channelId.protocol) TASK(taskId.type) msgType MESSAGE REJECTED, INVALID SERVICE ID (serviceId)

Explanation: IOAGATE rejected the specified message due to an invalid service identity (or transaction code) in the message.

The variables in this message are:

• channelId - the identity of the channel that rejected the message
• protocol - the current channel uses this communication protocol. Valid values are:
  • TCP - TCP/IP communication protocol
  • SNA - SNA communication protocol
• taskId - the internal identity of the channel task that detected the problem
• type - the internal type of the channel task that detected the problem
• msgType - the type of the message. Valid values are:
  • INCOMING
  • OUTGOING
  • INTERNAL
• serviceId - the transaction code

Corrective Action: If the message persists, contact BMC Customer Support.

ECAC6FE CHANNEL(channelId.protocol) TASK(taskId.type) msgType MESSAGE REJECTED, INVALID ADDR.SPACE ID(addrSpaceId)

Explanation: IOAGATE rejected the specified message because there was an invalid address space internal ID in the message.

The variables in this message are:

• channelId - the identity of the channel that rejected the message
• protocol - the current channel uses this communication protoco. lValid values are:
  • TCP - TCP/IP communication protocol
  • SNA - SNA communication protocol
• taskId - the internal identity of the channel task that rejected the message
• type - the internal type of the channel task that rejected the message
• msgType - the type of the message. Valid values are:
  • INCOMING
  • OUTGOING
  • INTERNAL
• addrSpaceId - the internal identity of the application address space

Corrective Action: If the message persists, contact BMC Customer Support.

ECAC6GE CHANNEL(channelId.protocol) TASK(taskId.type) msgType MESSAGE REJECTED, SERVICE(serviceId) DISABLED

Explanation: IOAGATE rejected the specified message because the service indicated by the service_ id transaction code was disabled by IOAGATE.

The variables in this message are:

• channelId - the identity of the channel that rejected the message
• protocol - the current channel uses this communication protocol. Valid values are:
  • TCP - TCP/IP communication protocol
  • SNA - SNA communication protocol
• taskId - the internal identity of the channel task that rejected the message
• type - the internal type of the channel task that rejected the message
• msgType - the type of the message. Valid values are:
  • INCOMING
  • OUTGOING
  • INTERNAL
• serviceId - the code of a transaction to be performed by IOAGATE

Corrective Action: If the message persists, contact BMC Customer Support.

ECAC6HE CHANNEL(channelId.protocol) TASK(taskId.type) msgType EXTENDED MESSAGE REJECTED, INVALID APPLICATION(appl)

Explanation: IOAGATE rejected the specified extended message due to an invalid application code specified in the message. An extended message format is used in IOAGATE-to-IOAGATE communication.

The variables in this message are:

• channelId - the identity of the channel that rejected the message
• protocol - the current channel uses this communication protocol. Valid values are:
  • TCP - TCP/IP communication protocol
  • SNA - SNA communication protocol
• taskId - the internal identity of the channel task that rejected the message
• type - the internal type of the channel task that rejected the message
• msgType - the type of the message. Valid values are:
  • INCOMING
  • OUTGOING
  • INTERNAL
• appl - the invalid application code

Corrective Action: If the message persists, contact BMC Customer Support.

ECAC6IE CHANNEL(channelId.protocol) TASK(taskId.type) msgType MESSAGE REJECTED, INVALID APPLICATION CODE(appl)

Explanation: IOAGATE rejected the specified message due to an invalid application code specified in the message.

The variables in this message are:

• channelId - the identity of the channel that rejected the message
• protocol - the current channel uses this communication protocol. Valid values are:
  • TCP - TCP/IP communication protocol
  • SNA - SNA communication protocol
• taskId - the internal identity of the channel task that rejected the message
• type - the internal type of the channel task that rejected the message
• msgType - the type of the message. Valid values are:
  • INCOMING
  • OUTGOING
  • INTERNAL
• appl - the invalid application code

Corrective Action: If the message persists, contact BMC Customer Support.

ECAC6JI REASON: LOCAL NODE(local_node_id) ALREADY CONNECTED TO PARTNER(partner_node_id)

Explanation: This message follows the ECAC68E message and specifies an exact reason for the handshake rejection. The reason is that the local IOAGATE received a handshake message from the partner IOAGATE, but connection between these IOAGATEs had been already established. This may happen when both IOAGATEs are configured with the CONNECTOR parameter set to LOCAL and the local IOAGATE had already succeeded in initiating and establishing the connection.

The variables in this message are:

• local_node_id - the identity of the local node in which the local IOAGATE is running
• partner_node_id - the identity of the partner node in which the partner IOAGATE is running

Corrective Action: No action is required.

ECAC6KI REASON: LOCAL NODE(local_node_id) IS CONNECTING TO PARTNER(partner_node_id)

Explanation: This message follows the ECAC68E message and specifies an exact reason for the handshake rejection. The reason is that both IOAGATEs are configured with the CONNECTOR parameter set to LOCAL and the local IOAGATE is not able to accept a handshake because it has been connecting to the specified Partner node.

The variables in this message are

• local_node_id - the identity of the local node in which the local IOAGATE is running
• partner_node_id - the identity of the partner node in which the partner IOAGATE is running

IOAGATE ignores the handshake message.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map. For more information on configuring the network map, see the INCONTROL for z/OS Installation Guide.

ECAC6LI REJECTION NOTICE (msgId) RECEIVED FROM PARTNER(partnerId):

Explanation: A diagnostic message has been received from the partnerId partner IOAGATE.

This ECAC6LI message is followed by the ECAC6QI message, which displays the diagnostic message that was received.

The variables in this message are:

• msgId - the identity of the diagnostic message
• partnerId - the identity of the partner IOAGATE

Corrective Action: No action is required.

ECAC6ME CHANNEL(channelId.protocol) TASK(taskId.type) GET-IOAGATE-ID REQUEST REJECTED, rsn

Explanation: The message indicates that either IOAGATE received an invalid GET-IOAGATE-ID request from a client or IOAGATE failed to create a response to this request.

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
• type - the internal type of the channel task that detected the problem
• rsn - the reason for the rejection of the request. Valid values for rsn are:
  • Failure to set the IP address/Hostname
  • Invalid request received

Processing continues. The client that sent the invalid request has been disconnected.

Corrective Action: If the message persists, contact BMC Customer Support.

ECAC6NE CHANNEL(channelId.TCP) TASK(taskId.type) CHECKSUM ENCRYPTION REQUEST REJECTED, rsn

Explanation: The message indicates that IOAGATE rejected a checksum encryption request from a client for the reason rsn.

The variables in this message are:

• channelId - the identity of the channel that rejected the request
• taskId - the internal identity of the channel task that rejected the request
• type - the internal type of the channel task that rejected the request
• rsn - the reason for the rejection of the requestValid values for rsn are:
  • Invalid CheckSum request
  • Encryption not configured
  • Encryption disabled
  • No Encryption processor
  • No CheckSum prepared
  • Invalid CheckSum arrived
  • Invalid algorithm given
  • Channel is not eligible

Processing continues. The client that sent the request has disconnected.

Corrective Action: Do the following:

1. Ensure that IOAGATE and the client use the same file of encryption keys.
2. Examine the JES log, DAIGLOG, and DATRACE outputs from IOAGATE for additional error indications and try to correct the problem.
3. If the message persists, contact BMC Customer Support.

ECAC6OE CHANNEL(channelId.TCP) TASK(taskId.type) INCOMING MESSAGE REJECTED, rsn.

Explanation: IOAGATE rejected an incoming message from a client for the reason rsn.

The variables in this message are:

• channelId - the identity of the channel that rejected the message
• taskId - the internal identity of the channel task that rejected the message
• type - the internal type of the channel task that rejected the message
• rsn - the reason for the rejection of the messageValid values for rsn are:
  • Message must be encrypted
  • Encryption not configured
  • Encryption disabled

Processing continues. The client that sent the message has disconnected.

Corrective Action: Do the following:

1. Ensure that IOAGATE and the client use the same file of encryption keys.
2. Examine the JES Log, DAIGLOG, and DATRACE outputs from IOAGATE for further information about the error and take appropriate corrective action.
3. If the message persists, contact BMC Customer Support.

ECAC6PI REASON NOTICE (msgId) RECEIVED FROM PARTNER(partnerId):

Explanation: The message indicates that a diagnostic message has come from the partner IOAGATE.

This ECAC6PI message is followed by the ECAC6QI message that displays the diagnostic message itself.

The variables in this message are:

• msgId - the identity of the diagnostic message
• partnerId - identity of the partner IOAGATE

Corrective Action: No action is required.

ECAC6QI diagMsg

Explanation: This information message follows messages ECAC6LI and ECAC6PI, and displays the diagnostic message that arrived from the partner IOAGATE that issued it.

In this message, diagMsg is the text of the diagnostic message that arrived from the partner IOAGATE.

Corrective Action: No action is required.

ECAC70I PROBABLE LOGMODE DEFINITIONS ERROR

Explanation: This information message indicates that the probable cause of the error reported in the preceding message is that an IOAGATE attempted to connect to a partner IOAGATE over the multiple connection (MC) SNA communication channel. However, the LOGMODE definitions of the partners probably do not match.

When two IOAGATEs attempt to connect, both send their LOGMODE parameters during the BIND process. If these parameters do not match, connection fails.

The ECAG89W, ECAG90E, or ECAG95E message, which precedes this message, provides more details about the error.

The ECAC70I message is issued for a multiple connection (MC) SNA communication channel only.

Connection between IOAGATEs fails.

Corrective Action: Check the LOGMODE definition for each partner in the appropriate SYS1.VTAMLST library. Ensure they are defined according to instructions in the appropriate step of the Control-O chapter of the INCONTROL for z/OS Installation Guide, and restart the IOAGATE.

ECAC71I PROBABLE ALLOCATION FAILURE NO RETRY

Explanation: This information message indicates that the probable cause of the connection failure reported in the preceding message is that a local IOAGATE attempted to connect to a partner IOAGATE over the multiple connection (MC) SNA communication channel, and perform a VTAM LU 6.2 allocation request. It also indicates that no attempt will be made to connect again.

The ECAG89W, ECAG90E, or ECAG95E message, which precedes this message, provides more details about the error.

The ECAC70I message is issued for a multiple connection (MC) SNA communication channel only.

Corrective Action: Check that the partner Gateway LU is active in VTAM and that it is defined according to instructions in the appropriate step in the Control-O chapter of the INCONTROL for z/OS Installation Guide. Then restart the IOAGATE. If the problem persists, call your system programmer for assistance.

ECAC72I PROBABLE ALLOCATION FAILURE RETRY

Explanation: This information message indicates that the probable cause of the connection failure reported in the preceding message is that a local IOAGATE attempted to establish a connection with a partner IOAGATE over the multiple connection (MC) SNA communication channel and performed a VTAM LU 6.2 allocation request. It also indicates that an attempt will be made to connect again.

The ECAG89W, ECAG90E, or ECAG95E message, which precedes this message, provides more details about the error.

The ECAC70I message is issued for a multiple connection (MC) SNA communication channel only.

Processing continues. Connection is retried after one minute.

Corrective Action: Ensure that the partner Gateway LU is active in VTAM and that it is defined according to instructions in the appropriate step in the Control-O chapter of the INCONTROL for z/OS Installation Guide. Then restart the IOAGATE. If the problem persists, call your system programmer for assistance.

ECAC73I PROBABLE MISMATCH IN VTAM DEFINITIONS

Explanation: This information message indicates that the probable cause of the connection failure reported in the preceding message, is that there is a mismatch in the IOAGATE LU definitions. An IOAGATE attempted to establish connection with a partner IOAGATE over the multiple connection (MC) SNA communication channel. However, the VTAM 6.2 LU is defined incorrectly.

The ECAG89W, ECAG90E, or ECAG95E message, which precedes this message, provides more details about the error.

The ECAC70I message is issued for a multiple connection (MC) SNA communication channel only.

The multiple connection SNA channel shuts down. Processing continues.

Corrective Action: Define the IOAGATE VTAM 6.2 LU according to instructions in the appropriate step in the Control-O chapter of the INCONTROL for z/OS Installation Guide. Then restart the IOAGATE.