Messages K001 - K048

K001

Connected to application &APPL - input please

K002

Connected to application &APPL - please sign on

K003

&CMD is not permitted now

K004

Invalid access authorization - please sign on

This message additionally contains the following insert:

&REA7

Reason why the sign-on failed. The values in &REA7 are described at message K147, see "Messages K147 - K189" .

K005

User identification &USER is locked - please sign on

K006

Invalid access authorization - please sign on

When output on a terminal, the text of this message contains the message number K004 instead of K006. The message number K006 is only visible when the message is output to other message destinations.

K007

User &USER already signed on - please sign on

This message additionally contains the following insert:

&REA7

Reason why the sign-on failed. The values in &REA7 are described at message K147, see "Messages K147 - K189".

K008

Sign-on accepted.

Last successful sign-on on &SGNT - input please

The first time a user signs on after a KDCDEF run, the insert &SGNT may contain question marks as no time of the last sign on is available.

K009

Transaction code &TAC is invalid (&RCDC) - input please

The &RCDC insert contains the internal return code KCRCDC, see section “Internal return code KCRCDC”.

K010

Transaction code &TAC is locked - input please

K011

Transaction &ATAC1 accepted - input please

K012 

&NUMMSGS asynchronous messages present

K013

Error in &CMD - input please

K016

Application shutdown pending - please sign off

K017

Service &TCVG terminated by UTM (&RCCC /&RCDC &RCF2A) - input please

This message informs a user of the abnormal termination of the service started by this user.

The complete message K017 in the SYSLOG file contains the following inserts:

PTRM	Name of the PTERM from which the terminated service was started.
PRNM	Name of the processor to which the terminal is connected.
BCAP	Name of the BCAM application to which the user has signed on.
LTRM	Name of the LTERM from which the service was started.
USER	Name of the user who started the service.
TCVG	Name of the service TAC of the service.
RCCC	Value of the compatible KCRCCC return code.
RCDC	Value of the incompatible KCRCDC return code.
&RCF2A *)	Secondary FHS or VTSU return code (if any).
TAC	Only for RCDC=KMxx return codes: Name of the TAC that caused the service to terminate. In all other cases this insert contains a blank.

*) on BS2000 systems only

K018

Sign-off for application &APPL accepted - please sign on

K019

Sign-offaccepted

K020

No message(s) present

K021

No input within the specified period

K022

The following message from &BCAP may have already been sent.

K023

&OMSG2

The message is called by the administration commandKDCSHUT WARN or the corresponding call to the administrator interface.

K024

Input message lost - please repeat

K025

Message from application &BCAP to LTERM &LTRM was truncated

A message to an LTERM partner could not be transmitted completely, and was output in truncated form.

The following error recovery action is possible:Increase the length specification in the TRMSGLTH operand in the KDCDEF generation.

K026

Broadcast to &LTRM accepted - input please

K027

Terminal &LTRM is locked - contact administrator or sign off

K029

Please insert card

K030

Card reader required - please sign on

K031

Wrong card - please sign on

K032

UTM-D connection message: &CON/&PRNM/&BCAP/&LPAP/&USER; reason1: &RCF1B; reason2: &RCF2B

In the following description of the return codes &RCF1B and &RCF2B, PLU (Primary Logical Unit) is the application in which SESCHA PLU=NO was generated, and SLU (Secondary Logical Unit) is the application in which PLU=YES was specified.

The &USER insert contains the UTM session name of the connection (LSES name).

&RCF1B	Meaning
C01	BIND_REJECTED	The BIND request or the BIND response has been rejected. No session can be set up.
C02	BIND_CHANGED	The BIND parameters have been modified. The BIND request may be modified by the SLU; while PLU can reject but not modify the BIND response. If the BIND response cannot be accepted by PLU, no session is set up.
C03	CONNECTION / SESSION FAILED	A connection or session cannot be set up.
C04	SESSION_FAILED	Session warm start could not be carried out.
C05	STSN_CHANGED	SLU cannot accept the proposed restart point.

&RCF2B	Meaning and possible action
CR00	Session and connection do no belong to the same LPAP. Response: check the KDCDEF generation.
CR01	The sessions were not able to agree on a valid restart point at session warm start. The applications were probably started with different KDCDEF states. Response: check whether either of the applications has been regenerated.
CR02	SLU has suggested a new restart point. If the session cannot be set up, the applications were probably started with different KDCDEF states. Response: check whether either of the applications has been regenerated.
CR03	Quiet command entered.
CR04	No suitable session available; reasons: more connections generated than sessions KDCLSES command entered with ACT = QUIET session not yet cleared down.
CR05	Connection setup request from TRANSIT-CD or partner application generated for this connection (NEA logs)
CR06	Connection setup in progress.
CR07	Inconsistency with respect to PLU specification in the connection message from the partner and in the UTM generation. Both partners were possibly generated as PLU. Response: check the generations of both partners.
CR08	Inconsistency with respect to PLU specification in the connection message from the partner and in the UTM generation. Both partners were possibly generated as SLU. Response: check the generations of both partners.
CR09 CR10 CR11 CR12	Incorrect structure of a connection message.
CR13	Resource bottleneck: no slot available for dynamic tables.
CR14	The name of the PLU session in the connection message is incorrect. Response: check the generations of both partners.
CR15 CR16 CR19 CR21	Session is still set up.
CR17 CR18 CR20	No suitable session available; reasons: more connections generated than sessions KDCLSES command entered with ACT = QUIET session not yet cleared down.
SC00	No reason given.
SC011	The partner is responding with an invalid FM profile. UTM supports FM profile 18 only.
SC021	The partner is responding with an invalid TS profile. UTM supports TS profile 4 only.
SC031	UTM can process a message in small units (request units). For this reason, PLU must support "multiple RU chains".
SC041	A request cannot be sent off until a previously requested response, if any, has arrived. PLU therefore has to operate in "immediate request mode".
SC051	Depending on the message type, openUTM either requests all types of acknowledgment or only a negative acknowledgment. PLU must therefore accept both definite and exception response.
SC071	Data compression is not supported for message transmission.
SC081	PLU must always be able to close a bracket.
SC091	Corresponds to reason SC03, but for SLU.
SC101	Corresponds to reason SC04, but for SLU.
SC111	Corresponds to reason SC05, but for SLU.
SC121	openUTM does not support 2-phase commit.
SC131	Corresponds to reason SC07, but for SLU.
SC141	Corresponds to reason SC08, but for SLU.
SC151	FM headers must be permitted.
SC16	The home session is insisting on a session warm start although the partner considers a session cold start to be sufficient.
SC17	The partner has indicated that the session has not terminated ("in bracket") without requesting a warm start. The session is assumed to have terminated (BETB).
SC181	A service is not terminated until indicated as such by both partners. This means that openUTM makes use of the "Bracket Termination Rule 1".
SC19	The user data in BIND is not correct. The partner is probably sending an faulty BIND. The UTM BCAM trace is needed for diagnostics.
SC231	In distributed processing, "half-duplex flip-flop" send or receive mode is used. This means that only one partner is authorized to send at any given time.
SC241	Both partners must be responsible for a session restart, if applicable.
SC25	BIND and KDCDEF generation are inconsistent with respect to the contention winner. Response: check the specification of the contention winner in both generations  (KDCDEF control statement SESCHA CONTWIN=Y/N).
SC26	PLU is requesting a send authorization at session warm start. If the session is not set up, the applications were probably started with different KDCDEF states. Response: check whether one of the applications has been regenerated.
SC27	SLU is requesting a send authorization at session warm start. If the session is not set up, the applications were probably started with different KDCDEF states. Response: check whether one of the applications has been regenerated.
SC281	UTM supports "two-stage pacing".
SC29	Inconsistent pacing counts, i.e.: SLU receive count not equal to PLU send count, or PLU receive count not equal to SLU send count. Response: check the pacing count (= window size) in both generations. (KDCDEF control statement SESCHA PACCNT= )
SC301	SLU is suggesting an illegal value for "maximum length of message segments from PLU" in the BIND response.
SC311	SLU is suggesting an illegal value for "maximum length of message segments from SLU" in the BIND response.
SC32	PLU is suggesting an illegal value for "maximum length of message segments from SLU" in the BIND request.
SC33	PLU is suggesting a value for "maximum length of message segments from PLU" in the BIND request which is modified by SLU.
SC341	Presentation Service (PS) usage field format must be defined as "basic format".
SC351	LU session type 6 is the only permissible session type.
SC361	Message coding is not supported.
SC37	Incorrect name of PLU session in BIND response. Response: check association of LSES and RSES in both generations (KDCDEF control statement LSES RSES=name)
SC38	Incorrect name of PLU session in BIND request. Response: see reason SC37
SC39	Incorrect name of SLU session in BIND response. Response: see reason SC37
SC40	Incorrect name of SLU session in BIND request. Response: see reason SC37
SC411	User Request Correlation (URC) is not supported UTM-D.
SY01	Session termination pending. Session cleardown has not yet been completed.
SY02	PET no send request The session is in the PTC status and there is no message for this partner.
SY03	PEND RS pending. PEND RS handling has not yet been completed.
SY04	Job-submitting conversation active. The job-submitting service is active.
SY05	Job submitter not available. The job submitted is not signed on or the job-submitting service is queued.
SY06	RESTART_VIA_SEND_RQ. The session is in the IN_BRACKET status and there is no message for this partner.
SY07	Session active The session is already active.

¹ Only in the case of heterogeneous links

K033

USER / LSES active : &PTRM/&PRNM/&BCAP/&LTRM/&USER &REST, &GLOBALSG

The K033 message is output:

• following successful connection setup when working without USERs

• following successful KDCSIGN when working with USERs

• following successful linkage of a session in a DTP connection.

&REST	Meaning
Y	Service restart
N	No service restart
U	Undefined, with UTM-D only

If a user signs on via an OSI-TP connection, the inserts have the following contents:

Insert	Contents
&PTRM	OSI-CON name
&PRNM	8 blanks
&BCAP	ACCESS-POINT name
&LTRM	OSI-LPAP name

A value is only entered for the insert &GLOBALSG 'Cluster Global Sign' in UTM cluster applications on Unix, Linux or Windows systems. The insert can have the following values:

&GLOBALSG	Meaning
Y	Global sign-on at the cluster
N	Local sign on at the node
A	The user was already signed on globally to the cluster at this node.
' '	Sign-on for an LU6.1 session user or a connection user.

K034

Transaction has been reset

K035

Service restart in progress

K036

Connection setup: &PTRM, &PRNM, &BCAP, &LTRM, &RSLT, &REA1

&RSLT	Meaning
Y	Connection set up
N	Connection was not set up; the cause is given in &REA1.

&REA1	Meaning
X'00'	Connection already set up
X'01'	PTERM/CON name unknown
X'02'	Processor name unknown
X'03'	PTYPE not accepted
X'04'	No LTERM assigned
X'05'	Incorrect connection password
X'06'	STATUS=OFF for this PTERM/CON
X'07'	STATUS=OFF for this LTERM/LPAP
X'08'	Resource bottleneck
X'0A'	Application shutdown
X'0B'	Partner already connected
X'0C'	Connection cleardown being executed
X'0D'	Negative transport system return code; see corresponding K065 message
X'0E'	Partner generated at another  application
X'0F'	UTM-D connection request rejected, e.g. due to UTM generation error or QUIET command
X'10'	PTERM name unknown and no LTERM pool available for this processor name
X'11'	No LTERM pool available for PTYPE and PTERM name unknown
X'12'	No further free entry available in terminal pool
X'13'	Partner already connected to LTERM pool
X'14'	Connection rejected due to insufficient characteristics of the transport connection (GROS)
X'15' *)	MUX connection rejected More detailed description in BIND response
X'16'	User is already connected
X‘17‘	The connection request has been rejected due to contention. The partner himself has initiated a connection setup.
X'18' *)	BCAM letter length too small
X‘1B‘	On application start, it was not possible to determine the IP address of the partner computer.
X‘1F‘	LPAP is set to quiet
X‘20‘	There is no suitable session available
X‘21‘	The session is already active
X‘22‘	The session is currently being terminated
X‘23‘	The local page is in PTC and does not have an output message for this session; it is necessary to wait for the restart of the local service to establish the session.
X‘24‘	PEND RS is being processed
X‘25‘	The job-submitting service is active
X‘26‘	The job-submitting user is not available
X‘27‘	It is necessary to wait for the restart of the local service to establish the session
X'29'	Terminal pool is generated at another UTM application name
X'2A' *)	Connection request from VTSU rejected, for instance because of unsupported PTYPE or incorrect connection letter
X'2B' *)	The connection request for an LTERM partner generated with PTYPE = *ANY is rejected because the type of the calling terminal or printer is not supported.
X'2C' *)	Connection request of a printer for a PTERM partner generated with PTYPE = *ANY and USAGE=D is rejected.
X'2D' *)	An invalid MUX protocol version is suggested on setting up the MUX connection.
X'2E'	The connection has not yet been completely cleared down, or the MUX session is still in "RELEASE-PENDING" status.
X'44' *)	Connection request refused by RSO, for instance because the printer is not known to RSO
X'45'	A connection cancel request occurred while waiting for confirmation of the establishment of a connection
X'46'	PTERM/CON was deleted by the administration
X'48'	A PTERM with the name of the multipool LTERM has already been generated.
X'55'	Rejected socket connection setup.
X'58'	Rejected confirmation of connection setup since the connection was interrupted in the interim.
X'5B' *)	Error in calling up the ICO function for converting the computer names (see K037).
X'60' *)	The SSL proxy used an invalid address to connect to the UTM application.
X'61' *)	A connection request from the SSL proxy is rejected by UTM because of a shortage of resources

The values indicated by *) only applies on BS2000 systems

This message, which is normally output to SYSLOG, helps to detect problems arising at connection setup.

For message output, the &REA1 insert is edited in printable form while at the program interface with MSGTAC / SYSLOG it appears in hexadecimal form.

K037

Host name mapping: &HST1 to &HST2

UTM uses this message to provide information about the assignment of real to local computer names or vice versa. The message is output every time the name is converted.

The complete message K037 in the SYSLOG file has the following inserts:

&HST1	Long or short computer name for which the assigned name is to be determined
&HST2	Short or long computer name that is assigned to the name in &HST1. If equals signs are returned in &HST2 instead of a computer name, this means that the name conversion call was unsuccessful.
&RSLT	Indicates whether or not the name conversion was successful: Y: The name conversion was successful N: The name conversion was not successful
&RCF2A	If &RSLT has the value ‘N’, a 4-byte long return code for the system function is output in this insert.

K038

Syntax error &SYN

K039

Startparameters &STRTPAR1 and &STRTPAR2 are mutually exclusive

K040

Warning level &WLEV for &PGPOOL no longer exceeded

K041

Warning level &WLEV for &PGPOOL exceeded

K042

Error reading start parameters 

K043

DMS error &DMSE for file &FNAM

The DMS error code is output in insert DMSE. 

The possible DMS error codes are described on "Error codes during file processing (DMS errors)" .

In the case of UTM cluster files, the insert &DMSE can contain the following error codes in addition to the error codes reported by the operating system:

ILCK	An error occurred while initializing a file lock.
LOCK	An error occurred while requesting a file lock.
ULCK	An error occurred while releasing a file lock.
DLCK	An error occurred while destroying a file lock.

K044

Reading the start parameters

K045

--- No message text ---

The only destination permitted for this message is MSGTAC; therefore no message text is defined for this message.

The message is output when a message output in acknowledgment mode is terminated with a positive print acknowledgment.

No default destination is defined for this message.

K046

Print error: &PALTRM / &CID / &DPID / &ERPRT

The message is output only for printers that are assigned to a printer control terminal. It is primarily intended for programmed error handling with the help of the MSGTAC program unit.

Further inserts of this message are: &PTRM, &PRNM, &BCAP, &LTERM, &IMSG2, &GNDATE, &GNTIME

The message is output in the following cases:

• termination of a printout with negative print acknowledgment

• repetition of a printout (in addition to the K022 message)

• connection setup to a printer is rejected 

No default destination is defined for this message.

The &ERPRT insert provides information on the error. Independent of this, the &IMSG2 insert gives further information.

&ERPRT	Meaning and contents of &IMSG2
A	Negative print acknowledgment. If the printer sends a logical print acknowledgment (return message), &IMSG2 contains the first 32 bytes of this acknowledgment (possibly padded with spaces). The exact structure of this print acknowledgment is described in the appropriate equipment user guides.
R	Repetition of a printout. &IMSG2 has no meaning. Connection setup is rejected.
C	Connection setup is rejected. &IMSG2 contains the DIAGNOSTIC-WORD.

K047

Invalid SVC 134 call (SVC for UTM): opcode = &OPCD1, RC = &RTCDThe SVC call is a UTM-internal interface. The return code in message K047 can have any of the following values:

&RTCD	Meaning
04	Illegal ROOTDATA address (UTM error1).
08	The compiled ROOT source program and the library with the UTM system modules are incompatible. There are two solutions to this problem: compile the ROOT source with the correct header files from utm-path/include link the application with the correct library utm-path/sys/libwork.a (UTM system modules)
0C	Invalid parameter list address (UTM error).
10	Invalid KDCS parameter area address UTM error. If the include files made available by openUTM for the KDCS parameter areas are used, this is a UTM error. If user-defined areas are used in the program unit for the KDCS parameter area, this is a user error. Action: check the alignment and address of the parameter area
14	Illegal KTA address in ROOTDATA, possibly due to: UTM error KDCS call in START-EXIT program unit KDCS call in SHUT-EXIT program unit KDCS call after UTM Term Application
18	Illegal contents in KTA header. Possible cause: UTM error
1C	Application names in ROOTDATA and KAA do not match, or illegal KAA header (UTM error).
20	Application names in ROOTDATA and KTA do not match (UTM error).
24	Parameter list address not aligned with word boundary (UTM error).
28	KDCS parameter area not aligned. If the include files made available by openUTM for the KDCS parameter areas are used, this is a UTM error. If user-defined areas are used in the program unit for the KDCS parameter area, this is a user error (alignment with halfword boundary). Action: check the alignment and address of the parameter area.
2C *)	Field SVC return code is not preset with X’FFFFFFFF’ (UTM error).
FF *)	SVC call could not be passed to the UTM subsystem. Cause: UTM was not defined or loaded as a subsystem.

¹ In the case of return codes of the UTM error type notify Software Support.
*) on BS2000 systems only