Messages ECAP00 through ECAPxx

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

ECAP01S READING FAILED WITH RC(rc) REASON(rsn)

Explanation: An attempt to process a network map specified in the ECAPARM configuration file failed.

The message ECAP0XE precedes this message, and identifies the problematic network map.

If a network map is specified in the ECAPARM configuration file, IOAGATE reads the map during initialization, and builds internal tables of connections in the main storage. The same network map is processed by a Control-O monitor and by each Control-O application server that participates in the communication described by this network map. To get the name of the network map, the Control-O monitor loads the same ECAPARM configuration file.

The variables in this message are:

rc - the return code

Valid values for rc are:

Return Code	Explanation
12	Member not found
16	Data set is not a library
24	LRECL is not 80
28	Data set in use
36	Data set not in the catalog
56	STAE detected an abend

rsn - the system failure reason code

IOAGATE disables the Control-O application defined in the network map definitions, and processing continues.

Corrective Action: Correct the problem indicated by the reason code rsn, and restart IOAGATE.

ECAP02E LUNAME= VALUE LONGER THAN 8 CHARACTERS

Explanation: The LUNAME parameter value in the specified line in the specified network map in the ECAPARM configuration file is too long.

If a network map is specified in the ECAPARM configuration file, IOAGATE reads the map during initialization and builds internal tables of connections in the main storage. The same network map is processed by a Control-O monitor and by each Control-O application server that participates in the communication described by this network map. To get the name of the network map, the Control-O monitor loads the same ECAPARM configuration file.

IOAGATE discards the line containing the problem, and processing continues. If the line is a part of a PARTNER statement that defines a connection for the current IOAGATE, processing of the map fails, and the application linked to the channel with this map is disabled.

Corrective Action: Change the value of LUNAME so that it complies with VTAM naming conventions, and restart IOAGATE.

ECAP03E NON-ALPHANUMERIC CHARACTER IN LUNAME= VALUE

Explanation: The LUNAME parameter value in the specified line in the specified network map in the ECAPARM configuration file contains a character that is not alphanumeric.

If a network map is specified in the ECAPARM configuration file, IOAGATE reads the map during initialization and builds internal tables of connections in the main storage. The same network map is processed by a Control-O monitor and by each Control-O application server that participates in the communication described by this network map. To get the network map name, the Control-O monitor loads the same ECAPARM configuration file.

Corrective Action: Change the value of LUNAME so that it complies with VTAM naming conventions, and restart IOAGATE.

ECAP04E INVALID FIRST CHARACTER IN LUNAME= VALUE

Explanation: The first character of the LUNAME parameter value in the specified line in the specified network map in the ECAPARM configuration file is invalid.

If a network map is specified in the ECAPARM configuration file, IOAGATE reads the map during initialization and builds internal tables of connections in the main storage. The same network map is processed by a Control-O monitor and by each Control-O application server that participates in the communication described by this network map. To get the network map name, the Control-O monitor loads the same ECAPARM configuration file.

Corrective Action: Change the value of LUNAME so that it complies with VTAM naming conventions, and restart IOAGATE.

ECAP05W THE STATEMENT IS OUT OF PLACE

Explanation: An invalid order of statements was discovered in the network map.

IOAGATE disables the channel that uses the indicated network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map, and restart IOAGATE.

ECAP06E port / host = REQUIRED IN TCP PARTNER IF CONNECTOR=LOCAL SPECIFIED

Explanation: Either the PORT or the HOST parameter in the TCP partner statement of the network map must be specified if the CONNECTOR parameter in that TCP partner is set to LOCAL.

IOAGATE disables the channel that uses the indicated network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map, and restart IOAGATE.

ECAP07E MAP DOES NOT BEGIN WITH LOCAL STATEMENT

Explanation: The network map must begin with a LOCAL statement.

IOAGATE disables the channel that uses the indicated network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map, and restart IOAGATE.

ECAP08W UNRECOGNIZED STATEMENT (stmt)

Explanation: The network map statement stmt was not recognized as valid.

IOAGATE disables the channel that uses the indicated network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map, and restart IOAGATE.

ECAP09E INVALID stmt STATEMENT

Explanation: The invalid statement stmt was discovered in the network map.

IOAGATE disables the channel that uses the indicated network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map, and restart IOAGATE.

ECAP0AW IMPROPER PARAMETER IN THE LOCAL STATEMENT

Explanation: An invalid parameter was discovered in the LOCAL statement of the network map.

IOAGATE disables the channel that uses the indicated network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map and restart IOAGATE.

ECAP0CE INVALID IP ADDRESS SPECIFIED IN HOST= PARAMETER

Explanation: An invalid IP address value was discovered in the HOST parameter of the network map.

IOAGATE changes the CONNECTOR value from LOCAL to PARTNER, and tries to continue processing the network map.

Corrective Action: Correct the IP address.

ECAP0DE NON-DIGIT CHARACTER IN PORT= PARAMETER

Explanation: A non-digit character was discovered in the PORT parameter of the network map.

IOAGATE changes the CONNECTOR value from LOCAL to PARTNER, and tries to continue processing the network map.

Corrective Action: Correct the PORT value.

ECAP0EE PORT= VALUE GREATER THAN 65534

Explanation: An invalid PORT parameter value was discovered.

The PORT parameter value must be in the range from 1024 through 65534.

IOAGATE changes the CONNECTOR value from LOCAL to PARTNER and tries to continue processing the network map.

Corrective Action: Correct the PORT value.

ECAP0FS NO LINE FOUND

Explanation: The network map is not valid because it contained no line.

IOAGATE disables the channel that uses the network map identified in the ECAP0XI message that precedes the ECAP0FS message.

Corrective Action: Specify the correct network map member.

ECAP0GE PORT= VALUE LESS THAN 1024

Explanation: The value of the PORT parameter is invalid. The value of the PORT parameter must be in the range from 1024 through 65534.

IOAGATE changes the CONNECTOR value from LOCAL to PARTNER, and tries to continue processing the network map.

Corrective Action: Correct the PORT value.

ECAP0HW NO VALUE SPECIFIED IN THE PORT= PARAMETER

Explanation: The PORT parameter has no value specified.

IOAGATE changes the CONNECTOR value from LOCAL to PARTNER, and tries to continue processing the network map.

Corrective Action: Set a value for the PORT parameter.

ECAP0IE LACK OF REQUIRED PARAMETERS IN protocol PARTNER STATEMENT

Explanation: Some required parameters were not found in the Partner statement of the network map.

In this message, protocol is the communication protocol to be used by the channel to which the network map is defined (the partner statement).

Valid values are:

TCP - the partner statement uses the network map defined in TCP channel
SNA - the partner statement uses to the network map defined in SNA channel

IOAGATE disables the channel that uses the indicated network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map and restart IOAGATE.

ECAP0KE INVALID APPL= PARAMETER SPECIFIED

Explanation: An invalid APPL parameter value was discovered in the SNA partner of the network map.

IOAGATE disables the channel that uses the indicated network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map and restart IOAGATE.

ECAP0LE NODE= PARAMETER REQUIRED IN THE PARTNER STATEMENT

Explanation: No NODE parameter was found in the PARTNER statement. The NODE parameter must be defined in the PARTNER statement of the network map.

IOAGATE disables the channel that uses the indicated network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map and restart IOAGATE.

ECAP0ME NO LOCAL STATEMENT REFERS TO THE CHANNEL NODE(node)

Explanation: The network map must have a LOCAL statement with a NODE parameter that matches the NODE value from the appropriate CHANNEL declaration.

In this message, node is the value of the NODE parameter in the CHANNEL declaration referring to the network map that is being analyzed.

IOAGATE disables the channel that uses the indicated network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map and restart IOAGATE.

ECAP0OW CONNECTOR=LOCAL ALTERED TO CONNECTOR=PARTNER

Explanation: This warning message is displayed by IOAGATE when the CONNECTOR value has changed from LOCAL to PARTNER.

IOAGATE tries to continue processing the network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map and restart IOAGATE.

ECAP0PW INVALID CONNECTOR= VALUE SPECIFIED, SET TO CONNECTOR=PARTNER

Explanation: The value of the CONNECTOR parameter is invalid.

IOAGATE changes the CONNECTOR value from LOCAL to PARTNER, and tries to continue processing the network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map and restart IOAGATE.

ECAP0QW INVALID LINE DROPPED

Explanation: IOAGATE could neither recognize the indicated line, nor detect any specific error in the line.

The line is ignored.

Corrective Action: Correct the network map and restart IOAGATE.

ECAP0RE LUNAME= SPECIFIED FOR TCP CHANNEL

Explanation: The SNA parameter LUNAME has been specified for a TCP channel.

IOAGATE disables the channel that uses the indicated network map, and tries to continue processing the network map.

Corrective Action: Correct the network map and restart IOAGATE.

ECAP0SE parm = PARAMETER IS INVALID FOR SNA CHANNEL

Explanation: The TCP parameter parm has been specified for a SNA channel.

IOAGATE disables the channel that uses the indicated network map, and tries to continue processing the network map.

Corrective Action: Correct the network map and restart IOAGATE.

ECAP0TS INTERNAL ERROR OCCURRED WHEN DISABLING parm/stmt

Explanation: A severe internal error occurred when IOAGATE tried to disable the parm parameter or the stmt statement.

In this message, parm/stmt is the parameter or statement that IOAGATE tried to disable.

This message is only issued when IOAGATE is configured for IOAGATE-to-IOAGATE communication.

IOAGATE disables the channel that uses the indicated network map, and tries to continue processing the network map.

Corrective Action: Contact BMC Customer Support.

ECAP0WE DUPLICATE NODE= SPECIFIED

Explanation: The same NODE parameter value has been entered twice.

This message is only issued when IOAGATE is configured for IOAGATE-to-IOAGATE communication.

IOAGATE disables the channel that uses the indicated network map and tries to continue processing the network map.

Corrective Action: Correct the network map and restart IOAGATE.

ECAP0XI ERROR DETECTED, MAP(mapId-channelId.protocol), LINE=lineNum :

Explanation: This message is a header message, and is followed by another message that describes precisely an error discovered in line lineNum.

The variables in this message are:

mapId - the identity of the network map in which IOAGATE discovered the error
channelId - the identity of the channel that uses the indicated network map
protocol - the current channel uses this communication protocol Valid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
lineNum - sequential number of the line in which IOAGATE discovered the error

Corrective Action: Correct the network map and restart IOAGATE.

ECAP0YE TCPVENDR PARAMETER MUST HAVE THE SAME VALUE IN ALL CHANNELS

Explanation: An error occurred while IOAGATE was checking ECAPARM. The TCPVENDR parameter in the channels defined in ECAPARM had different values.

IOAGATE goes down.

Corrective Action: Ensure that the TCPVENDR parameter has the same value in all channels of ECAPARM, then restart IOAGATE.

ECAP0ZE REQUESTED MAP NOT FOUND IN THE PARM LIBRARY

Explanation: IOAGATE failed to load the network map specified in the channel.

IOAGATE disables the channel that uses the indicated network map and tries to continue processing.

Corrective Action: Correct the name of the network map and restart IOAGATE.

ECAP10I IOAENV memName BUILT BY CCID(changeLevel) ON date is used

Explanation: This information message displays level information for the memName IOAENV parameters member used by IOAGATE in the current run.

The variables in this message are:

memName - the name of the parameters member Valid values are:
- ECAAPPL - table of supported applications
- ECAPDEF - table of defaults of numeric parameters
- ECASRVT - table of services (transactions)
changeLevel - the level of the change that was last applied to the indicated member
date - the date this member was last changed

Corrective Action: No action is required.

ECAP11S memName type PARAMETERS MEMBER UNAVAILABLE

Explanation: A severe error occurred when IOAGATE tried to load the specified IOAENV parameters member.

The variables in this message are:

memName - name of the parameters memberValid values are:
- ECAPARM - configuration file
- ECAAPPL - table of supported applications
- ECAPDEF - table of defaults of numeric parameters
- ECASRVT - table of services (transactions)
type - name of the parameters memberValid values are:
- SOURCE
- IOAENV

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP12S ECATMEM FAILED, rsn

Explanation: A severe internal error occurred when IOAGATE tried to verify an internal parameters member.

In this message, possible values for rsn are:

RC= return_code REASON= reason_code
INSUFFICIENT STORAGE
DDNAME NOT PROVIDED
MEMBER NAME NOT PROVIDED

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP13S memName type PARAMETERS MEMBER IS EMPTY

Explanation: A severe internal error occurred when IOAGATE tried to read the indicated IOAENV parameters member.

The variables in this message are:

memName - name of the parameters memberValid values are:
- ECAPARM - configuration file
- ECAAPPL - table of supported applications
- ECAPDEF - table of defaults of numeric parameters
- ECASRVT - table of services (transactions)
type - Name of the parameters member Valid values are:
- SOURCE
- IOAENV

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP16W NO IOAGATE-TO-IOAGATE CONNECTION WAS DEFINED

Explanation: The F IOAGATE,MAP modify command was issued, to display a network map, but failed because no IOAGATE-to-IOAGATE connection was configured in the current run of the local IOAGATE.

If a network map is specified in the ECAPARM configuration file, IOAGATE reads the map during initialization and builds internal tables of connections in the main storage. The NETWMAP parameter was not specified in the ECAPARM configuration file, or the multiple connection SNA channel was either disabled or not configured to function with a network map.

The F IOAGATE,MAP modify command is ignored. Normal processing continues.

Corrective Action: No action is required.

ECAP17E MAP(mapId -channelId.protocol) PROCESSING FAILED, RC(rc)

Explanation: An error was encountered in the network map identified by the variables in this message.

The variables in this message are:

mapId - the name of a member in the IOA PARM library that describes a map of network connections between IOAGATEs that allows one IOAGATE to communicate with another over a multiple connection (MC) channel
channelId - the identity of the channel that uses the network map mapId
protocol - the communication protocol used by the current channel Valid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
rc - the return code

Valid values for rc are:

Return Code	Explanation
8	"Disable map" error encountered
12	"Stop processing" error encountered

IOAGATE disables the channel that uses the indicated network map, and tries to continue processing.

Corrective Action: Correct the network map and restart IOAGATE.

ECAP18W NETWORK MAP(mapId) HAS BEEN PROCESSED WITH RC(rc)

Explanation: The network map mapId of IOAGATE connections was processed with a nonzero reason code (rc).

The variables in this message are:

mapId - the name of the member in the IOA PARM library that determines the map of IOAGATE connections, and enables one IOAGATE to communicate with another over a multiple connection (MC) channel
rc - the return code

Valid values for rc are:

Return Code	Explanation
04	Minor errors were detected in the map, or errors were detected that do not relate to a PARTNER statement describing the connections of the current IOAGATE. The network map is enabled.
12	severe errors were detected in the network map. Processing of the map failed.

Corrective Action: Do the following:

Check any error messages that precede this one.
Check the network map.
Correct the ECAPARM configuration file.
Restart IOAGATE.

ECAP19I NETWORK MAP(mapId) HAS BEEN PROCESSED SUCCESSFULLY

Explanation: This information message indicates that the mapId network map of IOAGATE connections was successfully processed.

To get the name of the network map, the Control-O monitor loads the same ECAPARM configuration file.

In this message, mapId identifies the member in the IOA PARM library that determines the map of IOAGATE connections, and enables one IOAGATE to communicate with another over a multiple connection (MC) channel.

Corrective Action: No action is required.

ECAP1AW NETWORK MAP(mapName) WAS SPECIFIED BUT NOT PROCESSED

Explanation: The network map mapName that is specified in the ECAPARM configuration file by the NETWMAP parameter has not been processed.

Other messages may clarify why the map has not been processed.

The Control-O monitor continues its startup, but without communication services through IOAGATE.

Corrective Action: If possible, determine from other messages why the map has not been processed. Correct the problem and restart IOAGATE and Control-O.

ECAP1BW NETWORK MAP (OR NODE) WAS NOT SPECIFIED IN ECAPARM(suffix)

Explanation: The ECAPARM configuration file with suffix suffix has been defined for Control-O, but either the NETWMAP (network map name) parameter or the NODE parameter or both have not been specified in this ECAPARM file.

The Control-O monitor continues its startup but without communication services through IOAGATE

Corrective Action: Specify both parameters, and restart IOAGATE and Control-O.

ECAP1XE DUPLICATE NODE nodeId DETECTED IN CHANNEL(channelId), CHANNEL DISABLED

Explanation: A duplicate node has been detected in the channelId channel, and IOAGATE has disabled that channel.

The variables in this message are:

nodeId - the identity of the node that is duplicated
channelId - the identity of the problematic channel

IOAGATE disables the channel that uses the indicated network map, and tries to continue processing.

Corrective Action: Correct the problem, using the diagnostics issued by the message, and restart IOAGATE.

ECAP20I IOAGATE-TO-IOAGATE CONNECTIONS NODE=node MAP=mapId APPL=CONTROL-O

Explanation: This message is the response to the F IOAGATE,MAP modify command, and is the header for ECAP22I messages.

The variables in this message are:

node - the identity of the current local node for which IOAGATE-to-IOAGATE connections are displayed
mapId - the name of the member in the IOA PARM library that determines the map of IOAGATE connections, and enables one IOAGATE to communicate with another over a multiple connection (MC) channel

Corrective Action: No action is required.

ECAP21I CHAN LUNAME LOGMODE PARTNER CONVERSATION ID STATUS

Explanation: This information message follows an ECAP20I message, which identifies the current local node, and is a header for ECAP22I messages, which specify the SNA connections that are available for the current local node.

The ECAP23I and ECAP24I messages may also follow.

This group of messages is displayed as a result of an F IOAGATE,MAP command.

Corrective Action: No action is required.

ECAP22I channelId luName logmode partner_id conversation_id status

Explanation: This information message specifies one of the available SNA IOAGATE-to-IOAGATE connections for the current local IOAGATE, using the network map specified in the last ECAP20I message. The ECAP20I message precedes and acts as a header for a single ECAP22I message, or a group of ECAP22I messages.

If a network map was specified in the ECAPARM configuration file, IOAGATE reads the map during initialization and builds internal tables of connections in the main storage. The same network map is processed by a Control-O monitor and by each Control-O application server that participates in the communication described by this map.

The variables in this message are:

channelId - the identity of the channel that controls the connection
luName - the Logical Unit name of the partner IOAGATE
logmode - the LOGMODE used by this connection
partner_id - the conversation ID of the outgoing conversation
conversation_id - the conversation identity of the incoming conversation
status - Status of the connection Valid values are:
- NOTALLOC - the conversation is not allocated.
- ALLOCTED - the conversation is allocated.
- ALLOCSND - the Send channel is allocated.
- ALLOCRCV - the Receive channel is allocated.

Corrective Action: No action is required.

ECAP23I CHAN TASK PARTNER PORT CONNECTOR STATUS SOCKET HOST

Explanation: This information message is a response to the F IOAGATE,CHAN modify command. It follows an ECAP20I message, which identifies the current local node, and is a header for ECAP24I messages, which identify the available TCP connections for the current local node.

Corrective Action: No action is required.

ECAP24I channelId taskId partner port connector status socket host

Explanation: This information message specifies one of the available TCP/IP connections for the current local IOAGATE using the network map specified in the last ECAP20I message. The ECAP23I message precedes and acts as a header for a single ECAP24I message, or a group of ECAP24I messages.

The variables in this message are:

channelId - the identity of the channel that controls this TCP/IP connection
taskId - the identity of the communication task of the channel that controls this TCP/IP connection
partner - the identity of the node on which the partner IOAGATE is running
port - the TCP/IP port number used to connect to the partner IOAGATE
connector - the mode of the current local IOAGATE specified by the CONNECTOR parameter in a network map. Valid values are:
- LOCAL - the current IOAGATE is an initiator of the connection to the partner IOAGATE, that is, CONNECTOR is set to LOCAL
- PARTNER - the current IOAGATE is not an initiator of the connection to the partner IOAGATE, that is, CONNECTOR is set to PARTNERThe current IOAGATE can accept connection from its partner IOAGATE.
status - Status of the connection. Valid values are:
- HNDSHAKE RCVD - A handshake message has been received.
- HNDSHAKE SENT - A handshake message has been sent.
- CONNECTED - A connection was successfully established with the partner IOAGATE.
- TAKING SOCKET - The connection is being taken by the recipient communication task.
- CONNECTED/TAKE - Connection has been established. The taking-socket process is about to be completed.
- GIVING SOCKET - Connection is being giving by the Listener task of the channel to the recipient communication task.
- CONNECTED/GIVE - Connection has been established. The giving-socket process is about to begin.
- GIVE REQUIRED - Connection has been established. The giving-socket process is being requested.
- GIVE FAILED - Connection has been established. The giving-socket process failed.
- H-SHAKE FAILED - The handshaking process has failed.
- RETRYING - The attempt to connect to the partner IOAGATE failed. Another attempt will be made in the time interval specified in the ALLOCINT parameter in the ECAPARM configuration file.
- CONNECTION IN PROGRESS - A Connect action has been initiated.
- CONNECTING - The Connect action is being processed.
- DISABLED - The IOAGATE-to-IOAGATE connection entry is disabled
- READY TO CONNECT - The local IOAGATE is ready to begin a Connect action.
- WAITING FOR CONNECTION - The local IOAGATE is ready to accept connection from its partner IOAGATE.
- DISCONNECTED - The connection to the partner IOAGATE has been disrupted.
- RECONNECTED - The connection has been re-established.
socket - the TCP/IP socket number assigned to connect (CONNECT is set to YES), or to be connected (CONNECT is set to NO) to the partner IOAGATE
host - The host name or IP address of the partner IOAGATE This data exactly reflects the specification in the network map.

Corrective Action: No action is required.

ECAP30E APSERVER ENTRY(entryId), INVALID ALIAS APPLICATION CODE(applicId) SPECIFIED, ALIAS DISABLED

Explanation: An invalid application code was specified as an alias in the APPL=(,) parameter of an APSERVER definition.

The same ECAPARM configuration file is processed by IOAGATE and by each application server that communicates with this IOAGATE. The APPL parameter of an APSERVER statement can be used to specify a list of alias codes. Each alias code specifies an application that can be served by the same application server as the others in the list, concurrently with the main application.

The variables in this message are:

entryId - a sequential number that identifies the APSERVER definition entry in the ECAPARM configuration file
applicId - the invalid application code that was specified as an alias

The specified alias application code is ignored, and processing continues.

Corrective Action: Check the ECAPARM configuration file, correct the file, and restart IOAGATE.

ECAP31E ECAPRM INTERNAL ERROR, APPLICATION ALIASES PROCESSING FAILED

Explanation: An internal error occurred during the processing of application aliases specified in an APPL parameter of an APSERVER statement.

Corrective Action: Contact BMC Customer Support.

ECAP32E NO RAW APSERVER ENTRIES FOUND

Explanation: An internal error occurred when IOAGATE was processing the ECAPARM configuration file. No APSERVER entry was found in the ECAPARM configuration file.

During initialization, IOAGATE reads and verifies the definitions specified in the ECAPARM configuration file. The same ECAPARM configuration file is processed by IOAGATE and by each application server that communicates with this IOAGATE.

IOAGATE shuts down.

Corrective Action: Correct the ECAPARM configuration file, and restart IOAGATE. If the problem persists, contact BMC Customer Support.

ECAP33S ECAPRM INTERNAL ERROR WORK AREA, SIZE(size) EXCEEDED ALLOWED MAXIMUM 64K

Explanation: A severe internal error occurred during checking of the ECAPARM configuration file. The size of the internal work area is invalid.

In this message, size is the size of the internal work area that exceeded the maximum.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP34E PARAMETER ARMELEM=arm_element_id INVALID, IMPROPER CHARACTER(chara) SPECIFIED

Explanation: While processing the ECAPARM configuration file, an invalid character was detected in the ARMELEM parameter.

The variables in this message are:

arm_element_id - the IOAGATE automatic restart management (ARM) element name
chara - the invalid character detected in the IOAGATE ARM element

The ARMELEM parameter is ignored. Normal processing continues.

Corrective Action: Using the diagnostics issued by the message, correct the problem, and restart IOAGATE.

ECAP35S ECAPRM INTERNAL ERROR, APSERVER ENTRY(entryId), SERVER= VALUE NOT SPECIFIED

Explanation: A severe internal error occurred in the ECAPARM configuration file because no value was specified for the SERVER parameter in the APSERVER definition.

In this message, entryId is a sequential number that identifies the APSERVER definition entry in the ECAPARM configuration file.

The specified APSERVER definition is disabled, and processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP37E MORE THAN 99 APPLICATION SERVERS DEFINED

Explanation: The number of APSERVER statements specified in the ECAPARM configuration file exceeds the maximum permitted. A maximum of 99 APSERVER statements may be specified in the ECAPARM configuration file.

During initialization, IOAGATE reads and verifies definitions specified in the ECAPARM configuration file. The same ECAPARM configuration file is processed by IOAGATE and by each application server that communicates with this IOAGATE.

IOAGATE shuts down.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP38E APSERVER ENTRY(entryId), UNKNOWN APPL(value) SPECIFIED, SERVER DISABLED

Explanation: An invalid application name was specified in an APPL parameter of an APSERVER definition in the ECAPARM configuration file. During initialization, IOAGATE reads and verifies definitions specified in the ECAPARM configuration file. The same ECAPARM configuration file is processed by IOAGATE and by each application server that communicates with this IOAGATE.

The variables in this message are:

entryId - the sequential number that identifies the APSERVER definition entry in the ECAPARM configuration file
value - the value specified by the user in the APPL parameter

The identified APSERVER definition entryId is ignored. Processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP39W CHANNEL(entryId), MAXIMUM NUMBER OF SERVERs PER CHANNEL(channelId) REACHED, APSERVER(server_id) DISABLED

Explanation: The number of APSERVER definitions linked to the identified channel exceeded the maximum number allowed, namely eight.

The variables in this message are:

entryId - the sequential number that identifies the CHANNEL definition entry in the ECAPARM configuration file
channelId - the identity of the channel to which the problematic APSERVER is linked
server_id - the identity of the problematic APSERVER

The identified APSERVER definition is disabled. Processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP3AE TOTAL NUMBER OF APPLICATION SERVER TASKS CANNOT EXCEED 500

Explanation: An internal error occurred because the number of application server tasks defined in the ECAPARM configuration file exceeds the maximum permitted. A maximum of 500 application server tasks may be defined in the ECAPARM configuration file.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP3BE APSERVER ENTRY (entryId.entry_typ.model), IMPROPER CHANNEL(channel) SPECIFIED FOR THE APPL (applName), SERVER DISABLED

Explanation: The communication model in the ECAPARM configuration file in an APSERVER definition does not match the communication model of the referenced channel. During initialization, IOAGATE reads and verifies the definitions in the ECAPARM configuration file. The same ECAPARM configuration file is processed by IOAGATE and by each application server that communicates with this IOAGATE.

The variables in this message are:

entryId - a sequential number that identifies the APSERVER definition entry in the ECAPARM configuration file
entry_typ - the type of application server defined by this APSERVER statement. Valid values are:
- CM - manager of the address space of an application server
- CS - application server
- CD - detector server
- CU - updater server
model - the communication model of the channel required by the application
channel - the identity of the channel referenced from the APSERVER definition
applName - the identity of the application server

The indicated APSERVER definition is ignored, and processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP3CS NO APPLICATION SERVER DEFINED IN ECAPARM

Explanation: A severe internal error occurred during initialization. No application server was defined in ECAPARM.

IOAGATE shuts down.

Corrective Action: Define at least one application server in ECAPARM.

ECAP3DE APSERVER ENTRY(entryId), UNKNOWN CHANNEL(value) SPECIFIED, SERVER DISABLED

Explanation: The server is disabled because a channel reference in an APSERVER definition does not exist in the ECAPARM configuration file.

During initialization, IOAGATE reads and verifies the definitions from the ECAPARM configuration file. IOAGATE, and each application server that communicates with this IOAGATE, process the same ECAPARM configuration file.

The variables in this message are:

entryId - the sequential number that identifies the APSERVER definition entry in the ECAPARM configuration file
value - the invalid value specified by the user as a channel reference

The specified APSERVER definition is disabled, and processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP3EE APSERVER ENTRY(entryId), MANDATORY PARAMETER APPL= WAS NOT SPECIFIED, SERVER DISABLED

Explanation: The server is disabled because no value was set for the APPL parameter in the APSERVER definition.

During initialization, IOAGATE reads and verifies the definitions specified in the ECAPARM configuration file. The IOAGATE, and each application server that communicates with this IOAGATE, process the same ECAPARM configuration file.

In this message, entryId is a sequential number that identifies the APSERVER definition entry in the ECAPARM configuration file.

The specified APSERVER definition is disabled. Normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP3FS INTERNAL ERROR. EXPANDED AND RAW APPL ENTRIES DIFFER

Explanation: A severe internal error occurred during the processing of the ECAPARM configuration file. Differences were found between the expanded and the raw application entries.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP3GW APSERVER ENTRY(entryId), IMPROPER COMPRESS= SPECIFIED(code), CHANGED TO DEFAULT(default_code)

Explanation: The value of the COMPRESS parameter in the ECAPARM configuration file is invalid. The COMPRESS parameter must be set to YES or NO.

The variables in this message are:

entryId - a sequential number that identifies the problematic APSERVER definition entry in the ECAPARM configuration file
code - the current invalid value of the COMPRESS parameter
default_code - the default value set by IOAGATE for the COMPRESS parameter for this application

The value specified for COMPRESS is replaced by the default value. Normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP3HE APSERVER ENTRY(entryId), ENCRYPT= PARAMETER IS NOT SUPPORTED FOR applId

Explanation: A value cannot be set for the ENCRYPT parameter for the application applId.

The variables in this message are:

entryId - a sequential number that identifies the problematic APSERVER definition entry in the ECAPARM configuration file
applId - the identity of the application for which encryption is not supported

The value set for the ENCRYPT parameter is ignored. Processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP41S NO CHANNEL ENTRY AVAILABLE

Explanation: A severe error occurred during checking of the ECAPARM configuration file. There is no valid CHANNEL definition in the ECAPARM configuration file.

IOAGATE shuts down.

Corrective Action: Do the following:

Check any error messages that precede this one.
Correct the ECAPARM configuration file.
Restart IOAGATE.

ECAP42W CHANNEL ENTRY(entryId), MANDATORY PARAMETER ID= WAS NOT SPECIFIED, CHANNEL DISABLED

Explanation: The ID parameter is not specified for the indicated channel in the CHANNEL definition.

In this message, entryId is a sequential number that identifies the problematic CHANNEL definition in the ECAPARM configuration file.

The specified CHANNEL definition is disabled, and normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP43W CHANNEL ENTRY(entryId), MANDATORY PARAMETER MODEL= WAS NOT SPECIFIED, CHANNEL DISABLED

Explanation: The MODEL parameter is not specified for the indicated channel in the CHANNEL definition.

In this message, entryId is a sequential number that identifies the problematic CHANNEL definition in the ECAPARM configuration file.

The specified CHANNEL definition is disabled, and normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP44W CHANNEL ENTRY(entryId), OPTIONAL PARAMETER SUBSYSTM= CAN BE USED WITH TCPVENDR=CA ONLY, PARAMETER IGNORED

Explanation: The optional SUBSYSTM parameter was specified in the ECAPARM configuration file with TCPVENDR set to IBM for an SNA channel or a TCP channel. The optional SUBSYSTM parameter is only valid for a TCP channel, and only with TCPVENDR set to CA.

In this message, entryId is a sequential number that identifies the problematic CHANNEL definition in the ECAPARM configuration file.

The SUBSYSTM parameter is ignored, and normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP45W CHANNEL ENTRY(entryId), ID(channelId) NOT UNIQUE, CHANNEL DISABLED

Explanation: The same channel ID is used in more than one CHANNEL definition in the ECAPARM configuration file. The channel ID must be unique for each CHANNEL definition in the ECAPARM configuration file.

During initialization IOAGATE reads and verifies definitions specified in the ECAPARM configuration file. The same ECAPARM configuration file is processed by IOAGATE and by each application server that communicates with this IOAGATE.

The variables in this message are:

entryId - a sequential number that identifies the problematic CHANNEL definition in the ECAPARM configuration file
channelId - the channel identity assigned by the user in the ECAPARM configuration file

The specified CHANNEL definition is disabled, and normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP46W CHANNEL ENTRY(entryId), MANDATORY PARAMETER PORT= WAS NOT SPECIFIED, CHANNEL DISABLED

Explanation: The PORT parameter is not specified for the indicated TCP channel in the CHANNEL definition.

In this message, entryId is a sequential number that identifies the problematic CHANNEL definition in the ECAPARM configuration file.

The specified CHANNEL definition is disabled, and normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP47W APPL.SERVER (applServer.addrSpaceId) DISABLED IN ECAPARM(suffix)

Explanation: During initialization, IOAGATE detected that the value of the SERVER parameter in the ECAPARM configuration file is DISABLE for the specified application server applServer. Therefore it will not be started.

The SERVER parameter can be specified manually in the APSERVER definition of the ECAPARM configuration file to enable or disable the definition. The default value is ENABLE.

The variables in this message are:

applServer - the name of the application server with the SERVER parameter set to DISABLE
addrSpaceId - the internal identity assigned to the application server address space
suffix - unique 1-character suffix identifying the ECAPARM configuration file that contains the SERVER parameter set to DISABLE

The specified application server is disabled. Normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP48W CHANNEL ENTRY(entryId), PARAMETERS APPLID= OR APPLIDS=(,) REQUIRED WHEN PROTOCOL=SNA AND MODEL=DC, CHANNEL DISABLED

Explanation: Either the APPLID or APPLIDS parameters is missing for the SNA channel entry in the ECAPARM configuration file. When the PROTOCOL parameter is SNA and the MODEL parameter is DC, either the APPLID or the APPLIDS parameter must be specified in the ECAPARM configuration file.

In this message, entryId is a sequential number that identifies the problematic CHANNEL definition in the ECAPARM configuration file.

The specified CHANNEL definition is disabled. Normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP49E CHANNEL ENTRY(entryId), MANDATORY PARAMETER PROTOCOL= WAS NOT SPECIFIED, CHANNEL DISABLED

Explanation: The PROTOCOL parameter is not defined for the specified channel.

In this message, entryId is a sequential number that identifies the problematic CHANNEL definition in the ECAPARM configuration file.

The specified CHANNEL definition is disabled. Normal processing continues.

Corrective Action: Set a value for the PROTOCOL parameter in the ECAPARM configuration file and restart IOAGATE.

ECAP4AS TASK-TO-ATTACH ENTRY(x) CHANNEL(channelId) INVALID STDTYPE(type) IN DESCRIPTOR

Explanation: A severe internal error occurred during processing of the ECAPARM configuration file.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP4BW CHANNEL(channelId) NUMBER OF SUPPORTED APPLICATIONS PER CHANNEL EXCEEDED MAXIMUM(num) APPLICATION(applicId) IGNORED

Explanation: Too many APSERVER definitions reference the same channel. During initialization, IOAGATE reads and checks the ECAPARM configuration file. The same ECAPARM configuration file is processed by IOAGATE and by each application server that communicates with this IOAGATE.

The variables in this message are:

channelId - the identity of the problematic channel
num - the maximum number of applications each channel can support
applicId - the identity of the application that exceeded the maximum number of applications

The identified application is ignored. Processing continues.

Corrective Action: Reduce the number of applications that reference the same channel, and restart IOAGATE.

ECAP4CW CHANNEL ENTRY(entryId) APPLID= NOT SPECIFIED, SNA CHANNEL DISABLED

Explanation: No APPLID parameter is specified for an SNA communication channel in the ECAPARM configuration file. For an SNA channel, an APPLID parameter must be specified. It may be specified with or without a NETWMAP parameter.

In this message, entryId is a sequential number that identifies the problematic CHANNEL definition in the ECAPARM configuration file.

The specified CHANNEL definition is disabled. Normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4DW CHANNEL ENTRY(entryId), PORT= VALUE MUST BE IN THE RANGE FROM 1024 THROUGH 65534

Explanation: This warning message indicates that the PORT parameter value specified in the ECAPARM configuration file is invalid.

The PORT parameter value must be in the range from 1024 through 65534.

In this message, entryId is the identity of the channel for which the PORT parameter was defined.

The specified channel is disabled and processing continues.

Corrective Action: Correct the value of the PORT parameter in the ECAPARM configuration file and restart IOAGATE.

ECAP4EW CHANNEL ENTRY(entryId), SUBPARAMETERS OF APPLIDS= PARAMETER ARE EQUAL, CHANNEL DISABLED

Explanation: The same subparameter value is specified twice for the APPLIDS parameter for the specified channel in the ECAPARM configuration file.

In this message, entryId is a sequential number that identifies the problematic CHANNEL definition in the ECAPARM configuration file.

The specified CHANNEL definition is disabled. Normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4FW CHANNEL ENTRY(entryId), SUBPARAMETER(subparm) OF APPLIDS= IS INVALID

Explanation: An invalid subparameter is specified for the APPLIDS parameter for the channel entry in the ECAPARM configuration file.

The variables in this message are:

entryId - a sequential number that identifies the problematic CHANNEL definition in the ECAPARM configuration file
subparm - the identity of the invalid subparameter

The specified CHANNEL definition is disabled and normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4GE NO APPLICATION SERVER AVAILABLE

Explanation: There is no valid APSERVER definition in the ECAPARM configuration file. If there are any APSERVER definitions in the ECAPARM configuration file, they are invalid or disabled.

IOAGATE shuts down.

Corrective Action: Do the following:

Check any other error messages that precede this one.
Correct the ECAPARM configuration file.
Restart IOAGATE.

ECAP4HS PROCESSING TABLE OF DEFAULTS(ECAPDEF) FAILED

Explanation: A severe internal error occurred during the processing of the ECAPDEF table of numeric parameters defaults.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP4IE ECAPARM(suffix) VALIDITY CHECK FAILED, handler WAS THE LAST WORKED PROCESSOR

Explanation: One or more errors occurred during the processing of the ECAPARM configuration file. This caused the file to fail a validity check, and processing of the file stopped.

The variables in this message are:

suffix - a 1-character suffix that identifies the ECAPARM configuration file
handler - the subroutine that was last active during the processing of the ECAPARM configuration file

IOAGATE shuts down.

Corrective Action: Do the following:

Check other error messages that precede this one.
Correct the ECAPARM configuration file.
Restart IOAGATE.

ECAP4JW GATEWAY PARAMETER(parm) OUT OF RANGE(min-max), DEFAULT(defaultValue) SET

Explanation: When processing the GATEWAY section of the ECAPARM configuration file, IOAGATE detected that the value of the numeric parameter parm predefined in the ECAPDEF table of numeric defaults is invalid.

The variables in this message are:

parm - the name of the parameter with the invalid value
min - the minimum valid value of the parm parameter
max - the maximum valid value of the parm parameter
defaultValue - the default value of the parm parameter

The parm parameter is set to the default value defaultValue. Normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4KW entryType ENTRY(entryId), PARAMETER(parm) OUT OF RANGE(min-max), VALUE(value) SET

Explanation: When processing the ECAPARM configuration file, IOAGATE found that the value of the numeric parameter parm was invalid.

The variables in this message are:

entryType - the section of the ECAPARM configuration file that contains the invalid parameter. Valid values are:
- CHANNEL - the channel definitions section
- APSERVER - the application server definitions section
entryId - a sequential number that identifies the definition entry in the ECAPARM configuration file that contains the invalid parameter
parm - the name of the invalid parameter
min - the minimum valid value of the parm parameter
max - the maximum valid value of the parm parameter
value - the value of the parm parameter that has been set

The parm parameter is set to the default value value. Normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4LE entryType ENTRY(entryId), MANDATORY PARAMETER(parm) OUT OF RANGE(min -max)

Explanation: When processing the ECAPARM configuration file, IOAGATE found that the value of the mandatory numeric parameter parm was invalid.

The variables in this message are:

entryType - the section of the ECAPARM configuration file that contains the invalid mandatory numeric parameter parm. Valid values are:
- CHANNEL - the channel definitions section
- APSERVER - the application server definitions section
entryId - a sequential number that identifies the definition entry in the ECAPARM configuration file that contains the invalid parameter
parm - the name of the invalid parameter
min - the minimum valid value of the parm parameter
max - the maximum valid value of the parm parameter

The parm parameter is ignored. IOAGATE tries to continue processing.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4ME entryType ENTRY(entryId), MANDATORY PARAMETER(parm) WAS NOT SPECIFIED

Explanation: When processing the ECAPARM configuration file, IOAGATE found that no value had been set for the mandatory parameter parm.

The variables in this message are:

entryType - the section of the ECAPARM configuration file that contains the mandatory parameter parm. Valid values are:
- CHANNEL - the channel definitions section
- APSERVER - the application server definitions section
entryId - a sequential number that identifies the definition entry in the ECAPARM configuration file that contains the parameter that lacks a value
parm - the name of the mandatory parameter that lacks a value

The parm parameter is ignored. IOAGATE tries to continue processing.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4NE GATEWAY MANDATORY PARAMETER(parm) OUT OF RANGE(min -max)

Explanation: When processing the GATEWAY section of the ECAPARM configuration file, IOAGATE detected that the value of the mandatory numeric parameter parm is invalid.

The variables in this message are:

parm - the name of the invalid parameter
min - the minimum valid value of the parm parameter
max - the maximum valid value of the parm parameter

The parm parameter is ignored. IOAGATE tries to continue processing.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4OE GATEWAY MANDATORY PARAMETER(parm) WAS NOT SPECIFIED

Explanation: When processing the GATEWAY section of the ECAPARM configuration file, IOAGATE detected that no value had been set for the mandatory parameter parm.

In this message, parm is the name of the mandatory parameter that lacks a value.

The parm parameter is ignored. IOAGATE tries to continue processing.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4PE CHANNEL(channelId) NETWORK MAP REQUIRED BY APSERVER, APPL.SERVER(applicId) DISABLED

Explanation: The channel channelId does not contain any network map specification. A network map specification is required by the application server applicId linked to this channel.

The variables in this message are:

channelId - the identity of the problematic channel
applicId - the identity of the application server that requires network map specification

The channel channelId is disabled. Normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4QW CHANNEL(channelId) DISABLED

Explanation: When trying to process a network map specified in the channel channelId, IOAGATE found the channel disabled.

In this message, channelId is the identity of the disabled channel.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4RW APPL.SERVER(applicId -add_space_id. channelId) DISABLED

Explanation: The application server identified in the message is disabled.

The variables in this message are:

applicId - the identity of the disabled application
add_space_id - the identity of the application server address space of the disabled application
channelId - the identity of the channel to which the problematic application server was linked

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4SS ALL CHANNELS DISABLED, PROCESSING STOPPED

Explanation: IOAGATE monitor has shut down, because all channels were disabled during the processing of the ECAPARM configuration file.

IOAGATE has shut down.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4TE CHANNEL(channelId) DISABLED, PARAMETER BIND= CANNOT BE SPECIFIED FOR SNA CHANNEL

Explanation: The TCP parameter BIND has been specified for channelId, an SNA channel. This channel has been disabled. The TCP parameter BIND cannot be specified for a SNA channel.

In this message, channelId is the identity of the disabled channel.

The channel is disabled. Normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4UE CHANNEL(channelId) DISABLED, BAD IP ADDRESS SPECIFIED IN BIND= PARAMETER

Explanation: An invalid IP address was specified in the BIND parameter.

In this message, channelId is the identity of the TCP channel that detected the problem.

The channel is disabled. Processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4VS ALL CHANNELs DISABLED, monitorId IS GOING DOWN.

Explanation: IOAGATE monitor is shutting down because all channels have become disabled.

In this message, monitorId is the STC name of the IOAGATE started task.

IOAGATE shuts down.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4WS VALUE OF THE parm NUMERIC PARAMETER(val) EXCEEDS WORKABLE MAXIMUM

Explanation: When processing the ECAPARM configuration file, IOAGATE found that the value val set for the numeric parameter parm exceeds a workable maximum.

The variables in this message are:

parm - the identity of the parameter in which the error was found
val - the invalid value of the problematic parameter

The parm parameter is ignored. Normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4XS entry_typ NUMERIC PARAMETER(parm) NOT FOUND IN ECAPDEF

Explanation: A severe internal error occurred during the processing of the ECAPDEF table of numeric parameter defaults. A numeric parameter was not found in the ECAPARM configuration file.

The variables in this message are:

entry_typ - the name of the section of the ECAPARM configuration file that should contain the parm parameter. Valid values are:
- GATEWAY - the global IOAGATE definitions section
- CHANNEL - the channel definitions section
- APSERVER - the application server definitions section
parm - the identity of the problematic parameter

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP4YE CHANNEL(channelId) DISABLED, PARAMETER SHRDBIND= CANNOT BE SPECIFIED FOR SNA CHANNEL

Explanation: The TCP parameter SHRDBIND was encountered in an SNA channel. The TCP parameter SHRDBIND cannot be specified for an SNA channel.

In this message, channelId is the identity of the TCP channel that detected the problem.

IOAGATE disables the specified channel and tries to continue normal processing.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4ZW CHANNEL ENTRY(channelId), LOGINMSG= CANNOT BE SPECIFIED FOR THE DC CHANNEL, PARAMETER IGNORED

Explanation: The LOGINMSG parameter was specified for the channelId channel, but channelId is not an MC channel.

The LOGINMSG parameter can only be specified for an MC channel.

IOAGATE disables the LOGINMSG parameter. Normal processing continues.

Corrective Action: Correct the channel definition.

ECAP50I ECAPARM(suffix) HAS BEEN PROCESSED SUCCESSFULLY

Explanation: This information message indicates that processing of the ECAPARM configuration file has ended successfully.

In this message, suffix is a 1-character suffix that identifies the ECAPARM configuration file

Corrective Action: No action is required.

ECAP51S PROCESSING OF ECAAPPL(suffix) SUPPORTED APPLICATIONS TABLE HAS FAILED

Explanation: A severe error occurred during the processing of the internal table of applications supported by IOAGATE.

During initialization, IOAGATE reads and verifies the declarations specified in the internal table of applications supported by IOAGATE. The same table is processed by IOAGATE and by each application server that communicates with this IOAGATE.

In this message, suffix is a unique 1-character suffix that identifies an ECAAPPL table of supported applications.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP52I ECAAPPL(suffix) SUPPORTED APPLICATIONS TABLE HAS BEEN PROCESSED SUCCESSFULLY

Explanation: This information message indicates that processing of the internal table of the applications supported by the IOAGATE succeeded.

In this message, suffix is a unique 1-character suffix that identifies an ECAAPPL table of supported applications.

Corrective Action: No action is required.

ECAP53S ECAPRM INTERNAL ERROR, DESCRIPTOR ADDRESS UNAVAILABLE

Explanation: A severe internal error occurred during the processing of the ECAPARM configuration file. A descriptor address was not found.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP54S ECAPRM INTERNAL ERROR, FAILURE TO LOCATE MCT TOKEN

Explanation: A severe internal error occurred during processing of the ECAPARM configuration file. An MCT token was not found.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP55W APSERVER(applicId), PARAMETER parm (val) CANNOT BE MODIFIED WITH VERSION(version)

Explanation: The specified parameter parm cannot be modified by the VERSION parameter, because the value of parm already has eight characters, which is the maximum. The VERSION parameter modifies a parameter by adding a 1-character version code to the existing value.

During initialization, IOAGATE reads and verifies the declarations specified in the ECAPARM configuration file. The same ECAPARM configuration file is processed by IOAGATE and by each application server that communicates with this IOAGATE.

The variables in this message are:

applicId - the identity of the application
parm - the parameter to be modified
val - the current value of the parameter
version - the value of the VERSION parameter that cannot be used

The VERSION parameter is ignored and processing continues.

Corrective Action: Correct the value assigned to VERSION and restart IOAGATE.

ECAP56S THERE IS A SEVERE STRUCTURE ERROR IN ECAAPPL(suffix) SUPPORTED APPLICATIONS TABLE

Explanation: A severe internal error occurred during ECAAPL processing. The structure of the internal table of applications supported by IOAGATE was found to be invalid.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP57W APPL APSERVER ENTRY(entryId), ALIAS= VALUE CAN BE DEFINED IN CM ENTRY ONLY

Explanation: The value specified for the ALIAS parameter in the internal table of supported applications is valid only for a CM type application server.

In this message, entryId is a sequential number that identifies the problematic APSERVER definition in the internal table of supported applications.

Initialization continues.

Corrective Action: Contact BMC Customer Support.

ECAP58S ECAPRM INTERNAL ERROR, BAD MCT ADDRESS OBTAINED

Explanation: A severe internal error occurred during the processing of the ECAPARM configuration file. The MCT address is not valid.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP59E APPL APSERVER(applicId), CMPRSTYP= PARAMETER IS A MUST WHEN COMPRESS=YES SPECIFIED

Explanation: An internal error encountered during the processing of the ECAAPPL table of internal parameters. The CMPRSTYP parameter is not specified in the internal table of supported applications, but the COMPRESS parameter is set to YES.

During initialization, IOAGATE reads and verifies the declarations specified in the internal table of applications supported by the IOAGATE. The same table is processed by IOAGATE and by each application server that communicates with this IOAGATE.

In this message, applicId is the problematic APSERVER definition in the internal table of supported applications.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP5AE ECAPARM (suffix) PROCESSING FAILED, RC=rc

Explanation: An internal error occurred during the processing of the ECAPARM configuration file.

The variables in this message are:

suffix - a 1-character suffix that identifies a unique ECAPARM configuration file used in this IOAGATE run

rc - a return code indicating the failure levelValid values for rc are:

Return Code	Explanation
08	An error occurred during ECAPARM processing. The ECAPARM processor is able to continue ECAPARM processing.
12	An error occurred during ECAPARM processing. The ECAPARM processor is NOT able to continue ECAPARM processing.

As indicated in the valid values for rc.

Corrective Action: Do the following:

Examine the IOAGATE logs, and try to determine the cause of the problem.
If possible, correct the problem and restart IOAGATE.
If the problem persists, contact BMC Customer Support.

ECAP5BS ECAAPL INTERNAL ERROR, ECAAPPL DESCRIPTOR ADDRESS UNAVAILABLE

Explanation: A severe internal error occurred during the processing of the specified table of internal parameters during initialization. The ECAAPL internal routine did not get the address of the ECAAPPL descriptor.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP5CS ECAAPL INTERNAL ERROR, NO PARAMETERS OBTAINED

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP5DS ECAAPL INTERNAL ERROR, NO APPLICATION ENTRY OBTAINED

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP5EE IMPROPER CHANNEL(channelId.protocol) SPECIFIED FOR APPL.SERVER (applServer.addrSpaceId), APPL.SERVER DISABLED

Explanation: The channel specified by the CHANID parameter in an APSERVER definition in the ECAPARM configuration file is not appropriate for the application declared by the definition.

During initialization, IOAGATE reads and checks the ECAPARM configuration file The same ECAPARM configuration file is processed by IOAGATE and by each application server that communicates with this IOAGATE.

The variables in this message are:

channelId - the identity of the problematic channel
protocol - the communication protocol of the problematic channel
applServer - the identity of the problematic application server
addrSpaceId - the internal identity of the problematic application server address space

The indicated application server applServer is disabled and processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP5FS ECAAPL INTERNAL ERROR, FAILURE TO LOCATE MCT TOKEN

Explanation: A severe internal error occurred during the processing of the specified table of internal parameters during initialization. The ECAAPL internal routine did not find the MCT token.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP5GI ECAPARM(suffix) CONFIGURATION FILE HAS BEEN PROCESSED WITH RC(04)

Explanation: This information message indicates that processing of the ECAPARM configuration file has ended with minor errors.

In this message, suffix is a 1-character suffix that identifies the ECAPARM configuration file

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP60I ECASRVT SERVICES TABLE HAS BEEN PROCESSED SUCCESSFULLY

Explanation: This information message indicates that processing of the ECASRVT internal table of services succeeded. During initialization, IOAGATE processes the ECASRVT internal table of services or request types supported by IOAGATE.

Corrective Action: No action is required.

ECAP61S PROCESSING OF ECASRVT SERVICES TABLE FAILED

Explanation: Processing of the ECASRVT internal table of services or types of transactions supported by IOAGATE failed. This is a severe internal error.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP6BS ECASRV INTERNAL ERROR, ECASRVT DESCRIPTOR ADDRESS UNAVAILABLE

Explanation: This is a severe internal error. The ECASRV internal routine did not get a descriptor address to process during processing of the ECASRVT internal table of services.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP6CS ECASRV INTERNAL ERROR, NO PARAMETERS OBTAINED

Explanation: This is a severe internal error. The ECASRV internal routine did not get any parameters during processing of the ECASRVT internal table of services.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP6DS ECASRV INTERNAL ERROR, NO SERVICE ENTRY OBTAINED

Explanation: This is a severe internal error. The ECASRV internal routine did not get any entry to process during processing of the ECASRVT internal table of services.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP6FS ECASRV INTERNAL ERROR, FAILURE TO LOCATE MCT TOKEN

Explanation: This is a severe internal error. The ECASRV internal routine could not find an MCT token during processing of the ECASRVT internal table of services.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP80S CHANNEL(channelId.TCP) HAS GONE DOWN DUE TO NO COMTASK AVAILABLE

Explanation: This is a severe error that can be issued for a multiple connection (MC) TCP communication channel only. All communication tasks that belong to the specified channel terminated.

In this message, channelId is the identity of the problematic channel.

This message follows ECAP88S. For more information, see messages ECAP86W, ECAP87W and ECAP88S.

The multiple connection (MC) TCP channel goes down, and processing continues.

Corrective Action: Do the following:

Examine IOAGATE logs to try to determine why the communication tasks went down.
If possible, correct the problem and restart IOAGATE.
If the problem persists, contact BMC Customer Support.

ECAP82S CHANNEL(channelId.TCP) NO COMTASK INITIALIZED DURING LAST interval sec

Explanation: A severe error was encountered during initialization of the multiple connection TCP channel. No communication task launched by the channel started during the specified time interval.

The variables in this message are:

channelId - the identity of the problematic TCP channel
interval - the time interval (in seconds) during which no communication task succeeded in initializing

The specified TCP channel goes down. IOAGATE tries to continue processing.

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.

ECAP83W CHANNEL(channelId.TCP) DISABLED

Explanation: This message warns that the channelId MC TCP channel has been disabled because an EADDRINUSE error occurred while IOAGATE was trying to bind the port specified in the BIND parameter in ECAPARM.

When IOAGATE goes down, this message is issued for a DC type channel
When CTMAS of the same installation is active on the same or another LPAR in the SYSPLEX, the DC channel used for communications with Control-M/EM is disabled. IOAGATE will go down if no other channels are defined for the same IOAGATE, but will stay up if there are additional channels which are OK.

Corrective Action: No action is required.

ECAP86W CHANNEL(channelId.TCP) COMTASK(taskId) CANNOT BE STARTED ANY MORE, THRESHOLD OF RESTARTS(threshold) REACHED

Explanation: A communication task of a multiple connection TCP channel has already shut down and restarted the maximum number of times. When an error prevents a TCP communication task from working normally, the TCP channel tries to resolve the problem by recycling the task. However, beyond a defined limit, the TCP channel assumes a severe problem, and prevents further recycling of the task.

This message can be issued for a multiple connection TCP channel only.

The variables in this message are:

channelId - the identity of the channel that has the problematic task
taskId - the internal identity of the problematic TCP communication task
threshold - the internally defined maximum number of times to recycle a communication task

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.

ECAP87W CHANNEL(channelId.TCP) num COMTASKS AMONG(channel_amount) DEFINED TO CHANNEL TERMINATED

Explanation: The specified number (num) of communication tasks became unavailable to a multiple connection (MC) TCP communication channel. A serious problem may be preventing the specified TCP channel from working properly. An ECAP86W message is issued before this message for each communication task that terminated.

This message can only be issued for a multiple connection (MC) TCP communication channel.

The variables in this message are:

channelId - the identity of the problematic channel
num - the number of communication tasks that terminated
channel_amount - the number of communication tasks configured to the specified channel

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.

ECAP88S CHANNEL(channelId.TCP) ALL COMTASKS DEFINED TO CHANNEL(num) TERMINATED

Explanation: No more active communication tasks are available for the specified channel. All communication tasks terminated, and none is allowed to restart. ECAP86W warning messages were previously issued for each communication task that went down. This message precedes message ECAP80S. For more information, see message ECAP86W.

This message can only be issued for a multiple connection (MC) TCP communication channel.

The variables in this message are:

channelId - the identity of the problematic channel
num - the number of communication tasks configured to the specified channel in the ECAPARM configuration file

The specified channel goes down and processing continues. If the indicated channel is the only one configured to IOAGATE, IOAGATE shuts down.

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.

ECAP90I ECAIPLS(suffix) IP LIST HAS BEEN {PROCESSED | REFRESHED} SUCCESSFULLY FOR CHANNEL(channel)

Explanation: This information message indicates that the IP list member was specified in the ECAPARM member for channel channel by means of the IPLIST parameter, and the IP list member was processed or refreshed (if the REFRESH command was issued) successfully.

The variables in this message are:

suffix - one-character suffix used to specify the individual ECAIPLS x IP list member name
channel - channel identity that the indicated ECAIPLS x IP list specified

Corrective Action: No action is required.

ECAP91I CHANNEL(channel) ECAIPLS(suffix) IP LIST MEMBER IS BEING CHECKED

Explanation: This information message indicates which specific IP list member is being processed. The message is issued in DAIGLOG output as a header for the group of ECAP93I messages issued for each line in the IP list member.

The variables in this message are:

channel - channel identity for which the indicated ECAIPLS x IP list was specified
suffix - one-character suffix used to specify the individual ECAIPLS x IP list member name

Corrective Action: No action is required.

ECAP92I END OF ECAIPLS(suffix) IP LIST MEMBER

Explanation: This information message indicates which specific IP list member was processed. The message is issued in DAIGLOG output as a footer after the group of ECAP93I messages issued for each line in the IP list member.

In this message, suffix is a one-character suffix used to specify the individual ECAIPLS x IP list member name.

Corrective Action: No action is required.

ECAP93I indication number: IPListLine

Explanation: This information message is issued in DAIGLOG output for each source IPListLine in the IP list member.

The variables in this message are:

indication - a short string indicating the result of a source IPListLine processing

Valid values of indication are:

indication	Explanation
no indication	Indicates that no error was detected in an IP list source line.
ERROR code FOUND	Indicates that an error with hexadecimal code code was found in an IP list source line. When such an indication is issued, message ECAP94I follows message ECAP93I and specifies an approximate column where the error detected. Additionally, another error message follows message ECAP94I to specify the exact reason for the error.
RECORD IGNORED	Indicates that an IP list source line was ignored because another line in the IP list repeats the current line. Message ECAP9BW that follows message ECAP93I specifies the sequential number of the duplicate line.
ALLOW IGNORED	Indicates that an IP list source line was ignored because there is a FORBID line in the IP list that was specified for the same IP address and a mask. Message ECAP9CE that follows message ECAP93I specifies the number of the FORBID line.
COMMENT LINE	Indicates that an IP list source line has an asterisk in the first column. The line is not processed.
BLANKED LINE	Indicates that an IP list source line contains no valid characters. The line is not processed.

number - the sequential number of an IP list source line
IPListLine - the contents of an IP list source line

Corrective Action: No action is required.

ECAP94I NEAR COLUMN NUM.column:

Explanation: This information message is issued in DAIGLOG output. It follows message ECAP93I when an error is detected in an IP list source line and indicates the approximate column where the error was detected. The message is issued for a source IP line when an error is detected in the line.

In this message, column is the approximate sequential number of the column in the IP list source line where the error was detected.

Corrective Action: No action is required.

ECAP95E EMPTY section SECTION

Explanation: No character was found between dots that form a section in a mask or IP address in the IP list source line indicated by message ECAP93I.

In this message, section is a portion of a mask or an IP address string between dots. Valid values are:

ADDRESS
MASK

The following system actions occur:

The channel for which the IP list is defined is disabled.
Processing continues.

Corrective Action: Correct the IP list member and try again.

ECAP96E VALUE IN SECTION EXCEEDS 255

Explanation: A value specified in a separate section of a mask or IP address exceeds 255 in the IP list source line indicated by message ECAP93I. The section is a portion of a mask or an IP address string between dots.

The following system actions occur:

Processing continues.
The channel for which the IP list is defined is disabled.

Corrective Action: Correct the IP list member and try again.

ECAP97E WRONG USAGE OF AN ASTERISK IN section

Explanation: An asterisk was improperly specified in a separate section of a mask or IP address in an IP list source line indicated by message ECAP93I. An asterisk can be specified in the first through fourth contiguous right-to-left sections of an IP address. An asterisk in a mask is not allowed.

In this message, section is a portion of a mask or an IP address string between dots. Valid values are:

ADDRESS
MASK

The following system actions occur:

Processing continues.
The channel for which the IP list is defined is disabled.

Corrective Action: Correct the IP list member and try again.

ECAP98E WRONG NUMBER OF SECTIONS IN {ADDRESS | MASK}

Explanation: The number of sections in a mask or IP address is not exactly four in the IP list source line indicated by message ECAP93I.

The following system actions occur:

Processing continues.
The channel for which the IP list is defined is disabled.

Corrective Action: Correct the IP list member and try again.

ECAP99E NEITHER ALLOW NOR FORBID STATEMENT

Explanation: A main keyword in the IP list source line indicated by message ECAP93I could not be identified. Each valid IP line must have either ALLOW or FORBID as a keyword.

The following system actions occur:

Processing continues.
The channel for which the IP list is defined is disabled.

Corrective Action: Correct the IP list member and try again.

ECAP9AE INVALID CHARACTER DETECTED

Explanation: An invalid character was detected in the IP list source line indicated by message ECAP93I. Message ECAP94I, which precedes message ECAP9AE, specifies the exact column where the invalid character was detected.

The following system actions occur:

Processing continues.
The channel for which the IP list is defined is disabled.

Corrective Action: Correct the IP list member and try again.

ECAP9BW DUE TO DUPLICATE RECORD NUMBER:number

Explanation: An IP list source line was ignored because there is a duplicate line in the IP list.

In this message, number is the number of the duplicate IP list source line.

Corrective Action: Correct the IP list member and try again.

ECAP9CW DUE TO FORBID RECORD NUMBER:number SPECIFIED FOR THE SAME ADDRESS

Explanation: This warning indicates that the ALLOW IP list source line was ignored because the FORBID line in the IP list was specified for the same IP address and a mask as in the ignored line.

In this message, number is the number of the FORBID line in the IP list.

Corrective Action: Correct the IP list member and try again.

ECAP9DE WRONG MASK: INCONSECUTIVE (FROM LEFT TO RIGHT) BITS DETECTED

Explanation: Inconsecutive bits were detected in a mask specified in the IP list source line that was indicated by message ECAP93I. The mask should be built with consecutive, left-to-right bits only.

The following system actions occur:

Processing continues.
The channel for which the IP list is defined is disabled.

Corrective Action: Correct the IP list member and try again.

ECAP9ES SEVERE ERROR ENCOUNTERED; ROUTINE(routine) RC(rc) REASON(reason)

Explanation: A severe error, with an rc return code and reason reason, was detected by the routine internal routine.

The variables in this message are:

routine - the name of the routine in which the indicated error case was detected.Valid values for routine are:
- IOAIPCV
- IOAIPLS
- IOAIPSH
rc - a non-zero error return code
reason - the hexadecimal error code specifying an exact error case.

The following system actions occur:

Processing stops.
The channel for which the IP list is defined is disabled.

Corrective Action: Contact BMC Customer Support.

ECAP9FS INTERNAL ERROR ENCOUNTERED; ROUTINE(routine) RC(rc) REASON(reason)

Explanation: A severe internal error, with an rc return code and reason reason, was detected by the routine internal routine.

The variables in this message are:

routine - the name of the routine in which the indicated error case was detected.Valid values for routine are:
- IOAIPCV
- IOAIPLS
- IOAIPSH
rc - a non-zero error return code
reason - the hexadecimal error code specifying an exact error case.

The following system actions occur:

Processing stops.
The channel for which the IP list is defined is disabled.

Corrective Action: Contact BMC Customer Support.

ECAP9GE IOAMEM SERVICE DETECTED AN ERROR; ROUTINE(routine) RC(rc) REASON(reason)

Explanation: The IOAMEM service detected an error when handling an IP list member. The IOAMEM routine is used when reading PDS members.

The variables in this message are:

routine - the name of the routine in which the indicated error case was detected.Valid values for routine are:
- IOAIPLS
- IOAIPSH
rc - a non-zero error return code
reason - the hexadecimal error code specifying an exact error case.

The following system actions occur:

IP list processing stops.
The channel for which the IP list is defined is disabled.
Processing continues.

Corrective Action: If it is not possible to locate the source of the error, contact BMC Customer Support.

ECAP9HW SYNTAX ERROR DETECTED IN ECAIPLS(suffix) IP LIST MEMBER, CHANNEL(channel)

Explanation: A syntax error was detected in an IP list member. Detailed messages specifying both the exact error and its location are issued in DAIGLOG output. See message ECAP93I.

The variables in this message are:

suffix - the one-character suffix used to specify the individual ECAIPLS x IP list member name.
channel - the channel identity for which the indicated ECAIPLS x IP list is specified

The following system actions occur:

Processing continues.
The channel for which the IP list is defined is disabled.

Corrective Action: Correct the IP list member and try again.

ECAP9IS UNKNOWN ERROR ENCOUNTERED; ROUTINE(routine) RC(rc) REASON(reason)

Explanation: An unknown error, with an rc return code and reason reason, was detected by the routine internal routine.

The variables in this message are:

routine - the name of the routine in which the indicated error case was detected.Valid values for routine are:
- IOAIPCV
- IOAIPLS
- IOAIPSH
rc - a non-zero error return code
reason - the hexadecimal error code specifying an exact error case.

The following system actions occur:

IP list processing stops.
The channel for which the IP list is defined is disabled.

Corrective Action: Contact BMC Customer Support.

ECAP9JE FAILURE TO LOAD MODULE module

Explanation: The module module failed to load.

In this message, module is the name of the module that failed to load.

The following system actions occur:

IP list processing stops.
The channel for which the IP list is defined is disabled.

Corrective Action: Contact BMC Customer Support.

ECAP9KE SPECIFIED IP LIST MEMBER ECAIPLS(suffix) DOES NOT EXIST, CHANNEL(channel)

Explanation: The specified IP list member could not be located in a dataset allocated by DAPARM DD statement.

The variables in this message are:

suffix - the one-character suffix used to specify the individual ECAIPLS x IP list member name.
channel - the channel identity for which the indicated ECAIPLS x IP list is specified

The following system actions occur:

IP list processing stops.
The channel for which the IP list is defined is disabled.
Processing continues.

Corrective Action: Correct the IP list member and try again.

ECAP9LE EMPTY IP LIST MEMBER ECAIPLS(suffix) SPECIFIED, CHANNEL(channel)

Explanation: The specified IP list member was found to be empty.

The variables in this message are:

suffix - the one-character suffix used to specify the individual ECAIPLS x IP list member name.
channel - the channel identity for which the indicated ECAIPLS x IP list is specified

The following system actions occur:

IP list processing stops.
The channel for which the IP list is defined is disabled.
Processing continues.

Corrective Action: Correct the IP list member and try again.

ECAP9ME INVALID IP LIST MEMBER member(suffix) NAME SPECIFIED, CHANNEL(channel)

Explanation: This error message indicates that an invalid name was specified for the channel channel in ECAPARM as an IP list. A valid name should be ECAIPLS(suffix).

The variables in this message are:

member - the member name specified in the IPLIST channel parameter.
suffix - the one-character suffix used to specify the individual ECAIPLS x IP list member name.
channel - the channel identity for which the indicated ECAIPLS x IP list is specified

The following system actions occur:

IP list processing stops.
The channel for which the IP list is defined is disabled.
Processing continues.

Corrective Action: Correct the IP list member and try again.

ECAP9NE MORE THAN 999 RECORDS SPECIFIED IN IP LIST MEMBER ECAIPLS(suffix), CHANNEL(channel)

Explanation: The specified IP list member contains more than 999 lines.

The variables in this message are:

suffix - the one-character suffix used to specify the individual ECAIPLS x IP list member name.
channel - the channel identity for which the indicated ECAIPLS x IP list is specified

The following system actions occur:

IP list processing stops.
The channel for which the IP list is defined is disabled.
Processing continues.

Corrective Action: Correct the IP list member and try again.

ECAP9OE THERE IS NO VALID RECORD IN SPECIFIED IP LIST MEMBER ECAIPLS(suffix), CHANNEL(channel)

Explanation: No valid lines were found in the specified IP list member.

The variables in this message are:

suffix - the one-character suffix used to specify the individual ECAIPLS x IP list member name.
channel - the channel identity for which the indicated ECAIPLS x IP list is specified

The following system actions occur:

IP list processing stops.
The channel for which the IP list is defined is disabled.
Processing continues.

Corrective Action: Correct the IP list member and try again.

ECAP9PE HEADER RECORD NOT FOUND IN SPECIFIED IP LIST MEMBER ECAIPLS(suffix), CHANNEL(channel)

Explanation: No header record was found in the specified IP list member. The IP list member must have ALLOW * or FORBID* as its first valid record.

The variables in this message are:

suffix - the one-character suffix used to specify the individual ECAIPLS x IP list member name.
channel - the channel identity for which the indicated ECAIPLS x IP list is specified

The following system actions occur:

IP list processing stops.
The channel for which the IP list is defined is disabled.
Processing continues.

Corrective Action: Correct the IP list member and try again.

ECAP9QW FAILURE TO REFRESH IP LIST MEMBER ECAIPLS(suffix) FOR CHANNEL(channel)

Explanation: The F monitor,REFRESH=IPListMember modify command was issued but was unsuccessful, probably due to syntax errors detected in the specified IP list member.

The variables in this message are:

suffix - the one-character suffix used to specify the individual ECAIPLS x IP list member name.
channel - the channel identity for which the indicated ECAIPLS x IP list is specified

The following system actions occur:

No changes are performed.
Normal processing continues.

Corrective Action: Correct the IP list member and try again.

ECAP9RW CANNOT REFRESH MEMBER member: NOT DEFINED IN A CHANNEL

Explanation: The F monitor,REFRESH=IPListMember modify command specified an IP list member name that is not defined in any channel.

In this message, member is the IP list (ECAIPLS x) member name.

No changes are performed. Normal processing continues.

Corrective Action: Correct the IP list member and try again.

ECAP9SE REFRESH FOR(member) FAILED WITH RC(rc) REASON(reason)

Explanation: The F monitor,REFRESH=IPListMember modify command was issued but was unsuccessful, probably due to internal errors encountered when processing the specified IP list member.

The variables in this message are:

member - the IP list (ECAIPLS x) member name.
rc - the return code value
reason - the cause of the error

No changes are performed. Normal processing continues.

Corrective Action: Correct the IP list member and try again.

ECAP9TE WRONG OR NO VALID DATA

Explanation: Wrong or invalid data was detected in the IP list source line indicated by message ECAP93I.

No changes are performed. Normal processing continues.

Corrective Action: Correct the IP list member and try again.

ECAP9UE INVALID IPV6 RECORD

Explanation: A string in an IP source line contains the colon (:) character, but is not a syntactically valid IPv6 address.

The following system actions occur:

If the error occurs during IOAGATE startup, the channel for which the IP list is defined is disabled. If it is the only channel, then IOAGATE will terminate.
If the error occurs during a MODIFY REFRESH command, the refresh fails, but processing continues.

Corrective Action: Correct the IP list member and try again.

Use the following valid IPv6 address formats:

full 39-character format,for example:
- AA12:EF01:2345:FDD6:ABCD:EF01:2345:6789,
zero-suppressed formats, for example:
- 2001:DB8:0:0:8:800:200C:417A
- 2001:DB8::8:800:200C:417A
- ::1

Do not use '/' to abbreviate addresses.

Do not use IPv4-mapped IPv6 addresses. For example:

::ffff:137.72.214.55 – incorrect
137.72.214.55 – correct representation of the above address

ECAP9VE INVALID IPV6 ADDRESS RANGE

Explanation: An IP source line contains a range of IPv6 addresses, but the second address is not higher than the first address.

If the range was specified in 2 lines:

ALLOWTO or FORBIDTO was specified before ALLOWFR or FORBIDFR, respectively.
ALLOWFR was not followed immediately by ALLOWTO, or FORBIDFR by FORBIDTO.

The following system actions might occur:

If the error occurs during IOAGATE startup, the channel for which the IP list is defined is disabled. If it is the only channel, then IOAGATE will terminate.
If the error occurs during a MODIFY REFRESH command, the refresh fails but processing continues.

Corrective Action: Correct the IP list member and try again.

ECAPA1E KEYRING PARAMETER IS A MUST IF SSL=YES SPECIFIED, CHANNEL(channelId) DISABLED

Explanation: When SSL=YES is specified in the ECAPARM configuration file, the KEYRING parameter must also be specified.

In this message, channelId is the identity of the channel.

The channel is disabled. If there are no other enabled channels in IOAGATE, IOAGATE shuts down.

Corrective Action: Specify a KEYRING parameter.

ECAPA2E USERID/KEYRING PARAMETER INVALID, CHANNEL(channelId) DISABLED

Explanation: The syntax of the KEYRING parameter is invalid.

In this message, channelId is the identity of the channel.

The channel is disabled. If there are no other enabled channels in IOAGATE, IOAGATE shuts down.

Corrective Action: Specify a proper KEYRING parameter. Refer to the chapter about installing IOA in the INCONTROL for z/OS Installation Guide.

ECAPA3E SSL NOT SUPPORTED BY IOAGATE IN z/OS LEVEL LOWER THAN z/OS 1.4, CHANNEL(channelId) DISABLED

Explanation: SSL support in IOAGATE requires z/OS 1.4 or later.

In this message, channelId is the identity of the channel.

The channel is disabled. If there are no other enabled channels in IOAGATE, IOAGATE shuts down.

Corrective Action: Specify SSL=NO in the ECAPARM configuration file.

ECAPB1I PARAMETER xxxxxx SUCCESSFULLY | replaced in | retrieved from | MEMBER member_name

Explanation: A parameter in a IOA PARM library member was retrieved or updated by Control-M/Enterprise Manager.

Corrective Action: No action is required.

ECAPB2E RC=(04) REASON=(reason) PROCESSING FAILED

Explanation: An IOA PARM library parameter, which was needed to process a request from the Control-M/Enterprise Manager, could not be located.

Corrective Action:Review recent changes to the CTMAA section of the CTMPARM member in the IOA PARM library and to the member referred to by the ECAPARM parameter in the CTMAA section. Browse or edit the IOA PARM library, to ensure that it is not held exclusively by a TSO user or a job (for example, for compression). If no problem is found, save the IOAGATE and Application Server sysouts and call BMC Customer Support.

ECAPB3E RC=(08) REASON=(reason) |INVALID PARAMETER (n) RECEIVED| additional_details

Explanation:The IOA PARM library editor program was called with invalid parameters. The invalid parameter is identified by n, which is the parameter number in the ECAPMED parameter list.

ECAPB4E RC=(12) REASON=(reason) FAILURE TO READ | WRITE | STOW MEMBER member_name

Explanation:A failure occurred while reading/writing/saving an IOA PARM library member.

Corrective Action:The failure might occur if the member is being edited in TSO, or the IOA PARM library needs to be compressed. If the problem persists, save the IOAGATE and Application Server sysouts and call BMC Customer Support.

ECAPB5E RC=(24) REASON=(reason) INTERNAL ERROR OCCURRED

Explanation:The IOA PARM library editor program encountered a logical error.

Corrective Action:Save the Application Server sysouts and call BMC Customer Support.

Parent Topic

ECA messages