Messages ECAG00 through ECAGxx

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

ECAG00I IOAGATE STARTED, RELEASE(relId) CCID(changeLevel)

Explanation: This information message indicates that the IOAGATE monitor started normally.

The variables in this message are:

relId - the official release and the maintenance level of the IOAGATE
changeLevel - the change that was last applied to the main module of IOAGATE

Corrective Action: No action is required.

ECAG01W MAINTENANCE LEVEL MODULE(ECALVL) UNAVAILABLE

Explanation: The ECALVL module that contains the release and maintenance level information relating to IOAGATE was not found in the STEPLIB load library.

Corrective Action: No action is required.

ECAG02E IOAGATE NOT APF AUTHORIZED

Explanation: IOAGATE is not APF-authorized. The main module of IOAGATE either resides in a non-APF-authorized library or does not have the AC=1 attribute. All Load libraries concatenated to IOAGATE STEPLIB must be APF authorized.

IOAGATE shuts down.

Corrective Action: Either add all STEPLIB library names to the IEAAPF00 member in SYS1.PARMLIB, or use some other means available at the site to make the STEPLIB libraries APF-authorized.

ECAG03I ****.channelId.protocol SECTION OF THE mapId NETWORK MAP ****

Explanation: This message is a header for the section of the network map that is in use by the indicated channel.

The variables in this message are:

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

Corrective Action: No action is required.

ECAG04E ATTACH FOR(mod) HAS FAILED

Explanation: IOAGATE could not attach an internal IOAGATE task during initialization. The system completion code indicates the exact reason for the failure.

Possible causes are:

The mod module is not in the IOA Load library.
There is not enough storage available for the IOAGATE.

IOAGATE shuts down.

Corrective Action: Find the reason code in the system log, and try to fix the problem. If necessary, increase the region size. If the problem persists, call your system programmer for assistance.

ECAG05S task (taskId.type-channelId) UNRECOVERABLE ERROR ENCOUNTERED, REASON (rsn): explanation

An unrecoverable error occurred in the identified channel task.

The variables in this message are:

task - the name of the channel task in which the error occurred
taskId - the internal identity of the channel task in which the error occurred
type - the internal type of the task in which the error occurred
channelId - the identity of the channel to which the task belongs
rsn - the reason code of the error
explanation - short explanation for the error

IOAGATE shuts down.

Contact BMC Customer Support.

ECAG06S FAILURE(rsn) TO OBTAIN A NEW LINKAGE INDEX

Explanation: IOAGATE failed to obtain a new linkage index from MVS. The first time IOAGATE starts with a specific ECAPARM configuration file, it requests a new linkage index from the operating system during initialization to perform cross memory communication with its partner application server address spaces. However, the attempt to obtain a linkage index failed.

The reason code rsn is an internal identifier that the operating system assigned to this specific problem.

IOAGATE shuts down.

Corrective Action: Call your system programmer for assistance.

ECAG07I SHUT DOWN UPON REQUEST FROM CONSOLE(console_id)

Explanation: This information message confirms that an operator issued the STOP command, which requests shutdown of the IOAGATE. The IEF404I message follows this message to indicate that shutdown is complete.

In this message, console_id is the identity of the console from which the STOP request was issued.

The value of console_id depends on whether this request was issued from a physical or virtual console. If it was a virtual console, the value of console_id may coincide with the user ID of the operator who issued this request, depending on your local configuration.

Corrective Action: No action is required.

ECAG08I * LIST OF CURRENT ALLOCATIONS *

Explanation: This information message indicates that IOAGATE allocated data sets to be used by IOAGATE or an application server manager in this run. It is a header for the full list of allocated data sets. Each occurrence of message ECAG09I that follows this message specifies a different allocated data set.

Corrective Action: No action is required.

ECAG09I ddName type dsn

Explanation: This information message identifies a data set allocated by IOAGATE for use by IOAGATE or an application server manager in this run. It is issued separately for each data set allocated.

The variables in this message are:

ddName - the name of the DD statement that allocates the data set
type - the type of allocation Valid values are:
- JCL - a DD statement specified permanently in JCL
- DYN - a DD statement allocated dynamically
dsn - the name of the data set allocated by the DD statement

Corrective Action: No action is required.

ECAG0AI MODIFY COMMAND ISSUED FROM CONSOLE (console_id) ACCEPTED, COMMAND(cmd)

Explanation: This information message indicates that a valid modify command was issued.

The variables in this message are:

console_id - the identity of the console from which the modify command was issued.The value of console_id depends on whether this request was issued from a physical or virtual console. If it was a virtual console, the value of console_id may coincide with the user ID of the operator who issued this request, depending on your local configuration.
cmd - the command that was issued

Corrective Action: No action is required.

ECAG0BW MODIFY COMMAND ISSUED FROM CONSOLE (console_id) REJECTED, COMMAND(cmd)

Explanation: The modify command that has been issued is invalid. The ECAG0CI and ECAG25I messages that follow this ECAG0BW message provide a list of valid modify commands.

The variables in this message are:

console_id - the identity of the console from which the modify command was issued.The value of console_id depends on whether this request was issued from a physical or virtual console. If it was a virtual console, the value of console_id may coincide with the user ID of the operator who issued this request, depending on your local configuration.
cmd - the command that was issued

The modify command is rejected. Normal processing continues.

Corrective Action: Issue a valid modify command.

ECAG0CI VALID MODIFY COMMANDS ARE:

Explanation: This information message introduces a list of valid modify commands after an invalid modify command was issued. Each of the ECAG25I messages that follows contains a valid modify command.

Corrective Action: No action is required.

ECAG0DI *** FOLLOWING ECAPARM(suffix) CONFIGURATION FILE IS USED ***

Explanation: This information message is the header for the specified ECAPARM configuration file that IOAGATE or an application server will use in this run. ECAG0EI messages follow this message. Each ECAG0EI message displays a line of the ECAPARM configuration file.

In this message, suffix is a 1-character ID that specifies a unique ECAPARM configuration file.

Corrective Action: No action is required.

ECAG0EI lineNum lineText

Explanation: Each occurrence of this message is a line of an ECAPARM configuration file that IOAGATE or an application server is currently using.

The variables in this message are:

lineNum - the sequential number of the current line of the ECAPARM configuration file
lineText - the contents of the current line of the ECAPARM configuration file

Corrective Action: No action is required.

ECAG0FI ISSUE "F monitorId,? " TO GET VALID COMMANDS

Explanation: The message indicates that the command F IOAGATE,modifyCommand was issued, but the modifyCommand modify command is invalid.

Corrective Action: Issue the command F IOAGATE,modifyCommand with a valid modify command.

To obtain a list of available modify commands, issue the command F IOAGATE,?

ECAG0GW THERE IS NO ACTIVE APPLICATION SERVER, monitorId TERMINATING

Explanation: IOAGATE tried to launch an application server address space, but no such address space started, and STAYUP is not set to YES in the ECAPARM configuration file.

IOAGATE shuts down.

Corrective Action: No action is required.

ECAG0HI ENABLED FOR THE AUTOMATIC RESTART MANAGEMENT FUNCTION

Explanation: A valid ARMELEM parameter was specified in the ECAPARM configuration file, and was registered as an element of automatic restart management (ARM) for IOAGATE.

Corrective Action: No action is required.

ECAG0II AUTOMATIC RESTART IN PROGRESS AFTER UNEXPECTED FAILURE

Explanation: The message indicates that IOAGATE failed unexpectedly, but ARM support is enabled, and the operating system is automatically restarting IOAGATE.

IOAGATE restarts and normal processing continues.

Corrective Action: No action is required.

ECAG0JW AUTOMATIC RESTART MANAGEMENT REQUEST FAILED R15(rc) REASON (rsn) short_explan

Explanation: The message indicates that when starting up, IOAGATE failed to activate automatic restart management (ARM).

The meaning of the variables in this message is shown in the following table:

rc	rsn	short_explan	Explanation
08	002C	ELEMENT NAME INVALID	An invalid element name was specified.
08	0150	ELEMENT NAME IN USE	The element name is registered in a different address space.
12	0004	NO ARM SUPPORT	The release of MVS or JES in use does not support the ARM function.
12	0104	MAX ARM USERS	The number of ARM users registered is the maximum permissible.
12	0160	NO ACCESS TO ARM CDS	This system provides no access to an ARM CDS.

ARM is not enabled. Normal processing continues.

Corrective Action: Correct the problem identified by the diagnostic information in this message, then restart IOAGATE.

ECAG0KW MODIFY(cmd) REJECTED, rsn

Explanation: The message indicates that an F IOAGATE,modifyCommand command was issued, and that the command was rejected for the reason specified in the message.

The variables in this message are:

cmd - the modify command issued by the operator. Valid values are:
- CLOSE
- OPEN
rsn - the reason for the rejection of the modify commandPossible reasons are:
- NO PARAMETER SPECIFIED
- INVALID CHANNEL SPECIFIED
- SPECIFIED CHANNEL WAS NOT CLOSED

The command is ignored. Normal processing continues.

Corrective Action: Correct the command and if necessary reissue it.

ECAG10I IOAGATE HAS BEEN INITIALIZED SUCCESSFULLY

Explanation: This information message indicates that IOAGATE completed the initialization process successfully.

Corrective Action: No action is required.

ECAG11S FUNCTION(func) STD(taskId.type) ECAGNRL OBTAINED ZERO STD ADDRESS

Explanation: IOAGATE detected a severe internal error. An IOAGATE task tried to run the ECAGNRL internal service routine.

The variables in this message are:

func - the internal numeric code of the function that IOAGATE tried to perform
taskId - the internal identity of the IOAGATE task that tried to run the service routine
type - the internal type of IOAGATE task that tried to run the service routine

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG12S FUNCTION(func) STD(taskId.type) ECAGNRL OBTAINED ZERO STDID

Explanation: IOAGATE detected a severe internal error. An IOAGATE task tried to run the ECAGNRL internal service routine.

The variables in this message are:

func - the internal numeric code of the function that IOAGATE tried to perform
taskId - the internal identity of the IOAGATE task that tried to run the service routine
type - the internal type of IOAGATE task that tried to run the service routine

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG13W CHANNEL(channelId.TCP) CONNECTION REJECTED, MAXIMUM NUMBER OF LINKS REACHED

Explanation: The maximum number of users is already connected to IOAGATE over the multiple connection TCP channel.

In this message, channelId is the identity of the channel over which communication was attempted.

The attempt to connect to IOAGATE over the specified multiple connection TCP channel fails, and normal processing continues.

Corrective Action: Try again later.

ECAG14I task (taskId.type.channelId) STARTED

Explanation: This information message indicates the normal start of an IOAGATE internal channel task.

The variables in this message are:

task - the IOAGATE task
taskId - the internal identity of the task
type - the internal type of the task
channelId - the identity of the channel to which the task belongs

Corrective Action: No action is required.

ECAG15I task (taskId.type.channelId) SHUT DOWN

Explanation: This information message indicates normal termination of an IOAGATE internal channel task.

The variables in this message are:

task - the IOAGATE task
taskId - the internal identity of the task
type - the internal type of the task
channelId - the identity of the channel to which the task belongs

Corrective Action: No action is required.

ECAG16S FUNCTION(func) STD(taskId.type) ECAGNRL OBTAINED INVALID MCT ADDRESS IN STD

Explanation: IOAGATE detected a severe internal error. An IOAGATE task tried to run the ECAGNRL internal service routine.

The variables in this message are:

func - the internal numeric code of the function that IOAGATE tried to perform
taskId - the internal identity of the IOAGATE task that tried to run the service routine
type - the internal type of IOAGATE task that tried to run the service routine

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG17S FUNCTION(func) ECAGNRL OBTAINED INVALID MCT

Explanation: IOAGATE detected a severe internal error. An IOAGATE task tried to run the ECAGNRL internal service routine.

In this message, func is the internal numeric code of the function that IOAGATE tried to perform.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG18S FUNCTION(func) STD(taskId.type) ECAGNRL OBTAINED ZERO FUNCTION ADDRESS

Explanation: IOAGATE detected a severe internal error. An IOAGATE task tried to run the ECAGNRL internal service routine.

The variables in this message are:

func - the internal numeric code of the function that IOAGATE tried to perform
taskId - the internal identity of the IOAGATE task that tried to run the service routine
type - the internal type of IOAGATE task that tried to run the service routine

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG19S FUNCTION(func) STD(taskId.type) ECAGNRL OBTAINED ZERO FUNCTION CODE

Explanation: IOAGATE detected a severe internal error. An IOAGATE task tried to run the ECAGNRL internal service routine.

The variables in this message are:

func - the internal numeric code of the function that IOAGATE tried to perform
taskId - the internal identity of the IOAGATE task that tried to run the service routine
type - the internal type of IOAGATE task that tried to run the service routine

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG1AS FUNCTION(func) STD(taskId.type) ECAGNRL OBTAINED INVALID STDID

Explanation: IOAGATE detected a severe internal error. An IOAGATE task tried to run the ECAGNRL internal service routine.

The variables in this message are:

func - the internal numeric code of the function that IOAGATE tried to perform
taskId - the internal ID of the IOAGATE task that tried to run the service routine
type - the internal type of IOAGATE task that tried to run the service routine

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG1BS FUNCTION(func) ECAGNRL FAILED TO LOCATE MCT TOKEN

Explanation: IOAGATE detected a severe internal error. An IOAGATE task tried to run the ECAGNRL internal service routine.

In this message, func is the internal numeric code of the function that IOAGATE tried to perform.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG1CS FUNCTION(func) ECAGNRL OBTAINED ZERO MCT IN TOKEN

Explanation: IOAGATE detected a severe internal error. An IOAGATE task tried to run the ECAGNRL internal service routine.

In this message, func is the internal numeric code of the function that IOAGATE tried to perform.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG1DS CHANNEL (channelId. TCP) FAILED, NO COMM. TASK IS AVAILABLE

Explanation: A severe error has arisen in the IOAGATE TCP multiple connection channel channelId, and no active communication task is under the control of that channel.

The specified multiple connection channel (channelId) goes down. If it is the only channel configured in IOAGATE, IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG20I IOAGATE SHUTTING DOWN

Explanation: This information message indicates that IOAGATE is shutting down, either as a result of a STOP command, or internal IOAGATE events.

IOAGATE shuts down.

Corrective Action: If the shutdown is not the result of an operator request, check the IOAGATE JES log, the DAIGLOG log and the DATRACE log for more information about the cause of the shutdown. If necessary, call your system programmer for assistance.

ECAG21S IOAGATE HAS FAILED (rsn) TO INITIALIZE

Explanation: IOAGATE failed to complete initialization. The reason code (rsn) is an internal ID that IOAGATE assigned to this specific problem.

IOAGATE shuts down.

Corrective Action: Check the IOAGATE JES log, the DAIGLOG log and the DATRACE log for more information about the cause of the failure. Try to restart the IOAGATE. If necessary, call your system programmer for assistance.

ECAG24W task (taskId.type.channelId) DETACHED BY FORCE

Explanation: IOAGATE forced a DETACH of an IOAGATE internal channel task. When this message is issued during IOAGATE termination, it indicates that an internal problem probably prevented the task from shutting down smoothly.

The message ECAG15I is issued after a smooth shutdown.

The variables in this message are:

task - the IOAGATE task
taskId - the internal identity of the task
type - the internal type of the task
channelId - the identity of the channel to which the task belongs

Termination continues.

Corrective Action: No action is required.

ECAG25I modify_command

Explanation: This information message usually follows messages ECAG0BW and ECAG0CI, which indicate that an invalid modify command was issued. This message might appear more than once. Each occurrence displays a valid modify command.

Corrective Action: No action is required.

ECAG29E ECAGNRL FAILED. STD(taskId.type) FUNCTION(func) RC(rsn)

Explanation: IOAGATE detected an internal error. The IOAGATE task tried to run the ECAGNRL internal service routine.

The variables in this message are:

taskId - the internal identity of the IOAGATE task that tried to run the service routine
type - the internal type of IOAGATE task that tried to run the service routine
func - the internal numeric code of the function that IOAGATE tried to perform
rsn - an internal identity that IOAGATE assigned to this specific problem

IOAGATE may shut down or continue, depending on the severity of the failure.

Corrective Action: If IOAGATE shuts down, contact BMC Customer Support.

ECAG2AE FILE OF KEYS IS UNAVAILABLE, ENCRYPTION DISABLED

Explanation: IOAGATE failed to allocate the file of encryption keys that is needed to initialize the encryption environment that is requested because ENCRYPT is set to YES in the ECAPARM configuration file.

The encryption environment is not established. Processing continues without encryption.

Corrective Action: Prepare a valid file of encryption keys of the type required for encryption to operate, both on IOAGATE and the workstation. For more information, see the description of the ENCRYPT parameter in the IOA chapter of the INCONTROL for z/OS Installation Guide.

ECAG2BE ENCRYPTION ROUTINE routineName IS UNAVAILABLE, ENCRIPTION DISABLED

Explanation: IOAGATE failed to load the encryption and decryption routine routineName when trying to initialize the encryption environment requested because ENCRYPT was set to YES in the ECAPARM configuration file.

The encryption environment is not established. Processing continues without encryption.

Corrective Action: Contact BMC Customer Support.

ECAG30E ECAPUT FAILED(rsn:text) CALLID (module.call_typ.call_id.queue_typ) TASK(taskId.type.channelId)

Explanation: IOAGATE detected an internal error. The IOAGATE task tried to run the ECAPUT internal service routine.

The variables in this message are:

rsn - an internal identity that IOAGATE assigned to this specific problem
text - a description of the failure
module - the module that requested the service
call_typ - the internal call typeValid values are:
- SHORT - a short configuration of parameters was used in the call
- CONID - a conversation identity was specified in the call
- SOCKT - a TCP socket number was specified in the call
call_id - an internal call identity indicating the specific call inside the module
queue_typ - the type of internal queue for which this call was issuedValid values are:
- INQ - the input queue
- OUQ - the output queue
taskId - the internal identity of the task that requested the service
type - the internal type of the task that requested the service
channelId - the identity of the channel to which the task belongs

IOAGATE continues processing or shuts down, depending on the failure severity.

Corrective Action: If IOAGATE shuts down, contact BMC Customer Support.

ECAG31W IOAGATE(monitorId) WITH ECAPARM(suffix) ALREADY ACTIVE IN SYSTEM(systemId) LINDEX(linkageIndex)

Explanation: Start of IOAGATE was attempted while IOAGATE was already active in the system. Two IOAGATEs with the same ECAPARM configuration file cannot run concurrently.

The variables in this message are:

monitorId - the started task (STC) name of the IOAGATE
suffix - a 1-character identity that specifies a unique ECAPARM configuration file used in this IOAGATE run
systemId - the unique identity of the MVS system on which the IOAGATE is running
linkageIndex - the MVS linkage index that enables cross-memory communication between IOAGATE and its partner application server address spaces

The newly started IOAGATE shuts down.

Corrective Action: If you must run a second IOAGATE in the same system concurrently, create and use an ECAPARM configuration file with a unique suffix.

ECAG32I IOAGATE(monitorId) WITH ECAPARM(suffix) RUNNING IN SYSTEM(systemId)

Explanation: This information message displays some main system attributes of the active IOAGATE. The ECAG33I message follows this message with more main system attributes.

The variables in this message are:

monitorId - the started task (STC) name of the IOAGATE
suffix - a unique 1-character suffix that specifies the ECAPARM configuration file used in this IOAGATE run
systemId - the unique identity of the MVS system on which the IOAGATE is running

Corrective Action: No action is required.

ECAG33I LINDEX(linkageIndex) OBTAINED(date) QNAME(qName) RNAME(rName)

Explanation: This message displays some main system attributes of the active IOAGATE. During initialization, IOAGATE retrieves an MVS linkage index to perform cross memory communication with its partner application server address spaces. The linkage index obtained from MVS is kept by IOAGATE in an MVS name/token pair.

The ECAG32I message precedes this message and displays different system attributes.

The variables in this message are:

linkageIndex - the MVS linkage index
date - the date the MVS linkage index was obtained
qName - the major name of the IOAGATE system resource
rName - the minor name of the IOAGATE system resource

Corrective Action: No action is required.

ECAG34I SERVER TASK S T A T U S JOB/CHANNEL/SIID STEP/JOBID/MODULE UTILIZATION

Explanation: This information message indicates that an F IOAGATE,STATUS command was issued. It is a header for subsequent ECAG35I messages.

The STATUS command can be issued manually by the operator, or automatically by IOAGATE, as a result of internal problems.

Corrective Action: No action is required.

ECAG35I type taskId.addrSpaceId status channelId/siId step/jobId/mod utilization

Explanation: This information message specifies a server task of an application server address space that was issued.

The variables in this message are:

type - the server task type Valid values are:
- CM - the manager of the address space of an application server
- CS - application server
- CD - detector server
- CU - updater server
taskId - the internal identity of the server task assigned by IOAGATE during initializationThe first character is a code that indicates the application. If this server task is busy handling a request for an alias application, this code indicates the alias. The next three digits form a unique sequential number of the task.
addrSpaceId - the internal identity of the application server address space to which the specified task belongs

status - This variable has a primary status field (START, READY, UP, DOWN, BUSY, WAIT, SUSPEND, FAILED, PENDING or X'hexvalue'), and may include a secondary status filed and additional information next to it. Each status field is described in the following table, in the order listed, with its secondary status fields and additional information that may overflow into fields that follow.

Primary Status	Description, Secondary Status, and Information
START	The server task is starting. It may also show Time in seconds to handle a request, or be in a primary status. Startup timed out - The server did not startup within the required time.
READY	The server task started and is ready to handle requests. It may also show recovered to indicate that the server recovered successfully.
UP	Server task started, for a task that does not use cross-memory communication with the IOAGATE address space.
DOWN	The server task is down. It may also show one of the following to indicate an automatic recovery status or the reason for the DOWN status: awaits recovery - Recovery was suspended for this server task because of internal temporary problems. recovery disabled - Recovery was disabled for this server task because the MAXRECOV parameter of the ECAPARM configuration file is set to zero. recovery timed out - The server failed to recover before maximum time elapsed. recovery failed of threshold - Recovery was blocked for this server task because the MAXRECOV parameter of the ECAPARM configuration file is at its maximum value. stopped - The DOWN status is the result of automatic recovery stopping. failed - The DOWN status is the result of the failure of automatic recovery. unknown - There is no known reason for the DOWN status. timer on - The timer for the DOWN status is running.
BUSY	The server task is busy handling a request. May also show the time in seconds to handle a request.
WAIT	The non-CM server task is down and cannot be recovered until its CM server is ready. This may also show: Time in seconds to handle a request or being in a WAIT state. CM to be ready - Non CM server is waiting for its CM server to be ready.
SUSPEND	The server task failed and cannot be recovered for the time being due to temporary internal problems. May also show the time in seconds to handle a request or be in a SUSPEND state.
FAILED	The server task failed. May also show: timer on timer is running.
PENDING	IOAGATE is waiting for this server task to send an internal acknowledgment to IOAGATE address space. May also show: ACK pending - A server is in PENDING status. Time in seconds to handle a request or be in a PENDING state.
X’ hex_value'	The status of a server task is unknown. May also show: unexpected status - Unknown status is represented by the combination of internal status flags. SST damaged - An internal control block that describes a server task is damaged.

channelId/ siId - This field shows more status field information, or specifies the channel and service request in two parts, channelId and siId, where
channelId is the ID of the channel linked to the indicated server task in the ECAPARM configuration file The first two characters specify the channel ID assigned in the ECAPARM configuration file. The rest of channelId is MULTI or DUAL, where MULTI is for a multiple connection (MC) model of a communication channel, and DUAL is for a dual connection (DC) model of a communication channel.
siId is a Service Instance ID (SIID) that specifies the service request being handled by a server taskThe value is displayed only when the status of a server task is BUSY.
step - the step name of a startup JCL procedure used to run the application server address spaceThis is displayed for a CM server task only.
jobId - the STC JOBID of the application server assigned to its address space by JES This is displayed for a CM server task only.
mod - the name of the program that implements the server task This is displayed for a CM server task only.
utilization - the percent of time the server task was busy handling the request during the last 40 seconds

Corrective Action: No action is required.

ECAG36W APPL.SERVER(addrSpaceId) CANNOT BE STOPPED

Explanation: An attempt to issue an F IOAGATE,STOPASID= addrSpaceId command failed. Either the specified address space ID is not ready or the server address space is already down.

In this message, addrSpaceId is the internal ID of the application server address space.

The modify command is rejected. Normal processing continues.

Corrective Action: Use the F IOAGATE,STATUS command to check the status of the server address space.

ECAG37I STOP FOR APPL.SERVER (applServer.addrSpaceId) INITIATED

Explanation: This information message indicates that an F IOAGATE,STOPASID=addrSpaceId command was performed successfully. A STOPASID command shuts down a specific application server address space.

The variables in this message are:

applServer - the full name of the application server
addrSpaceId - the internal identity of the application server address space

Corrective Action: No action is required.

ECAG38I IOAGATE(monitorId) WITH ECAPARM(suffix) EXCLUSIVELY OWNS HEARTBEAT RESOURCE Q(qName) R(rName)

Explanation: This information message displays the name of the heartbeat resource of the running IOAGATE for a specific application server. When the application server is launched, IOAGATE issues a heartbeat ENQ request to acquire the specified resource exclusively as a heartbeat mechanism between the application server and IOAGATE. If the resource is available in the application server address space, it means that the IOAGATE stopped.

IOAGATE acquires a heartbeat resource for each application server it launches.

The variables in this message are:

monitorId - the STC name of the IOAGATE
suffix - a unique 1-character suffix identifying the ECAPARM configuration file that is used in this IOAGATE run
qName - the major name of the heartbeat resource
rName - the minor name of the heartbeat resourceAn application server ID acts as the minor name.

Corrective Action: No action is required.

ECAG39W SERVER TASK(taskId) CURRENTLY CANNOT BE STOPPED

Explanation: An attempt to issue an F IOAGATE,STOPTID=taskId command to stop the specified server task failed. The specified server task is either not ready, or is already down.

In this message, taskId is the internal ID of a server task.

The modify command is rejected. Normal processing continues.

Corrective Action: Use the F IOAGATE,STATUS command to check the status of the server task, and reissue the command later.

ECAG3AS FAILURE(rsn) TO CREATE A NEW NAME/TOKEN PAIR ON SYSTEM LEVEL

Explanation: IOAGATE failed to create a new MVS name or token pair in which to keep a linkage index. During initialization, IOAGATE obtains a linkage index to perform cross memory communication with its partner application server address spaces. IOAGATE keeps the linkage index in an MVS name or token pair.

Possible values of rsn are:

04 - duplicated name used
16 - user not authorized
28 - parameter LEVEL invalid
32 - parameter NAME invalid
36 - parameter PERSIST invalid
64 - unexpected error

IOAGATE shuts down.

Corrective Action: Call your system programmer for assistance.

ECAG3BW SERVER TASK(taskId) DOES NOT EXIST

Explanation: An attempt to issue an F IOAGATE,STOPTID=taskId command to stop the specified server task failed, because the specified server task ID was incorrect. The variable taskId must be a correct internal ID of a server task.

The modify command is rejected. Normal processing continues.

Corrective Action: Use the F IOAGATE,STATUS command to identify the correct taskId, and reissue the command.

ECAG3CI PUTTER(taskId.type) submitting controlMsg for Server(serverId)

Explanation: This information message indicates that a PUTTER task of IOAGATE submitted the internal control message controlMsg for the application server serverId.

Corrective Action: No action is required.

ECAG3DI GETTER(taskId.type) controlMsg confirmed for Server(serverId)

Explanation: An IOAGATE GETTER task of IOAGATE received a confirmation for the internal control message controlMsg sent earlier by an IOAGATE PUTTER task. The confirmation control message controlMsg was sent by the application server serverId.

Corrective Action: No action is required.

ECAG3EW PUTTER(taskId.type) Obsolete SIB thrown away, SIID=siId APPL=appl SID=serviceId Time difference=timeDiff

Explanation: An IOAGATE PUTTER task discovered an irrelevant SIB internal control block with the attributes identified in this message. The problematic control block was created before the specified PUTTER task was started.

The variables in this message are:

taskId - the internal ID of this PUTTER task
type - the type of this PUTTER task
siId - the Service Instance ID
appl - the application code
serviceId - the identity of the Service
timeDiff - The time difference between the time when the problematic SIB block was created and the time when the PUTTER task started.

The SIB control block is destroyed. Normal processing continues.

Corrective Action: No action is required.

ECAG3FW FAILURE TO UNLOCK CHAIN OF SIBs:ALREADY UNLOCKED UNLOCKER (taskId.type.callId):module

Explanation: This warning message is issued if the chain of SIB control blocks is already unlocked when attempting to unlock it.

Corrective Action: No action is required.

ECAG3GS FAILURE TO UNLOCK CHAIN OF SIBs:LOCKED BY (taskId) UNLOCKER (taskId.type.callId):module

Explanation: This severe error message is issued if the chain of SIB control blocks has been locked by some other task, indicated by LOCKED BY (taskId) when attempting to unlock it. In this case, the unrecoverable error indicator is set to ON, SVCDUMP is initiated, and IOAGATE goes down.

Corrective Action: No action is required.

ECAG3HI IOAGATE Token: Name=tokenName LX=index Obtained=date System=systemName

Explanation: This information message indicates that the F IOAGATE,SHOWTOKEN modify command was issued in the IOAGATE address space to display the MVS token of the current IOAGATE.

The variables in this message are:

tokenName - the name of the MVS token of the current IOAGATE
index - the Linkage Index used by this IOAGATE to establish cross-memory communication
date - the date when the Linkage Index of IOAGATE was obtained from MVS
systemName - the name of the MVS system on which the current IOAGATE is running

Corrective Action: No action is required.

ECAG3IW LAST READY CS SUBTASK IN (xxxx.yyyy) ASSIGNED. OCCURED (nnn) TIMES.

Explanation: The message is issued when IOAGATE assigns a transaction to the last ready CS server subtask in an application server address space that serves Control-D/Page ON Demand requests. This message will not be issued more than once per minute in order not to flood the console with such messages.

The variables in this message are:

xxxx is the procedure name of the application server.
yyyy is the qualifier (after the dot) of the specific application server address space. The qualifier allows distinguishing between the address spaces when multiple application server address spaces are started.
nnn is the number of times the last ready CS has been assigned since the last time message ECAG3IW has been issued, including the current occurrence for which this ECAG3IW is issued.

For example, if the following messages appear:

10:05:00 ECAG3IW ...OCCURED (001) TIMES.

10:06:00 ECAG3IW ...OCCURED (005) TIMES.

This means that at 10:05:00 the last ready CS has been assigned and that in the following minute the last ready CS has been assigned 5 times.

When the last ready CS is assigned, it means that any new request must wait until a busy CS in the same address space finishes handling its request and becomes ready.

Corrective Action: In general, BMC recommends that you define enough CS subtasks and application server address spaces so that this situation rarely, if ever, occurs.

ECAG40W APPL.SERVER (applServer.addrSpaceId) CANNOT BE STARTED, CHANNEL(channelId) DISABLED

Explanation: The specified application server cannot be started. During initialization, IOAGATE detected errors in the indicated CHANNEL definition and disabled it. As a result, the application server that referenced this channel became unusable.

Variables in this message are:

applServer - the full name of the application server
addrSpaceId - the internal identity of an application server address space
channelId - the channel identity referenced by the application server

Corrective Action: Check the IOAGATE DAIGLOG log and the DATRACE log for more information. Try to correct the CHANNEL definition, and restart IOAGATE.

ECAG41E SERVER TASK (applServer.type.taskId.addrSpaceId) FAILED WHEN HANDLING A REQUEST, USER(userId) SIID(serviceInstanceId)

Explanation: IOAGATE detected a server task failure. The server task was handling the specified user request when IOAGATE detected the failure.

Attributes of the failed server are:

applServer - the name of the application server
type - the server task type. Valid values are:
- CM - the manager of the address space of an application server
- CS - application server
- CD - detector server
- CU - updater server
taskId - the internal identity of this server task
addrSpaceId - the internal identity of the application server address space to which the specified server task belongs
userId - the identity of the user whose request was in process
serviceInstanceId - the service instance ID (SIID) that determines the service request being handled by the server task

IOAGATE does the following:

clears resources allocated by cross memory communication with the failed server task
initiates automatic recovery for the failed server task, if the option was not blocked by MAXRECOV parameter in the ECAPARM configuration file
continues communication with other server tasks.

Corrective Action: Check the error messages of the application server address space to determine why the server task terminated. Fix the problem and try again.

ECAG43W AN ATTEMPT TO CREATE A MESSAGE FOR appl REMOTE APPLICATION FAILED rsn

Explanation: IOAGATE failed to create a notification message for a remote IOAGATE that supports the application appl. The reason for the failure is identified by the variable rsn.

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

Possible values for rsn are:

No PDTs are available
The proper PDT is not available
The PLT table is not available
No PLTs are available
The proper PLT is not available

Corrective Action: Contact BMC Customer Support.

ECAG46W APPL.SERVER (applServer.type.taskId.addrSpaceId. channelId) ALREADY ACTIVE

Explanation: An F IOAGATE,STARTASID= addrSpaceId command failed. Either the specified ID is invalid, or this server address space is already up.

The variables in this message are:

applServer - the name of the application server
type - the CM server task type
taskId- the internal identity of this server task
addrSpaceId - the internal identity of this application server address space
channelId - the identity of the channel to which the specified application server is linked

The modify command is rejected.

Corrective Action: Correct the application server address space ID, and reissue the command.

ECAG47I START FOR APPLICATION SERVER(applServer.addrSpaceId) INITIATED

Explanation: This information message indicates that an F IOAGATE,STARTASID=addrSpaceId command was performed successfully. The STARTASID command starts a specific application server address space.

The variables in this message are:

applServer - the name of the application server
addrSpaceId - the internal identity of the application server address space

Corrective Action: No action is required.

ECAG49I CHANNEL(channelId.SNA) USER(userId) LOGGED ON, CONVID(conversation_id) APPLID(applId)

Explanation: This information message indicates that the specified user successfully logged on to IOAGATE over a multiple connection (MC) SNA channel.

The variables in this message are:

channelId - the identity of the channel over which the specified user logged on to IOAGATE
userId- the identity of the user whose logon request was performed
conversation_id- VTAM LU 6.2 (APPC) conversation identity
applId - VTAM LU 6.2 (APPC) application identity of the partner

Corrective Action: No action is required.

ECAG4AI STOP FOR SERVER TASK (applServer.type.taskId.addrSpaceId) INITIATED

Explanation: This information message indicates that an F IOAGATE,STOPASID=addrSpaceId command was issued and performed successfully. The STOPASID command shuts down a specific application server address space.

The variables in this message are:

applServer - the name of the application server shut down
type - the CS server task type
taskId - the internal identity of this server task
addrSpaceId - the internal identity of the application server address space

Corrective Action: No action is required.

ECAG4BE SERVER TASK(applServer.type.taskId.addrSpaceId) FAILED WHEN BEING STARTED

Explanation: IOAGATE detected a server task failure before the task completed its startup.

The variables in this message are:

applServer - the full name of the application server
type - the server task type Valid values are:
- CD - detector server
- CS - application server
- CU - updater server
taskId - the internal identity of this server task
addrSpaceId - the internal identity of the application server address space to which the failed server task is assigned

Automatic recovery is initiated for the failed server task if the option was not blocked by the MAXRECOV parameter in the ECAPARM configuration file, and processing continues.

Corrective Action: Check the error messages of the application server address space to determine why the server task failed, try to fix the problem, and try again.

ECAG4CE APPL.SERVER (applServer.type.task-id.addrSpaceId. channelId) FAILED WHEN BEING STARTED

Explanation: IOAGATE detected an application server failure before the server completed its startup.

The variables in this message are:

applServer - the name of the application server
type - the CM server task type
taskId- the internal identity of this application server task
addrSpaceId - the internal identity of the application server address space
channelId - the identity of the channel to which the application server is linked

Automatic recovery is initiated for the failed application server if the option was not blocked by the MAXRECOV parameter in the ECAPARM configuration file. Processing continues.

Corrective Action: Check the error messages of the application server address space to determine why the application server failed, try to fix the problem, and restart IOAGATE.

ECAG4DE SERVER TASK (applServerName.type.taskId.addrSpaceId) FAILED

Explanation: IOAGATE detected a server task failure.

The variables in this message are:

applServer - the name of the application server
type - the server task typeValid values are:
- CD - detector server
- CS - application server
- CU - updater server
taskId - the internal identity of this server task
addrSpaceId - the internal identity of the application server address space to which the failed server task is assigned

IOAGATE does the following:

clears resources allocated for cross memory communication with the failed server task
initiates automatic recovery for the failed server task, if the option was not blocked by MAXRECOV parameter in the ECAPARM configuration file
continues communication with other server tasks.

Corrective Action: Check the error messages of the application server address space to determine why the server task failed, try to fix the problem, and restart IOAGATE.

ECAG4GI SERVER TASK (applServerName.type.taskId.addrSpaceId) HAS BEEN STOPPED BY OPERATOR

Explanation: This information message indicates that the operator issued the command F IOAGATE,STOPTID=taskId, and that command was successfully performed. The STOPTID command shuts down a specific server task.

The variables in this message are:

applServerName - the name of the application supported by the server that was stopped
type - the internal type of the server task that was stopped
taskId - the internal identity of this server task
addrSpaceId - the internal identity of the application server address space to which this server task is assigned

Corrective Action: No action is required.

ECAG4HW APPL.SERVER(addrSpaceId) DOES NOT EXIST

Explanation: An F IOAGATE,STARTASID=addrSpaceId command was issued by the operator, and failed. The STARTASID command starts a specific application server address space that either was shut down or failed. The specified address space ID (addrSpaceId) is not a valid address space ID.

In this message, addrSpaceId is the invalid address space ID that was specified.

Corrective Action: Correct the address space ID and reissue the command.

ECAG4IW APPL.SERVER (applServerName.type.taskId.addrSpaceId.channelId/jobId) WENT DOWN BECAUSE OPERATOR STOPPED SERVER TASK(taskId)

Explanation: The specified application server address space went down because an operator stopped the single or last active CS server task running under the control of the identified application server.

The variables in this message are:

applServer - name of the application supported by the server that has gone down
type - the internal type of the server task that has gone down
taskId - the internal identity of the server task that has gone down
addrSpaceId - the internal identity of the application server address space to which the server task that has gone down is assigned
channelId - the identity of the channel to which the identified application server is linked
jobId - STC JOBID of the application server assigned to its address space by JES

Corrective Action: No action is required.

ECAG4JI TERMINATION FOR SERVER TASK(applServer.type.taskId.addrSpaceId) INITIATED

Explanation: An F IOAGATE, CTID= taskId CANCEL TASK modify command has been issued by the user.

The variables in this message are:

applServer - the name of the application supported by the server to which the modify command was issued
type - the internal type of the server task which is to be terminated
taskId - the internal identity of the server task which is to be terminated
addrSpaceId - the internal identity of the application server address space to which the task taskId is assigned

IOAGATE issues an internal control message that causes the application server address space addrSpaceId to terminate the server task taskId. Normal processing continues.

Corrective Action: No action is required.

ECAG4KW SERVER TASK(applServer.type.taskId.addrSpaceId) HAS BEEN TERMINATED BY IOAGATE, USER(userId) SIID(serviceInstanceId)

Explanation: The specified server task has been terminated by IOAGATE.

The variables in this message are:

applServer - the name of the application supported by the server on which the task was terminated
type - the internal type of the server task that was terminated
taskId - the internal identity of the server task that was terminated
addrSpaceId - the internal identity of the application server address space to which the terminated server task taskId is assigned

Corrective Action: Analyze the IOAGATE outputs to identify the reason of the termination. If the problem persists, contact BMC Customer Support.

ECAG4LE APPL.SERVER (applServerName.addrSpaceId.proc.stcId-channelId/jobId) FAILED

Explanation: The specified application server address space failed.

The variables in this message are:

applServer - name of the application supported by the server that has gone down
addrSpaceId - the internal identity of the application server address space to which the server task that has gone down is assigned
proc - the name of the procedure of the application server address space
stcId - the name of the JCL procedure used to start the application server address space
channelId - the identity of the channel to which the identified application server is linked
jobId - STC JOBID of the application server assigned to its address space by JES

Normal processing continues, and, if recovery is not blocked for this application server, the IOAGATE tries to recover the server.

Corrective Action: No action is required.

ECAG50I CHANNEL(channelId.SNA) DEALLOCATE RECEIVED FROM PARTNER, APPLID(applId) CONVID(conversation_id)

Explanation: This information message indicates that a DEALLOCATE APPC command was received from a client or partner IOAGATE for the specified conversation ID.

The variables in this message are:

channelId - the identity of the channel over which the conversation that was deallocated was established
applId - VTAM LU 6.2 (APPC) application ID of the IOAGATE
conversation_id - VTAM LU 6.2 (APPC) internal conversation identity

Corrective Action: No action is required.

ECAG55W CHANNEL(channelId.protocol) TASK(taskId.type) IS STARTING UP ALTHOUGH NO APPL.SERVER HAS COME UP YET

Explanation: A communication channel has waited for at least one application server linked to the channelId channel to become ready, but none has come up.

The variables in this message are:

channelId - the identity of the channel to which the problematic application server is linked
protocol - the communication protocol used by the current channel. Valid values are:
- TCP - TCP/IP
- SNA - SNA
taskId - the internal identity of this channel task
type - the internal type of this channel

IOAGATE discontinues waiting until at least one application server linked to the channelId channel is ready. The channelId channel continues initializing.

Corrective Action: This warning message may, but does not necessarily, indicate a real problem on the application server. Examine the JES logs of all application servers linked to the channelId channel and try to find the cause for the failure of the application server to start in time.

ECAG56I REJECTED:SID=serviceId SIID=serviceInstanceId SEQ= seqNumber APPLIC=appl ASID=addressSpaceId LAST=turn_around C/E=compression/encryption TYPE=t1 /t2 /t3. USER=userId

Explanation: This message follows the messages ECAC60E, ECAC61E, ECAC62E, ECAC64E, ECAC65E, ECAC66E, ECAC67E, ECAC68E, ECAC6CE, ECAC6DE, ECAC6EE, ECAC6FE, ECAC6GE, ECAC6HE, ECAC6IE, ECAC6ME, ECAG58E, and provides details of the rejected transaction.

The variables in the message are:

serviceId - the type of the transaction that was rejected
serviceInstanceId - the service instance identity (SIID) of the transaction rejected by IOAGATE
seqNumber - the sequential number of the rejected message in a given direction within the same transactionThese numbers start from 000001.
appl - the short code of the application to which the rejected transaction was assigned
addressSpaceId - the internal address space identity of the application server to which the rejected transaction was assigned
turn_around - internal indication of the nature of the transaction. Valid values are:
- T - Turn AroundThis was the last message in this direction and a response was required
- L - LastThe current message was the last in the service, meaning, the end of transaction.
- ' ' (Blank) - the current message was not the last in the service, and more messages are expected
compression - whether compression is in use. Valid values are:
- A (Accept) - Used only by D applications, to indicate that the D client will accept compressed data from IOAGATE.
- D (Compressed) - Used only by D applications, to indicate that this message contains compressed data.
- Y - Compression is in use.
- I (Ignore) - The compression indication field is used differently.
- ' ' (Blank) - No compression is in use.
encryption - whether encryption is in use. Valid values are:
- Y (Yes) - DES or 3DES encryption is in use.
- ' ' (Blank - No encryption is in use.
t1 - whether the message is regular or extended. Valid values are:
- R (Regular) - The message is regular.
- E (Extended) - The message is extended.
t2 - indicates the message type. Valid values are:
- B - Big message
- C - Confirmation
- D - Data
- E - Error
- F - End of download or upload
- R - Request
- S - Start of download or upload
- ( - Start of file transfer
- ) - End of file transfer
t3 - indicates the record type. Valid values are:
- ! - Do not Process the message indication
- A - Handshake CONNECT message
- C - Handshake CONFIRM message
- R - Handshake REJECT message
- I - Handshake Information message
- A - Active job file record
- A - Attach request
- B - Short database update
- C - Condition
- C - Communication update message
- D - Cancel request
- F - Modify server request
- F - Force job
- G - Synchronization record
- H - Control resource
- I - Initialization
- J - Edit JCL
- L - Log
- M - Internal IOAGATE message
- N - New job
- O - Order job
- Q - Quantitative resource
- R - Control resource
- S - Statistics record
- T - Alert
- V - View sysout file
- Z - WS Synchronization record
userId - the identity of the user associated with this transaction

Corrective Action: No action is required.

ECAG57W CHANNEL(channelId.protocol) TASK(taskId.type) IS STARTING UP ALTHOUGH APPL.SERVER(applServerId -addrSpaceId) HAS NOT COME UP YET

Explanation: The channelId communication channel has waited for the applServer application server that is linked to become ready, but applServer has not come up.

The variables in this message are:

channelId - the identity of the channel to which the problematic application server is linked
protocol - the communication protocol used by the current channel. Valid values are:
- TCP - TCP/IP
- SNA - SNA
taskId - the internal identity of this channel task
type - the internal type of the channelId channel
applServerId - the internal identity of the application server linked to the channelId channel
addrSpaceId - the internal identity of the application server address space linked to the channelId channel

IOAGATE discontinues waiting until at the application server linked to the channelId channel is ready. The channelId channel continues initializing.

Corrective Action: This warning message may, but does not necessarily, indicate a real problem on the application server. Examine the JES log of the applicId application server and try to find out why the application server failed to start in time.

ECAG58E CHANNEL(channelId.protocol) TASK(taskId.type) TIMEOUT OCCURRED WHILE WAITING FOR A MESSAGE FROM PARTNER

Explanation: This information message indicates that a request was canceled because an expected message did not arrive within a defined time-out interval.

The variables in this message are:

channelId - the identity of the channel in which the specified time-out occurred
protocol - the communication protocol used by the current channel. Valid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
taskId - the internal ID of this channel task
type - the internal type of this channel

If the expected message is not critical, IOAGATE continues executing. If the expected message is critical, the corresponding SNA channel goes down.

Corrective Action: If the problem persists, call BMC Customer Support for assistance.

ECAG59W CHANNEL(channelId.protocol) TASK(taskId.type) "DO NOT PROCESS" INDICATION RECEIVED, MESSAGE DISCARDED

Explanation: This information message indicates that the specified channel received a request with a "Do not process (!)" indication.

The variables in this message are:

channelId - the identity of the channel in which the specified event occurred
protocol - the communication protocol used by the current channel. Valid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
taskId - the internal ID of this channel task
type - the internal type of this channel

Corrective Action: No action is required.

ECAG5AI DISCARDED: msg

Explanation: This message follows ECAG59W or ECAG5BW and displays the discarded transaction.

Corrective Action: No action is required.

ECAG5BW CHANNEL(channelId.protocol) TASK(taskId.type) HANDSHAKE MESSAGE REJECTED: THERE IS NO MAP SPECIFIED

Explanation: This message warns that the specified channel received a handshake used by IOAGATE-to-IOAGATE communication, but the local IOAGATE is not configured to be a partner IOAGATE.

The variables in this message are:

channelId - the identity of the channel that detected the event
protocol - the communication protocol used by the channe. Valid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
taskId - the internal identity of the channel task that detected the event
type - the internal type of the channel task that detected the event

Corrective Action: No action is required.

ECAG5CI CHANNEL(channelId.protocol) processed FOR INCOMING CONNECTIONS, APPLICATION(applicId)

Explanation: This information message indicates that an F IOAGATE,<cmd_modify> command was successfully performed.

The variables in this message are:

channelId - the identity of the channel against which the modify command was performed
protocol - the communication protocol used by channelId. Valid values are:
- TCP - TCP/IP
- SNA - SNA
processed - the type of action. Valid values are:
- CLOSED - channelId has been successfully closed for incoming connections
- OPENED - channelId has been successfully opened for incoming connections
applicId - the identity of the application that channelId serves

Corrective Action: No action is required.

ECAG5DI IOAGATE WILL BE SHUT DOWN AS SOON AS ALL CLIENTS HAVE DISCONNECTED

Explanation: This information message indicates that an F IOAGATE,CLOSE=ALL,SHUT modify command was successfully performed.

Processing continues. IOAGATE will be shut down as soon as all active clients have been disconnected.

Corrective Action: No action is required.

ECAG5EW SHUT SPECIFICATION REJECTED, THERE ARE OPEN CHANNELS

Explanation: An F IOAGATE,CLOSE=channelId,SHUT modify command was issued but the SHUT subcommand was rejected because a channel was found to be open and active.

Corrective Action: If required, close the open channels and re-issue the F IOAGATE,CLOSE=ALL,SHUT modify command.

ECAG5FW MODIFY(OPEN=ALL) IGNORED, ALL CHANNELS OPEN

Explanation: An F IOAGATE,OPEN=ALL modify command was issued, but was rejected because all active channels are already open.

Corrective Action: No action is required.

ECAG5GI SHUT COMMAND ISSUED EARLIER BY "CLOSE,SHUT" HAS BEEN CANCELED

Explanation: An F IOAGATE,OPEN=ALL/ channelId modify command was issued, but the CLOSE=ALL,SHUT command had already been issued.

The action that was ordered by the SHUT subcommand has been canceled.

Corrective Action: No action is required.

ECAG5HI IOAGATE GOES DOWN DUE TO COMMAND "CLOSE=.,SHUT" ISSUED EARLIER

Explanation: An F IOAGATE,OPEN=ALL,SHUT modify command was issued some time ago, and all active clients have been disconnected.

IOAGATE goes down.

Corrective Action: No action is required.

ECAG5II CHANNEL(channelId.protocol) TASK(taskId.type) INCOMING CONNECTION REJECTED: CHANNEL CLOSED

Explanation: This information message indicates that an F IOAGATE,CLOSE=ALL/ channelId modify command was issued against the channelId channel, and this channel was closed.

The variables in this message are:

channelId - the identity of the channel that was closed by the modify command
protocol - the communication protocol used by channelId. Valid values are:
- TCP - TCP/IP
- SNA - SNA
taskId - the internal identity of the channel task that detected the connection attempt
type - the internal type of the taskId channel task

The attempt to connect to the channelId channel is rejected. Normal processing continues.

Corrective Action: No action is required.

ECAG5TE LE PREINITIALIZATION FAILED, MOD=modname,FUNC=function,RC=return_code

Explanation: Language Environment Preinitialization services is used to create a persistent C environment for INCONTROL C programs. An error occurred while using this facility. The subtask involved will be abended with code U0186.

The variables are defined as follows:

modname - name of the program that issued the call
function – one of the following:
- INIT – environment initialization
- CSUB,TRM-CSUB – calling a C program
- TERM – terminating the environment
return_code (selection):
- rc= 8: failure to load a C program. Program might be missing from STEPLIB.
- rc=12: insufficient storage for the preinitialization environment
- rc=16: An active environment already exists
- rc=32: Abend occurred in preinitialization services

Corrective Action:

For INIT return codes 8 or 12, check your environment. In other cases, notify BMC Customer Support.
For a Control-D PC transfer, a previous error (such as, an error reading the file during the transfer or an abend in the transmission program) might have caused this error. For immediate transfers, exit and enter the online session before trying more transfers.
For IOAGATE or Control-M monitor, if they shut down, restart them.

ECAG5UE TCP/IP STACK stack UNAVAILABLE, ERRNO=errno. CHANNEL channelId DISABLED.

Explanation: An IOAGATE channel was defined with ESTACK=stack in ECAPARMx. The z/OS system has dual stack mode TCP/IP, but the specified stack is not running.

Corrective Action: Either bring up the started task specified in ESTACK parameter, or remove the ESTACK parameter. Then recycle IOAGATE.

ECAG61S CHANNEL(channelId.SNA) IOAGATE INTERNAL COMMUNICATION ERROR, SEND INDICATION NOT RECEIVED

Explanation: IOAGATE discovered a protocol violation. After the sending side of a dual connection (DC) SNA channel allocates a conversation with its partner or client, the partner application should reverse the conversation direction. Due to a protocol violation, the conversation direction was not reversed. This message can occur only for dual connection (DC) SNA channels.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG62I CHANNEL(channelId.TCP) COMTASK(taskId) SOCKET(socket) USER(userId) LOGGED ON FROM ipAdd

Explanation: This information message indicates that a user successfully logged on to IOAGATE over a multiple connection (MC) TCP channel.

The variables in this message are:

channelId - the identity of the channel on which this user logged on to IOAGATE
taskId - the identity of the TCP/IP communication task to which this user was assigned
socket - TCP/IP socket number of this connection
userId - the identity of the user who logged on
ipAdd - IP address of the user that logged on

Corrective Action: No action is required.

ECAG63I CHANNEL(channelId.SNA) DEALLOCATE SENT TO PARTNER, APPLID(applId) LU(luName)

Explanation: This information message indicates that a DEALLOCATE APPC command was sent to a partner or client.

Conversation parameters:

channelId - the identity of the channel this partner or client was using
applId - VTAM LU 6.2 (APPC) application ID of the IOAGATE
luName - VTAM LU 6.2 (APPC) LU name of the partner or client

Corrective Action: No action is required.

ECAG64I CHANNEL(channelId.SNA) CONVERSATION STARTED WITH PARTNER APPLID(applId) LU(luName) MODE(mode)

Explanation: This information message indicates that a conversation started between IOAGATE and its partner or client. The specified partner or client started a conversation with IOAGATE. The message can be issued for a dual connection (DC) SNA channel only.

Conversation parameters are:

channelId - the identity of the channel on which the specified conversation started
applId - VTAM LU 6.2 (APPC) application identity of the IOAGATE
luName - VTAM LU 6.2 (APPC) LU name of the partner or client
mode - the mode in use. Valid values are:
- SENDER - the sender mode of the DC SNA channel conversation
- RECEIVER - the receiver mode of the DC SNA channel conversation

Corrective Action: No action is required.

ECAG65I CHANNEL(channelId.SNA) DEALLOCATE RECEIVED FROM PARTNER APPLID(applId) LU(luName)

Explanation: This information message indicates that a DEALLOCATE APPC command was received from a partner or client. The partner deallocated the conversation with IOAGATE.

Conversation parameters are:

channelId - the identity of the channel over which the specified conversation was occurring when it was terminated
applId - VTAM LU 6.2 (APPC) application identity of the IOAGATE
luName - VTAM LU 6.2 (APPC) LU name of the partner or client

Corrective Action: No action is required.

ECAG66W CHANNEL(channelId.SNA) TPEND EXIT INVOKED, APPLID(applId) LU(luName) REASON(rsn)

Explanation: The VTAM operator broke the connection between the partner or client and the indicated SNA channel. This message indicates that the TPEND exit was invoked.

Attributes of the connection are:

channelId - the identity of the SNA channel that was connected to the partner or client
applId - VTAM LU 6.2 (APPC) application identity of the IOAGATE
luName - VTAM LU 6.2 (APPC) LU name of the partner or client
rsn - code indicating what happenedFor the explanation for each value of rsn, see the VTAM Programming for LU 6.2 Manual

Processing continues, and IOAGATE tries to recycle the specified SNA channel.

Corrective Action: For an explanation of TPEND reason codes, see the VTAM Programming for LU 6.2 Manual. Call your system programmer for assistance.

ECAG67W CHANNEL(channelId.SNA) ATTN LOSS EXIT INVOKED, APPLID(applId) LU(luName)

Explanation: The partner or client and IOAGATE were disconnected. This message precedes the message ECAG68I, which contains VTAM diagnostic information.

The attributes of the broken connection are:

channelId - the identity of the channel on which the disconnection occurred
applId - VTAM LU 6.2 (APPC) application identity of the IOAGATE
luName - VTAM LU 6.2 (APPC) LU name of the partner or client

IOAGATE attempts to recycle the indicated SNA channel.

Corrective Action: Read the message ECAG68I to identify and fix the problem, if possible. If you cannot resolve the problem, call your system programmer for assistance.

ECAG68I RPL6SNSI(rpl6sns_code) RPL6RC(rpl6rsn_code) RPL6DETP(rpl6detp_code) RPLSONCD(rplsoncd_code)

Explanation: This information message displays VTAM diagnostic information for a network systems programmer. It follows message ECAG67W, which announces disconnection of IOAGATE from its partner or client.

RPL6 fields that are documented in the VTAM Programming for LU 6.2 are:

rpl6sns_code - sense code returned by VTAM
rpl6rsn_code - RPL6 reason code returned by VTAM
rpl6detp_code - DETP reason code returned by VTAM
rplsoncd_code - SONCD UNBIND type code returned by VTAM

Corrective Action: Try to determine the cause of the problem, and correct it. If you cannot resolve the problem, call your system programmer for assistance.

ECAG69I CHANNEL(channelId.SNA) READY FOR COMMUNICATIONS, APPLID(applId)

Explanation: This information message indicates that the SNA channel of the IOAGATE is waiting for an ALLOCATE request from a partner or client. This message is issued during a multiple connection (MC) SNA channel startup.

Attributes of the SNA channel are:

channelId - the identity of the channel that is ready for communications
applId - VTAM LU 6.2 (APPC) application ID of the IOAGATE

Corrective Action: No action is required.

ECAG70I PROBABLE CAUSE: TEMPORARY STORAGE SHORTAGE

Explanation: This information message indicates that the probable reason for the failure of a VTAM request is a temporary shortage of main storage for VTAM. This message follows a message that announces failure of a VTAM request, such as an APPC command, or an OPEN or CLOSE ACB command, and precedes message ECAG81I, ECAG84I, or ECAG85I, which indicates the action that will be taken by IOAGATE. This message can be issued for an SNA channel only.

Processing continues, but the SNA channel fails.

Corrective Action: If the problem persists, consider tuning the VTAM buffer. Call your system programmer for assistance.

ECAG71I PROBABLE CAUSE: VTAM IS HALTING

Explanation: This information message indicates that VTAM is probably going down. This message follows a message that announces failure of a VTAM request, such as an APPC command, or an OPEN or CLOSE ACB command. It precedes message ECAG81I, ECAG84I, or ECAG85I, which indicates the action that will be taken by IOAGATE. This message can be issued for an SNA channel only.

SNA channel fails. Processing continues.

Corrective Action: If the problem persists, call your system programmer for assistance.

ECAG72I PROBABLE CAUSE: APPLID NOT DEFINED

Explanation: This information message indicates that the probable reason for the failure of a VTAM OPEN ACB command is that VTAM does not recognize the VTAM LU 6.2 (APPC) application ID specified in the OPEN ACB command. This message follows message ECAG91W, which announces the command failure, and precedes message ECAG83E, which specifies the action that will be taken by IOAGATE. This message can be issued for an SNA channel only.

Possible causes are:

The Major node where APPLID is defined is not active.
The APPLID defined to VTAM does not match the APPLID or APPLIDS defined to IOAGATE in the ECAPARM SNA channel declaration.

Processing continues, but the SNA channel fails.

Corrective Action: Activate the Major node, or correct the APPLID or APPLIDS specifications in the SNA channel declaration in the ECAPARM configuration file. If the problem persists, call your system programmer for assistance.

ECAG73I PROBABLE CAUSE: APPLID DEFINED IMPROPERLY

Explanation: This information message indicates that the probable reason for failure of a VTAM OPEN ACB command is that the VTAM LU 6.2 (APPC) application ID specified in the OPEN ACB command is probably not a valid application definition, although it is known to VTAM. This could happen, for instance, if the APPLID or APPLIDS defined to IOAGATE in the ECAPARM configuration file is incorrect, but happens to match the name of another resource known to VTAM.

This message follows a message that announces failure of the VTAM OPEN ACB command, and precedes message ECAG83E, which specifies the action that will be taken by the IOAGATE. This message can be issued for an SNA channel only.

Processing continues, but the SNA channel fails.

Corrective Action: Correct the APPLID or APPLIDS specifications in the SNA channel declaration in the ECAPARM configuration file. If the problem persists, call your system programmer for assistance.

ECAG74I PROBABLE CAUSE: ACB HAS ALREADY BEEN OPENED

Explanation: This information message indicates that the probable reason for the failure of a VTAM OPEN ACB command is that the VTAM LU 6.2 (APPC) application ID specified in the OPEN ACB command is already open and in use by another application.

Possible causes are:

Another IOAGATE with the same APPLID is already up.
The APPLID defined to the IOAGATE in the ECAPARM configuration file is incorrect, but matches the name of another resource known to VTAM.

This message precedes message ECAG85I, which specifies the action that will be taken by IOAGATE. This message can be issued for an SNA channel only.

Processing continues, but the SNA channel fails.

Corrective Action: Correct the APPLID specifications in the SNA declaration in the ECAPARM configuration file, or shut down the address space that uses the same APPLID. If the problem persists, call your system programmer for assistance.

ECAG75I PROBABLE CAUSE: APPLID INACTIVATED

Explanation: This information message indicates that the probable cause of the failure of a VTAM OPEN ACB command is that the VTAM LU 6.2 (APPC) application ID is inactive. This message precedes message ECAG81I, which specifies the action that will be taken by the IOAGATE. This message can be issued for an SNA channel only.

Processing continues, but the SNA channel fails.

Corrective Action: Activate the application defined by the APPLID. If the problem persists, call your system programmer for assistance.

ECAG76I PROBABLE CAUSE: VTAM IS NOT ACTIVE

Explanation: This information message indicates that the probable cause of the failure of a VTAM request, such as an APPC command, or an OPEN or CLOSE ACB command, is that VTAM is down. This message precedes message ECAG85I, which specifies the action that will be taken by the IOAGATE. This message can be issued for an SNA channel only.

Processing continues, but the SNA channel fails.

Corrective Action: Call your network systems programmer for assistance.

ECAG77I PROBABLE CAUSE: PARTNER DISCONNECTED

Explanation: This information message indicates that the probable cause of the failure of a VTAM APPC command is that the conversation was lost due to disconnection from the partner or client. This message follows message ECAG90E, which announces that an APPC command failed, and precedes message ECAG81I, which specifies the action that will be taken by the IOAGATE. This message can be issued for an SNA channel only.

Processing continues, but the SNA channel fails.

Corrective Action: Check the message issued by the partner or client and proceed accordingly. If the problem persists, call your system programmer for assistance.

ECAG78I PROBABLE CAUSE: CONNECTION LOST

Explanation: This information message indicates that the probable cause of failure of a VTAM APPC command is a communication disruption. This may be due to a resource failure on the route to or from the partner or client. This message precedes message ECAG81I, which specifies the action that will be taken by the IOAGATE. This message can be issued for an SNA channel only.

Processing continues, but the SNA channel fails.

Corrective Action: Try to determine the cause of the communication disruption and correct it. If the problem persists, call your system programmer for assistance.

ECAG79I PROBABLE CAUSE: SESSION TERMINATED

Explanation: This information message indicates that the probable cause of failure of a VTAM APPC command is the termination of a VTAM session, possibly because of a protocol error. This message precedes message ECAG81I, which indicates the action that will be taken by the IOAGATE. This message can be issued for an SNA channel only.

Processing continues, but the SNA channel fails.

Corrective Action: Call your system programmer for assistance. If the problem persists, contact BMC Customer Support.

ECAG81I CHANNEL(channelId.SNA) RE-START COMMUNICATION WILL BE ATTEMPTED

Explanation: This information message indicates that an attempt will be made to restart the specified SNA channel. Restarting an SNA channel involves preparing to receive a conversation allocation request from the partner or client LU, including opening the ACB if it is not already open. This message follows other messages that provide details about an error that occurred.

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

IOAGATE attempts to restart the indicated channel.

Corrective Action: No action is required.

ECAG82I CHANNEL(channelId.SNA) RE-CYCLE COMMUNICATION WILL BE ATTEMPTED

Explanation: This information message indicates that an attempt will be made to recycle the SNA channel. Communication is recycled when VTAM is going down, or when the retry limit is exceeded. Recycling communication for a SNA channel involves deallocating the conversation (if there is any), closing and re-opening the ACB, and preparing to receive a conversation allocation request from the partner or client LU. This message follows other messages that provide details about the error that occurred.

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

IOAGATE attempts to recycle the indicated SNA channel.

Corrective Action: No action is required.

ECAG83E IOAGATE WILL BE SHUT DOWN

Explanation: IOAGATE will shut down because of an error that occurred. This message follows other messages that provide details about the error.

IOAGATE shuts down.

Corrective Action: If the shutdown is due to an error in the IOAGATE, contact BMC Customer Support.

ECAG84I OPERATION WILL BE RE-ATTEMPTED

Explanation: This information message indicates that a failed operation will be retried. This message follows other messages that provide details about an error that occurred. This message can be issued for an SNA channel only.

Normal processing continues, and the failed operation is retried until it succeeds or until the retry limit is reached. When the retry limit is exceeded, an attempt is made to recycle the SNA channel.

Corrective Action: No action is required.

ECAG85I OPERATION WILL BE RE-ATTEMPTED IN A MINUTE

Explanation: This information message indicates that a failed operation will be retried after one minute. This message follows other messages that provide details about an error that occurred. This message can be issued for a SNA channel only.

Normal processing continues, and the failed operation is retried after one minute.

Corrective Action: No action is required.

ECAG87I CHANNEL(channelId.SNA) ESTABLISHED CNOS APPLID(applId) LU(luName) LOGMODE(logmode) MINWNL(minwnl) MINWNR(minwnr) SESLIM(seslim_code)

Explanation: This information message indicates that a multiple connection (MC) SNA channel established CNOS connection with a partner IOAGATE.

Parameters of the established connection are:

channelId - Channel ID of the local IOAGATE
applId - VTAM LU 6.2 (APPC) application identity of the local IOAGATE
luName - VTAM LU 6.2 (APPC) application identity of the partner IOAGATE
logmode - LOGMODE used in this connection
minwnl - Minimum contention winner sessions for the local IOAGATE
minwnr - Minimum contention winner sessions for the partner IOAGATE
seslim - Maximum number of sessions between the local and the partner IOAGATEs

Corrective Action: No action is required.

ECAG88I CHANNEL(channelId.SNA) SESSION ALLOCATED LU(luName) CONVID(conversation_id) SID(session_id)

Explanation: This information message indicates that the sending conversation with a partner IOAGATE was allocated over a multiple connection (MC) SNA channel.

The variables in this message are:

channelId - the identity of the channel over which the specified session was allocated
luName - VTAM LU 6.2 (APPC) LU name of the partner IOAGATE
conversation_id - VTAM LU 6.2 (APPC) conversation identity
session_id - Session identity

Corrective Action: No action is required.

ECAG89W CHANNEL(channelId.SNA) APPCCMD(appc_command) FAILED APPLID(applId) R15(r15_rc) R0(r0_rsn) RPL6RC(rpl6_rsn) PARTNER LU(luName)

Explanation: An APPC command issued by a multiple connection (MC) SNA channel failed. This message precedes message ECAG84I, which specifies the action that will be taken by IOAGATE. This message may follow another message that provides more information about the error.

The variables in this message for the system programmer are:

channelId - the identity of the channel that issued the APPC command
appc_cmd - the failed APPC command
applId - VTAM LU 6.2 (APPC) application identity of the local IOAGATE
r15_rc - Return code returned by VTAM in R15
r0_rsn - Reason code returned by VTAM in R0
rpl6_rsn - RPL6 reason code returned by VTAM in RPL6
luName - VTAM LU 6.2 (APPC) application ID of the partner IOAGATE

For more information on appc_cmd, r15_rc, r0_rsn, and rpl6_rc, see the VTAM Programming for LU 6.2 Manual.

Corrective Action: If another message follows with a probable cause of the error, perform the user action recommended for that message. Otherwise, call your system programmer for assistance.

ECAG90E CHANNEL(channelId.SNA) APPCCMD(appc_cmd) FAILED APPLID(applId) R15(r15_rc) R0(r0_rsn) RPL6RC(rpl6_rsn) PARTNER LU(luName)

Explanation: An APPC command issued by a multiple connection (MC) SNA channel failed.

This message precedes message ECAG84I, which specifies the action that will be taken by IOAGATE. This message may follow another message that provides more information about the error.

The variables in this message for the system programmer are:

channelId - the identity of the channel that issued the APPC command
appc_cmd - the failed APPC command
applId - VTAM LU 6.2 (APPC) application identity of the local IOAGATE
r15_rc - return code returned by VTAM in R15
r0_rsn - reason code returned by VTAM in R0
rpl6_rsn - RPL6 reason code returned by VTAM in RPL6
luName - VTAM LU 6.2 (APPC) application identity of the partner IOAGATE

For more information on appc_cmd, r15_rc, r0_rsn, and rpl6_rc, see the VTAM Programming for LU 6.2 Manual.

Corrective Action: If another message follows with a probable cause of the error, perform the user action recommended for that message. Otherwise, call your system programmer for assistance.

ECAG91W CHANNEL(channelId.SNA) OPEN ACB FAILED, APPLID(applId) ACBERFLG(acb_err_flag)

Explanation: An OPEN ACB command issued by a multiple connection SNA channel failed. This message precedes a message that specifies the action that will be taken by IOAGATE. This message may follow another message that provides more information about the error.

The variables in this message for the system programmer are:

channelId - the identity of the channel that issued the OPEN command
applId - VTAM LU 6.2 (APPC) application identity of the local IOAGATE
acb_err_flag - ACBERFLG flags returned by VTAM

Corrective Action: If another message follows with a probable cause of the error, perform the user action recommended for that message. Otherwise, call your system programmer for assistance.

ECAG93W CHANNEL(channelId.SNA) CLOSE ACB FAILED, APPLID(applId) ACBERFLG(acb_err_flag)

Explanation: A CLOSE ACB command issued by a multiple connection SNA channel failed. This message precedes a message that specifies the action that will be taken by IOAGATE. This message may follow another message that provides more information about the error.

The variables in this message for the system programmer are:

channelId - the identity of the channel that issued the CLOSE command
applId - VTAM LU 6.2 (APPC) application identity of the local IOAGATE
acb_err_flag - ACBERFLG flags returned by VTAM

Corrective Action: If another message follows with a probable cause of the error, perform the action recommended for that message. Otherwise, call your system programmer for assistance.

ECAG94W CHANNEL(channelId.SNA) SETLOGON FAILED, APPLID(applId) R15(r15_rc) R0(r0_rsn) RPLRTNCD(rplrtncd_code) RPLFDBK2(rplfdbk2_code)

Explanation: A SETLOGON command issued by a multiple connection (MC) SNA channel failed. This message precedes a message that specifies the action that will be taken by IOAGATE. This message may follow another message that provides more information about the error.

The variables in this message for the system programmer are:

channelId - the identity of the channel that issued the SETLOGON command
applId - VTAM LU 6.2 (APPC) application identity of the local IOAGATE
r15_rc - return code returned by VTAM in R15
r0_rsn - reason code returned by VTAM in R0
rplrtncd_code - RPLRTNCD returned by VTAM in RPL
rplfdbk2_code - RPLFDBK2 returned by VTAM in RPL

For more information on r15_rc, r0_rsn, rplrtncd_code, and rplfdbk2_code, see the VTAM Programming for LU 6.2 Manual.

Corrective Action: If another message follows with a probable cause of the error, perform the user action recommended for that message. Otherwise, call your system programmer for assistance.

ECAG95E CHANNEL(channelId.SNA) APPCCMD(appc_cmd) FAILED AFTER num RETRIES APPLID(applId) PARTNER LU(luName)

Explanation: An APPC command issued by a multiple connection (MC) SNA channel failed after a number of retries. This message precedes a message that specifies the action that will be taken by the local IOAGATE. This message may follow another message that provides more information about the error.

The variables in this message for the system programmer are:

channelId - the identity of the channel that issued the APPC command
appc_cmd - the failed APPC command
num - the number of retries before failure
applId - VTAM LU 6.2 (APPC) application identity of the SNA channel
luName - VTAM LU 6.2 (APPC) application identity of the partner IOAGATE

Corrective Action: For more information on appc_cmd, see the VTAM Programming for LU 6.2 Manual.

The IOAGATE recycles the specified SNA channel.

If another message follows with a probable cause of the error, perform the user action recommended for that message. Otherwise, call your system programmer for assistance.

ECAG96E CHANNEL(channelId.SNA) APPCCMD SEND NOT COMPLETED WITHIN 10 MINUTES, APPLID(applId) PARTNER LU(luName)

Explanation: A SEND operation issued by a multiple connection (MC) SNA channel was not completed within the specified time interval. This message precedes a message that specifies the action that will be taken by the local IOAGATE. This message may follow another message that provides more information about the error.

The variables in this message are:

channelId - the identity of the channel that issued the APPC command
applId - VTAM LU 6.2 (APPC) application identity of the SNA channel
luName - VTAM LU 6.2 (APPC) LU name of the partner IOAGATE

The IOAGATE recycles the specified SNA channel.

Corrective Action: If another message follows with a probable cause of the error, perform the user action recommended for that message. Otherwise, call your system programmer for assistance.

ECAG97E CHANNEL(channelId.SNA) GENCB FAILED, APPLID(applId) R15(r15_rc) R0(r0_rsn) RPLRTNCD(rplrtncd_code) RPLFDBK2(rplfdbk2_code)

Explanation: A GENCB operation issued by a multiple connection SNA channel failed. This message precedes a message that specifies the action that will be taken by the local IOAGATE.

The variables in this message for the system programmer are:

channelId - the identity of the SNA channel that issued the GENCB operation
applId - VTAM LU 6.2 (APPC) application ID of the SNA channel
r15_rc - return code returned by VTAM in R15
r0_rsn - reason code returned by VTAM in R0
rplrtncd_code - RPLRTNCD returned by VTAM in RPL
rplfdbk2_code - RPLFDBK2 returned by VTAM in RPL

For more information on r15_rc, r0_rsn, rplrtncd_code, and rplfdbk2_code, see the VTAM Programming for LU 6.2 Manual.

IOAGATE shuts down.

Corrective Action: Try to determine the cause of the failure using the diagnostic information in the message. If you cannot resolve the problem, call your system programmer for assistance.

ECAG98I CHANNEL(channelId.SNA) CONVERSATION STARTED, LU(luName) CONVID(conversation_id) SID(session_id) APPLID(applId)

Explanation: This information message indicates that the specified conversation started between the IOAGATE and its partner. A specific partner started a conversation with the IOAGATE.

The variables in this message are:

channelId - the identity of the SNA channel on which the conversation was started
luName - VTAM LU 6.2 (APPC) LU name of the partner IOAGATE
conversation_id - VTAM LU 6.2 (APPC) conversation identity
session_id - session identity
applId - VTAM LU 6.2 (APPC) application identity of the IOAGATE

Corrective Action: No action is required.

ECAG99W CHANNEL(channelId.SNA) ATTN LOSS EXIT INVOKED, LU(luName) APPLID(applId) SID(session_id)

Explanation: A session between the specified LU and the local IOAGATE ended. A partner IOAGATE ended the connection to the local IOAGATE.

The variables in this message are:

channelId - the identity of the SNA channel on which the connection was terminated
luName - VTAM LU 6.2 (APPC) application identity of the partner IOAGATE
applId - VTAM LU 6.2 (APPC) application identity of the local IOAGATE
session_id - session identity

Corrective Action: No action is required.

Parent Topic

ECA messages

Messages ECAG00 through ECAGxx

ECAG00I IOAGATE STARTED, RELEASE(relId) CCID(changeLevel)

ECAG01W MAINTENANCE LEVEL MODULE(ECALVL) UNAVAILABLE

ECAG02E IOAGATE NOT APF AUTHORIZED

ECAG03I ****.channelId.protocol SECTION OF THE mapId NETWORK MAP ****

ECAG04E ATTACH FOR(mod) HAS FAILED

ECAG05S task (taskId.type-channelId) UNRECOVERABLE ERROR ENCOUNTERED, REASON (rsn): explanation

ECAG06S FAILURE(rsn) TO OBTAIN A NEW LINKAGE INDEX

ECAG07I SHUT DOWN UPON REQUEST FROM CONSOLE(console_id)

ECAG08I ***** LIST OF CURRENT ALLOCATIONS *****

ECAG09I ddName type dsn

ECAG0AI MODIFY COMMAND ISSUED FROM CONSOLE (console_id) ACCEPTED, COMMAND(cmd)

ECAG0BW MODIFY COMMAND ISSUED FROM CONSOLE (console_id) REJECTED, COMMAND(cmd)

ECAG0CI VALID MODIFY COMMANDS ARE:

ECAG0DI *** FOLLOWING ECAPARM(suffix) CONFIGURATION FILE IS USED ***

ECAG0EI lineNum lineText

ECAG0FI ISSUE "F monitorId,? " TO GET VALID COMMANDS

ECAG0GW THERE IS NO ACTIVE APPLICATION SERVER, monitorId TERMINATING

ECAG0HI ENABLED FOR THE AUTOMATIC RESTART MANAGEMENT FUNCTION

ECAG0II AUTOMATIC RESTART IN PROGRESS AFTER UNEXPECTED FAILURE

ECAG0JW AUTOMATIC RESTART MANAGEMENT REQUEST FAILED R15(rc) REASON (rsn) short_explan

ECAG0KW MODIFY(cmd) REJECTED, rsn

ECAG10I IOAGATE HAS BEEN INITIALIZED SUCCESSFULLY

ECAG11S FUNCTION(func) STD(taskId.type) ECAGNRL OBTAINED ZERO STD ADDRESS

ECAG12S FUNCTION(func) STD(taskId.type) ECAGNRL OBTAINED ZERO STDID

ECAG13W CHANNEL(channelId.TCP) CONNECTION REJECTED, MAXIMUM NUMBER OF LINKS REACHED

ECAG14I task (taskId.type.channelId) STARTED

ECAG15I task (taskId.type.channelId) SHUT DOWN

ECAG16S FUNCTION(func) STD(taskId.type) ECAGNRL OBTAINED INVALID MCT ADDRESS IN STD

ECAG17S FUNCTION(func) ECAGNRL OBTAINED INVALID MCT

ECAG18S FUNCTION(func) STD(taskId.type) ECAGNRL OBTAINED ZERO FUNCTION ADDRESS

ECAG19S FUNCTION(func) STD(taskId.type) ECAGNRL OBTAINED ZERO FUNCTION CODE

ECAG1AS FUNCTION(func) STD(taskId.type) ECAGNRL OBTAINED INVALID STDID

ECAG1BS FUNCTION(func) ECAGNRL FAILED TO LOCATE MCT TOKEN

ECAG1CS FUNCTION(func) ECAGNRL OBTAINED ZERO MCT IN TOKEN

ECAG1DS CHANNEL (channelId. TCP) FAILED, NO COMM. TASK IS AVAILABLE

ECAG20I IOAGATE SHUTTING DOWN

ECAG21S IOAGATE HAS FAILED (rsn) TO INITIALIZE

ECAG24W task (taskId.type.channelId) DETACHED BY FORCE

ECAG25I modify_command

ECAG29E ECAGNRL FAILED. STD(taskId.type) FUNCTION(func) RC(rsn)

ECAG2AE FILE OF KEYS IS UNAVAILABLE, ENCRYPTION DISABLED

ECAG2BE ENCRYPTION ROUTINE routineName IS UNAVAILABLE, ENCRIPTION DISABLED

ECAG30E ECAPUT FAILED(rsn:text) CALLID (module.call_typ.call_id.queue_typ) TASK(taskId.type.channelId)

ECAG31W IOAGATE(monitorId) WITH ECAPARM(suffix) ALREADY ACTIVE IN SYSTEM(systemId) LINDEX(linkageIndex)

ECAG32I IOAGATE(monitorId) WITH ECAPARM(suffix) RUNNING IN SYSTEM(systemId)

ECAG33I LINDEX(linkageIndex) OBTAINED(date) QNAME(qName) RNAME(rName)

ECAG34I SERVER TASK S T A T U S JOB/CHANNEL/SIID STEP/JOBID/MODULE UTILIZATION

ECAG35I type taskId.addrSpaceId status channelId/siId step/jobId/mod utilization

ECAG36W APPL.SERVER(addrSpaceId) CANNOT BE STOPPED

ECAG37I STOP FOR APPL.SERVER (applServer.addrSpaceId) INITIATED

ECAG38I IOAGATE(monitorId) WITH ECAPARM(suffix) EXCLUSIVELY OWNS HEARTBEAT RESOURCE Q(qName) R(rName)

ECAG39W SERVER TASK(taskId) CURRENTLY CANNOT BE STOPPED

ECAG3AS FAILURE(rsn) TO CREATE A NEW NAME/TOKEN PAIR ON SYSTEM LEVEL

ECAG3BW SERVER TASK(taskId) DOES NOT EXIST

ECAG3CI PUTTER(taskId.type) submitting controlMsg for Server(serverId)

ECAG3DI GETTER(taskId.type) controlMsg confirmed for Server(serverId)

ECAG3EW PUTTER(taskId.type) Obsolete SIB thrown away, SIID=siId APPL=appl SID=serviceId Time difference=timeDiff

ECAG3FW FAILURE TO UNLOCK CHAIN OF SIBs:ALREADY UNLOCKED UNLOCKER (taskId.type.callId):module

ECAG3GS FAILURE TO UNLOCK CHAIN OF SIBs:LOCKED BY (taskId) UNLOCKER (taskId.type.callId):module

ECAG3HI IOAGATE Token: Name=tokenName LX=index Obtained=date System=systemName

ECAG3IW LAST READY CS SUBTASK IN (xxxx.yyyy) ASSIGNED. OCCURED (nnn) TIMES.

ECAG40W APPL.SERVER (applServer.addrSpaceId) CANNOT BE STARTED, CHANNEL(channelId) DISABLED

ECAG41E SERVER TASK (applServer.type.taskId.addrSpaceId) FAILED WHEN HANDLING A REQUEST, USER(userId) SIID(serviceInstanceId)

ECAG43W AN ATTEMPT TO CREATE A MESSAGE FOR appl REMOTE APPLICATION FAILED rsn

ECAG46W APPL.SERVER (applServer.type.taskId.addrSpaceId. channelId) ALREADY ACTIVE

ECAG47I START FOR APPLICATION SERVER(applServer.addrSpaceId) INITIATED

ECAG49I CHANNEL(channelId.SNA) USER(userId) LOGGED ON, CONVID(conversation_id) APPLID(applId)

ECAG4AI STOP FOR SERVER TASK (applServer.type.taskId.addrSpaceId) INITIATED

ECAG4BE SERVER TASK(applServer.type.taskId.addrSpaceId) FAILED WHEN BEING STARTED

ECAG4CE APPL.SERVER (applServer.type.task-id.addrSpaceId. channelId) FAILED WHEN BEING STARTED

ECAG4DE SERVER TASK (applServerName.type.taskId.addrSpaceId) FAILED

ECAG4GI SERVER TASK (applServerName.type.taskId.addrSpaceId) HAS BEEN STOPPED BY OPERATOR

ECAG4HW APPL.SERVER(addrSpaceId) DOES NOT EXIST

ECAG4IW APPL.SERVER (applServerName.type.taskId.addrSpaceId.channelId/jobId) WENT DOWN BECAUSE OPERATOR STOPPED SERVER TASK(taskId)

ECAG4JI TERMINATION FOR SERVER TASK(applServer.type.taskId.addrSpaceId) INITIATED

ECAG4KW SERVER TASK(applServer.type.taskId.addrSpaceId) HAS BEEN TERMINATED BY IOAGATE, USER(userId) SIID(serviceInstanceId)

ECAG4LE APPL.SERVER (applServerName.addrSpaceId.proc.stcId-channelId/jobId) FAILED

ECAG50I CHANNEL(channelId.SNA) DEALLOCATE RECEIVED FROM PARTNER, APPLID(applId) CONVID(conversation_id)

ECAG55W CHANNEL(channelId.protocol) TASK(taskId.type) IS STARTING UP ALTHOUGH NO APPL.SERVER HAS COME UP YET

ECAG08I * LIST OF CURRENT ALLOCATIONS *