mmm session could not be started. connection name=aa...aa, logical terminal name=bb...bb
reason code=(cc...cc,dd...dd,ee...ee)

mmm: MCF identifier

aa...aa: Connection name

bb...bb: Logical terminal name

cc...cc: Termination code

03000001: A line error occurred.

dd...dd: Detail information

ee...ee: Action code

The session start failed due to the problem indicated in the detail information. Detail information and action codes are listed in the table below.

S: Suspends the start of the session.

O: Contact the OpenTP1 administrator.

Countermeasure: Determine the cause of the error by referring to the message output immediately before this message, as well as the detail information shown in the detail information list, then proceed as indicated in that message.

Detail information

When the termination code is 03000001:

Detail information	Meaning
01xxxxxx 02xxxxxx 03xxxxxx 04xxxxxx	A lower-layer error occurred. For details of the detail information, refer to the reason code explanations in the manual XNF/S-E2 Description.
6xxxxxxx	An XNF macro error occurred. Detail information (6fgghhhh) f: Macro type 1: hl_open 2: hl_close 3: hl_bind 4: hl_unbind 5: hl_connect 6: hl_listen 7: hl_snd 8: hl_snddis 9: hl_rcv a: hl_rcvdis b: hl_look c: hl_ctl gg: Error information on the HNA primary station hhhh: Error code of the HNA primary station For details, see the manual XNF/S-E2 Description.
71010001	The sequence number at request sending for a terminal does not match that upon response reception.
71010002	A timeout of the response monitoring timer occurred for request sending for a terminal.
71000006	+RSP was received during chain data sending.
71000007	INIT-SELF was received.
71000008	LUSTAT (status code=00020000: no input device) was received.
71000009	LUSTAT for which an unrecognizable status code was specified was received.
7101000a	Not enough shared memory.
7101000b	Data was received before the session started.
7101000c	An invalid response was received.
7101000d	A timeout of the send right transfer data reception monitoring timer occurred after SIGNAL was sent.
7101000e	A timeout of the CANCEL reception monitoring timer occurred after a rejection response was sent.
7101000f	A timeout of the READ ALL command response message reception monitoring timer occurred.
71010010	A timeout of the Gaiji request message response monitoring timer occurred.
71010011	A message send request occurred in a video terminal fitted with the component printer.
72zz****	An error was detected in TP1/NET/HNA-560/20 or XNF/S-E2 for a received request message. The system sense code (high-order two bytes of the sense code) of the received negative response is set in ****. For details of sense codes, refer to the sense code list. ZZ indicates the type of the received request message.
73zz****	An error was detected in TP1/NET/HNA-560/20 for a received request message. The system sense code (high-order two bytes of the sense code) of the received negative response is set in ****. For details of sense codes, refer to the sense code list. ZZ is the type of the received request message.
74zz****	A negative response was received from the terminal in response to the request message which was sent. The system sense code (high-order two bytes of the sense code) of the received negative response is set in ****. For details of sense codes, refer to the sense code list. ZZ is the type of the request message which was sent.
7ffffff3	The SSCP-LU transparent data report destination PLU name was defined in the XNF/S-E2 definition.
7ffffff4	The PLU name is invalid.
7ffffff5	Another AP is using the same PLU name.
7ffffff6	PP of communication management is not installed.
7ffffff7	The PU or SLU names have already been assigned.
7ffffff8	The SLU name is not defined for XNF/S-E2.
7ffffff9	The PU name is not defined for XNF/S-E2.
7ffffffa	The PU or SLU name is the same as the PLU name.
7ffffffb	The upper limit on the number of files that can be opened was exceeded in a single process.
7ffffffc	fds is full because the maximum number of PLUs was exceeded.
7ffffffd	A signal was received.
7ffffffe	Communication management terminated with xnfstop of the operator.
7fffffff	Communication management is being initialized or reinitialized.

When the termination code is 06000001:

Detail information	Meaning
00020000	The device received data of CDI=Y (send right transfer). However, there is no input device.
081c0000	The device caused a fixed error. (LU type 3)
081cb000	The device caused a fixed error. (LU type 2 auxiliary device)
081cd000	The device caused a fixed error. (LU type 2 main device)
08310000	The power of the main device was turned off or the physical connection with the TCE section was broken.

Action codes

Action code	Content
xxxxxx01	No action
xxxxxx02	If necessary, restart the session (logon input or session start command input from the terminal).
xxxxxx03	Check the buffer size specified in the exchange buffer group definition of the MCF configuration definition, recreate the MCF configuration definition, then reactivate OpenTP1.
xxxxxx04	Enter the xnfact (PU activation) command. Once the specified time has elapsed, establish the connection.
xxxxxx05	Determine the cause of the error by referring to the detail information. Remove the cause of the error. If there is no system problem, start the session (logon input or session start command input from the terminal).
xxxxxx06	Enter the xnfact (SLU activation) command. Once the specified time has elapsed, establish the connection.
xxxxxx07	By referring to the detail information, determine why the terminal sent the termination request. If there is no system problem, establish the connection.
xxxxxx08	Determine the cause of the error by referring to the detail information. Remove the cause of the error. Once the specified time has elapsed, establish the connection.
xxxxxx09	Check the XNF/S-E2 definition, then reactivate the system.
xxxxxx0a	If XNF/S-E2 stops, activate XNF/S-E2, then establish the connection. If XNF/S-E2 has not stopped, determine the cause of the error by referring to the detail information, remove the cause of the error, and then establish the connection.
xxxxxx0c	Obtain the console log, trace file, and dump information, then contact the maintenance personnel. If necessary, enter the connection establishment command, then establish the connection.
xxxxxx0d	Check the number of buffers specified in the exchange buffer group definition of the MCF configuration definition, recreate the MCF configuration definition, then reactivate OpenTP1.
xxxxxx0e	Reestimate the amount of memory required for OpenTP1 operation, increase the amount of virtual memory, then reactivate the system.
xxxxxx10	Determine the cause of the error by referring to the detail information. Remove the cause of the error. If there is no system problem, enter the connection establishment command and establish the connection.
xxxxxx11	Determine the cause of the error by referring to the detail information, then remove the cause of the error.
xxxxxx12	Determine the cause of the timeout. Remove the cause of the error. Once the specified time has elapsed, start the session (logon input or session start command input from the terminal).