mmm communication error detected for connection. connection name=aa...aa reason code=bb...bb detail error information=cc...cc stop code=dd...dd error detail code=ee...ee line name=ff...ff

A communication error was detected for the connection to the remote system.

mmm: MCF identifier

aa...aa: Connection name

bb...bb: Reason code (Maintenance information)

cc...cc: Detail error information (Detailed error information for the communication manager)

dd...dd: Stop code (Stop code for the communication manager)

ee...ee: Error detail code (Error detail code for the communication manager)

ff...ff: line name

S:

HSC1 procedure:

• In the event of an HSC procedure error, recovers the connection.
• In all other cases, shuts down the connection.

HSC2 procedure:

• If the mode is synchronous at the time of a send failure, the corresponding logical terminal is placed under implicit shutdown.
• If the mode is asynchronous at the time of a send fail, a retry takes place according to the mcftalccn specification in the MCF communication configuration definition.
• In the event of an HSC procedure error, disconnects the line (connected), and implicitly shuts down the logical terminal (rejects termination if an HSC error is detected during a termination request). However, the system does not shut down the logical terminal if a DLE.EOT send request has been accepted from the UAP before the UAP is notified of the detection of an HSC procedure error.
• In all other cases, shuts down the connected logical terminal.

O: Contact the OpenTP1 administrator.

Countermeasure:

HSC1 procedure:

Eliminate the error cause.

HSC2 procedure:

Eliminate the error cause. (For unsuccessful origination, retry origination after a sufficiently long period has elapsed.)