Messages K104 - K146

K104

UTM-D &UTMDEVT (&RCVDANNO): &LSES , &LPAP , &AGUS

; old state: ( &OCVST, &OTAST ); action: &ACTION; new state: ( &NCVST, &NTAST ).

In the case of communication via LU6.1, the message is output on the following events:

• One of the following timers times out:

  • Session/association occupation timer (time1 in the WAITTIME parameter in the LTAC statement). In this case, &LSES contains blanks.
    Exception: Timeout after occupation of a contention loser session.
    Special case: If the session occupation timer of a contention winner session equals 0 and there is no session free at the end of the program unit, this is treated like the timeout of a timer.

  • Response timer (time2 in the WAITTIME parameter in the LTAC statement).
    In this case, &LSES and &AGUS contain different names.

  • Prepare-to-commit timer (value of PTCTIME in the UTMD statement).
    &LSES and &AGUS are identical.

• A connection loss if the session is occupied

  • by a conversation with an open transaction or

  • by a conversation that has initiated transaction termination.

• In the case of a session restart where the session is occupied by a service that has initiated transaction termination

In the case of communication via OSI TP, the message is output on the expiry of one of the following timers. &LSES always contains blanks.

• Association occupancy timer (for dialog jobs see value time1 in KCDEF statement LTAC, parameter WAITTIME, for asynchronous jobs internal value of 60 seconds).
  In the case of an asynchronous job, &ACTION contains the value ASYNCH.

• Response timer (for dialog jobs, see value time2 in KCDEF statement LTAC, parameter WAITTIME, for asynchronous jobs, see value time2 in KCDEF statement UTMD, parameter CONCTIME).
  In the case of a dialog job, processing waits for the response and in the case of asynchronous jobs, processing waits for the acknowledgment from the job receiver. In the case of an asynchronous job, &ACTION contains the value ASYNCH.

• PEND KP and PGWT KP timers (see KDCDEF statement MAX, parameter TERMWAIT or PGWTTIME).

• Ready timer (see KDCDEF statement UTMD with parameter PTCTIME or KDCDEF statement MAX with parameter PGWTTIME)

Inserts	Meaning
&UTMDEVT	Event in response to which the message is issued
	RESTART	Session restart
	DISCON	Connection loss
	TIMEOUT	Time out
&RCVDANNO	Last announcement received at the UTM exchange. In the case of &UTMDEVT = TIMEOUT, the last two bytes in &RCVDANNO have the following meaning:
	X'F330' X'F331'	Timer expiry in OSI-TP job-receiving service after sending a message to a job submitter in a transaction (see KDCDEF statement MAX, parameter TERMWAIT or PGWTTIME).
	X'F332'	Timer expiry in OSI-TP job submitter service after all job receivers have been requested to initiate the end of the transaction. The timer corresponds to the greater of the generated values time in the KDCDEF statements MAX PGWTTIME= and time2 in the KDCDEF statement LTAC WAITTIME= of the participating LTACs.
	X'F333'	Expiry of the ready timer in the OSI-TP job-receiving service (KDCDEF statement UTMD, parameter PTCTIME or KDCDEF statement MAX PGWTTIME=).
	X'F400'	Expiry of the OSI-TP association occupancy timer for a dialog job (time1 in KDCDEF statement LTAC, parameter WAITTIME).
	X'F520'	Expiry of the OSI-TP association occupancy timer for an asynchronous job (internal 60-second timer).
	X'F522'	Expiry of the timer which monitors the reception of an acknowledgment for a queued message sent via an OSI-TP association (time2 in KDCDEF statement UTMD, parameter CONCTIME).
	X'F534'	Expiry of the OSI-TP response timer in the job-submitter service for a dialog job. The timer corresponds to the greater of the generated values time in the KDCDEF statements MAX PGWTTIME= and time2 in the KDCDEF statement LTAC WAITTIME= of the participating LTACs
	X'F800'	Expiry of the LU6.1 session occupancy timer for a dialog job (time1 in KDCDEF statement LTAC, parameter WAITTIME).
	X'F933'	Expiry of the Prepare-to-Commit timer in the LU6.1 jobreceiving service (KDCDEF statement UTMD, parameter PTCTIME or KDCDEF statement MAX, parameter PGWTTIME).
	X'F934'	Expiry of the LU6.1 response timer in a dialog job (The timer corresponds to the greater of the generated values for time in the KDCDEF statement MAX PGWTTIME= and time2 in the KDCDEF statement LTAC WAITTIME= of the participating LTACs).
	X'F935'	Expiry of the LU6.1 response timer in a dialog job after reestablishment of the LU6.1 session (The timer corresponds to the greater of the generated values for time in the KDCDEF statement MAX PGWTTIME= and time2 in the KDCDEF statement LTAC WAITTIME= of the participating LTACs)
	X'F936'	Expiry of the LU6.1 response timer on service restart after the establishment of a session (time2 in KDCDEF statement LTAC, parameter WAITTIME)
&AGUS	Name of the job submitter (user, session or association)
&ACTION	Response taken by openUTM:
	COMMIT	Terminate transaction
	RESET	Roll back transaction
	WAIT	Nothing
	STPROG	Continuation program start
	ASYNCH	Re-execution of the asynchronous job.
&OCVST &OTAST &NCVST &NTAST	Service and transaction status of the job submitter specified in &AGUS (before and after the action specified in &ACTION). Possible values:
	O O	Service and transaction are open.
	O P	The service is open and has initiated the end of the transaction.
	O C	The service is open and the transaction terminated.
	C C	The service and transaction have been terminated.
	O R	The transaction was rolled back and the service remains open.
	Z R	The transaction has been rolled back and the service has been terminated.

K105

UTM-D &SYST mismatch; &LSES , &LPAP , &AGUS

&SYST contains the system with which a mismatch occurred:
DB = database / LPAP = other application

K112	A password change is not possible at this time

K118

Global transaction ID (length, data): (&LTHGTRID,&GTRID)
atomic action ID (length, data): (&AAIS,&AAID)

K119

OSI-TP error information: &OSLPAP, &USER, &TAC, &DIA1, &DIA2, &DIA3

The explanations in the tables below refer to (primitive) log elements at the XAP-TP interface. These data elements have the following meaning:

Data element	Meaning
APM_ALLOCATE_CNF	Response (confirmation) to an association’s request for an OSI-TP dialog. A negative response means that no association could be provided.
TP_BEGIN-DIALOGUE_REQ	Request to the partner to start an OSI-TP dialog.
TP_BEGIN_DIALOGUE_IND	Indication that the partner wants to start an OSI-TP dialog.
TP_BEGIN_DIALOGUE_CNF	Response to the request to start an OSI-TP dialog. A negative response means that the partner has rejected the dialog.
TP_END_DIALOGUE_REQ	Request to the partner to terminate the OSI-TP dialog.
TP_END_DIALOGUE_IND	Indication that the partner wants to terminate the OSI-TP dialog.
TP_U_ABORT_IND	Indication that the remote TP Service User1 has aborted the OSI-TP dialog.
TP_P_ABORT_IND	Indication that the remote TP Service Provider2 has aborted the OSI-TP dialog.
TP_DATA_IND	Indication that data has been transferred by the partner.
TP_U_ERROR_IND	Indication that the partner has reported an error.
TP_HANDSHAKE_IND	Indication of a synchronization (handshake) request by the partner.
APUTM_ABORT_REQ	Request to abort a connection.

¹TP Service User: UTM application
²TP Service Provider: System section which provides the OSI-TP service. In the case of openUTM; this is the XAP-TP component.

The &DIA1 insert contains the reason for outputting message K119.

&DIA1	Meaning
1	A negative APM_ALLOCATE_CNF was received.
2	A negative TP_BEGIN_DIALOGUE_CNF was received.
3	A TP_BEGIN_DIALOGUE_IND was rejected by openUTM.
4	A TP_U_ABORT_IND or TP_P_ABORT_IND was received.
5	A TP_ERROR_IND was received.
6	UTM does not support reception of TP-HANDSHAKE-IND for a dialog message.
7	openUTM does not support reception of TP-END-DIALOGUE-IND from the client for a dialog message. A dialog RTAC may have been generated for an asynchronous LTAC.
8	With the unchained transactions functional unit, openUTM requires that the transaction starts with a dialog.
9	The association was rejected with APUTM_ABORT_REQ.
10	Resource bottleneck in UTM

The inserts &DIA2 and &DIA3 contain additional information depending on the value of &DIA1:

&DIA1	&DIA2 / Meaning	&DIA3 / Meaning
1	Cause of rejection:	Diagnostic information:
	0 = ACSE Service User 1 = ACSE Service Provider	-1	No reason given
		1	Association Establishment Timeout For UTM applications on BS2000 systems this might be caused by a missing BCMAP-Entry.
		2	Application Context Name is not supported
		3	Job submitter's Application Process Title (APT) is unknown
		4	Job submitter's Application Identifier (APID) is unknown
		5	Job submitter's Application Entity Qualifier (AEQ) is unknown
		6	Job submitter's Application Entity Identifier (AEID) is unknown
		7	Job receiver's Application Process Title (APT) is unknown
		8	Job receiver's Application Identifier (APID) is unknown
		9	Job receiver's Application Entity Qualifier (AEQ) is unknown
		10	Job receiver's Application Entity Identifier (AEID) is unknown
	2 = Presentation Service Provider	-	Not relevant
	6 = TP Service Provider	-1	No reason given.
		0	CCR version 2 not available.
		1	Incompatible TP protocol version
		2	No contention winner association available. Possible cause: The number of associations in the partner application is smaller than in the local UTM application.
	7 = Association Pool Manager	-1	No reason given.
		4	Association Pool Manager cannot construct any further associations.
		6	Local or remote Application Entity Title (AET) is unknown.
		7	No matching association found for the specified AET.
2	Cause of rejection:	Diagnostic information:
	2 = TP Service Provider 3 = TP Service User	0	No reason given.
		1	TPSU title not known.
		2	TPSU title permanently unavailable.
		3	The possible reasons are: TPSU title temporarily unavailable. No free OSI TP instance table for the ACCESS-POINT is available in the partner application. No free dialog table available. There is another resource bottleneck in openUTM. Message K119 with &DIA1=10 at the job receiver contains more detailed information about the type of bottleneck. Action: Generate a larger number of associations for the ACCESS-POINT's OSI-LPAP partner at the partner application.
		4	No TPSU title specified.
		5	Functional unit not supported.
		6	Combination of functional units not supported.
		7	Association reserved for partner.
		8	Partner AEI unknown.
		11	Functional Unit Shared Control not supported by openUTM.
		12	TPSU title cannot be decoded.
		13	Type of TPSU title not supported.
		14	TPSU title is too long.
	2 = TP Service Provider 3 = TP Service User	15	Decoding error for user data.
		16	Decoding error for security data.
		17	Abstract syntax (UTMSEC) unknown or not generated.
		18	User ID unknown or partner application generated without USER or user ID rejected, e.g. due to incorrect password.
		19	Partner not available, e.g. locked (STATUS=OFF) or due to QUIET command.
		20	User ID or password too long.
		21	Warning level 2 for page pool exceeded.
		22	The possible reasons are: Invalid transaction code Transaction code locked No administration rights.
		23	Transaction code not generated with CALL=FIRST.
		24	Asynchronous service cannot be started. The queue level generated for the asynchronous TAC (maximum number of messages in the message queue) has already been reached.
		25	Dialog service cannot be started because the transaction code has been generated as an asynchronous TAC (KDCDEF statement TAC TYPE=A).
		26	Combination of functional unit and restart functionality (KDCDISP) is not supported.
3	Cause of rejection:	Diagnostic information:
	3 = TP Service User	4	No TPSU title specified
		11	Functional Unit Shared Control not supported by openUTM.
		12	TPSU title cannot be decoded.
		13	Type of TPSU title not supported.
		14	TPSU title is too long.
		15	Decoding error for user data.
		16	Decoding error for security data.
		17	Abstract syntax (UTMSEC) unknown or not generated.
		18	User ID unknown or partner application generated without USER or user ID rejected, e.g. due to incorrect password. For more detailed information, see the previous message K147.
		19	Partner not available, e.g. locked (STATUS=OFF) or due to QUIET command.
		20	User ID or password too long.
		21	Warning level 2 for page pool exceeded.
4	Cause of rejection:	Diagnostic information:
	2 = TP Service Provider 3 = TP Service User	0	No reason given.
		1	A permanent error has occurred.
		2	TP_BEGIN_TRANSACTION_REQ rejected.
		3	A temporary error has occurred.
		4	A protocol error has occurred.
		5	Collision of two TP_END_DIALOGUE_REQ primitives.
		6	Collision of TP_BEGIN_TRANSACTION_REQ and TP_END_DIALOGUE_REQ.
9	Cause of rejection:	Diagnostic information:
	3 = TP Service User	21	Warning level 2 for page pool reached. The queued message could not be saved.
		31	The KDCFILE file is full: The message could not be saved.
		32	Decoding error for the UDT data of a TP_DATA_IND primitive
		The association is interrupted in all cases.

&DIA1	&DIA2 / Meaning		&DIA3 / Meaning
10	Affected resources:		Diagnostic information:
	11	No free OSI TP instance table for this ACCESS-POINT is available in the application of the job-submitting service. The cause is a message to an OSI TP partner when all OSI TP instance tables are occupied. The message is entered in a queue. Action: Generate a larger number of associations for the access point's OSI-LPAP partners.1	Not relevant
	12	No free OSI TP instance table for this OSI-LPAP partner is available in the application of the job-submitting service. The cause is a message to the OSI TP partner when all OSI TP instance tables are occupied. The message is entered in a queue. Action: Generate a larger number of associations for the access point's OSI-LPAP partners.1	OSI-LPAP index
	13	The instance is occupied in XAPTP in the application of the job-submitting service. The message is entered in a queue. Action: Generate a larger number of associations for the access point's OSI-LPAP partners.1	UTM instance index
	14	In the application of the job-submitting service, an error occurred while reading the queued message to be sent. The message is entered in a queue.	Not relevant
	15	No free OSI TP node table available. This error can occur in both an application of a job-submitting service and in an application of a job-receiving service. In an application of a job-submitting service, the message is entered in a queue. Action: Generate a larger number of associations for the OSI-LPAP partners.1	Not relevant
	16	There is no free OSI TP service available in the application of the job-receiving service. Action: Generate a larger number of associations for the OSI-LPAP partners.1	Not relevant
	17	There is no free OSI TP user table for the OSI-LPAP partner in the application of the job-receiving service. Possible cause: A dialog program unit whose association has been interrupted in the interim is still active for the OSI-LPAP partner.	OSI-LPAP index

¹ KDCDEF generation OSI-LPAP ASSOCIATIONS=

K120

Password expired - please sign on

K122

Your password is valid for &NUMDAYS more day(s) only

K123

LTERM does not have the rights to continue the service - please sign on

K124

Error: &RCOSTS (&RCXAPTP) at startup of XAP-TP occurred in phase: &PHAXAPTP

This message is output as a diagnostic aid for errors which occur when starting XAP-TP

Meaning of the inserts:

&RCOSTS	Return code specifying the error in more detail. Depending on the phase (value of &PHAXAPTP), the return codes have different meanings. If the return code is not listed in the following table, it is an internal error (in this event, you must write a problem report).
&RCXAPTP	Return code specifying the internal error in more detail.
&PHAXAPTP	Phase during start of XAP-TP. Possible values: INIT (passing of the generation values to XAP-TP) START/RECOVERY (OPEN and BIND of the instances and recovery of incomplete transactions).

&PHAXAPTP	&RCXAPTP	Meaning
INIT	18	The OSS version is lower than 4.0A20.
	20	KDCFILE and ROOT do not match. Possible cause: A new KDCFILE was generated with KDCDEF (new: with OSI-TP, old: without OSI-TP); the UTM application was, however, not relinked or the ROOT source was not recompiled.
	16 60 85	Not enough memory space could be allocated to cover the OSI-TP-specific generation values.
	21	The KCSALME call to create the transfer buffer for the transfer syntaxes returned a bad return code.
	41	The "apext_init" sequence has already been executed.
	44	The KCSALME call to create the transfer buffer for the abstract syntaxes returned a bad return code.
	63	The KCSALME call to create the transfer buffer for the access points returned a bad return code.
	99	A function called by "apext_att" returned a bad return code. This return code can also mean that the address space that the OSS wants to allocate for its shared memory in a follow-up task is already being used as shared memory (e.g. by KAA, XAPTP global memory). Response: try to start additional tasks.
	102	Error on attach. Action: Check whether an application is already signed-on under this name at this computer.
	106	XAPTP "apext_att" call Return code: APEXT_ATTACH_INVEREF Meaning: The waiting point reference specified in the OSS o_attach call is invalid or is not (or no longer) recognized. Possible cause: Follow-on task cannot be started because the application has already been terminated.

K125	Password not complex enough - contact administrator or sign off

K127

Internal error in UTM - ROOT: &ERCD6

Insert &ERCD6 contains the reason why message K127 was output.

&ERCD6	Meaning
RT04	Incorrect action index in KDCRTMM

K128

UTM-D job rejected: &CON/&PRNM/&BCAP/&LPAP &LSES &REA1 &RCDC &TAC

If the job is an OSI-TP UTM-D job, the inserts have the following meanings:

&CON:	OSI-CON name
&PRNM:	Eight blanks
&BCAP	ACCESS-POINT name
&LPAP	OSI-LPAP name

Insert &REA1 contains the reason why message K128 was output.

&REA1	Meaning
X'01'	Invalid transaction code LU6.1: DPN or PRN in FMH-5 or FMH-6 or the first 8 characters of the message OSI-TP: Recipient tpsu title in TP-BEGIN-DIALOGUE-RI &RCDC contains an error code KCRCDC
X'02'	Transaction code not generated with CALL=FIRST LU6.1: DPN or PRN in FMH-5 or FMH-6 or the first 8 characters of the message OSI-TP: Recipient tpsu title in TP-BEGIN-DIALOGUE-RI
X'03'	An asynchronous service is to be started, TAC is generated with TYPE= D LU6.1: Message with begin bracket and end bracket OSI-TP: Receipt of an TP-END-DIALOGUE-RI protocol element
X'04'	A dialog service is to be started, TAC is generated with TYPE=A LU6.1: Message with begin bracket and change direction OSI-TP: Receipt of TP-GRANT-CONTROL-RI or TP-HANDSHAKE-AND-GRANT-CONTROL-RI.
X'05'	An asynchronous service is to be started but the QLEV of the asynchronous TAC has already been reached. LU6.1: The connection is cleared down. OSI-TP: The connection is cleared down.
X'06'	Only in the case of heterogeneous connections via LU6.1: A asynchronous message was received with RQE. openUTM expects RQD2. Action: In the case of CICS, it is necessary to specify NOCHECK and PROTECT in the START command.
X'07'	Only for heterogeneous connection using LU6.1: A message was received with EC and RQD2 but neither CD nor EB is set. Response: modify CICS or IMS program.

K129

&CMD - start parameter not allowed at this moment! Statement ignored

K130

Task priority &TPRIO not allowed for task &TASK! Priority not changed.

K132

&OBJ1 and &OBJ2 have not been generated by the same KDCDEF run

K133

Program for &EXIT missing!

K134

Message to &DEST has been placed into dead letter queue. &NMSG message(s) in dead letter queue

As soon as the generated threshold is reached, this message informs the administrator of asynchronous messages which have been sent to the dead letter queue after abnormal processing.

The inserts have the following meaning:

Insert	Meaning
&DEST	Original destination of the message which resulted in the dead letter queue threshold being reached.
&NMSG	Generated threshold value for the number of messages in the dead letter queue.

K135

UPIC message :
&PTRM/&PRNM/&BCAP/&LTRM/&UPCREAS/&UPCSTAT/&UPCPROT/&UPVENC1/&UPPENC2

A problem occurred in interoperation with a UPIC client. The value of insert &UPCREAS indicates the cause of the problem. The possible values for &UPCREAS and their meanings are described in the following table.

&UPCREAS	Meaning	Reason / Response
01	UPIC client sends without send right	Error in product UPIC or UTM
02	UPIC client sends protocol which is too short	Error in product UPIC
03	UPIC client proposes a protocol version which is not supported for the connection setup	UPIC version incompatible with openUTM version
04	UPIC client sends invalid protocol	UPIC error
05	UPIC client has initiated abortion of the conversation	Effect of the UPIC function Deallocate() (CMDEAL())
06	UPIC client has not sent a TAC	UPIC error or subsequent error after a suppressed service restart
07	TAC sent by the UPIC client is not generated LTERM/USER don’t have a key is administrator TAC and the USER is not administrator is existing and program does not exist.	User error (Side info or SETTP)
08	UPIC client has sent a TAC generated with CALL=NEXT	User error
09	UPIC client has sent a TAC which is locked/deleted, or has too low encryption	User error (Side info or SETTP)
0A	UPIC client has sent a TAC which is too short	UPIC error
0B	UPIC client has sent a TAC when a service is open	UPIC error
0C	UPIC client has sent a TAC for a continuation section	UPIC error
0D	UTM page pool is too small for input message	Page pool for application generated too small (statement MAX PGPOOL)
0E	UPIC client grants only send right when a message is open	UPIC error
0F	UPIC client grants send right when a message is open without closure of current message section	UPIC error
10	UPIC client has sent a TAC generated with TYPE=A (asynchronous TAC)	User error
11	UPIC client is assigned to an LTERM with STATUS=OFF (locked) on connection setup	Normal behavior
12	UPIC client is assigned to an LTERM with STATUS=OFF (locked) on message receipt	Normal behavior Administrator has locked LTERM
13	UPIC client has sent USER with invalid length	UPIC error
14	UPIC client has sent invalid USER or PASSWORD	User error
15	UPIC client has sent invalid data for service restart, e.g. KDCDISP without USER or with additional user data.	User error
16	UPIC client has sent invalid data for service restart, e.g. KDCDISP for USER with RESTART=NO	User error
17	UPIC partner has sent a user but the UTM application is generated without users.	User error
18	Invalid length of the protocol token received.	UPIC error
19	Invalid protocol token has been received.	UPIC error
1A	Overall length of the received data is inconsistent.	UPIC error or transport system error
1B	The protocol token for data was not the last protocol token.	UPIC error
1C	Two protocol tokens for the service were received.	UPIC error
1D	Two protocol tokens for the user ID were received.	UPIC error
1E	Two protocol tokens for the password were received.	UPIC error
1F	Two protocol tokens for the form were received.	UPIC error
20	Two protocol tokens for the function key were received.	UPIC error
21	No protocol tokens for data were received.	UPIC error
22	Inconsistent sign-on data was received.	UPIC error
23	A protocol token was received for a user ID, but not for a service.	UPIC error
24	Invalid function key.	UPIC error
25	Protocol token for a form was received in a data fragment.	UPIC error
26	Protocol token for a function was received in a data fragment.	UPIC error
27	Invalid encryption level	UPIC or UTM error
28	Length of the received user message is invalid	UPIC error
29	An error occurred during the protocol discussion	UPIC or UTM error
2A	Two protocol tokens were received for encrypted data	UPIC error
2B	Two protocol tokens were received for one encrypted password	UPIC error
2C	Two protocol tokens were received for one RSA key	UPIC error
2D	Two protocol tokens were received for one DES or AES key	UPIC error
2E	Two protocol tokens were received for one cursor	UPIC error
2F	Two protocol tokens were received for one protocol discussion	UPIC error
30	No protocol tokens were received for encrypted data	UPIC error
31	One protocol token for one password and one encrypted password were received	UPIC error
32	An error occurred while decrypting the password	UPIC or UTM error
33	The decrypted password is longer than the length supported by openUTM in this version.	UPIC error or the UPIC version supports longer passwords
34	An error occurred while reading the DES key	UPIC or UTM error
35	The RSA key cannot be sent	UPIC error
36	An error occurred while reading the RSA key	UPIC error
37	An error occurred while encrypting the data	UPIC error
38	An error occurred while decrypting the data	UPIC or UTM error
39	The message was encrypted with a lower encryption level than was negotiated for the service.	UPIC error
3A	The protocol discussion could not be completed	UPIC error
3B	An error occurred while exchanging keys	UPIC error
3C	The UPIC client does not support encryption	Normal behavior, change UTM generation
3D	Two protocol tokens were received for the transaction status	UPIC error
3E	Two protocol tokens were received for the client context	UPIC error
3F	The length of the user message in the connection letter is not compatible with the protocol version	UPIC error
40	openUTM does not support encryption	Normal behavior, change UTM generation
41	Two protocol tokens received for new password	UPIC error
42	Two protocol tokens received for encrypted new password	UPIC error
43	Protocol tokens received for new password and encrypted new password	UPIC error
44	Impermissible operation code occurred with the call of the internal function PASSWD_ENCRYPT_PROC to decrypt a password.	UPIC error
45	Two protocol tokens received for the client type.	UPIC error
46	No RSA key could be found.	Activate one of the RSA keys
47	UPIC client proposes no protocol version for the connection setup.	No UPIC client or UPIC error
48	UPIC client sends protocol version that was not negotiated.	UPIC error
49	The password received from the client is longer than supported by openUTM in this version.	UPIC error or the UPIC version supports longer passwords
4A	The new password received from the client is longer than supported by openUTM in this version.	UPIC error or the UPIC version supports longer passwords
4B	The decrypted password received from the client is longer than supported by openUTM in this version.	UPIC error or the UPIC version supports longer passwords
4C	The TAC received from the client is longer than supported by openUTM in this version.	UPIC error or the UPIC version supports longer TACs
4D	The USER received from the client is longer than supported by openUTM in this version.	UPIC error or the UPIC version supports longer USERs
4E	The format received from the client is longer than supported by openUTM in this version.	UPIC error or the UPIC version supports longer formats
4F	The function key received from the client is longer than supported by openUTM in this version.	UPIC error or the UPIC version supports longer function keys
50	The DES or AES key received from the client is too long.	UPIC error
51	The encrypted password received from the client is too long.	UPIC error
52	The encrypted new password received from the client is too long.	UPIC error
53	Two protocol tokens received for GTRID	JConnect error
54	The GTRID received from the client is too long.	JConnect error
55	A protocol token has been received for GTRID although one transaction is still open.	JConnect error
56	The client sent a token which is not supported by the server in this version.	UPIC error
57	The client sent a token which may only be sent by the server.	UPIC error
58	The client sent a token which may only be sent by the server.	UPIC error
59	The client sent a token which may only be sent by the server.	UPIC error
5A	The client sent a token which may only be sent by the server.	UPIC error
5B	The client sent a token which is not supported by the server in this version.	UPIC error
5C	The client sent a token which may only be sent by the server.	UPIC error
5D	The client sent a token which may only be sent by the server.	UPIC error
5E	The client sent a token which may only be sent by the server.	UPIC error
5F	The client sent a token which may only be sent by the server.	UPIC error
60	A GTRID was received in a sign-on conversation.	JConnect error
61	The length of the client type token is invalid.	UPIC error
62	The server expected an encrypted message.	UPIC error
63	The encrypted message is shorter as announced in the protocol data.	UPIC error
64	The IV-token for the user message is missing.	UPIC error
65	The IV-token for the user message was received more than once.	UPIC error
66	The IV-token for the password is missing.	UPIC error
67	The IV-token for the password was received more than once.	UPIC error
68	The IV-token for the new password is missing.	UPIC error
69	The IV-token for the new password was received more than once.	UPIC error
6A	The client sent a Diffie-Hellman token which may only be sent by the server.	UPIC error
6B	The client Diffie-Hellman token was received more than once or it is illegal in the current context.	UPIC error
6C	The client did not sent an AES-key.	UPIC error
6D	The client did not sent a Diffie-Hellman token.	UPIC error
6E	The length of the IV-Token is invalid.	UPIC error
6F	Error while generating a Diffie-Hellman key pair.	UTM error; the encryption functionality might be unavailable
70	Error while generatig the Diffie-Hellman secret.	UTM error
71	Encryption error for algorithm AES-GCM	UTM error
72	Decryption error for algorithm AES-GCM	UTM error
73	UPIC client supports encryption but proposes a protocol version with which encrypted communication is not possible.	UPIC version < V07.0 and UTM version >= V7.0A

The inserts &UPCSTAT and &UPCPROT are used for diagnosis in error situations.

Inserts &UPVENC1 and &UPPENC2 are used for diagnosing data encryption.

The first byte of &UPVENC1 contains the ENCRYPTION_LEVEL of the message, the second byte of &UPVENC1 contains the ENCRYPTION_LEVEL of the
conversation.

The first byte of &UPPENC2 contains the ENCRYPTION_LEVEL of the session, the second byte of &UPPENC2 contains the ENCRYPTION_LEVEL of the partner.

K136

(First) SYSLOG file is &FNAM

openUTM outputs this message in the start phase. &FNAM contains the name of the SYSLOG file. If the SYSLOG is created as a file generation group, &FNAM then contains the name of the first file generation which is written by openUTM.

K137

SYSLOG switched to file &FNAM

openUTM has successfully switched to a new SYSLOG file generation. The switchover was initiated by the administration or by the automatic size monitoring facility. &FNAM contains the name of the new SYSLOG file generation.

K138

SYSLOG file &FNAM closed

Two situations should be differentiated:

• the SYSLOG is maintained as a single file:
  The last UTM task of the application has closed the SYSLOG file. &FNAM contains the name of the SYSLOG file.

• the SYSLOG is maintained as a SYSLOG FGG:
  A SYSLOG file generation was closed by the last openUTM task (i.e. completely). This file generation is now freely available. It is no longer required by UTM. &FNAM contains the name of the closed file generation.

K139	Switching SYSLOG failed! Still using file &FNAM The attempt to switch to a new SYSLOG file generation has failed. openUTM continues working with the file generation &FNAM. It may be possible to ascertain the reason for the error occurring on switchover from the DMS error code in the preceding message K043.
K140	There is no supported MUX protocol version in the range from &MXP1 to &MXP2
K141	The MUX protocol version &MXP1 is not supported
K142	Release pending timeout for session. PTERM: &PTRM MUX-PTERM: &MXPT
K143	UTM-D: STSN sequence numbers response differ from request. Request: &STS1, &STS2 Response: &STS3, &STS4
K145	Due to a transaction recovery no sign-on can be processed by user &USER at this time - please sign on
K146	Monitoring BCAM waiting time. OPCODE=&BCMOPCD, RTCODE= &BCMRTCD, standard header= &STDHEAD, TSN= &TASK, BCAM appliname= &BCAP