openUTM-LU62 Gateway error messages at runtime

	Messages concerning the OSI-TP protocol stack for connections between the proxy container and the openUTM-LU62 Gateway begin with letter P. All of these messages are described in the section  P messages . All other messages of the openUTM-LU62 Gateway begin with the string u62_tp[<comp>]<nnn>. In this prefix, <comp> specifies the sub-component of the openUTM-LU62 Gateway and <nnn> the message number.
004	Error on signal handling, errno &ERRNO (&ERRTEXT) Action: Inform system service.
006	Error opening the configuration file &FILENAME, errno &ERRNO (&ERRTEXT) Action: For ERRNO see the section  System error codes  or inform system service.
010	The instance for the local LU name &LUNAME is already running Action: Inform system service.
012	Internal error occurred Action: Inform system service.
015	PID file &PIDFILE cannot be created, errno &ERRNO (&ERRTEXT) Action: For ERRNO see the section  System error codes  or inform system service.
016	Write to PID file &PIDFILE failed, errno &ERRNO (&ERRTEXT) Action: For ERRNO see the section  System error codes  or inform system service.
026	Crash of openUTM-LU62 in module &MODULNAME Action: Inform system service. Save the contents of the following directory: On Solaris and Linux systems: /opt/lib/utmlu62/PROT On Windows systems: <gateway_home>\utmlu62\PROT If possible, you should reproduce the error with the instance trace activated.
027	Shutdown by the XAP-TP provider: &REASON Action: Inform system service. Save the contents of the following directory: On Solaris and Linux systems: /opt/lib/utmlu62/PROT On Windows systems: <gateway_home>\utmlu62\PROT If possible, you should reproduce the error with the XAP-TP trace activated.
036	Error in allocating a new shared memory of length &LEN, errno &ERRNO (&ERRTEXT) Action: For ERRNO see System error codes or inform system service.
040	Error in the configuration of the local LU &LLUNAME or of the partner LU &RLUNAME Action: Generation error in one of the following proxy components: On Solaris systems: SNAP-IX On Linux and Windows systems: IBM Communications Server
048	The node is deactivated: No conversations can be established The node of the SNAP-IX or IBM Communications Server was presumably deactivated by the administrator. It is no longer possible to start conversations to the EIS partner. Action: Check the following proxy component: On Solaris systems: SNAP-IX On Linux and Windows systems: IBM Communications Server
302	Conversation rejected, TP Name &TPNAME, job submitted by LU6.2 side: Restart of the nominated control instance not completed yet. This can occur when the connection to the EIS partner is re-established after a crash, but the connection between the openUTM-LU62 Gateway and the proxy container has not yet been re-established. Action: Repeat the job.
303	Incoming conversation (TP Name &TPNAME, job submitted by LU6.2 side) supplies initialization data that will be discarded by openUTM-LU62. Action: Inform system service.
304	Conversation rejected, TP Name &TPNAME, job submitted by LU6.2 side: Security data not supported by the OSI TP partner or contain invalid characters. Action: Inform system service.
305	Conversation rejected, TP Name &TPNAME, job submitted by LU6.2 side: The alias name &ALIAS of the partner LU is not identical with the configured name &CONFALIAS. Action: Check the openUTM-LU62 Gateway generation.
306	Conversation rejected, TP Name &TPNAME, job submitted by LU6.2 side: Service TPs using mapped (!) conversations are not supported! The LU6.2 partner has attempted to start a conversation with a non-printable TP name (i.e. a transaction code between X'00' and X'3F'). The openUTM-LU62 Gateway does not support these types of service TPs, except for the resync-TP X'06F2'. This message appears, for example, when the EXEC CICS START function that addresses the service TP X'02' in the openUTM-LU62 Gateway is used.
307	Conversation rejected, TP Name &TPNAME, job submitted by LU6.2 side: Configuration error: The net name of the local and/or of the partner LU has been changed! Action: Check the openUTM-LU62 Gateway generation.
308	Conversation rejected, TP Name &TPNAME, job submitted by LU6.2 side: Error in the exchange of the log names between the local and the remote LU! The LU6.2 partner has opened a conversation to the openUTM-LU62 Gateway with synclevel 2 although the log names have not yet been exchanged between the two LUs, or a fatal error occurred the last time the log names were exchanged. The openUTM-LU62 Gateway reacts to this protocol violation by immediately closing the conversation. Action: The administrator of the transactional resources must check which actions must be reset. System service cannot check this.
309	RECEIVE_ALLOCATE rejected due to configuration error: The local LU alias name &LUNAME is not configured! Action: Check the generation of The openUTM-LU62 Gateway On Solaris systems: SNAP-IX On Linux and Windows systems: IBM Communications Server
310	RECEIVE_ALLOCATE failed: LU6.2 base software is not running! Action: Start the following proxy component: On Solaris systems: SNAP-IX On Linux and Windows systems: IBM Communications Server
311	RECEIVE_ALLOCATE failed: system error (errno &ERRNO ) occurred: &ERRTEXT Error On Solaris systems: in SNAP-IX On Linux and Windows systems: in the IBM Communications Server Action: For ERRNO see System error codes or inform system service.
312	Allocation of a conversation to the LU6.2 partner rejected, TP Name &TPNAME, job submitted by OSI TP side. Action: Check the generation of The openUTM-LU62 Gateway On Solaris systems: SNAP-IX On Linux and Windows systems: IBM Communications Server
313	Allocation of a conversation to the LU6.2 partner rejected, TP Name &TPNAME, job submitted by OSI TP side: The LU6.2 base software is not running! Reason: The proxy component is not started. Action: Start the following proxy component: On Solaris systems: SNAP-IX On Linux and Windows systems: IBM Communications Server
314	Allocation of a conversation to the LU6.2 partner rejected, TP Name &TPNAME, job submitted by OSI TP side: system error (errno &ERRNO ) occurred: &ERRTEXT Error On Solaris systems: in SNAP-IX On Linux and Windows systems: in the IBM Communications Server Action: For ERRNO see System error codes or inform system service.
315	Actively allocated conversation to LU6.2 partner deallocated (TP Name &TPNAME, job submitted by OSI TP side) again due to a configuration error: The net name of the local and/or of the partner LU has been changed! Action: Check the generation of The openUTM-LU62 Gateway On Solaris systems: SNAP-IX On Linux and Windows systems: IBM Communications Server
320	Allocation of a conversation to LU6.2 partner failed, TP Name &TPNAME, job submitted by OSI TP side: Allocation error (code = &ERRTEXT) No conversations to the TP &TPNAME of the LU6.2 partner can be actively opened at the moment. (&TPNAME is in this case the CICS transaction code, for example.) The error code &ERRTXT then contains the return code of the corresponding LU6.2 call in plain text. Action: Start the CICS application.
321	Allocation of a conversation to LU6.2 partner failed, TP Name &TPNAME, job submitted by OSI TP side: Inconsistency in the configurations of openUTM-LU62 and the LU6.2 base software Action: Check the generation of The openUTM-LU62 Gateway On Solaris systems: SNAP-IX On Linux and Windows systems: IBM Communications Server
322	Allocation of a conversation to LU6.2 partner failed, TP Name &TPNAME, job submitted by OSI TP side: Security data invalid Action: Inform system service.
332	Conversation to the LU6.2 partner (TP Name &TPNAME, job submitted by OSI TP side) terminated by shutdown of the LU6.2 base software! Action: Check the diagnostic information and restart On Solaris systems: SNAP-IX On Linux and Windows systems: IBM Communications Server
333	Conversation to the LU6.2 partner (TP Name &TPNAME, job submitted by LU6.2 side) terminated by shutdown of the LU6.2 base software! Action: Check the diagnostic information and restart On Solaris systems: SNAP-IX On Linux and Windows systems: IBM Communications Server
334	Conversation to the LU6.2 partner (TP Name &TPNAME, job submitted by OSI TP side) terminated by conversation error! Possibly caused by an administrative shutdown of all sessions. Action: Inform the administrator or system service.
335	Conversation to the LU6.2 partner (TP Name &TPNAME, job submitted by LU6.2 side) terminated by conversation error! Possibly caused by an administrative shutdown of all sessions. Action: Inform the administrator or system service.
336	User control data received on a conversation to the LU6.2 partner (TP Name &TPNAME, job submitted by OSI TP side) => Termination of the conversation by openUTM-LU62! Action: Inform system service.
337	User control data received on a conversation to the LU6.2 partner (TP Name &TPNAME, job submitted by LU6.2 side) => Termination of the conversation by openUTM-LU62! Action: Inform system service.
338	Return code AP_STATE_CHECK received on a conversation to the LU6.2 partner (TP Name &TPNAME, job submitted by OSI TP side) => Termination of the conversation by openUTM-LU62! Action: Inform system service.
339	Return code AP_STATE_CHECK received on a conversation to the LU6.2 partner (TP Name &TPNAME, job submitted by LU6.2 side) => Termination of the conversation by openUTM-LU62! Action: Inform system service.
340	Incoming conversation to the LU6.2 partner rejected, (TP Name &TPNAME, job submitted by LU6.2 side) Expiration of the timer for the supervision of the association allocation This maximum wait time is configurable in the openUTM-LU62 Gateway using the parameter ALLOC-TIME, where the default value is 30 seconds. If this message appears often, you should either increase the session limit or decrease the number of parallel connections for the openUTM-LU62 Gateway. Alternatively, inform system service.
341	Incoming conversation to the LU6.2 partner rejected, (TP Name &TPNAME, job submitted by OSI TP side) Expiration of the timer for the supervision of the association allocation This maximum wait time is configurable in the openUTM-LU62 Gateway using the parameter ALLOC-TIME, where the default value is 30 seconds. If this message appears often, you should either increase the session limit or decrease the number of parallel connections for the openUTM-LU62 Gateway. Alternatively, inform system service.
350	XAP-TP provider rejects association allocation (TP Name &TPNAME): result = &RES, source = &SRC, reason = &RSN The proxy container rejects the association. Action: See the proxy container messages.
351	XAP-TP provider reports loss of association (TP Name &TPNAME): source = &SRC, reason = &RSN, event = &EVT The proxy container rejects the association. Action: See the proxy container messages.
352	OSI-TP partner (XAP-TP user) rejects begin dialogue request: TP Name &TPNAME, job submitted by LU6.2 side The proxy container rejects the dialog request. Action: See the corresponding proxy container message or inform system service.
353	OSI-TP partner (XAP-TP user) rejects begin dialogue request: TP Name &TPNAME, job submitted by OSI TP side: Reason = &RSN The proxy container rejects the dialog request. Action: See the corresponding proxy container message or inform system service.
354	Diagnostic information in the initialization data of AP_TP_BEGIN_DIALOGUE_CNF: 0xhhhh (d,d) hhhh represents the hexadecimal value and d,d represent the according decimal values. For UTM as OSI-TP partner, the initialization data contains further information on the reason, why the dialog has been rejected. The first value shows whether the fault is transient (1) or permanent (2). The second value shows the detailed reason for rejection. For the meaning of these values see K messages , description DIA3 in message K119 for DIA1=2.
361	Incoming dialogue rejected, job submitted by OSI-TP side: Cannot decode local TPSU title Action: Inform system service.
373	Incoming dialogue rejected, TP Name &TPNAME, job submitted by OSI-TP side: Restart of the nominated control instance not completed yet Action: Repeat the job.
374	Incoming dialogue rejected, TP Name &TPNAME, job submitted by OSI-TP side: Remote application process title is not consistent with the configuration Action: Check the generation of the proxy container and the openUTM-LU62 Gateway.
375	Incoming dialogue rejected, TP Name &TPNAME, job submitted by OSI-TP side: Remote application entity qualifier is not consistent with the configuration Action: Check the generation of the proxy container and the openUTM-LU62 Gateway.
390	OSI-TP dialogue aborted by partner (XAP-TP provider), TP Name &TPNAME, job submitted by LU6.2 side Action: See the corresponding proxy container message or inform system service.
391	OSI-TP dialogue aborted by partner (XAP-TP provider), TP Name &TPNAME, job submitted by OSI TP side Action: See the corresponding proxy container message or inform system service.
392	OSI-TP dialogue aborted by partner (XAP-TP user), TP Name &TPNAME, job submitted by LU6.2 side Action: See the corresponding proxy container message or inform system service.
393	OSI-TP dialogue aborted by partner (XAP-TP user), TP Name &TPNAME, job submitted by OSI TP side Action: See the corresponding proxy container message or inform system service.
408	OSI-TP partner indicates heuristic mix. TP Name &TPNAME, job submitted by &PARTNER side Probably the transaction between the proxy container and openUTM-LU62 Gateway is inconsistent. Action: You usually need to change the participating database manually in this case to recoordinate the inconsistent database records. Inform system service.
409	OSI-TP partner indicates heuristic hazard. TP Name &TPNAME, job submitted by &PARTNER side Probably the transaction between the proxy container and openUTM-LU62 Gateway is inconsistent. Action: You usually need to change the participating database manually in this case to recoordinate the inconsistent database records. Inform system service.
410	Syncpoint request received from LU6.2 job-receiving service. TP Name &TPNAME. Transaction is aborted. A job receiving program on the CICS side has requested a syncpoint (e.g. EXEC CICS SYNCPOINT) without having been requested to do so by the proxy container. This is prohibited. The transaction is aborted. &TPNAME specifies the transaction code on the CICS side. Action: Change the CICS application program.
420	Error during resynchronization of a transaction. LU6.2 partner does not accept the state &STATE. A transaction has been interrupted in the commit phase due to a loss of the connection on the LU6.2 side. An error has occurred during resynchronization with the LU6.2 partner. The transaction cannot be reset or aborted. Action: You usually need to change the participating database manually in this case to recoordinate the inconsistent database records. The administrator must abort the transaction manually.
421	Log name error during resynchronization of a transaction. A transaction has been interrupted in the commit phase due to a loss of the connection on the LU6.2 side. An error has occurred during resynchronization with the LU6.2 partner. The transaction cannot be reset or aborted. Action: You usually need to change the participating database manually in this case to recoordinate the inconsistent database records. The administrator must abort the trans action manually.
423	Protocol error of LU6.2 partner: Compare States &LUWSTATE &RRI received in state &STATE1/&STATE2. Malfunction of the EIS partner. Action: You usually need to change the participating database manually in this case to recoordinate the inconsistent database records. Inform the EIS partner's administrator.
424	LU6.2 partner indicates a protocol error. State: &STATE1/&STATE2, TP Name &TPNAME, job submitted by &PARTNER side. Action: Inform system service.
425	Invalid log record (error type &ERROR). Transaction is removed. A faulty log record was read during a warm start of the openUTM-LU62 Gateway. The transaction recorded in this log record can therefore not be resynchronized. Action: You usually need to change the participating database manually in this case to recoordinate the inconsistent database records. The administrator must abort the transaction manually.
426	Problem at the XAP-TP interface. &EVENT received. Action: Inform system service.
427	Error &ERRNO when issuing &CALL. An error has occurred in a Solaris or Linux system call. This can lead to the abnormal termination of the openUTM-LU62 Gateway. Action: For ERRNO see System error codes or inform system service.
510	The LU (alias name = &ALIASNAME, net name = &NETNAME) has returned an abnormal reply to the Exchange Logname command. Action: Inform system service.
511	A cold start has been attempted by LU (alias name = &ALIASNAME, net name = &NETNAME), but the local LU has logical units of work that are awaiting resynchronization from the previous activation. Action: Inform system service.