Messages ECAA00 through ECAAxx

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

ECAA00I APPLICATION SERVER(D001) MANAGER STARTED, RELEASE(releaseId) CREATED (timeStamp) CCID(changeLevel)

Explanation: This information message indicates normal startup of the address space of the application server.

The variables in this message are:

• releaseId - the official release and the maintenance level of the IOAGATE
• timeStamp - the date and time when the main module of the application server manager was compiled
• changeLevel - the level of the change that was last applied to the main module of the manager of the application server

Corrective Action: No action is required.

ECAA01I APPLICATION SERVER GOES DOWN DUE TO IOAGATE SHUTDOWN

Explanation: This information message indicates that the manager of the application server detected that the IOAGATE is down. The shutdown may be due to an operator request or to an error.

The server address space shuts down.

Corrective Action: If the shutdown was due to a problem, check the IOAGATE messages for errors that may have caused the shutdown.

ECAA02I APPLICATION SERVER GOES DOWN DUE TO STOP REQUEST FROM CONSOLE(consoleId)

Explanation: This information message indicates that the application server was shut down because a STOP command was issued to its address space.

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

The address space of the application server shuts down.

Corrective Action: No action is required.

ECAA03I APPLICATION SERVER EXCLUSIVELY OWNS HEARTBEAT RESOURCE Q(qName)R(rName)

Explanation: This information message indicates that the application server successfully acquired the specified heartbeat resource.

During initialization, an application server issues an ENQ request to acquire the indicated resource exclusively. The resource acts as a heartbeat mechanism between the IOAGATE and the address space of the server. If the resource becomes available in the address space of the IOAGATE, it indicates an application server failure.

The variables in this message are:

• qName - major name of a heartbeat resource of the application server
• rName - minor name of a heartbeat resource of the application server

Corrective Action: No action is required.

ECAA04S ECAAMGR INTERNAL ERROR, TASKLIST EXHAUSTED

Explanation: The manager of an application server encountered a severe internal error.

The address space of the server shuts down with a return code of 44.

Corrective Action: Contact BMC Customer Support.

ECAA05E APPLICATION SERVER ENDED DUE TO CRITICAL TASK TERMINATION

Explanation: A critical server task terminated. A server task may be defined as critical in the address space of an application server. If a critical task fails, the server address space goes down. The CD server task is always critical.

The server address space shuts down with a return code of 68.

Corrective Action: Check the error messages of the server address space for the cause of the critical task termination. If there are no other active application server address spaces, recycle the IOAGATE.

ECAA06W SERVER TASK(type. taskId) TERMINATED

Explanation: This message warns that one server task of the server address space terminated. The message may be accompanied by error messages issued by the failed server task itself.

The variables in this message are:

• type - server task type:
• CM - manager of the address space of an application server
• CS - application server
• CD - detector server
• CU - updater server
• taskId - the internal ID of a server task

If the terminated task was critical or was a single CS task, the server address space shuts down. Otherwise, normal processing continues, and, if recovery is not blocked for this server task, the IOAGATE tries to recover the server task, when message ECAB41I may be issued.

Corrective Action: If there are any error messages that relate to the server address space, check them to determine and fix the cause of the task termination. Restart the server task using the F IOAGATE,STARTTID=taskId command.

ECAA07E APPLICATION SERVER GOES DOWN DUE TO TERMINATION OF ALL CS SERVER TASKS

Explanation: The last CS server task ended. The application server address space cannot function when there is no CS server task available.

The server address space shuts down with a return code of 12.

Corrective Action: Check the other error messages that relate to the server address space to determine the cause of the CS task termination. If there are no other active server address spaces, recycle the IOAGATE.

ECAA08E APPLICATION SERVER GOES DOWN DUE TO IOAGATE NOT RESPONDING

Explanation: IOAGATE does not respond to the application server address space. The IOAGATE probably experienced internal problems and could not respond to an application server.

The server address space shuts down with a return code of 64.

Corrective Action: Do the following:

1. Examine the error messages that relate to the IOAGATE.
2. Increase the system priority of both

• the IOAGATE
• an application server address space

1. Recycle the IOAGATE.

ECAA09E APPLICATION SERVER GOES DOWN DUE TO CHANNEL(channelId) DISABLING

Explanation: Application server manager ended. An application server address space cannot function when there is no channel available to communicate with the partner or client.

The server address space shuts down.

Corrective Action: Examine the error messages that relate to the channelId channel. Recycle the IOAGATE.

ECAA0AI CHAN PROT TASK VENDOR SUBS PORT/LU STATUS LINKS APPL

Explanation: This information message provides header information about communication channels defined in the ECAPARM configuration file. ECAA0BI messages that follow provide details for each channel. This message is issued once, in response to an F IOAGATE,CHANNEL (or CHAN) command.

Corrective Action: No action is required.

ECAA0BI channelId protocol task softwareVendor subsystem port / luName status links applications

Explanation: This information message provides detailed information about a single communication channel. It is issued for each communication channel in response to an F IOAGATE,CHANNEL (or CHAN) command.

Each occurrence of this message identifies a communication channel defined in the ECAPARM configuration file. If you have enabled a DC (dual connection) communication channel, the information is provided in two ECAA0BI messages. A set of these messages provides information about all the channels. The ECAA0AI message provides headings for the set.

The variables in this message are:

• channelId - This channel ID consists of two subfields:
  • the communication model specifier for the channel
  • a 2-character channel ID assigned by the user in the ECAPARM configuration file. Valid communication model specifiers are: MC - a multiple connection channel, DC - a dual connection channel
• protocol - The current channel uses this communication protocol. Valid values are:
  • TCP -TCP/IP communication protocol
  • SNA -SNA communication protocol
• task - the name of a communication task. This variable is used only for an enabled DC channel. Valid values are:
  • SNDR - the sender communication task of the DC channel
  • RCVR - the receiver communication task of the DC channel
• softwareVendor - the vendor of the TCP/IP software. Valid values are:
  • IBM - IBM TCP/IP software is used by the channel
  • CA - TCPaccess software of Computer Associated International, Inc. is used by the channel
• subsystem - subsystem name for the TCPaccess software
• port - the TCP/IP communication port number used by a TCP channel to listen for connection. In the case of an enabled DC communication channel, two consecutive port numbers are used, and these are identified in two ECAA0BI messages.
• luName - VTAM LU 6.2 (APPC) application ID used by an SNA channel to communicate over the APPC network
• status - the current status of the channel. Valid values are:
  • DOWN - the channel is not started
  • UP/OPEN - the channel is open, up and running
  • UP/CLOSED - the channel has been closed for new incoming connections, but it is still up and running
  • DISABLED - the channel was disabled, either in the ECAPARM configuration file by the CHANNEL parameter set to DISABLE, or by IOAGATE during initialization
• links - the number of current connections for this channel
• links% -the percentage of the supported number of connections currently utilized
• applications - a list of application identities that refer to this channel in the ECAPARM configuration file

Corrective Action: No action is required.

ECAA0CS INVALID ECAPARM(suffix) OBTAINED, THERE’S NO APSERVER STATEMENT FOR APPL.SERVER

Explanation: The application server address space obtained an improper ECAPARM configuration member. The most likely cause was an incorrect PARM library allocated by the DAPARM DD statement.

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

The server address space shuts down with a return code of 60.

Corrective Action: Check and correct the ECAPARM configuration file, the DAPARM DD allocation, or both.

ECAA0DS APPL.SERVER FAILED TO ACQUIRE HEARTBEAT RESOURCE Q(qName)R(rName)

Explanation: An application server failed to acquire the specified heartbeat resource.

During initialization, an application server issues an ENQ request to acquire the indicated resource exclusively. The resource acts as a heartbeat mechanism between the IOAGATE and the address space of the server. An application server failure is indicated if the resource becomes available in the address space of the IOAGATE. Failure to acquire the heartbeat resource by an application server is a severe error.

The variables in this message are:

• qName - the major name of a heartbeat resource of the application server
• rName - the minor name of a heartbeat resource of the application server

The application server shuts down.

Corrective Action: Do the following:

1. Examine the other error messages that relate to the server address space to determine the cause of the failure.
2. Try to correct the problem.
3. Restart IOAGATE.
4. If the problem persists, call your systems programmer for assistance.

ECAA0ES UNRECOVERABLE INTERNAL ERROR ENCOUNTERED: rsn

Explanation: The application server manager encountered a severe internal error when handling the MAXMSGSZ ECAAPPL parameter.

Valid values for rsn are:

• no SDT address
• no SDT of CS
• no MAXMSGSZ

The address space of the server shuts down with a return code of 96.

Corrective Action: Contact BMC Customer Support.

ECAA0FS UNRECOVERABLE APPLICATION ERROR ENCOUNTERED

Explanation: A severe internal application error occurred in the application server.

The application server shuts down.

Corrective Action: Examine any other error messages that relate to the server address space to determine the cause of the failure, take appropriate corrective action, and restart IOAGATE.

ECAA0HI IOAGATE HAS GONE DOWN

Explanation: This information message in an application server address space indicates that this application has detected IOAGATE going down.

The application server address space goes down with a return code of 112.

Corrective Action: Attempt to identify and correct the problem that caused IOAGATE to go down.

ECAA0IW SERVER TASK(type. taskId) CANCELLED(U007) BY ioagateName BECAUSE THE TASK WAS BUSY FOR TOO LONG

Explanation: The ioagateName application server manager cancelled the taskId task of the application server with a completion code of U007.

When a server task is busy for longer than the period defined for this application server by the BUSYDUR parameter, the following events occur:

• A request to cancel the task is generated automatically by IOAGATE.
• Message ECAB4BW is issued.

This message (ECAA0IW) is followed by message ECAA06W.

The variables in this message are:

• type - the server task type. Valid values are:
  • CM - manager of the address space of the application server
  • CS - application server
  • CD - detector server
  • CU - updater server
• taskId - the internal ID of a server task
• ioagateName - the name of the IOAGATE started task that generated the cancel request

The system action depends on the nature of the terminated task, as follows:

• If the terminated task was either critical or a single CS task, the server address space shuts down. If recovery is not blocked for this application server, the IOAGATE tries to recover the server.
• Otherwise, normal processing continues, and, if recovery is not blocked for this server task, the IOAGATE tries to recover the server task.

Corrective Action: Attempt to find the cause for the cancellation of the taskId server task. Try increasing the value of the BUSYDUR parameter.

ECAA0JW SERVER TASK(type. taskId) CANCELED(U007) FROM CONSOLE (consoleId)

Explanation: This message warns that the application server manager has cancelled a server task of the application server with a completion code of U007. This is the result of a CANCTID= taskId request issued by the operator in the IOAGATE address space.

This message is followed by message ECAA06W.

The variables in this message are:

• type - the server task type. Valid values are:
  • CM - manager of the address space of the application server
  • CS - application server
  • CD - detector server
  • CU - updater server
• taskId - the internal ID of a server task
• consoleId - the identity of the console from which the CANCTID request was issuedThe value of consoleId depends on whether this request was issued from a physical or virtual console. If it was a virtual console, the value of consoleId may coincide with the user ID of the operator who issued this request, depending on your local configuration.

The system action depends on the nature of the terminated task, as follows:

• If the terminated task was either critical or a single CS task, the server address space shuts down. If recovery is not blocked for this application server, the IOAGATE tries to recover the server.
• Otherwise, normal processing continues, and, if recovery is not blocked for this server task, the IOAGATE tries to recover the server task.

Corrective Action: No action is required.

ECAA0LW APPL.SERVER TASK(type.taskId) ABENDED; COMPLETION CODE ({Sxxx | Uxxx})

Explanation: This message warns that one server task of the application server address space abended.

The variables in this message are:

• type - server task type:Valid values are:
  • CS - application server
  • CD - detector server
  • CU - updater server
• taskId - the internal identity of a server task
• compCode - completion code

If the terminated task was critical or was a single CS task, the server address space shuts down. Otherwise, normal processing continues, and, if recovery is not blocked for this server task, IOAGATE tries to recover the server task, when message ECAB41I may be issued.

Corrective Action: If there are any error messages that relate to the server address space, check them to determine and fix the cause of the task abend. Restart the server task using the MODIFY IOAGATE,STARTTID=taskId command.

ECAA0MS SSL=NO FOR CTM/ appl1 DOESN'T MATCH SSL=YES FOR CTM/ appl2 ON ioagateName/ systemID

Explanation: When IOAGATE started, it discovered that SSL support is not defined the same way (whether YES, AT-TLS, or NO) in the corresponding channels for CTMAS and for CTMCAS, which are defined in different IOAGATEs.

The IOAGATE that issues this message has SSL=NO in the ECAPARM configuration file, while another IOAGATE that is already up has SSL=YES or SSL=AT-TLS in its ECAPARM configuration file.

The variables in this message are:

• appl1 - either EM or CM, depending on whether this IOAGATE supports CTMAS or CTMCAS
• appl2 - either EM or CM, depending on whether the other IOAGATE supports CTMAS or CTMCAS
• ioagateName - the name of the other IOAGATE
• systemID - the system identification of the other IOAGATE

Since the other IOAGATE has SSL=YES or SSL=AT-TLS and this IOAGATE has SSL=NO, the lower security level for this IOAGATE is not accepted. IOAGATE disables the channel and goes down if there is no other active channel.

Corrective Action: ECAPARM channel definitions should be corrected so that the channel definitions for both CTMAS and CTMCAS will have either SSL=YES, SSL=AT-TLS, or SSL=NO.

ECAA0MW SSL=YES FOR CTM/ appl1 DOESN'T MATCH SSL=NO FOR CTM/ appl2 ON ioagateName/ systemID

Explanation: When IOAGATE started, it discovered that SSL support is not defined the same way (whether YES, AT-TLS, or NO) in the corresponding channels for CTMAS and for CTMCAS, which are defined in different IOAGATEs.

The IOAGATE that issues this message has SSL=YES or SSL=AT-TLS in the ECAPARM configuration file, while another IOAGATE that is already up has SSL=NO in its ECAPARM configuration file.

The variables in this message are:

• appl1 - either EM or CM, depending on whether this IOAGATE supports CTMAS or CTMCAS
• appl2 - either EM or CM, depending on whether the other IOAGATE supports CTMAS or CTMCAS
• ioagateName - the name of the other IOAGATE
• systemID - the system identification of the other IOAGATE

IOAGATE continues the startup.

Corrective Action: ECAPARM channel definitions should be corrected so that the channel definitions for both CTMAS and CTMCAS will have either SSL=YES, SSL=AT-TLS, or SSL=NO.

ECAA0NS SSL=NO FOR CTM/ appl1 DOESN'T MATCH SSL=YES FOR CTM/ appl2

Explanation: When IOAGATE started, it discovered that SSL support is not defined the same way (whether YES, AT-TLS, or NO) in the corresponding channels for CTMAS and for CTMCAS, which are defined in the same IOAGATE.

This was discovered when the second channel was initializing and had SSL=NO, while another channel that was already initialized had SSL=YES or SSL=AT-TLS.

The variables in this message are:

• appl1 - either EM or CM, depending on whether this channel supports CTMAS or CTMCAS
• appl2 - either EM or CM, depending on whether the other channel supports CTMAS or CTMCAS

IOAGATE disables the channel that has SSL=NO and goes down if there is no other active channel.

Corrective Action: ECAPARM channel definitions should be corrected so that the channel definitions for both CTMAS and CTMCAS will have either SSL=YES, SSL=AT-TLS, or SSL=NO.

ECAA0NW SSL=YES FOR CTM/ appl1 DOESN'T MATCH SSL=NO FOR CTM/ appl2

Explanation: When IOAGATE started, it discovered that SSL support is not defined the same way (whether YES, AT-TLS, or NO) in the corresponding channels for CTMAS and for CTMCAS, which are defined in the same IOAGATE.

This was discovered when the second channel was initializing and had SSL=YES or SSL=AT-TLS, while another channel that was already initialized had SSL=NO.

The variables in this message are:

• appl1 - either EM or CM, depending on whether this channel supports CTMAS or CTMCAS
• appl2 - either EM or CM, depending on whether the other channel supports CTMAS or CTMCAS

IOAGATE continues the initialization of the channel with SSL=YES or SSL=AT-TLS.

Corrective Action: ECAPARM channel definitions should be corrected so that the channel definitions for both CTMAS and CTMCAS will have either SSL=YES, SSL=AT-TLS, or SSL=NO.

ECAA0OS IOAGATE name IS ALREADY ACTIVE FOR THE SAME ENVIRONMENT ON lpar

Explanation: An attempt to start IOAGATE failed because another IOAGATE for the same Control-M environment is already active on another LPAR.

Corrective Action: If the IOAGATE is required to run on this LPAR, first stop IOAGATE name on LAPR lpar.

ECAA0PE CHANNEL(channelId.TCP) TASK(taskId.type) CONNECTION REJECTED. SSL=AT-TLS SPECIFIED, BUT IS NOT ACTIVE ON CONNECTION

Explanation: This message indicates that SSL=AT-TLS was specified in ECAPARMx for this channel, indicating that a secure connection is required to be handled by AT-TLS, but AT-TLS is not active on the connection. The connection is terminated.

The variables in this message are:

• channelId - identity of the TCP channel that is listening to the specified port
• taskId - internal identity of this communication task
• type - internal type of this communication task

Corrective Action: Configure a suitable TTLSRule statement in the system's AT-TLS Policy Agent Configuration file, and refresh the Policy Agent (PAGENT) address space.

ECAA0QW CHANNEL(channelId.TCP) TASK(taskId.type) SSL=NO SPECIFIED, BUT AT-TLS IS ACTIVE ON THIS CONNECTION

Explanation: This warning message indicates that SSL=NO was specified in ECAPARMx for this channel, indicating that a secure connection is not required, but AT-TLS is active on the connection.

The variables in this message are:

• channelId - identity of the TCP channel that is listening to the specified port
• taskId - internal identity of this communication task
• type - internal type of this communication task

Corrective Action: To eliminate this message, specify SSL=AT-TLS in ECAPARMx.

ECAA0RE CHANNEL(channelId.TCP) TASK(taskId.type) CONNECTION CLOSED - POSSIBLY BY AT-TLS. SEE TRACE/TCPIP FOR DETAILS

Explanation: A TCP connection was established, and then was immediately closed by a component other than IOAGATE. This may occur when AT-TLS is configured for the connection, but the handshake fails or non-encrypted data is sent. In this case, additional information may be available in the TCPIP started task, or in the IOAGATE trace output if trace level=200 is active.

The variables in this message are:

• channelId - identity of the TCP channel that is listening to the specified port
• taskId - internal identity of this communication task
• type - internal type of this communication task

Corrective Action: Examine the relevant TCPIP started task and/or IOAGATE traces, and remediate the issue, as required. For example, set the client to use SSL, or ensure that certificates match.

ECAA0SI CHANNEL(channelId.TCP) TASK(taskId.type) AT-TLS IS ACTIVE ON THIS CONNECTION

Explanation: This information message indicates that AT-TLS is active on the connection that was just established with an Enterprise Manager or Control-M Configuration Manager client. This message follows message ECAT02I.

The variables in this message are:

• channelId - identity of the TCP channel that is listening to the specified port
• taskId - internal identity of this communication task
• type - internal type of this communication task

Corrective Action: No action is required.

ECAA0TE CHANNEL(channelId.TCP) TASK(taskId.type) CONNECTION REJECTED. SSL=YES SPECIFIED AND AT-TLS IS ACTIVE ON CONNECTION

Explanation: This message indicates that SSL=YES was specified in ECAPARMx, indicating that IOAGATE is to handle the secure connection using native SSL support, but AT-TLS is also active on the connection. In this case, double encryption would occur and IOAGATE would not be able to successfully communicate with the client. The connection is terminated.

The variables in this message are:

• channelId - identity of the TCP channel that is listening to the specified port
• taskId - internal identity of this communication task
• type - internal type of this communication task

Corrective Action: If the secure connection should be handled by AT-TLS, specify SSL=AT-TLS in ECAPARMx. Otherwise, disable the AT-TLS rule and refresh PAGENT.

ECAA0UI CHANNEL(channelId.TCP) TASK(taskId.type) AT-TLS IS ACTIVE ON THIS CONNECTION

Explanation: This information message indicates that AT-TLS is active on the connection that was just established with a WebAccess client. This message follows message ECAG62I.

The variables in this message are:

• channelId - identity of the TCP channel that is listening to the specified port
• taskId - internal identity of this communication task
• type - internal type of this communication task

Corrective Action: No action is required.

ECAA10S IOAGATE MIGHT BE DOWN, HEARTBEAT RESOURCE Q(qName)R(rName) AVAILABLE

Explanation: An application server determined that the specified IOAGATE heartbeat resource is available.

During initialization, an application server checks the IOAGATE heartbeat resource availability to see if the IOAGATE is up and running. If the resource is available, then the IOAGATE is down. For more information, see the ECAG38I message.

The variables in this message are:

• qName - the major name of a heartbeat resource of the IOAGATE
• rName - the minor name of a heartbeat resource of the IOAGATE

The application server address space shuts down with a return code of 16.

Corrective Action: Check the IOAGATE logs to determine why IOAGATE is down, try to fix the problem and restart IOAGATE.

ECAA11S ECAAMGR INTERNAL ERROR, func CALL FAILED WITH RC(rsn)

Explanation: The application server manager encountered a severe internal error when trying to call the func function.

Possible func and rsn (reason code) combinations, and their explanations, are shown in the following table:

The application server address space shuts down.

Corrective Action: Contact BMC Customer Support.

ECAA12I INITIALIZATION PROCEDURE(mod) COMPLETED SUCCESSFULLY

Explanation: This information message indicates that the application server invoked the mod initialization module, and that the module completed successfully. During initialization, an application server invokes an initialization module if it is specified in the ECAPARM configuration file for that server.

Corrective Action: No action is required.

ECAA13E INITIALIZATION PROCEDURE(mod) FAILED WITH RC(rsn)

Explanation: The application server invoked the mod initialization module, and the module failed. During initialization, an application server invokes an initialization module if it is specified in the ECAPARM configuration file for the application server.

The variables in this message are:

• mod - the module that failed
• rsn - the reason code indicating the failure level. Failure levels of 08 and above are fatal, and bring the application server down

The application server address space shuts down with a return code of 56.

Corrective Action: Do the following.

1. Examine the log of the application server for other error messages.
2. Correct any problems.
3. Restart IOAGATE.
4. If the problem persists, report the module name and reason code to BMC Customer Support.

ECAA14I MODIFY HANDLER (modName) WAS LOADED

Explanation: This information message indicates that the application server successfully loaded the modName module. The loaded module is a handler that performs MODIFY commands dedicated for the application server. The application server loads this module during initialization.

Corrective Action: No action is required.

ECAA15I PINGING(pingId) NODE(node)

Explanation: Message indicates that the F CTOAS,PING MODIFY command was issued in the Control-O application server address space and a PING message was sent to the partner Control-O application server.

The variables in this message are:

• pingId - the internal identity of this ping message
• node - the node identity of the partner application server

Corrective Action: No action is required.

ECAA16I PING(pingId) REQUEST RECEIVED FROM(node) SERVER(serverId)

Explanation: This information message indicates that the F CTOAS,PING MODIFY command was issued in the Control-O application server of the partner and a PING request message has arrived at the local Control-O application server.

The variables in this message are:

• pingId - the internal identity of this PING message
• node - the node identity of the partner application server
• serverId - The started task identity of the partner Control-O application server

Corrective Action: No action is required.

ECAA17I PING(pingId) RESPONSE FROM(node) ARRIVED IN nnn MILLISECONDs

Explanation: This information message indicates that the F CTOAS,PING MODIFY command was issued in the Control-O Application server and the response ping message has arrived from the pinging partner Control-O application server.

The variables in this message are:

• pingId - the internal identity of this ping message
• node - the node identity of the partner Control-O application server
• nnn - the time interval in milliseconds required for a ping message to travel in both directions

Corrective Action: No action is required.

ECAA18W PING DROPPED, NODE (node) rsn

Explanation: This information message indicates that the F CTOAS,PING MODIFY command was issued in the Control-O Application server, but the command was not performed for the reason rsn.

Valid values for rsn are:

• NOT FOUND IN PDT - severe internal error
• NOT FOUND IN PLT - severe internal error
• MBX WRITE DISABLED - mailbox error encountered
• COMMUNICATION ERROR - an IOAGATE-to-IOAGATE connection was not established

Corrective Action: No action is required.

ECAA19I ctrl_msg received for Server(servr_id).

Explanation: The application server servr_id received the internal control message ctrl_msg from IOAGATE.

Valid values for ctrl_msg are:

• INITIALIZE - internal control command to initialize an application server
• ATTACHSERVER - internal control command to start an application server task
• CONNECTIONUP - internal control command to inform an application server task that the communication channel is up and running

Corrective Action: No action is required.