This group includes messages for the IOA (infrastructure) product.
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.
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:
IOAGATE has propagated the setting of ENCRYPT to YES for the indicated Application server. Normal processing continues.
Corrective Action: No action is required.
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:
Corrective Action: Contact BMC Customer Support.
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:
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.
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.
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.
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.
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:
Corrective Action: No action is required.
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:
Corrective Action: No action is required.
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:
Corrective Action: No action is required.
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:
Corrective Action: No action is required.
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:
Corrective Action: No action is required.
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:
Corrective Action: No action is required.
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:
Corrective Action: No action is required.
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:
Corrective Action: No action is required.
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:
Corrective Action: No action is required.
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:
Corrective Action: No action is required.
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:
Corrective Action: No action is required.
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 IOAGATE or application server address space shuts down, with a return code of 52 in either case.
Corrective Action: Do the following:
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:
The MODASID command is not processed. Normal processing continues.
Corrective Action: Correct and reissue the MODASID command.
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:
Corrective Action: No action is required.
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.
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.
Explanation: IOAGATE encountered a severe internal problem during initialization.
IOAGATE shuts down.
Corrective Action: Contact BMC Customer Support.
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.
Parent Topic |