Messages K071 - K101

K071

Internal Error in database connection &DBCON: operation=&OPCD1, error=&ERCD3, DB-trace-info=&DBTRAC

The inserts have the following meanings:

&DBCON	= XA (database connection via XA)
&OPCD1	DB operation code, see section “DB Diagarea”
&ERCD3	KCRCDC error code , see section “Internal return code KCRCDC”
&DBTRAC	DB trace information. The possible values and their meanings are described in the discussion of the relevant database system.
	If the DB system is connected via the XA interface then the 4 DB trace information bytes have the following meanings:
	Byte 1	Resource Manager index (cf sequence in the start parameters)
	Bytes 2 and 3	Operation code of XA call, output hexadecimal and platform-dependent (EBCDIC or ASCII),
	Byte 4	Return code of XA call, output hexadecimal and platform-dependent

K072

There is a mismatch in the number of &STMT entries in ROOT and KDCFILE.

This message is output when it is recognized at the start of the application that the number of programs  in the ROOT and KDCFILE generation do not match. The start of the application or process is terminated with the message K049, code 40.

Response: regenerate ROOT and/or KDCFILE

K073

The attribute &ATTR of &STMT &PROG in ROOT and KDCFILE does not match.

This message is output if when a task is started it is found that the entries of the  PROGRAM table in ROOT and in the KDCFILE do not match. The first insert indicates the attribute in which the entries differ.

The start of the application or the process is aborted with message K049, code 41.

Response: regenerate ROOT and/or KDCFILE

K074

Program exchange completed; &CTYP &PROG &PVER

(see K075)

K075

Program exchange aborted by process  &PID; &CTYP &PROG &PVER

K074 or K075 are issued after a positive or negative termination of a program exchange. The inserts give information as to which part of the application program were exchanged or which part could not be exchanged:

&PID:	Process ID of the process for which program exchange was aborted.
&CTYP:	APPL, Exchange of the entire application program LMOD, Exchange of a shared object
&PROG:	Name of the shared object (only when CTYP=LMOD)
&PVER:	Version number of the shared object (only when CTYP=LMOD)

K076

Error during asynchronous administration with transaction code &ADTC; KCRCCC=&RCCC, KCRCDC=&RCDC

K077

Internal cluster communication with &PTRM/&PRNM/&BCAP/&LTRM successful: &CLSIGT

The message K077 is only output if test mode is active.

During internal cluster communication, a &CLSIGT message was sent to another node application. &CLSIGT can have the following values:

&CLSIGT	Meaning
1	Check the availability of the monitored node application (check alive request).
2	Check for changes in the cluster configuration
4	Administration job
8	Job to wake up one of the processes waiting at a GSSB or ULS
16	Response to an availability query from the monitoring node application (check alive response)

No action is required.

K078

&ERRNAME &ERRCODE: in &REA3

The message can be output by openUTM when the application is started, when handling signals, or when a work process is terminated.

Message K078 is output by UTM in several variants that depend on the event that has occurred.

K078

K078

K078

yyyyyyyyy: IN module-name zzzzzzzz

yyyyyyyyy: zzzzzzzz

xxxxxxxx yyyyyyyyy: IN module-name text

xxxxxxxx

contains a short code for the error that has occurred (see table).

yyyyyyyyy

error code of the function called (for more information see preceding K078).

zzzzzzzz

specific, context-related error message.

module-name

contains the name of the module in which this error has occurred (for internal diagnostics)

text          contains additional information on specific errors

xxxxxxxx	Error cause	Response
ALME	Not possible to provide sufficient memory on memory request	Insufficient memory, tune system if necessary
APPLI 01	DMS error on accessing the applifile The applifile is located under utmdirectory/applifile and contains the name and status of the UTM application	User error
APPLI 02	Application in applifile not known or utmwork was started for testing before utmmain prepared start	User error
APPLI 03	Application in applifile not started	User error
ARG 01	Invalid number of arguments at start of utmwork	User error: Start utmwork with correct arguments or utmwork has the wrong version
ATEXIT 00	The atexit() function was called on process termination.	Information message
ATEXIT 01	System program unit requests process termination with exit().	Information message
ATEXIT 02	Application program unit requests process termination with exit().	Information message, followed by PEND ERROR.
ATEXIT 03	The atexit() function was called recursively on process termination.	Information message
ATEXIT 04	System program unit illegally requests process termination with exit().	Information message, followed by TERM APPLICATION.
BIND	Error loading a load module: The insert 'LMOD: name / version ': provides further information	See preceding K078
COB 01	cobtidy() suppressed after exit() in Micro Focus COBOL application program	Information message
COB 02	Start of COBOL application program suppressed after exit() in the Micro Focus COBOL application program.	Information message
COB 03	JMPCINT3() and JMPCINT4() suppressed after exit() in the NetCOBOL application program.	Information message
COB 04	Start of COBOL application program suppressed after exit() in the NetCOBOL application program.	Information message
CPUT 00	The system was not able to supply the CPU time for the process.	Information message
CPUT 01	The system was not able to supply the CPU time for the child processes.	Information message
CPUT 02	The CPU time for the process was set to the maximum value LONG_MAX.	Information message
CRE 01	The environment variable UTM_MAIN_KILL_TIME is set	Information message
DIAG 01	The environment variable UTM_BREAK_BEFORE_KCSTRMA is set	Information message (on Windows systems only)
DIAG 02	The environment variable UTM_ABORT_WITH_EXCEPTION is set	Information message
DIAG 03	The environment variable UTM_CORE_DUMP is set to NO	Information message
DIAG 04	The environment variable UTM_EXIT_CORE is set to YES	Information message
DIAG 05	The environment variable UTM_ABORT_WITH_EXCEPTION is set	Information message
DIAG 06	exit() call in application program results in termination of the utmwork process	Information message
DIAG 07	exit() call in system section results in termination of the utmwork process	Information message
DIAG 08	The environment variable UTM_MAIN_KILL_TIME is set	Information message
DLCLOSE 01SHL_UNLOAD 01FreeLibrary 01	Error closing a shared object.	Check UTM generation and return code.
DLOPEN 01 SHL_LOAD 01 LoadLibrary 01	Error loading a shared object.	Check UTM generation and return code. Check LD_LIBRARY_PATH environment variable or SHLIB_PATH environment variable on HP-UX
DLSYM 01 SHL_FINDSYM 01GetProcAddress 01	Error fetching the address for a symbol in a shared object.
dlclose shl_unload FreeLibrary	Diagnostic message on closing a shared object.	Information message
dlopen shl_load LoadLibrary	Diagnostic message on dynamically loading programs. These messages only occur when test mode is on.	Information message
dlsym shl_findsym GetProcAddress	Diagnostic messages on fetching the address for a symbol in a shared object.	Information message
ENV 00	Specification of the type of UTM application: standalone / cluster / node_recovery / beanconnect	Information message
ENV 01	Specifications on the operating system	Information message
ENV 02	Specification of the bit mode of the UTM application: standalone/cluster/beanconnect	Information message
ENV 03	The compare and swap algorithm was switched off.	Information message
ENV 04	The environment variable UTM_NO_GCORE_DUMP is set to YES. I.e. no gcore is also generated when a UTM-DUMP is generated. By default, a gcore is also generated when a UTM dump is generated.	Information message (on Unix and Linux systems only)
ENV 05	The environment variable UTMPATH for the access to the UTM message library libxmsgs.so is not set.	Set environment variable UTMPATH
EXIT xx	Signal number xx at start or shut exit. "STARTEXIT" or "SHUTEXIT" is entered in the additional field.	User error
HOST 01	The environment variable UTM_NET_HOSTNAME is set. The host name file <file> is being used.	Information message
HOST 02	The environment variable UTM_NET_HOSTNAME is set. However, the host name file <file> could not be used because of DMS error <error>.	User error
IPC 01	Invalid return code when initializing the IPC.	Check UTM generation (MAX ICPTRACE) or call KDCREM
IPC 02	Memory bottleneck when creating the IPC shared memory	Check UTM generation. Tune SHMMAX kernel parameter.
IPC 03	The environment variable UTM_IPC_LETTER is set	Information message
IPC 04	The environment variable UTM_IPC_EXTP_LETTER is set	Information message
IPC 05	Number of IPC letters changed	Information message
IPC 06	Number of IPC elements changed	Information message
IPC 07	The environment variable UTM_IPC_EXTP_LETTER is set	Information message
KCSASIO	Complete text: K078 KCSASIO: error KCSTRMA ("&REAS>") file: "<&FNAME>" position:<&POS>" Cause: Processing aborted with reason &REAS due to incorrect (= too large) file position &POS for file &FNAME.	On KDCDEF run: Reduce size of files, e.g. generate more page pool files (MAX PGPOOLFS=)
	Complete text: K078 "KCSASIO notice: write to "&FNAME" took "&SEC" secs" Cause: Writing to file &FNAME took &SEC seconds.	Information message
	Complete text: K078 "KCSASIO notice: read from "&FNAME" took "&SEC" secs" Cause: Reading from file &FNAME took &SEC seconds.	Information message
KCSCHKD	Complete text: K078 "KCSCHKD notice: back to "lost" directory "&DIR" ok" Cause: A process has set its directory &DIR due to an I/O error	Information message
KCSROPN	Complete text: K078 "KCSROPN notice: reopening for file "&FNAME"" Cause: The file &FNAME has been opened again due to an I/O error.	Information message
	Complete text: K078 "KCSROPN notice: reopening return_code for file "&FNAME" is "&DMSERR"" Cause: A return code was returned when the file was reopened. &DMSERR = " " (i.e. blanks) means "OK"	Information message
KCXOFLK	A lock call was rejected with errno. Complete text K078 KCXOFLK LOCK-WAIT/ LOCK-IMM error "&ERRNO" for file "&FILENAME"	Diagnostic message
KDCS 00	"KDCS" call in START exit, SHUT exit or INPUT exit	Correct program unit
MEM 01	Memory bottleneck when starting the application. Full text: K078 MEM 01 in utmwork nn Bytes not available.	Check storage requirements; tune operating system
MSG 01	The environment variable UTM_MSG_DATE is set to NO	Information message
MSG 02	The environment variable UTM_MSG_PID is set to NO	Information message
MSG 03	The optional application-specific message library (libxmsgs.so / or libxmsgs.dll) with user-specific message destinations was loaded successfully	Information message when this optional function is used successfully
MSG 04	The UTM message library libxmsgs.so is not available	Check UTM installation or environment variable UTMPATH
NET 01	The environment variable UTM_APPLI_CONLET is set	Information message
OSS 02	Error while allocating/signing on to the OSS shared memories	Check UTM generation or call kdcrem
OSS 03	Error while loading the OSS shared memories into the address space.	Check UTM generation
PIPE 01	The environment variable UTM_PIPE_TIME is set	Information message
READ 01	Inconsistent KDCFILE when starting the application.	User error.
SEM 01	Error when creating the semaphore. This can occur in openUTM under Windows systems if, for example, a dtp is still running when the application is started	In UTM generation reduce the value of number1 in MAX SEMARRAY.
SEM 02	Error signing on to a semaphore	System error
SIGALRM	Unexpected signal SIGALRM received in utmwork process	Information message, signal is ignored.
SIGFUNC	Call to a user signal routine is registered in openUTM	Information message (on Unix and Linux systems only)
SIGINF	Invalid signal received in utmwork process	Information message, signal is ignored.
SIGNAL	Signal received in utmwork process.	Information message followed by either PEND ERROR or TERM APPLICATION or call to the user signal routine (on Unix and Linux systems only)
SIGREGNO	Registration of a user signal routine not possible because STXIT=OFF is set.	Information message (on Unix and Linux systems only)
SIGRESTORE	Application-specific signal routine for SIGALRM is not permitted.	Information message
SIGSTACK	Output of stack information	Information message
SIGTRAP	SIGTRAP signal received in utmwork process.	Information message, signal is either ignored or application is terminated with TRMA IPCREM.
SSL 00	Loading of the openSSL library was successful.	Information message
SSL 01	Error during loading of the openSSL library.	User error Response: Wrong or missing value of environment variable
SSL 02	Missing functionality of the openssl library.	User error Response: Provide appropriate openssl library
STARTEXIT	Startexit terminated the work process with exit().	Information message
STXIT OFF	Message: "STXIT OFF in utmwork: termination of utmwork process creates gcore dump"	Information message
STXIT OFF	Message: "STXIT OFF in utmwork: exit() call produces termination of utm- work process with abort().	Information message
SYSPROT 01	The environment variable UTM_REDIRECT_FILES is set	Information message
SYSPROT 02	The environment variable UTM_MAIN_NODIRECT is set	Information message
TIMR 01	The environment variable UTM_TIMER_RETRY is set	Information message
UNBIND	Error unloading a load module. The insert ' LMOD: name / version ' provides further information.	See preceding K078
VERS 01 VERS 02	Version or bit mode of the program and the KDCA file incompatible.	User error Response: set UTMPATH correctly
VSVI1	Error finding program addresses. The insert ' for program: name' provides further information.	See preceding K078

K078	WARNING : in KDCRTBF! No XA-Connection generated, but startparameters given! A start parameter was specified for the Resource Manager but none was generated. Modify UTM generation or start parameter!

K079

Accounting problem - reason: &REA2

The error cause is given in the insert &REA2:

&REA2	Meaning
28	Error in BS2000 accounting write task. UTM deactivates accounting. The application continues to run

Response: check to see if the utmlog process still exists.

Once the error has been rectified, the UTM administrator can reactivate the costing and/or accounting phase with the KDCAPPL command.

K080

KDCMON is not active.

K081

Statistics: &IMSG1/&OMSG1/&CONU/&ATAC2/&LWRT/&HITR/&WTBF

Inserts	Meaning
&IMSG1	Number of terminal input messages 1)
&OMSG1	Number of terminal output messages 1)
&CONU	Number of connected users
&ATAC2	Number of unprocessed ATACs 1)
&LWRT	Number of log writes
&HITR	Cache hit rate 1)
&WTBF	Cache waits for buffer

This message is written every hour on the hour and in the case of normal termination of the application. The values marked with ¹) are subsequently reset to 0.

K082

Wrong file &FNAM

K083

File &FNAM has been destroyed.

K084

&OBJ1 &VER1 &OST1 &BMD1 and &OBJ2 &VER2 &OST2 &BMD2 are not compatible.

K085

&FNKT functions are not available.

K086

UTM-D error information: &PTRM, &PRNM, &BCAP, &LTRM, &USER, &SYSD, &USSD, &FMH7, &AGUS

Inserts	Meaning
&PTRM	Name of LU6.1 connection (CON)
&PRNM	Processor name
&BCAP	BCAM application name
&LTRM	Name of LPAP parameter
&USER	User ID
&SYSD	SNA sense code (system)
&USSD	SNA sense code (user)
&FMH7	Error message from the remote application
&AGUS	ID of job-submitting user

The following values are possible for the inserts &SYSD and &USSD with homogeneous interconnection:

&SYSD&USSD	Meaning
08120000	Resource bottleneck (e.g. page pool full)
08130000 081B0000	Contention: A request to occupy a session was rejected by the contention loser application because the contention winner application had already occupied the session for a job.
08641003	Invalid or locked TAC
0864C5E2	PEND ER from UTM
0864C5D9	PEND ER from the application program unit
0864D9E2	PEND RS from UTM
0864D9E4	PEND RS from the application program unit
0866D9E2	PEND RS from UTM
0866D9E4	PEND RS from the application program unit
10030000	Invalid or locked TAC

K088

UTM-D session start : &LSES/&RSES/&LPAP
SR-STATE: &SRFG PET &PSQN
SAVED : &ESQS &EBSS
ACT. : &ESQR &ESRR &EBSR

UTM-D session start. The message contains diagnostic information

Inserts	Meaning
&LSES	LSES name
&RSES	RSES name
&LPAP	LPAP name
&SRFG	Status bits from the LSES table entry (SR)
&PSQN	PET sequence numbers Two 2 byte numbers: sequence number sent saved sequence number sent current
&ESQS	Secured sequence numbers Two 2-byte numbers: SLU TO PLU PLU TO SLU
&EBSS	Secured bracket state "BETB" = BETween Bracket "INBR" = IN Bracket Receive (local side without send authorization) "INBS" = IN Bracket Send (local side with send authorization)
&ESQR	Current sequence numbers (from STSN request) Total of 5 bytes: SEC_TO_PRI_SQN (2 bytes) PRI_TO_SEC_SQN (2 bytes) ACTION_CODE_SEC_TO_PRI (2 bits) 00: ignore 01: set 10: test 11: set and test ACTION_CODE_PRI_TO_SEC (2 bits) 00: ignore 01: set 10: test 11: set and test RESERVED (4 bits)
&ESRR	Current sequence numbers RSP(STSN) Total 5 bytes: SEC_TO_PRI_SQN (2 bytes) PRI_TO_SEC_SQN (2 bytes) ACTION_CODE_SEC_TO_PRI (2 Bit) 00: ignore 01: set 10: test 11: set and test ACTION_CODE_PRI_TO_SEC (2 bits) 00: ignore 01: set 10: test 11: set and test RESERVED (4 bits)
&EBSR	Current bracket state "BETB" = BETween Bracket "INBR" = IN Bracket Receive (local side without send authorization) "INBS" = IN Bracket Send (local side with send authorization)

K089

Request to delete asynchronous message ( &GNDATE/&GNTIME ) for destination &DEST accepted.
&GNUSER / &USER / (&DLDATE/&DLTIME) / &CHAIN

&CHAIN	Meaning
NO	No negative confirmation job of the deleted message was present.
DEL	The negative confirmation jobs should also be deleted.
ACT	The negative confirmation job should be activated, i.e. inserted in the message chain of its receiver.

Any positive confirmation job is always deleted when the job is executed.

K090

Request to delete all asynchronous messages for destination &DEST accepted.
&USER / (&DLDATE/&DLTIME)

K091

Due to a resource bottleneck no sign-on can be processed by application &BCAP at this time - try later

This message additionally contains the following insert:

&REA7

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

K092

Please enter password and optional new password

K093

Service cannot be stacked.

K094

Sequence of unsuccessful sign-on attempts

With this message openUTM initiates a silent alarm to indicate a sequence of unsuccessful sign-on attempts by a user or from a client. A response to this situation can be made in the application via the MSGTAC program unit, for example. The SIGNON SILENT-ALARM=nnn parameter of the KDCDEF utility can be used to set the number of unsuccessful attempts after which openUTM is to generate message K094.

The message contains the following inserts:

Inserts	Meaning
&PTRM	Terminal name
&PRNM	Processor name
&BCAP	Application name
&LTRM	Logical terminal name
&USER	User ID
&RCF1B	Reason for the rejection
&REA4	Originator of the rejection (L=LTERM, U=USER, B=BOTH)

Insert &USER contains the login name of the last unsuccessful sign-on attempt in the sequence. This may be a login name generated for the application or any character string passed to UTM as a login name.

Insert &RCF1B consists of three characters indicating the reason why the last sign-on attempt in the sequence was rejected. It is set by UTM as for return fields KCRSIGN1 and KCRSIGN2 of KDCS call SIGN ST.

The &REA4 insert specifies, if the user (U), the client LTERM (L) or both (B) have caused the message. The counter for the unsuccessful sign-on attempts is reset to zero.

K095

KDCOFF effective - input please

K096

End of stacking - input please

K097

Input for new password cannot be used - please sign on

K098

Input exit  &RCF1C &RCF2B - input please

This message is generated if errors are detected by UTM or by the exit itself when the INPUT exit is called.

Insert &RCF1C indicates what openUTM discovered during or after the INPUT exit:

&RCF1C	Meaning
IN00	INPUT exit call okay from UTM standpoint
IN01	Error in calling up INPUT exit via IUTMHLL
IN02	KDCS call in INPUT exit
IN03	Output parameters do not match KCICCD
IN04	Illegal value in KCICCD
IN05	DB USER CALL in INPUT exit
IN06	Signal in INPUT exit

Insert &RCF2B indicates what the INPUT exit has entered in the KCIERRCD output parameter in the case of KCICCD = ’ER’.

K099

&MSG

K101

Bottleneck - please repeat last input

This message is output in response to any of the following events:

• If a dialog input message should be buffered in the page pool due to a TAC class waiting situation, and there is not enough room in the page pool

• If an input message destined for an asynchronous program, a TAC queue or a temporary file is to be saved to the page pool and either warn level 2 has been exceeded or there is not enough room in the page pool

• If an input message is intended for an asynchronous program, a TAC queue or a temporary queue, and the number of messages saved for this asynchronous TAC, this TAC queue or this temporary queue has already reached or exceeded the generated value of QLEV, and the temporary queues were generated with QMODE=STD