Messages ECAE00 through ECAExx

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

ECAE01I ENCRYPTION ENVIRONMENT INITIALIZED SUCCESSFULLY

Explanation: This information message indicates that ENCRYPT was set to YES in the ECAPARM configuration file for at least one Application server, and that IOAGATE has successfully initialized the encryption environment.

Corrective Action: No action is required.

ECAE02W CHANNEL(channelId.TCP) TASK(taskId.type) ENCRYPTION PROPAGATED ON APPL.SERVER(applServerName.addrSpaceId)

Explanation: This message indicates that more than one application server is linked in the ECAPARM configuration file to the channelId channel, and that ENCRYPT was set to YES for at least one of these servers. The specified channel automatically propagates the ENCRYPT=YES setting on all the servers linked to the channel.

The variables in this message are:

• channelId - the identity of the channel that propagates ENCRYPT=YES for all application servers linked to this channel
• taskId - the internal identity of the channel task that propagates ENCRYPT=YES for each application server linked to this channel
• type - the internal type of the channel task that propagates ENCRYPT=YES for each application server linked to this channel
• applServerName - the full name of the application server for which ENCRYPT was set to YES
• addrSpaceId - the internal ID of the application server address space

IOAGATE has propagated the setting of ENCRYPT to YES for the indicated Application server. Normal processing continues.

Corrective Action: No action is required.

ECAE0VE FAILURE TO DECRYPT AN INCOMING MESSAGE: rsn

Explanation: IOAGATE encountered an internal error when trying to decrypt an incoming message.

In this message, rsn is a reason code that shows the reason for the failure.

Valid values for rsn are:

• Failure to get ENC_key - failure to retrieve an encryption key
• ENC_decr function failed - the decryption function failed

Corrective Action: Contact BMC Customer Support.

ECAE0WE APPL.SERVER(applServerName.addrSpaceId) HAS BEEN DISABLED DUE TO FAILURE TO INITIALIZE ENCRYPTION

Explanation: IOAGATE failed to initialize the encryption environment requested by the setting of ENCRYPT to YES in the ECAPARM configuration file for the Application server applServerName.

The variables in this message are:

• applServerName - the name of the Application server that requested the encryption
• addrSpaceId - the internal identity of the address space of the Application server that requested the encryption

Processing continues. The indicated Application server is not started.

Corrective Action: Check the JES log, DAIGLOG, and DATRACE outputs of IOAGATE for additional error indications. Try to correct the problem. If the problem persists, contact BMC Customer Support.

ECAE0XE ENCRYPTION DISABLED DUE TO FAILURE TO LOAD THE FILE OF KEYS

Explanation: When establishing the encryption environment, IOAGATE failed to load the file of keys that is used to perform encryption and decryption.

Processing continues. The encryption function has been disabled. The Application server that requests encryption is not started.

Corrective Action: Transfer the appropriate file of keys from the client side. If the problem persists, contact BMC Customer Support.

ECAE0YS ENCRYPTION PROCESSOR FAILED: INVALID ACTION CODE(actn_code) RECEIVED

Explanation: IOAGATE encountered a severe internal error when trying to perform an internal encryption or decryption function.

In this message, actn_code is the invalid action code that was received by the encryption processor.

The Application server that tried to perform the internal encryption or decryption function shuts down.

Corrective Action: Contact BMC Customer Support.

ECAE0ZS ENCRYPTION PROCESSOR FAILED: MCT UNAVAILABLE

Explanation: IOAGATE encountered a severe internal error when trying to perform an internal encryption or decryption function.

The Application server that tried to perform the internal encryption or decryption function shuts down.

Corrective Action: Contact BMC Customer Support.

ECAE40I CHANNEL(channelId.TCP) ALL TASKS STARTED, PORT(port) APPLICATION(applicId)

Explanation: This information message indicates that all communication tasks belonging to the specified dual connection (DC) TCP communication channel started successfully. During initialization, IOAGATE starts the tasks of all communication channels defined in the ECAPARM configuration file.

The variables in this message are:

• channelId - the channel identity assigned by the user in the ECAPARM configuration file
• port - the TCP/IP communication port number used by the specified TCP channel to listen for connection
• applicId - the application linked to the specified channel

Corrective Action: No action is required.

ECAE41I CHANNEL(channelId.SNA) ALL TASKS STARTED, APPLIDS(applId1,applId2) APPLICATION(applicId)

Explanation: This information message indicates that all communication tasks of the indicated dual connection (DC) SNA communication channel started successfully. During initialization, IOAGATE starts the tasks of all communication channels defined in the ECAPARM configuration file.

The variables in this message are:

• channelId - the channel identity assigned by the user in the ECAPARM configuration file
• applId1, applId2 - VTAM 6.2 (APPC) LU application IDs specified by the APPLIDS parameter in the ECAPARM configuration file for the channel
• applicId - the application linked to the channel

Corrective Action: No action is required.

ECAE42I CHANNEL(channelId.TCP) ALL TASKS STARTED, PORT(port) APPLICATIONS(applicId)

Explanation: This information message indicates that all communication tasks of the specified multiple connection (MC) TCP communication channel started successfully. During initialization, IOAGATE starts the tasks of all communication channels defined in the ECAPARM configuration file.

The variables in this message are:

• channelId - the channel identity assigned by the user in the ECAPARM configuration file
• port - the number of the TCP/IP communication port that the specified TCP channel uses to listen for connection
• applicId - a list of the applications linked to the channel

Corrective Action: No action is required.

ECAE43I CHANNEL(channelId.SNA) ALL TASKS STARTED, APPLID(applId) APPLICATIONS(applicId)

Explanation: This information message indicates that all communication tasks belonging to the indicated multiple connection (MC) SNA channel started successfully. During initialization, IOAGATE starts the tasks of all communication channels defined in the ECAPARM configuration file.

The variables in this message are:

• channelId - the channel identity assigned by the user in the ECAPARM configuration file
• applId - VTAM 6.2 (APPC) LU APPLID parameter specified in the ECAPARM configuration file for a multiple connection SNA channel
• applicId - List of applications linked to the channel

Corrective Action: No action is required.

ECAE44I CHANNEL(channelId.protocol) RUNNING IN NODE(node_id) WITH NETWORK MAP(mapId)

Explanation: This information message indicates that the indicated multiple connection (MC) communication channel supporting IOAGATE to IOAGATE communication started successfully. During initialization, IOAGATE starts the communication channels defined in the ECAPARM configuration file.

The variables in this message are:

• protocol - the communication protocol used by the current channel, which may be TCP (TCP/IP) or SNA
• channelId - the channel identity assigned by the user in the ECAPARM configuration file
• node_id - the node in which the local IOAGATE is running
• mapId - a member in the IOA PARM library that describes a map of network connections between IOAGATEs that enables one IOAGATE to communicate with another over a multiple connection SNA channel

Corrective Action: No action is required.

ECAE45I CHANNEL(channelId.TCP) IS UP, PORT(port) APPLICATION(applicId)

Explanation: This information message indicates that the specified dual connection (DC) TCP communication channel of the IOAGATE is up. The dual connection TCP communication channel was initialized successfully, and is ready for communication.

The variables in this message are:

• channelId - the channel identity assigned by the user in the ECAPARM configuration file
• port - the number of the TCP/IP communication port used by the TCP channel to listen for connection
• applicId - the identity of the application supported by the application server that is linked to the channel

Corrective Action: No action is required.

ECAE46I CHANNEL(channelId.TCP) IS UP, PORT(port) APPLICATIONS(applicId)

Explanation: This information message indicates that the specified multiple connection (MC) TCP communication channel of the IOAGATE is up. The multiple connection TCP communication channel was initialized successfully, and is ready for communication.

The variables in this message are:

• channelId - the channel identity assigned by the user in the ECAPARM configuration file
• port - the number of the TCP/IP communication port that the TCP channel uses to listen for connection
• applicId - the identity of the application supported by the application server that is linked to the channel

Corrective Action: No action is required.

ECAE47I CHANNEL(channelId.SNA) IS UP, APPLIDS(applId1,applId2) APPLICATION(applicId)

Explanation: This information message indicates that the specified dual connection (DC) SNA communication channel of the IOAGATE is up. The dual connection SNA communication channel was initialized successfully, and is ready for communication.

The variables in this message are:

• channelId - the channel identity assigned by the user in the ECAPARM configuration file
• applId1, applId2 - VTAM 6.2 (APPC) LU application identities specified by the APPLIDS parameter in the ECAPARM configuration file for the channel
• applicId - the identity of the application supported by the application server that is linked to the channel

Corrective Action: No action is required.

ECAE48I CHANNEL(channelId.SNA) IS UP, APPLID(applId) APPLICATIONS(applicId)

Explanation: This information message indicates that the specified multiple connection (MC) SNA communication channel is up. The multiple connection SNA communication channel was initialized successfully, and is ready for communications.

The variables in this message are:

• channelId - the channel identity assigned by the user in the ECAPARM configuration file
• applId - VTAM 6.2 (APPC) LU application ID specified by APPLID parameter in the ECAPARM configuration file for the channel
• applicId - the identity of the application supported by the application server that is linked to the channel

Corrective Action: No action is required.

ECAE49W CHANNEL(channelId.TCP) PORT(port), RECYCLING INITIATED DUE TO APPL.SERVER (applServerName.addrSpaceId) FAILURE

Explanation: IOAGATE detected a failure of the specified application server. As a result of the application server failure, IOAGATE initiated recycling of the indicated TCP channel.

The variables in this message are:

• channelId - the channel identity assigned by the user in the ECAPARM configuration file
• port - the number of the TCP/IP communication port that the TCP channel uses to listen for connection
• applServerName - the name of the failed application server
• addrSpaceId - the internal identity of the failed application server address space

Corrective Action: No action is required.

ECAE4AW CHANNEL(channelId.SNA) APPLIDS(applId1,applId2), RECYCLING INITIATED DUE TO APPL.SERVER (applServerName.addrSpaceId) FAILURE

Explanation: IOAGATE detected a failure of the specified application server. As a result of the application server failure, IOAGATE initiated recycling of the indicated SNA channel.

The variables in this message are:

• channelId - the channel identity assigned by the user in the ECAPARM configuration file
• applId1, applId2 - VTAM 6.2 (APPC) LU application identities specified by APPLIDS parameter in the ECAPARM configuration file for the channel
• applServerName - the name of the failed application server
• addrSpaceId - the internal identity of the failed application server address space

Corrective Action: No action is required.

ECAE50S LOAD FAILED FOR MODULE(mod)

Explanation: An attempt to load the mod module into the main memory of either the IOAGATE or application server address space failed. 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.

The IOAGATE or application server address space shuts down, with a return code of 52 in either case.

Corrective Action: Do the following:

1. Examine the reason code for the failure in the system log.
2. Try to correct the problem.
3. If necessary, increase the region size.
4. If the problem persists, call your system programmer for assistance.

ECAE51W ERROR IN MODASID COMMAND rsn

Explanation: IOAGATE detected an error in the F IOAGATE,MODASID modifyCommand, modifyCommandParms command that was issued. The MODASID command is used to submit a modify command, expressed as MODASID parameters, that will be executed in the address space of the application server.

Possible values of rsn are:

• COMMAND IS EMPTY - there are no parameters in the MODASID command
• ADDR.SPACE IS DOWN - the address space of the application server specified in the MODASID command is not active
• BAD APPL.SERVER ID - the address space of the application server specified in the MODASID command does not exist

The MODASID command is not processed. Normal processing continues.

Corrective Action: Correct and reissue the MODASID command.

ECAE52I MODIFY(modifyCommand, modifyCommandParms) FOR SERVER(applServerName.type.taskId.addrSpaceId) SUBMITTED

Explanation: This information message indicates that IOAGATE accepted and submitted the command F IOAGATE,MODASID=modifyCommand, modifyCommandParms. The MODASID command is used to submit a modify command, expressed as MODASID parameters, that will be executed in the address space of the application server.

The variables in this message are:

• modifyCommand - the modify command to be performed in an application server address space
• modifyCommandParms - the parameters, if any, required by modifyCommand
• applServerName - the name of the application server
• type - the CD server task type
• taskId - the internal identity of the server task
• addrSpaceId - the internal identity of the application server address space

Corrective Action: No action is required.

ECAE53W NO APPLICATION SERVER HAS BECOME AVAILABLE IN THE LAST interval MINUTES

Explanation: No application server address space started in the specified time interval, either since IOAGATE launched the application servers defined in the ECAPARM configuration file or since the previous ECAE53W warning. There might be a problem that prevents an application server from being started in time.

In this message, interval is the number of minutes between occurrences of this warning message. The default interval is three minutes.

Processing continues. If the STAYUP parameter is set to YES in the ECAPARM configuration file, this message is issued every three minutes until at least a single application server becomes available. Otherwise, after issuing five ECAE53W warnings, IOAGATE shuts down.

Corrective Action: Check the IOAGATE JES log, the DAIGLOG log, and the DATRACE log for more information. Try to correct the problem. If the problem persists, contact BMC Customer Support.

ECAE54S IOAGATE IS GOING DOWN, NO APPLICATION SERVER HAS BECOME AVAILABLE IN THE LAST num MINUTES

Explanation: No application server address started in the specified number (num) of minutes since IOAGATE launched the application servers defined in the ECAPARM configuration file. Some problem is preventing application servers from starting in time. Several ECAE53W warnings precede this message.

This message can be issued only if the STAYUP parameter is set to NO in the ECAPARM configuration file. For more information, see message ECAE53W.

Corrective Action: Check the IOAGATE JES log, the DAIGLOG log, and the DATRACE log for more information. Try to correct the problem. If the problem persists, contact BMC Customer Support.

ECAE56S module INTERNAL ERROR, INVALID PARAMETERS PASSED TO module

Explanation: IOAGATE encountered a severe internal problem during initialization.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAE57I monitorId is staying up due to STAYUP=YES specification in ECAPARM

Explanation: This information message indicates that all Application servers either failed or did not start. IOAGATE cannot go down, because the STAYUP parameter is set to UP in the ECAPARM configuration file.

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

The IOAGATE monitor continues to run.

Corrective Action: No action is required.