Messages K191 - K320

K191	Dump will be written without &SUFF-file because of request memory error (&RQM bytes requested).

K192	Node recovery for node &NNM1 on host &HST1, RESET-PTC=&RSPTC This message is output at stdout and stderr  at the start of a node recovery.
K193	PTC found : ID=&PTCID, USER=&USER, LPAP=&LPAP, LSES=&LSES, USER-type=&USTYPPTC On a node recovery, this message is output once for every transaction with PTC status.
K194	After node recovery: Number of still locked GSSB: &GBLNBR, number of still locked ULS: &ULLNBR This message is output at the end of node recovery. If the failed node application for which a node recovery has been performed still has GSSB locks, then this can impair the running UTM cluster application.

K199

ROOT-Termination initiated with TERM-UNIT: &TRMTYP, reason: &ROOTTRMR

Message K199 is issued for diagnostic purposes. In some cases preceding messages contain additional information.

The inserts have the following meanings:

&TRMTYP	Identifies the type of process termination: PROG: Work process is terminated with subsequent restart of utmwork. STEP: Work process is terminated without restarting utmwork.
&ROOTTRMR	Reason for terminating the process. The following values are possible:

&ROOTTRMR	Meaning
01	Dynamic ROOT generated but no parameters specified for it
02	Link error while dynamically loading the ROOT module
03	Invalid/Incorrect ROOT module linked
04	Incorrect version of the ROOT module
06	Link error while loading the message module
07	Incorrect version of the message module
10	Call for determining task info returns error
11	Error while requesting memory for start parameters
12 *)	No DB generated but ORACLE start parameters
13 **)	Cluster filebase and filebase specified simultaneously
15 *)	Catid parameter and filebase contain a ":"
16 *)	STARTNAME and ENTER-PROC parameters specified simultaneously
17 *)	Maximum length for ENTER-PROC parameter exceeded
18	Error while reading in the start parameters
20	Error while requesting memory for UTM Diagarea
21	Error while requesting memory for DB Diagarea
25	A signal has been issued
26	KDCTRMA was called
27	Error while initializing the language environment
28	Error while disabling the language environment
30 *)	Link error for the FORMCON module
31	Invalid operation code with KDCRTFH call
32 *)	Error when calling format start parameter
33 *)	Error while initializing formating
36 **)	exit() call in a program unit
40	Normal end of application
41	KDCS call in SHUT exit
43 *)	Error while canceling write protection (ROOTDATA)
44 *)	Error while setting write protection (ROOTDATA)
45	Unload (replace) program
46	Errored ROOT action table
47 *)	Error while closing the STXIT
48	Error while requesting buffer
49 *)	Error while dynamically initializing the voice connection
50	Error while calling START exit
51	Error while starting monitoring of the program runtime
52	Error while loading the application program
53	Error while replacing the application program
54	Incorrect index when loading a shared object
55	Invalid index for ROOT action table
56	Invalid ROOT action table
57	Error while calling START exit
58	Error while terminating program unit
59	Error in transition between user code and UTM system code
69 *)	Incorrect DB parameter
70	Error with respect to the start parameters for the database system
71	UTM error while handling the start parameters for the database system
72	Database error while starting a transaction
73	Database call in INPUT exit
74	Database call in START exit
75	Incorrect operation code in KDCRTDB
76 *)	Timer STXIT during database call
77 *)	Error requesting memory for transaction management
78	Database not active or database administration error
79	Incorrect UTM behavior when signing on to the database
80	Canceling a database transaction from signal handling
81	Error when signing on to the database
82 *)	Error in Get install Path for BIND (DBCON)
83 *)	Error while loading the connection module for the database (will be repeated)
84 *)	Error in Get Install Path DB modlib
85	Incorrect version of the connection module for the database
86 *)	Error in database connection via XA (mismatch)
87 *)	Error while dynamically loading the XA connection module
88 *)	The database connection module was loaded incorrectly (upper instead of lower address space).
90	PEND ER called from user code / UTM system code
91	Connection loss with PGWT
92 **)	The application program is reloaded due to a request from a user error routine
95	KCSSTRT error routine enabled

*) values only appear on BS2000 systems

**) values only appear on Unix, Linux and Windows systems

K201

XA( &TSNPID) Resource Manager support using X/Open &XASPEC

&XASPEC identifies the version of the XA connection. The insert can have thevalues XA-CAE-Spec or XA-P-Spec.

K202

XA( &TSNPID) RM instance &INSTNUM, &TEXT32, &RMSTAT

The message provides information about the status of the XA connection.

The inserts have the following meanings:

&INSTNUM	Serial number of the Resource Manager instance, starting with 1. The numbering corresponds to the sequence of the start parameters.
&TEXT32	Name of the Resource Manager.
&RMSTAT	Status of the connection. The following values are possible:

&RMSTAT	Meaning
opened	The Resource Manager has been opened
reopened	The Resource Manager has been opened after a restart
closed	The Resource Manager has been closed

K203

XA( &TSNPID) RM &TEXT32,&INSTNUM - recovered transactions: &RTAANZ

The inserts have the following meanings:

&TEXT32	Name of the Resource Manager.
&INSTNUM	Serial number of the Resource Manager instance, starting with 1. The numbering corresponds to the sequence of the RMXA start parameters.
&RTAANZ	Number of recovered transactions.

K204

XA( &TSNPID) precommit requires global rollback - reason: &XATXT USER: &USER TAC: &TAC

TA=&INTTAID

Precommit failed, global transaction will be rolled back.

The inserts have the following meanings:

&XATXT

Reason for precommit failure. The following values are possible:

&XATXT	Meaning
XA_RBROLLBACK	Rollback for unspecified reason
XA_RBCOMMFAIL	Rollback due to a internal communication error in the Resource Manager
XA_RBDEADLOCK	Rolback due to a deadlock
XA_RBINTEGRITY	Rollback due to a resource inconsistency
XA_RBOTHER	Rollback for unspecified reason
XA_RBPROTO	Rollback due to an internal protocol error in the Resource Manager
XA_RBTIMEOUT	Rollback due to transaction period timeout
XA_RBTRANSIENT	Rollback due to a temporary error

&INTTAID

Description of the UTM transaction which triggered the global rollback of the other transactions.

Byte 0 contains the instance number of the Resource Manager.

If the XID (= XA transaction identifier) was created in an OSI-TP job-receiver transaction then the AAID (Atomic Action IDentifier) is added here.

&USER

User-Id of the current transaction

&TAC

Transaction code of the current transaction

K205

XA( &TSNPID) transaction committed - reason: &XATXT USER: &USER TAC: &TAC TA=&INTTAID

The inserts have the following meanings:

&XATXT	Reason for committing the transaction. Possible reasons: "Recovery" or "Int.Event".
&INTTAID	Description of the UTM transaction that was committed (for contents, see K204).
&USER	User-Id of the current transaction
&TAC	Transaction code of the current transaction

K206

XA( &TSNPID) transaction rolled back - reason: &XATXT USER: &USER TAC: &TAC

TA=&INTTAID

The inserts have the following meanings:

&XATXT	Reason for the rollback. Possible reasons: "Recovery" or "Int.Event".
&INTTAID	Description of the UTM transaction that was committed (for contents, see K204)
&USER	User-Id of the current transaction
&TAC	Transaction code of the current transaction

K207

XA( &TSNPID) transaction is unknown to the RM&INSTNUM USER: &USER TAC: &TAC

TA=&INTTAID

The inserts have the following meanings:

&INSTNUM	Instance number of the Resource Manager, see K203 .
&INTTAID	Description of the UTM transaction that is unknown to the RM (for contents, see K204 )
&USER	User-Id of the current transaction
&TAC	Transaction code of the current transaction

K210

XA( &TSNPID) Error: &XATXT - open RM: &TEXT32,&INSTNUM

K211

XA( &TSNPID) Error: &XATXT - close RM: &TEXT32,&INSTNUM

The inserts in the messages K210, K211 and K216 have the following meanings:

&TEXT32	Name of the Resource Manager.
&INSTNUM	Instance number of the Resource Manager, see K203 .
&XATXT	Keyword for the return code from the called XA function. Possible values:

&XATXT	Meaning
XA_OK	Normal execution
XA_NOMIGRATE	The transaction was suspended but the context cannot be migrated and the transaction can only be continued in the sameprocess.
XA_HEURHAZ	The transaction may have been heuristically terminated due to a possible internal RM error.
XA_HEURRB	The transaction has been internally rolled back due to a heuristic Resource Manager decision.
XA_HEURMIX	The transaction has been internally partially committed and partially rolled back due to a heuristic Resource Manager decision.
XA_RETRY	The call to the routine must be repeated
XA_RDONLY	The transaction was "read_only" and was committed
XA_RBROLLBACK	Rollback for unspecified reason
XA_RBCOMMFAIL	Rollback due a communication error
XA_RBDEADLOCK	Rollback due to a deadlock
XA_RBINTEGRITY	Rollback due to a resource inconsistency
XA_RBOTHER	Rollback for unspecified reason
XA_RBPROTO	Rollback due to an internal RM protocol error
XA_RBTIMEOUT	Rollback due to a transaction period timeout
XA_RBTRANSIENT	Rollback due to a temporary error
XAER_ASYNC	An asynchronous operation is still outstanding
XAER_RMERR	A non-recoverable error has occurred in the Resource Manager. Possible cause: The Resource Manager was not initialized or was incorrectly initialized
XAER_NOTA	The transaction identifier is invalid or is unknown to the Resource Manager
XAER_INVAL	Invalid function arguments were specified. It is possible that the Open or Close strings contain incorrect parameters.
XAER_PROTO	The routine was called internally in the RM in the wrong context.
XAER_RMFAIL	The Resource Manager is no longer available
XAER_DUPID	The transaction identifier already exists in the Resource Manager. openUTM terminates the service. To eliminate this residual XID left by XAER_DUTSNPID from the Resource Manager, the database administrator should remove this transaction. Possible action: shut down and restart the database.
XAER_OUTSIDE	The Resource Manager is operating outside of the transaction.

K212	XA( &TSNPID) xa_start(&XAFLAG) - return code: &XATXT USER: &USER TAC: &TAC TA=&INTTAID
K213	XA( &TSNPID) xa_end(&XAFLAG) - return code: &XATXT USER: &USER TAC: &TAC TA=&INTTAID
K214	XA( &TSNPID) xa_commit() - return code: &XATXT USER: &USER TAC: &TAC TA=&INTTAID

K215

XA( &TSNPID) xa_rollback() - return code: &XATXT USER: &USER TAC: &TAC
TA=&INTTAID

The inserts in the messages K212 to K215 have the following meanings:

&XATXT	Keyword for the return code from the called XA function. Possible values, see K211.
&XAFLAG	Keyword that describes the flags on an xa_start() or xa_end() call.
&INTTAID	Description of the UTM transaction during which the return code occurred (for contents, see K204 )
&USER	User-Id of the current transaction
&TAC	Transaction code of the current transaction

K216

XA( &TSNPID) return code: &XATXT - recover PTC list, RM: &TEXT32,&INSTNUM

For the meaning and content of the inserts, see K211.

K217

XA( &TSNPID) xa_prepare() - return code: &XATXT USER: &USER TAC: &TAC
TA=&INTTAID

For the meaning of the inserts, see K211 (&XATXT) and K215 (&INTTAID).

K218

XA( &TSNPID) xa_forget() - return code: &XATXT USER: &USER TAC: &TAC
TA=&INTTAID

For the meaning of the inserts, see K211 (&XATXT) and K215 (&INTTAID).

K220

XA( &TSNPID) Error: xa_switch definition not found for specified RM: &TEXT32

A Resource Manager (RM) for which the RMXA start parameter was specified was not defined in the KDCDEF generation.
&TEXT32 contains the name Resource Manager.

K221

XA( &TSNPID) Error: Start parameters not found for defined RM: &TEXT32

No start parameters are specified for a Resource Manager (RM) present in the KDCDEF generation.
&TEXT32 contains the name Resource Manager.

K222

XA( &TSNPID) Error: Linked RM is not &XASPEC compatible: &TEXT32

The Resource Manager (RM) does not use the XA interface that was specified during KDCDEF UTM generation.
&TEXT32 contains the name of the Resource Managers and &TEXT32 the XA interface specified during generation.

K223

XA( &TSNPID) Syntax error in start parameters:

The following line contains the incorrect line from the start parameter file.

K224

XA( &TSNPID) &XACALL - return code &XATXT from RM instance &INSTNUM, &TEXT32 is not XA( CAE) compliant

The Resource Manager (RM) returns an unexpected return code.

The inserts have the following meanings:

&XACALL	Name of the call to the XA interface, e.g. xa_start().
&XATXT	Keyword for the return code from the called XA function (see K211 ).
&INSTNUM	Instance number of the Resource Manager, see K203 .
&TEXT32	Name of the Resource Manager.

K225

XA( &TSNPID) recursive call of XA module: function: &XADBC1 - STXIT/signal in DB/XA connection for &XADBC2

The meaning of the inserts is as follows:

&XADBC1	Name of the called function in the UTM/XA connection module. Value DBCATA indicates that a timer STXIT occurred during processing of function &XADBC2 and thus the transaction will be rolled back.
&XADBC2	Name of the function in which an error was detected in the UTM/XA connection module.

K230

XA( &TSNPID) Int. error: &TEXT32

&TEXT32

Specifies an internal error.  This may, for example, indicate a lack of memory space for malloc().

K231

XA( &TSNPID) Int. error: PETA not supported

Preliminary end of transaction not supported.

K232

XA( &TSNPID) Int. error: DBSTAT secondary opcode inconsistent

The secondary operation code of the primary operation code DBSTAT is inconsistent.

K233

Heur. decision in task / process &TSNPID, RM=&INSTNUM in
&XACALL(&DBCALL), xa-rc=&XATXT, LTHGTRID=&LTHGTRID, GTRID=&GTRID

The meaning of the inserts is as follows:

&INSTNUM	Instance number of the Resource Manager (RM), see K203 .
&XACALL	Name of the call to the XA interface, e.g. xa_start().
&DBCALL	Name of the called UTM-DB interface function
&XATXT	Keyword for the return code from the called XA function (see K211 ).
&GTRID	Global transaction ID (gtrid) of the UTM transaction in accordance with the XA/CAE specification (for contents, see K204 ).
&LTHGTRID	Length of the global transaction ID.

K235	Name resolution for &PRNM lasts &TCPMS milliseconds (socket call: &TCPCL, returncode: &TCPRC, IP address: &IPADDR). The message is issued if the name resolution takes longer than 1000 milliseconds. Meaning of the inserts see message K236.

K237	XA( &TSNPID) Error at &DBCALL: Oracle-Password and -User have to be specified by KDCDEF-Generation. &TSNPID is the pid of the process and &DBCALL always has the value DBSTPA (DB start parameter analysis). The start of the application is aborted.
K238	XA( &TSNPID) Warning at &DBCALL: Clear-text User or Password for Oracle-DB in start parameter.
K239	Asynchronous message from &GNUSER to &LPAP could not be delivered because of permanent error and was deleted.
K251	Version V&IMPVER of filebase &FBASUPD does not match current version V&DEFVER.
K252	&UPDERR error An error occurred while requesting memory with online import. Or Error in KDCUPD: If &UPDERR is set to the value PARAM, then this points to a syntax error. KDCUPD aborts. Response: enter the correct command! Otherwise an error will occur when requesting memory, when reading in data, etc. Response: write a problem report with documentation.
K255	DMS error &DMSE on file &FNAM Error in file processing. Response: according to DMS error code, see "Error codes during file processing (DMS errors)" .
K256	File type of &FNAM is not a valid UTM type.  The file is not of type KDCFILE (KDC, pool, conf file).
K257	Application run was not terminated correctly
K258	File &FNAM has already been used
K260	Unknown version &DEFVER of filebase &FBASUPD
K261	Inconsistent file &FNAM The file is not consistent in itself Response: restore the file or repeat generation.
K262	Wrong file &FNAM The file was overwritten by another KDCFILE file; see sdterr log for further details. Response: make correct file available or repeat generation.

K263

No start-up has yet been performed with the file &FNAM.

K269

&OBJ1 &OST1 &BMD1 and &OBJ3 &OST2 &BMD2 are not compatible

K273

Error &TRMA in module &UPDMODULDescription of the causes of the error for message K273, plus action:

&TRMA	Cause	Action
BFMMER	Error initializing buffer management (cluster)	if necessary, increase virtual address space or PM
CFGERR	Error processing the cluster configuration file	previous diagnostic messages, or if there are none: inconsistent node name sequence
CONSER	Internal error	Write PR and provide documentation
DMSERR	A DMS error has occurred	See message K255
DxxxRD	DMS error xxx on reading the first page	Depends on DMS error code, see also "Error codes during file processing (DMS errors)"
DxxxWR	DMS error xxx on writing the first page
xxxx01	DMS error xxxx on reading the first KAA page
GMDTER	Error checking the cluster GSSB file	See previous diagnostic messages
INCONS	Error during consistency checks	See messages K261/K262
LOOKLT	Error searching for LTERM	Write PR and provide documentation
LOOKFL LOOKFU	Error searching for initiator (LTERM, USER)	Write PR and provide documentation
LOOKLT	Error searching for LTERM	Write PR and provide documentation
LOOKTC	Error searching for TAC	Write PR and provide documentation
LOOKUS	Error searching for USER	Write PR and provide documentation
OPWRON	Internal error	Write PR and provide documentation
PPMMER	Cluster page pool management file incorrect.	See previous diagnostic messages
READxx *)	DMS error	See start error code xx in K049
REQKTA	'Request memory' error for KTA	See REQM01
REQM01	'Request memory' error for 1st page	Regenerate system if necessary
REQM02	Insufficient memory when creatingshared memoryfor UTM cache	Check operation system generation or reduce the CACHESIZE operand
SHM002 **)	Cause: UTM application is running at the moment. A KDCUPD run is therefore not possible.	Response: terminate the application.
UMDTER	Error checking the cluster ULS file	See previous diagnostic messages
UPDSTA	File has already been processed with KDCUPD	None
USFERR	Error opening the cluster user file	See previous diagnostic messages
WRDB01 *)	Abort in KDCUPD write module. Cause: The number of DB systems in the new KDCFILE is smaller than in the old KDCFILE. Can occur only if old and new KDCFILE are generated with UTM-S. K307 is also output.	Modify the generation of the new KDCFILE
WRDB02 *)	Abort in KDCUPD write module. Cause: The type of database(s) in the new KDCFILE is different from the type in the old KDCFILE. Can occur only if old and new KDCFILE are generated with UTM-S. K307 is also output.	Modify the generation of the new KDCFILE
WRDB03 *)	Abort in the KDCUPD write module. Cause: at least 1 DB system is in the old KDCFILE and there are more DB systems in the new KDCFILE than in the old KDCFILE. Can occur only if old and new KDCFILE are generated with UTM-S. K307 is also output.	Modify the generation of the new KDCFILE
WRFORM *)	Abort in the KDCUPD write module. Cause: the old KDCFILE was generated with formatting and the new KDCFILE without formatting, both KDCFILEs are generated with the variant UTM-S.	Modify the generation of the new KDCFILE
WRITxx *)	DMS error	See start error code xx in K049
...GSB ....GB	Error during GSSB handling	Write PR and compile documentation
...TLS ....TL	Error during TLS handling	Write PR and compile documentation
...ULS ....UL	Error during ULS handling	Write PR and compile documentation
..DIAL	Error during transfer of chained services	Write PR and compile documentation
...ASY ....AS	Error handling FPUTs or DPUTs to LTERM	Write PR and compile documentation
...IMS ....IM	Error handling FPUTs or DPUTs to TAC	Write PR and compile documentation
...UPI ....UP	Error while processing a dialog message for UPIC	Write problem report and create documentation
...SOC ....SO	Error while processing a dialog message for SOCKET	Write problem report and create documentation
...UMS ....UM	Error while processing a user queue message	Write problem report and create documentation
...QMS ....QM	Error while processing a queue message	Write problem report and create documentation
...LSB	Error in LSSB handling	Write PR and compile documentation
xxxx99 *)	Internal error in KDCUPD	Write PR and compile documentation

The values marked with *) only appear on BS2000 systems and the values marked with **) only appear on Unix, Linux and Windows systems.

Further &TRMA error codes may be the term application codes of openUTM.In this case, you should always write a PR and compile relevant documentation.

K274	Terminated with a dump
K277	At least one node application was not terminated correctly. For more details, see stderr log.
K278	At least one node application has already been started.
K279	Error in cluster-handling, see (possible) diagnostic message before
K300	&UPDPRO percent of &PGPOOL used.
K303	&UKCOP data transferred. KCRN = &UKCRN, type = &UPDTYP, KCLM = &UKCLM.
K304	Service data transferred for user &USER. Service type = &TACTYPE, height of stack = &UKCHSTA
K305	Used pages of &PGPOOL for &UPDTYP: &PGS1 overall, &PGS2 for &UKCRN.
K306	Used pages of &PGPOOL for &UPDTYP: &PGS1.

Note
The data could not be transferred for the following KDCUPD messages in which the text begins with a "*" (asterisk).

K310

* &UPDTYP &UKCRN not found

See Note, above.

K311

* &UPDTYP &UKCRN not found. No data transferred

See Note, above.

K314

* Warning: LPUT data cannot be transferred

See Note, above.

K317

* &UKCOP data not transferred. KCRN= &UKCRN, Type = &UPDTYP, KCLM =
&UKCLM, KCRCCC = &RCCC, KCRCDC = &RCDC . Caused by LTERM = &LTRM , user = &USER

See Note, above.

K318

* &UPDTYP &UKCRN : sender of asynchronous message not found. LTERM = &LTRM, user = &USER

See Note, above.

K320

* Service data for user &USER not transferred. Service type = &TACTYPE, reason: &UERCODE, &UERINFO, &RCDC

See Note, above.

The insert &UERRCODE indicates why the service data for USER &USER was not transferred. The insert &UERRINFO contains additional information.

&UERRCODE	&UERRINFO	Meaning
EDIT *)	name	The edit profile name is not generated.
KBLTH	bytes	The generation parameter MAX KB in the new KDCFILE is too small. The service requires the number of bytes specified for “bytes”.
LOCK ERR *)	tac	The user does not have the necessary key for the transaction code "tac" in his/her key set
LSSBS	number	The number "number" of LSSBs in a service of the user is larger than the generation value (MAX LSSBS = ).
LTERM	lterm	The sender LTERM "lterm" is not defined.
MISSMATCH		The user is generated in the new KDCFILE with RESTART=NO or the user type has changed (connection user ID yes/no).
NRCONV	number	The number "number" of stacked services of the user is larger than the generation value (MAX NRCONV = ).
PAGEPOOL		The page pool is too small (MAX PAGEPOOL = ).
RESSHORT		The UTM table entries for administrating service data are not sufficient. More user IDs, sessions and/or tasks were generated in the new KDCFILE than in the old or the value of ASYNTASKS is less than in the old KDCFILE.
TAC	name	The transaction code "name" is invalid.
TRMSGLTH		The message for a continuation program is too large (MAX TRMSGLTH = ).
VGMSIZE *)	size	The service memory (size in KB) is larger than the generation value in the new KDCFILE (MAX VGMSIZE=).

*) values only appear on BS2000 systems.