Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

UTM dump error codes

The Group column in the table below describes to which reason group the dump code error code belongs. The following groups exist:

A

The cause is a user error, e.g. an error in

  • generating and administering UTM applications

  • generating the system (e.g. division of the address space)

  • programming a format exit

U

The cause is an error in the UTM code.

S

The cause is an error in another system component (software or hardware).

F

The dump is a continuation dump, another task has caused the application to terminate abnormally.

D

The UTM dump was created for diagnostic purposes. The UTM work task continues running.

M

The cause is a memory bottleneck.

X

The cause is an error in the XAP-TP code (OSI TP).

Multiple classifications are possible, e.g. ADS.

You must write a problem report for error diagnosis for all errors of groups U and S and all error codes not listed in the table below. A number of different documents are required for diagnosis. For detailed information and a list of the required documents, refer to section "Producing error documentation".
In the following table, the values marked with *) appear only on BS2000 systems and the values marked with **) appear only on Unix, Linux and Windows systems.

Code

Group

Meaning

ADMI98

D

The local data area is too small.

AHQA00

MX

XAP-TP component.
KCOCOTA module, QueueAnno() function.
The mGetBufferSpace() macro issued the return code LB_NOMEM.

AHSA02

SUX

XAP-TP component.
Module KCOCOTA, function SendAnno().
The system interfaces call KCOBRSE supplied a bad return code.

AINF01

S

The return code is not equal X'00' after the AINFcall.

ALAxxx **)

ASU

Error number xxx when calling shmat() in KCSALME.

ALGxxx **)

ASU

Error number xxx when calling shmget() in KCSALME.
For possible cause, see start error 33, or KDCREM was not called before application start or shared-memory bottleneck due to overly large CACHESIZE
Note: ALG022 can occur when the shared-memory to be allocated is larger than the machine-specific maximum (tuning parameter SHMMAX).
Note: ALG028 can occur when the maximum number of possible shared-memory [X] segments was reached.
Action: Modify the KDCDEF generation or tune the UNIX kernel.

ALME01 *)

ASU

Illegal system return code during KCSALME call.
If this error occurs in a tool, it generally means that the virtual storage is insufficient for the request to be processed.
Action: Extend the address space for the ID.
For KDCDUMP an estimation of uses virtual storage is given in the chapter "KDCDUMP messages".

ALME02 *)

ASU

UTM tried to create a memory pool for KAA tables, but the memory pool already exists. Possible cause: a task of the 'old' UTM application has not completed program/task termination.
Action: check whether all tasks of the 'old' application have left the system. A task may, for instance, still be present in the system because a console message has not been answered. Then restart.

ALME03 *)

AMS

Error when creating or connecting a data space. For detailed information see BS2000 return code in diagnostic message on SYSOUT or SYSLST.

AREC01 *)

SU

Error during $AREC call for the writing of a record by the BS2000 Accounting Routine

ASA006

SUX

XAP-TP component.
Module KCOASAM was called with the operation code ASAM_ATTACH. Bad return code from bBuildPAddr.

ASA007

SUX

XAP-TP component.
Module KCOASAM was called with the operation code ASAM_ATTACH. First task of the application, but OSS issued return code NOTFIRST.

ASA009

SX

XAP-TP component.
Module KCOASAM was called with the operation code ASAM_ATTACH. OSS returned the return code "INVEREF" for an "attach" call.

ASA010

SX

XAP-TP component.
Module KCOASAM was called with the operation code ASAM_ATTACH. OSS returned a bad return code for an "attach" call.

ASA011

FSX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_DETACH". On the "detach" call, OSS returned the return code "ERROR".
The task is already in the termination phase after another task has abnormally terminated the application. OSS returned an incorrect error code because openUTM still has to fetch an event from OSS.

ASA012

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_DETACH". On the "detach" call, OSS returned the return code "INVAREF".

ASA013

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_DETACH". On the "detach" call, OSS returned a bad return code

ASA033

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_IND". The returned application context name is too long.

ASA034

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_IND". OSS returns the return code "ERROR" on the "assin" call.

ASA035

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_IND". OSS returns the return code "INVREF" on the "assin" call.

ASA036

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_IND". OSS returns a bad return code on the "assin" call.

ASA043

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_IND". OSS returns the return code "ERROR" on a positive "assrs" call.

ASA044

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_IND". Bad return code from "PutElement".

ASA045

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_IND". OSS returns a bad return code on a positive "assrs" call.

ASA046

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_IND". OSS returned the return code "ERROR" on the negative "assrs" call.

ASA048

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_IND". OSS returned a bad return code on the negative "assrs" call.

ASA049

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_IND". Bad return code from "PutElement".

ASA051

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_CNF". The returned Application Context Name is too long.

ASA052

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_CNF". OSS returned the return code "ERROR" on the "asscf" call.

ASA053

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_CNF". OSS returned the return code "INVREF" on the "asscf" call.

ASA054

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_CNF". OSS returned a bad return code for an "asscf" call.

ASA060

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_CNF". OSS returned the return code "ERROR" on the "aborq" call.

ASA062

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_CNF". OSS returned a bad return code for an "aborq" call.

ASA064

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_CNF". OSS returned an invalid diagnostic value on a negative confirmation.

ASA065

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_CNF". OSS returned an invalid "result source" value on a negative association confirmation.

ASA066

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_CNF_TIMEOUT". OSS returned the return code "ERROR" on the "aborq" call.

ASA068

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_CNF_TIMEOUT". OSS returned a bad return code on the "aborq" call.

ASA071

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ABORT_IND". OSS returned the return code "ERROR" on the "aboin" call.

ASA072

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ABORT_IND". OSS returned the return code "INVREF" on the "aboin" call.

ASA073

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ABORT_IND". OSS returned a bad return code on the "aboin" call.

ASA080

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_P_ABORT_IND". OSS returned the return code "ERROR" on the "paboin" call.

ASA081

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_P_ABORT_IND". OSS returned the return code "INVREF" on the "paboin" call.

ASA082

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_P_ABORT_IND". OSS returned a bad return code on the "paboin" call.

ASA083

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_CNF". Bad return code from "PutElement".

ASA084

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_CNF". Bad return code from "PutElement".

ASA085

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ASS_CNF_TIMEOUT". Bad return code from "PutElement".

ASA088

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_RELEASE_IND". OSS returned the return code "ERROR" on the "relin" call.

ASA089

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_RELEASE_IND". OSS returned the return code "INVREF" on the "relin" call.

ASA090

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_RELEASE_IND". OSS returned a bad return code on the "relin" call.

ASA091

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_RELEASE_IND". OSS returned an invalid value for "release reason".

ASA092

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_RELEASE_IND". OSS returned the return code "ERROR" on the "aborq" call.

ASA094

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_RELEASE_IND". OSS returned a bad return code on the "aborq" call.

ASA095

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_RELEASE_IND". OSS returned the return code "ERROR" on the "relrs" call.

ASA097

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_RELEASE_IND". OSS returned a bad return code on the "relrs" call.

ASA099

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ABORT_REQ". OSS returned an invalid value for "abort diagnostic".

ASA100

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ABORT_REQ". OSS returned the return code "ERROR" on the "aborq" call.

ASA101

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ABORT_IND". Bad return code from "PutElement".

ASA102

SX

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_ABORT_REQ". OSS returned a bad return code on the "aborq" call.

ASA104

AX

XAP-TP component.
The function "bBuildPAddr" of the module KCOASAM was called. The presentation selector of a local access point or of a remote partner is too long.

ASA105

AX

XAP-TP component.
The function "bBuildPAddr" of the module KCOASAM was called. The session selector of a local access point or of a remote partner is too long.

ASA116

SX

XAP-TP component.
The function "BuildRemoteAet" of the module KCOASAM was called. The APT has "form2" format, but the AEQ doesn't have "form2" format.

ASA120

SX

XAP-TP component.
The function "BuildRemoteAet" of the module KCOASAM was called. The APT has the "form1" format, but the AEQ doesn't have "form1" format.

ASA122

SX

XAP-TP component.
The function "BuildRemoteAet" of the module KCOASAM was called. The APT has neither the "form1" format nor the "form2" format.

ASA128

M

XAP-TP component.
The "CopyDefinedContext" function of the module KCOASAM was called. Bad return code of "PutElement".

ASA137

M

XAP-TP component.
The module "KCOASAM" was called with the opcode "ASAM_GO_IND". The association is not locked.

ASA139

SX

XAP-TP component.
KCOASAM was called with the operation code ASAM_P_ABORT_IND. Bad return code from "PutElement".

ASA151

SX

XAP-TP component.
KCOASAM was called with the operation code ASAM_RELEASE_IND. Bad return code from "PutElement".

ASA152

SX

XAP-TP component.
KCOASAM was called with the operation code ASAM_ABORT_REQ. Bad return code from "PutElement".

ASA153

SX

XAP-TP component.
KCOASAM was called with the operation code ASAM_ABORT_REQ. Bad return code from "SacfSeparator".

ASA155

SX

XAP-TP component.
KCOASAM was called with the operation code ASAM_ABORT_IND. Bad return code from "SacfSeparator".

ASA156

SX

XAP-TP component.
KCOASAM was called with the operation code ASAM_P_ABORT_IND. Bad return code from "SacfSeparator".

ASA157

SX

XAP-TP component.
KCOASAM was called with the operation code ASAM_RELEASE_IND. Bad return code from "SacfSeparator".

ASIO01

AU

File is not identified as open during KCSASIO call.

ASIO02 **)

AU

Invalid (i.e. too large) position for writing into file detected when calling KCSASIO.
Additional information: The file name and the current position are output in an additional message "K078 KCSASIO ...".

ASIO03 **)

AU

Invalid (i.e. too large) write request for writing to file detected when calling
KCSASIO.Additional information: See ASIO02

ASIO04 **)

AU

Invalid (i.e. too large) position for reading from file detected when calling KCSASIO.
Additional information: See ASIO02

ASIO05 **)

AU

Invalid (i.e. too large) read request for reading from file detected when calling
KCSASIO.
Additional information: See ASIO02

ASIO06 **)

AU

Generic Error on positioning in file when calling KCSASIO.

ASIS99

D

Normal execution of command "KDCSHUT KILL" or the call to the program interface for administration with the opcode KC_SHUTDOWN and the subopcode1 KC-KILL.

ATAxxx **)

AU

Error on connecting a shared-memory to the work process.
If xxx is the value for EINVAL, there is a conflict between a shared-memory of the user and a shared-memory of the UTM application. If a shared object is generated and used with LOADMODE=ONCALL, this can also cause an error with the value EINVAL.
Action: In these cases, the error can be avoided by deactivating the shared-memory monitoring facility on starting the application.

BFMM05

M

UTM cluster application
It was not possible to request another buffer segment. The virtual address space may be too small.

BFMM21

ASU

UTM cluster application
A timeout occurred while releasing a file lock.
Action: See CCFG19.

BFMM22

SU

UTM cluster application
A bad return code was returned when releasing a file lock.

BRSREM **)

F

UTM application was terminated with the KDCREM utility.

BRSE01 *)

S

Invalid parameter QUEUE_DISCIPLINE when creating a bourse or when sending or receiving an announcement.
Invalid parameter LENGTH_OF_ANNO when sending an announcement.
Bad return code returned from bourse interface.

BRSE02 *)

S

Error on enqueuing of the task at WORK bourse (chamber 1)

BRSE03 *)

S

Error on enqueuing of the task at task specific bourse (chamber 1).

CACHT1

F

Another task has terminated the application abnormally (=continuation dump)

CACHT2

F

(See CACHT1)
Another task has terminated the application abnormally (=continuation dump)

CACHT3

F

(See CACHT1)
Another task has terminated the application abnormally (=continuation dump)

CACHT4

F

(See CACHT1)
Another task has terminated the application abnormally (=continuation dump)

CACHT5

F

(See CACHT1)
Another task has terminated the application abnormally (=continuation dump)

CC-...

D

Diagnostic dump generated on the basis of a primary KDCS return code. The prefix CC- is followed by the primary KDCS return code (e.g. CC-84Z). Activation and deactivation via the message dump function.

CCFG07

SU

UTM cluster application
Module KCCCFG, entry KCCCGFB
Bad return code from KCSGLHN.

CCFG19

ASU

UTM cluster application
Module KCCCFG, opcode CCFG_READ_CLUSTER_FILE
Timeout when requesting shared lock.
Action: See section "Actions when locking UTM cluster files" .

CCFG20

SU

UTM cluster application
Module KCCCFG, opcode CCFG_READ_CLUSTER_FILE
Bad return code when requesting shared lock.

CCFG21

ASU

UTM cluster application
Module KCCCFG,
Timeout when requesting exclusive lock.
Action: See CCFG19.

CCFG22

SU

UTM cluster application
Module KCCCFG
Bad return code when requesting the exclusive lock.

CCFG29

ASU

UTM cluster application
Module KCCCFG, timeout when releasing file lock.
Action: See CCFG19.

CCFG30

SU

UTM cluster application
Module KCCCFG, opcode CCFG_READ_CLUSTER_FILE
Bad return code when releasing the file lock.

CCFG32

ASU

UTM cluster application
Module KCCCFG, opcode CCFG_REGISTER_COMPLETE
Invalid version of cluster configuration file.

CCFG33

ASU

UTM cluster application
Module KCCCFG, opcode CCFG_REGISTER_COMPLETE
Corrupt cluster configuration file.

CCFG34

ASU

UTM cluster application
Module KCCCFG, opcode CCFG_REGISTER_COMPLETE
Invalid application name in cluster configuration file.

CCFG35

ASU

UTM cluster application
Module KCCCFG, opcode CCFG_REGISTER_COMPLETE
The cluster configuration file was regenerated during operation.

CCFG41

ASU

UTM cluster application
Module KCCCFG, opcode CCFG_OPEN_CLUSTER_FILE
Timeout when initializing global lock.
Action: See CCFG19.

CCFG42

SU

UTM cluster application
Module KCCCFG, opcode CCFG_OPEN_CLUSTER_FILE
Bad return code when initializing the global lock.

CCFG43

ASU

UTM cluster application
Module KCCCFG, opcode CCFG_CLOSE_CLUSTER_FILE
Timeout when destroying global lock.
Action: See CCFG19.

CCFG44

SU

UTM cluster application
Module KCCCFG, opcode CCFG_CLOSE_CLUSTER_FILE
Bad return code when destroying the global lock.

CCFG45

SU

UTM cluster application
Module KCCCFG, opcode CCFG_INIT_KAA
Bad return code from KCSGLHN

CCFG49

S

UTM cluster application
Module KCCCFG, opcode READ_CLUSTER_FILE
Bad return code when reading the cluster file.

CCFG50

A

UTM cluster application
Module KCCCFG, opcode READ_CLUSTER_FILE
Corrupt cluster file.

CCFG51

A

UTM cluster application
Module KCCCFG, opcode READ_CLUSTER_FILE
Invalid version of cluster configuration file.

CCFG52

A

UTM cluster application
Module KCCCFG, opcode READ_CLUSTER_FILE
Invalid application name in cluster configuration file.

CCFG53

A

UTM cluster application
Module KCCCFG, opcode READ_CLUSTER_FILE
The cluster configuration file was regenerated during operation.

CCFG55

A

UTM cluster application
Module KCCCFG, opcode NODE_FAILURE
Corrupt cluster configuration file.

CCFG56

A

UTM cluster application
Module KCCCFG, opcode NODE_FAILURE
Invalid version of cluster configuration file.

CCFG57

A

UTM cluster application
Module KCCCFG, opcode NODE_FAILURE
Invalid application name in cluster configuration file.

CCFG58

A

UTM cluster application
Module KCCCFG, opcode NODE_FAILURE
The cluster configuration file was regenerated during operation.

CCFG62

ASU

UTM cluster application
Module KCCCFG, opcode CCFG_RESET_START_SERIALIZATION
Timeout when releasing lock.
Action: See CCFG19.

CCFG63

SU

UTM cluster application
Module KCCCFG, opcode CCFG_RESET_START_SERIALIZATION
Bad return code when releasing lock.

CCFG64

ASU

UTM cluster application
Module KCCCFG, opcode CCFG_RESET_START_SERIALIZATION
Timeout when destroying lock.
Action: See CCFG19.

CCFG65

SU

UTM cluster application
Module KCCCFG, opcode CCFG_RESET_START_SERIALIZATION
Bad return code when destroying lock.

CCFG71

AU

UTM cluster application
KCCCFG module, opcode READ_CLUSTER_FILE or
CHECK_CLUSTER_FILE
The local node is marked as failed in the cluster configuration file.

CCFG72

AU

UTM cluster application
KCCCFG module, opcode CCFG_NODE_FAILURE
The local node is marked as failed in the cluster configuration file.

CCKF02

SU

UTM cluster application
Module KCCCKF
Unexpected return code from KCCFILA when opening the KDCFILE.

CCKF03 **)

SU

UTM cluster application
Module KCCCKF
Unexpected return code from KCCGFLK on unlock.

CCKF04

SU

UTM cluster application
Module KCCCKF
Unexpected return code from KCCFILA when closing the KDCFILE.

CCTR17

AU

The node application is registered but the journal file could not be opened.
Possibly the journal files were deleted.
The abnormal termination may also occur after a previous start error.

CDTN02

M

XAP-TP component.
Module KCOCOHF, function CheckDtnidTtnid().
The macro mGetBufferSpace() issued the return codeLB_NOREM.

CFMM05

D

On send, the length in DCF does not match that specified in the letter header.

CLREST

D

UTM cluster application
The dump is only generated during a node application warm start with test mode enabled. It is used for diagnostic purposes following possible errors during the warm start of the cluster.

COBOL6 **)

A

The internal NETCOBOL function CBL_SETJMP was called within libwork.so although NETCOBOL is not supported on AIX.

COBOL7 **)

A

The internal NETCOBOL function CBL_LONGJMP was called within libwork.so although NETCOBOL is not supported on AIX.

COBOL8 **)

A

The internal function coblongjmp was called within libwork.so although no COBOL program is generated.

COBOL9 **)

A

The internal function cobsavenv2 was called within libwork.so although no COBOL program is generated.

CONS03

A

The KDCFILE was overwritten during operation.
Possible cause: KDCDEF run in current application.
Action: Check start procedure

CSND04

MX

XAP-TP component.
Invalid return code after calling PutElement() to request a dynamic buffer for
concatenator send data.

CSND05

SX

XAP-TP component.
Invalid return code after calling an OSS presentation function.

CTPF04

M

XAP-TP component:
The return code of PutElement was not equal to DM_OK.

DC....

D

Diagnostic dump generated on the basis of a secondary KDCS return code. The prefix DC is followed by the secondary KDCS return code (e.g. DCKS17). Activation and deactivation via the message dump function.

DIAGCL

D

UTM cluster application
A node application has been terminated abnormally. Before termination, all the
other node applications were informed of the abnormal termination if this was
still possible. The informed node applications write a diagnostic dump.

DIAGDP

D

A diagnostic dump has been generated by means of the administration
command "KDCDIAG DUMP=YES" or by calling the program interface for
administration with the opcode KC_CREATE_DUMP.

DMCA00

M

XAP-TP component.
Module KCOCODM, function ConnectDynMemArea().
The function ConnectSharedMem() issued the return code MEM_NOMEM.

EDITER *)

ADS

Error in conjunction with the edit profile used.

EHHP00

M

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The return code from mGetBufferSpace() was not equal to LB_OK.

EHHP01

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_datain() returned the return code P_ERROR.

EHHP02

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_datain() returned the return code P_INVREF.

EHHP03

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_datain() returned an unknown return code

EHHP04

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_typein() returned the return code P_ERROR.

EHHP05

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_typein() returned the return code P_INVREF.

EHHP06

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_typein() returned an unknown return code.

EHHP07

SX

XAP-TP function.
Module KCOXFEH, function HandlePresEvent().
The function CalcUserDataLth() returns 0 for length of user data after calling
the OSS function p_typein().

EHHP08

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_synin() returned the return code P_ERROR.

EHHP09

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_synin() returned the return code P_INVREF.

EHHP10

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_synin() returned an unknown return code.

EHHP12

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The function CalcUserDataLth() returns zero for length of user data after
calling the OSS function p_synin().

EHHP13

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_syncf() returned the return code P_ERROR.

EHHP14

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_syncf() returned the return code P_INVREF.

EHHP15

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_syncf() returned an unknown return code.

EHHP17

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The function CalcUserDataLth() returns zero for length of user data after
calling the OSS function p_syncf().

EHHP18

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_tkgin() returned the return code P_ERROR.

EHHP19

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_tkgin() returned the return code P_INVREF.

EHHP20

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_tkgin() returned an unknown return code.

EHHP21

S

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_tkgin() did not return the token S_T_MINOR.

EHHP22

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_tkpin() returned the return code P_ERROR.

EHHP23

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_tkpin() returned the return code P_INVREF.

EHHP24

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_tkpin() returned an unknown return code.

EHHP25

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_tkpin() did not return the token S_T_MINOR.

EHHP26

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The function CalcUserDataLth() returns zero for length of user data after
calling the OSS function p_tkpin().

EHHP27

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_minin() returned the return code P_ERROR.

EHHP28

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_minin() returned the return code P_INVREF.

EHHP29

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_minin() returned an unknown return code.

EHHP30

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The function CalcUserDataLth() returns zero for length of user data after
calling the OSS function p_minin().

EHHP31

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_mincf() returned the return code P_ERROR.

EHHP32

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_mincf() returned the return code P_INVREF.

EHHP33

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function p_mincf() returned an unknown return code.

EHHP34

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The function CalcUserDataLth() returns zero for length of user data after calling the OSS function p_mincf().

EHHP35

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The function o_event() returned the unexpected event P_MAJIN.

EHHP36

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The function o_event() returned the unexpected event P_MAJCF.

EHHP37

SX

XAP-TP component.
Module KCOXFEH, function HandlePresEvent().
The OSS function o_event() returned an unexpected event type.

EHRP01

MX

XAP-TP component.
Module KCOXFEH, function ReloadPresEvent().
The macro mGetBufferSpace() issued a return code not equal to LB_OK.

EHSP00

SX

XAP-TP component.
Module KCOXFEH, function StorePresEvent().
StorePresEvent() is to store a presentation event in DynMem. However, an event is already stored for the corresponding association (mValLth(g, &pAss->PendingEvnt.h) > 0).

EHSP01

M

XAP-TP component.
Module KCOXFEH, function StorePresEvent().
The function PutElement() issued the return code DM_NOMEM.
Action: Increase the value for the size of the OSI scratch area in the KDCDEF generation (parameter MAX OSI-SCRATCH-AREA).

EKAA11

S

UTM cluster application
Timeout when releasing the file lock for the JKAA file.
Action: See CCFG19.

EKAA12

S

Incorrect return code from KCCGFLK when releasing the file lock for the JKAA file.

EKAA13

S

UTM cluster application
Timeout when destroying the file lock for the JKAA file.
Action: See CCFG19.

EKAA14

S

Incorrect return code from KCCGFLK when destroying the file lock for the JKAA file.

ENCERR

DSU

UTM expected an encrypted message, but received an unencrypted message. There is no application abort pending. The dump is only for diagnostic purposes.

ENDE01

SU

The KAA pointer in KTA doesn't point to a KAA.

ENDE02

AU

Interrupt with locked KAA.

ENDE03

ASU

Abnormal task termination between writing a confirmatory record and the (temporary) end of the UTM transaction.
Possible cause: System shut down with UTM application running  or RUNOUT-STXIT or FORCE-JOB-CANCEL during this period.

ENDE04

SU

The cache cannot be released.

ENDE05

SU

The KAA cannot be released.

ENDE06

ASU

Error when opening the SYSLOG file.
This error may occur after abnormal termination of a UTM task (e.g. by CANCEL-JOB/FORCE-JOB-CANCEL) if the user accesses the SYSLOG file before the application has terminated. It causes 1 PAM page (at most) with SYSLOG messages to be lost.
Action: Check start procedure (access to SYSLOG)

ENDE07 *)

AS

A task was terminated abnormally (e.g. CANCEL-JOB/FORCE-JOB-CANCEL, TERM macro) and at this time it was the only task connected to a SLOT memory pool. At termination of this task the memory pool is disabled by the operationg system. As a consequence the UTM-application becomes inoperable.
Action: Avoid abnormal termination of UTM-tasks

ENDE10 *)

ASU

A task was terminated abnormally while it had already completed the start-up phase (possible reasons: system dump, FORCE-JOB-CANCEL, etc.). As a consequence the application is terminated abnormally as well.

ENDE11

DSU

The application was terminated normally, but on disconnect from the OSS access point, OSS delivered a return code other than OK. If test mode is activated, a UTM diagnostic dump is initiated.

ENDE12

ASU

A task terminated (either normally or abnormally). Not enough tasks remain to continue processing the application (e.g. because there are tasks in the PGWT).

ENDE14

F

A task terminated (either normally or abnormally) and the task has still not called KCSTRMA. However, the status of the application is TERM_APPL. KCSTRMA was called with ENDE14 to ensure that all tasks generate a UTM dump if the application terminates abnormally.

ENDE15 *)

ADU

A task was terminated abnormally while in state TPR (possible reasons: system dump, FORCE-JOB-CANCEL, etc.). As the termination occurred during the start of the task and it was not the first task of the application only a diagnostic dump of this task is initiated. The application run is not terminated.

ENDE16 *)

AD

Abnormal termination of the application run caused by abnormal termination of a task in state TU (possible reasons: TERM-STXIT, CANCEL-JOB, LOGOFF, etc.). If test mode is switched on, then at each abnormal termination of a task in state TU a diagnostic dump with reason ENDE16 is initiated.

ENDE19

ASU

Only UTM system processes are running for the application. All normal processes were terminated. The reason may be an error in the start procedure or a start error when restarting the tasks after PEND ER or program exchange.

ENDPET

A

An UTM-D application cannot be terminated normally, because services still exist with the transaction status PTC (prepare to commit) or because no acknowledgments have been received for asynchronous messages sent to other applications.
In this case no UTM dump is generated. openUTM will perform a warm start at the next application start.

EVGE00

M

XAP-TP component.
Module KCOXFEV, function GetOssEvent().
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

EVGE01

S

XAP-TP component.
Module KCOXFEV, function GetOssEvent().
The return parameter <o_echain> contained an invalid value after calling the OSS function o_event().

EVGE03

SX

XAP-TP component.
Module KCOXFEV, function GetOssEvent().
The OSS function o_event() returned the return code O_ACS and the user data were not yet received completely on the call.

EVGE05

ASX

XAP-TP component.
Module KCOXFEV, function GetOssEvent().
The OSS function o_event() returned the return code O_ERROR. This can also happen when BCAM is terminated (BCEND).

EVGE06

SX

XAP-TP component.
Module KCOXFEV, function GetOssEvent().
The OSS function o_event() returned the return code O_INVEREF.

EVGE07

SX

XAP-TP component.
Module KCOXFEV, function GetOssEvent().
The OSS function o_event() returned the return code O_TIMEINT.

EVGE08

SX

XAP-TP component.
Module KCOXFEV, function GetOssEvent().
The OSS function o_event() returned the return code O_WAKEINT.

EVGE09

SX

XAP-TP component.
Module KCOXFEV, function GetOssEvent().
The OSS function o_event() returned the return code O_SYSTEM.

EVGE10

SX

XAP-TP component.
Module KCOXFEV, function GetOssEvent().
The OSS function o_event() returned the return code O_LOOK.

EVGE11

SX

XAP-TP component.
Module KCOXFEV, function GetOssEvent().
The OSS function o_event() returned the return code O_TRANSPORT.

EVGE12

SX

XAP-TP component.
Module KCOXFEV, function GetOssEvent().
The OSS function o_event() returned the return code O_SESSION.

EVGE13

SX

XAP-TP component.
Module KCOXFEV, function GetOssEvent().
The OSS function o_event() returned an unknown return code.

EVNT03

ASX

XAP-TP component.
Module KCOXFEV, function aputm_event().
The OSS function o_event(O_EVALLOOK) returned the return code
O_ERROR.
This can also occur when BCAM is terminated (BCEND).The error also occurs if a UTM application with OSI TP has been started and terminated again in the dialog with two tasks and another UTM application with the same ACCESS-POINT is then started in the dialog as a follow-up task in one of the two tasks.

EVNT04

SX

XAP-TP component.
Module KCOXFEV, function aputm_event().
The OSS function o_event(O_EVALLOOK) returned the return code O_INVEREF.

EVNT05

SX

XAP-TP component.
Module KCOXFEV, function aputm_event().
The OSS function o_event(O_EVALLOOK) returned the return code O_TIMEINT.

EVNT06

SX

XAP-TP component.
Module KCOXFEV, function aputm_event().
The OSS function o_event(O_EVALLOOK) returned the return code O_WAKEINT.

EVNT07

SX

XAP-TP component.
Module KCOXFEV, function aputm_event().
The OSS function o_event(O_EVALLOOK) returned the return code O_SYSTEM.

EVNT08

SX

XAP-TP component.
Module KCOXFEV, function aputm_event().
The OSS function o_event(O_EVALLOOK) returned the return code O_TRANSPORT.

EVNT09

SX

XAP-TP component.
Module KCOXFEV, function aputm_event().
The OSS function o_event(O_EVALLOOK) returned the return code O_SESSION.

EVNT10

SX

XAP-TP component.
Module KCOXFEV, function aputm_event().
The OSS function o_event(O_EVALLOOK) returned the return code O_PRESENTATION.

EVNT11

SX

XAP-TP component.
Module KCOXFEV, function aputm_event().
The OSS function o_event(O_EVALLOOK) returned the return code O_ACSE.

EVNT12

SX

XAP-TP component.
Module KCOXFEV, function aputm_event().
The OSS function o_event(O_EVALLOOK) returned an unknown return code.

EXIT00 **)

AU

Illegal exit() call recognized during execution of UTM system coding.

EXPI32

ASU

UTM cluster application
Bad return code from KCCGFLK when locking the cluster GSSB file.
Action: See CCFG19.

EXPI34

ASU

UTM cluster application
Bad return code from KCCGFLK when locking the cluster ULS file.
Action: See CCFG19.

EXPI35

ASU

UTM cluster application
Bad return code from KCCGFLK when locking the cluster ULS file.
Action: See CCFG19.

EXPI36

ASU

Bad return code from KCCGFLK when locking the cluster GSSB file.
Action: See CCFG19.

EXPI51

A

A periodic write was called by a task because the restart area of the task has become full. The task wishes to write another page of the restart area but no pages have become free through periodic write.
The cause may be a restart area which was generated too small, with the result that restart information of a single transaction is longer than the restart area (e.g. transaction with access to "numerous" page pool pages).
Action: Increase the number parameter in the generation statement "MAX RECBUF=(number,...)".

EXPI95

A

See EXPI51, but occurs in RESET_TA_RTN.

FHCV03 **)

S

Formatting system is not supported.

FILE00 **)

AU

Invalid file name / invalid file number of fgg-file when calling KCSFILE()
Possible cause: fgg-file(s) copied or deleted.
Action: Write PR or create a new fgg.

FMMM10

A

AN input message cannot be stored because the page pool is full.
Action: Increase page pool by increasing MAX PGPOOL=(number,...) in KDCDEF generation.

FMSM05

DSU

KCDFMSM was called with opcode PRSP_BID even though the session status is not WAIT_OF_BID_RSP.

FMSM12

S

Illegal LSES_WORK_STATE when receiving RTR.

FMTERR *)

ADS

The dump serves to diagnose the formatting error. It only contains KDCROOT data and is output in test mode only.

FREE01

AX

XAP-TP component.
Module KCOXFFO, function ap_free().
More than APFREE_MAX_TO_REL storage areas are to be released.

GETR00 **)

AU

Record length less than 0 when calling KCSGETR.
Possible cause: invalid input file.

GETR01 **)

AU

On reading the record length field of a record, fewer than 4 bytes were read in KCSGETR.
Possible cause: invalid input file

GETR02 **)

AU

Record read has a record length < 5 after reading of the record length field in KCSGETR.
Possible cause: invalid input file.

GETR03 **)

AU

On reading a record, fewer bytes were read in than expected after reading of the record length field in KCSGETR.
Possible cause: invalid input file.

GETR04 **)

AU

On reading a record with KCSGETR an invalid record was found.
Possible cause: invalid input file.

GFLKT1

F

UTM cluster application
Lock hierarchy infringed after Term Application (continuation dump).

GFLKT2

F

(see GFLKT1)
UTM cluster application
Lock hierarchy infringed after Term Application (continuation dump).

GLHN03 **)

A

Length of local hostname is greater than 64.

GMDT11

SU

UTM cluster application
Module KCCGMDT, opcode UPDATE_AND_UNLOCK_GSSB.
unexpected return code from KCCGFLK (lock GSSB file).
Action: See CCFG19.

GSYS00 **)

S

XAP-TP component.
Module KCOCOHF, function GetSystemInfo().
The function uname() issued a negative return code.

INPERR

AD

Error in INPUT exit was detected.

IOyxxx **)

ASU

ASIO return code: An unrecoverable error has occurred during file processing, yxxx = DMS error code.
Action: See section "Error codes during file processing"
Note: IOW009 from READ module of KDCUPD can occur if LPAP or OSI-LPAP messages of dead letter queue shall be transfered and the old kdcfile or old pagepool files are read only.
Action: Set write access for old kdcfile or old page pool files and repeat KDCUPD run.

IODxxx *)

ASU

ASIO return code: DMS error occurred and could not be corrected, Dxxx=DMS error code.
Note: IOD991 from READ module of KDCUPD can occur if LPAP or OSI-LPAP messages of dead letter queue shall be transfered and the old kdcfile or old page pool files are read only.
Action: Set write access for old kdcfile or old page pool files and repeat KDCUPD run.

IPC000 **)

ASU

IPC shared memory segment has been overwritten. A check takes place with every KDCS call.

IPC035 **)

A

Error on locking the IPC shared memory segment, this may be caused by KDCREM being called while the application is still running.

IPC037 **)

FU

IUTMIPC indicates that the application is terminated abnormally (= continuation dump). See also U306 with insert UERRNO=37.

IPCEND **)

F

A work process terminated outside of the control of openUTM. The application is therefore terminated.
Possible cause: see note for message U231

IPCREM **)

F

UTM application was terminated with the KDCREM utility.

ISLP00 *)

A

The subsystem VTSU is not started.

ISLP01 *)

S

The maximum SCB length is larger than expected by UTM.
Possible reason: A new version of subsystem VTSU is started and requires larger SCBs.

ISLP02 *)

ASU

Bad return code from VTSU when initializing a dynamic SCB.
Possible reason: Subsystem VTSU is not started or already deactivated.

ISLP03 *)

ASU

Bad return code from VTSU when analyzing first 8 characters of message.
Possible reason: The function key is not known by VTSU.

ISLP04 *)

SU

VTSU error when analyzing the UTM command.

ISLP05 *)

ASU

VTSU error when editing a dialog input message.
Possible reason: s. ISLP03.

ISLP06 *)

SU

VTSU detects a faulty output message.

ISLP09 *)

AU

Task-specific buffer for restart information too small.
Action: Increase MAX RECBUF=(...,length) specification in KDCDEF generation

ISLP11 *)

AU

(see ISLP09)
Task-specific buffer for restart information too small.
Action: Increase MAX RECBUF=(...,length) specification in KDCDEF generation

ISLP12 *)

AU

(see ISLP09)
Task-specific buffer for restart information too small.
Action: Increase MAX RECBUF=(...,length) specification in KDCDEF generation

ISLP13 *)

AU

Buffer for asnychronous output message is to small.
Action: Increase MAX TRMSGLTH=<length> specification in KDCDEF generation

ISLP42 *)

ASU

Bad return code from VTSU when requesting length of SCB during start of UTM task.
Possible reasoN

  • Terminal type not supported.
  • Subsystem VTSU not started.

ISLPT1 *)

F

Another task has terminated the application abnormally (= follow-up dump)

ISLPT4 *)

F

(see ISLPT1)
Another task has terminated the application abnormally (= follow-up dump)

JFC011

ASU

UTM cluster application
Timeout on KCCGFLK call in KCCJFCT with opcode CLOSE_FILES.
Action: See CCFG19.

JFC012

ASU

UTM cluster application
Timeout with opcode CLOSE_FILES.
Action: See CCFG19.

JFC016

SU

UTM cluster application
Error on the first readControlPage call in KCCJFCT with opcode CHECK_UNPROC_ENTRIES.

JFC018

SU

UTM cluster application
Error on the 2nd readControlPage call in KCCJFCT with opcode CHECK_UNPROC_ENTRIES.

JFC055

SU

UTM cluster application
Error on the first readControlPage call in KCCJFCT with opcode SET_NODE_PROCESSING_STATE.

JFC058

SU

UTM cluster application
Error on the 2nd readControlPage call in KCCJFCT with opcode SET_NODE_PROCESSING_STATE.

JFC067

SU

UTM cluster application
Error when reading the administration page in KCCJFCT with opcode SET_NODE_CR_SEQNR.

JFC071

SU

UTM cluster application
Error on the first readControlPage call in KCCJFCT with opcode GET_NODE_CR_SEQNR.

JFC072

SU

UTM cluster application
Error on the 2nd readControlPage call in KCCJFCT with opcode GET_NODE_CR_SEQNR.

JFC076

SU

UTM cluster application
Error on the readControlPage call in KCCJFCT with opcode RESET_NODE_CR_SEQNR.

JFC082

SU

UTM cluster application
Error on the 2nd readControlPage call in KCCJFCT with opcode RESET_DYNADM_LOCK.

JFC083

SU

UTM cluster application
Error on the first readControlPage call in KCCJFCT with opcode RESET_DYNADM_LOCK.

JFC400

ASU

UTM cluster application
Timeout on KCCGFLK call (lock) in KCCJFCT, internal function setFileLock.
Action: See CCFG19.

JFC401

ASU

UTM cluster application
Error on KCCGFLK call (lock) in KCCJFCT, internal function setFileLock.
Action: See CCFG19.

JFC402

SU

UTM cluster application
Error on KCCGFLK call (lock) in KCCJFCT, internal function setFileLock.

JFC404

SU

UTM cluster application
Timeout on KCCGFLK call (unlock) in KCCJFCT, internal function releaseFileLock.

JFC405

ASU

UTM cluster application
Error on KCCGFLK call (unlock) in KCCJFCT, internal function releaseFileLock.
Action: See CCFG19.

JFC420

SU

UTM cluster application
Error on KCCFILA call (write), first administration page in the journal file in KCCJFCT, internal function initControlPages.

JFC421

SU

UTM cluster application
Error on KCCFILA call (write) in KCCJFCT, internal function initControlPages.

JFC430

SU

UTM cluster application
Error on the first readControlPage call in KCCJFCT, internal function switchFiles.

JFC431

SU

UTM cluster application
Error on the 2nd readControlPage call in KCCJFCT, internal function switchFiles.

JFC460

SU

UTM cluster application
Error on the first readControlPage call in KCCJFCT, the first readControlPage call in KCCJFCT, internal function checkControlPages.

JFC501

SU

UTM cluster application
Error on KCCFILA call in KCCJFCT, internal function readPages.

JFC507

SU

UTM cluster application
Error on KCCFILA call in KCCJFCT, internal function writePages.

JFC512

SU

UTM cluster application
Error on KCCFILA call in KCCJFCT, internal function writeControlPage.

JFC550

SU

UTM cluster application
Error when reading an administration page in KCCJFCT with opcode
GET_JOURNAL_FILE_INFO.

JFC561

SU

UTM cluster application
Error on readControlPage call in KCCJFCT with opcode SET_COPY_STATE.

JFC570

SU

UTM cluster application
Error on readControlPage call in KCCJFCT with opcode SET_KAA_INFO.

JFC572

SU

UTM cluster application
Error on the 2nd readControlPage call in KCCJFCT with opcode SET_KAA_INFO.

JFC580

SU

UTM cluster application
Error on readControlPage call in KCCJFCT with opcode GET_KAA_INFO.

JFC581

SU

UTM cluster application
Error on the 2nd readControlPage call in KCCJFCT with opcode GET_KAA_INFO.

JFC583

SU

UTM cluster application
Error on the 3rd readControlPage call in KCCJFCT with opcode GET_KAA_INFO.

JFC584

SU

UTM cluster application
Error on the 4th readControlPage call in KCCJFCT with opcode GET_KAA_INFO.

JFC590

SU

UTM cluster application
Error on the first readControlPage call in KCCJFCT with opcode SET_GLOBAL_ADM_LOCK.

JFC591

SU

UTM cluster application
Error on the 2nd readControlPage call in KCCJFCT with opcode SET_GLOBAL_ADM_LOCK.

JFC594

SU

UTM cluster application
Error on the 3rd readControlPage call in KCCJFCT with opcode GET_GLOBAL_ADM_LOCK.

JFC595

SU

UTM cluster application
Error on the first readControlPage call in KCCJFCT with opcode RESET_GLOBAL_ADM_LOCK.

JFC596

SU

UTM cluster application
Error on the 2nd readControlPage call in KCCJFCT with opcode RESET_GLOBAL_ADM_LOCK.

JFC598

SU

UTM cluster application
Error on the first readControlPage call in KCCJFCT with opcode GET_GLOBAL_ADM_LOCK.

JFC599

SU

UTM cluster application
Error on the 2nd readControlPage call in KCCJFCT with opcode GET_GLOBAL_ADM_LOCK.

JFC611

SU

UTM cluster application
Error on the 2nd readControlPage call in KCCJFCT, routine checkAllProcessed.

JFC613

SU

UTM cluster application
Error on the first readControlPage call in KCCJFCT, routine checkAllProcessed.

JFC626

SU

UTM cluster application
Error on readControlPage call in KCCJFCT, routine checkAndRepair.

LATC01 **)

FSU

The lock mechanism is not functioning at the time when KCSLATC is called.
See LATC02

LATC02 **)

ASU

Error when calling KCXLOCK of the ATC lock bourse. Because the locks are implemented with semaphores in openUTM for Unix, Linux and Windows systems, an error code was returned for a semaphore operation.
The cause may be that the user deleted a semaphore of the application (either by means of a Unix, Linux or Windows system function or KDCREM).

LATC03 **)

SU

Max. number of locks per task exceeded.

LATC04 **)

SU

KCSLATC called under IPC lock.

LATCT1

F

During a request for a lock, the status of an application is set to TERM APPLICATION. The task is also terminated (= continuation dump).

LCAC01 **)

FSU

The lock mechanism is not functioning at the time when KCSLKAA / KCSLCAC / KCSPCMM is called. See LCAC02.

LCAC02 **)

ASU

Error on calling KCXLOCK of the KAA/CACH/PCMM lock bourse. Since in openUTM for Unix, Linux and Windows systems the locks are implemented by means of semaphores, as error code was reported with a semaphore operation.
The reason may be that the user has deleted a semaphore for the application (either through a Unix, Linux or Windows system function or through KDCREM).

LCAC03 **)

SU

Max. number of locks per task exceeded.

LCAC04 **)

SU

KCSLCAC called under IPC lock.

LCACT1

F

During a request for a lock, the status of an application is set to TERM APPLICATION. The task is also terminated (= continuation dump).

LKAA01 **)

FSU

The lock mechanism is not functioning at the time when KCSLKAA is called.
See LKAA02.

LKAA02 **)

ASU

Error on calling KCXLOCK of the KAA/CACH/PCMM lock bourse. Since in openUTM for Unix, Linux and Windows systems the locks are implemented by means of semaphores, as error code was reported with a semaphore operation.
The reason may be that the user has deleted a semaphore for the application (either through a Unix, Linux or Windows system function or through KDCREM).

LKAA03 **)

SU

Max. number of locks per task exceeded.

LKAA04 **)

SU

KCSLKAA called under IPC lock.

LKAAT1

F

During a request for a lock, the status of an application is set to TERM APPLICATION. The task is also terminated (= continuation dump).

LKLC26

FU

During locking of an entry, a situation is detected where the service is already entered in a queue chaining facility.
System error or continuation dump if the application is currently being abnormally terminated (through error or KDCSHUT KILL).
The case of a continuation dump may be recognized from the fact that the reason for the abort in message K060 is not LKLC26, and that a further dump has already been generated.

LKLC42

AU

Bourse wait time elapsed.
Action: Change KDCDEF generation, increase the RESWAIT=(...,time2) parameter in the MAX statement. This may also be caused by a hardware error that results in an operator message that needs to be answered but the answer was not sent or it was sent too late.
Check the console protocol in this case.

LKLC51

AU

See LKLC42

LKLC64

AU

See LKLC42

LKLCT1

F

Another task has terminated the application abnormally (=continuation dump)

LKLCT2

F

See LKLCT1

LKLCT3

F

See LKLCT1

LKLCT4

F

See LKLCT1

LKMTC0

F

Another task has abnormally terminated the application (= Continuation dump before KCSBRSE call)

LKMTC1

F

Another task has abnormally terminated the application (= Continuation dump after KCSBRSE call)

LKMTKP

D

This diagnostic dump is generated if TESTMODE=ON provided that the PEND KP flag is not reset in the lock field when the unlock is performed.

LPCM01 **)

FSU

The lock mechanism is not functioning at the time when KCSPCMM is called.
See LPCM02.

LPCM02 **)

ASU

Error when calling KCXLOCK of the ATC lock bourse. Because the locks are implemented with semaphores in openUTM for Unix, Linux and Windows systems, an error code was returned for a semaphore operation.
The cause may be that the user deleted a semaphore of the application (either by means of a Unix, Linux or Windows system function or KDCREM).

LPCM03 **)

SU

Max. number of tasks exceeded.

LPCM04 **)

SU

KCSLPCM called under IPC lock.

LPCMT1

F

During a request for a lock, the status of an application is set to TERM APPLICATION. The task is also terminated (= continuation dump).

LWRT02

SU

Error when opening the user log file <filebase>.USLA (copy A).

LWRT03

SU

Error when opening the user log file <filebase>.USLB (copy B).

LWRT04

ASU

Error on  SETL call for user log file <filebase>.USLA.
Write manipulations may have been performed to the current file generation or the base may have been modified. Use the KDCLOG command to switch while the application is running.
Action: If the next UTM application start is also aborted with LWRT04: Delete the user log file (i.e.the entire FGG) and regenerate it.

LWRT05

ASU

Error on  SETL call for user log file <filebase>.USLB.
The reason may be as described for LWRT04.

LWRT06

SU

Error on SETL call for user log file <filebase>.USLB during positioning back to beginning of file following an unsuccessfully concluded write job (e.g. due to disk storage bottleneck).

LWRT07

SU

Error on SETL call for user log file <filebase>.USLA during positioning back to beginning of file following an unsuccessfully concluded write job (e.g. due to disk storage bottleneck).

LWRT08

SU

Error with PUT call for writing an LPUT record to the user log file <filebase>.USLA.

LWRT09

SU

Error with PUT call for writing an LPUT record to the user log file <filebase>.USLB.

LWRT10

SU

Error with CLOSE call for the user log file <filebase>.USLB.

LWRT11

SU

Error with CLOSE call for the user log file <filebase>.USLA

LWRT17

A

KCSLWRT requested a buffer via KCSALME for writing to the user log file, and the buffer cannot be made available.
Action: Check memory requirements and operating system generation.

LWRT19

SU

Faulty RELSE call for copy A of user log file.

LWRT20

SU

Same as LWRT19, but for copy B.

MACF02

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MACF03

M

XAP-TP component.
The return code of SetTimer() was not equal to TI_OK.

MACF04

M

XAP-TP component.
The return code of GetLogRecord was not equal to MACF_OK.

ME....

D

Diagnostic dump generated on the basis of a specific UTM message. The prefix ME is followed by the message number of the UTM message (e.g. MEK135).
Activation and deactivation via the message dump function.

MFCR04

M

XAP-TP component.
The return code of GetLogRecord was MACF_NO_MEM.

MFCR07

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFCR08

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFCR09

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFCR10

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFCR11

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFCR16

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFCR17

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFCR18

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFCR19

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFCR20

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFCR21

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFCR24

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFDM03

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFDM04

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFDM05

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFDM06

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFRM05

AX

XAP-TP component.
On TP_RECOVER_REQ, no free dialog table entry for a transaction branch is available.
Possible cause: the number of associations in the previous application run was greater than the number of associations in the current run.

MFRM06

AX

(see MFRM05)
XAP-TP component.
On TP_RECOVER_REQ, no free dialog table entry for a transaction branch is available.
Possible cause: the number of associations in the previous application run was greater than the number of associations in the current run.

MFRM07

AX

(see MFRM05)
XAP-TP component.
On TP_RECOVER_REQ, no free dialog table entry for a transaction branch is available.
Possible cause: the number of associations in the previous application run was greater than the number of associations in the current run.

MFRM08

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFRM09

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFRM10

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFRM11

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFRM12

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFRM13

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFRM14

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFRM15

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFRM16

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFRM17

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFRM18

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFRM19

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFRM21

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFRM24

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFRM25

AX

XAP-TP component.
No free table entry available for a log damage record.
Action: Delete log damage records with TP_UPDATE_LOG_DAMAGE_REQ or increase the value of nMaxLogDamRec.

MFT102

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFT103

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFT104

M

XAP-TP component.
The return code of ChangeDescriptor was not equal to DM_OK.

MFT105

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFT106

M

XAP-TP component.
The return code of CopyElement was not equal to DM_OK.

MFT107

M

XAP-TP component.
The return code of CopyElement was not equal to DM_OK.

MFT108

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFT109

M

XAP-TP component.
The return code of CopyElement was not equal to DM_OK.

MFT110

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFT111

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFT113

M

XAP-TP component.
The return code of ChangeDescriptor was not equal to DM_OK.

MFT114

M

XAP-TP component.
The return code of CopyElement was not equal to DM_OK.

MFT115

M

XAP-TP component.
The return code of ChangeDescriptor was not equal to DM_OK.

MFT119

M

XAP-TP component.
The return code of GetLogRecord() was not equal to MACF_OK.

MFT120

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFT121

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFT122

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFT123

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFT124

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFT126

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFT127

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFT128

M

XAP-TP component.
The return code of CopyElement was not equal to DM_OK.

MFT129

M

XAP-TP component.
The return code of CopyElement was not equal to DM_OK.

MFT130

M

XAP-TP component
The return code of PutElement was not equal to DM_OK.

MFT131

M

XAP-TP component
The return code of PutElement was not equal to DM_OK.

MFT132

M

XAP-TP component
The return code of PutElement was not equal to DM_OK.

MFT133

M

XAP-TP component.
The return code of CopyElement was not equal to DM_OK.

MFT134

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFT135

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFT138

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFT139

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFT141

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFT142

M

XAP-TP component.
The function CopyElement issued a return code other than DM_OK.

MFT147

M

XAP-TP component.
The function PutElement issued a return code other than DM_OK.

MFT151

M

XAP-TP component.
The function PutElement issued a return code other than DM_OK.

MFTP03

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFTP04

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFTP05

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFTP06

M

XAP-TP component.
The return code of PutElement was not equal to DM_OK.

MFTP07

M

XAP-TP component.
The return code of SetTimer was not equal to TI_OK.

MFTP10

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFTP11

M

XAP-TP component.
The return code of RequestBuffer() was not equal to LB_OK.

MFTP12

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFTP15

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFTP16

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFTP17

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFTP18

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFTP19

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFTP20

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MFTP24

M

XAP-TP component.
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

MOVE03

AU

Invalid overlapping of destination and source area in KCSMOVE or KCSMOVEP.

MSCFER *)

DSU

Diagnostic dump following an error on an MSCF call when a task signs on or signs off at MSCF.

MSG000

DU

KCSCRMS was called with an invalid message ID. A diagnostic dump is written and the message "K000 MESSAGE NOT DEFINED" is output.

MUX001 *)

DS

Incorrect length specification in protocol header.
Possible reason: partner is not a MUX partner.

MUX003 *)

DSU

Unexpected return code from KCSLKLC. Possibly due to protocol error in partner application.

MUX004 *)

DS

Incorrect operation code in protocol header.
Possible reason: partner is not a MUX partner.

NDRCVY

D

The dump is only generated at the end of a node recovery with test mode enabled. It is used for diagnostic purposes following possible errors after a node recovery.

NET001 **)

M

Error when requesting memory area for the table of the local application names in the net process.

NET002 **)

M

Error when requesting memory area for the connection table in the net process.

NET003 **)

M

Error when requesting memory area for the application table in the net process.

NET006 **)

ASU

In the net process, at least one Bcamappl could not attached to the transport system.

NET011 **)

SU

Error when registering the CMX callback routine in utmnet.

NET014 **)

SU

Error when calling t_conin() in the net process.

NET019 **)

SU

In the net process, an invalid DATAGO event received from the transport system.

NET020 **)

SU

Error when calling t_event() in the net process.

NET022 **)

SU

Error when calling t_info() in the net process.

NET023 **)

SU

Error when calling t_datarq() in the net process.

NET031 **)

SU

Error when initializing the thread attributes in the net process.

NET032 **)

SU

Error when setting the detach attributes for the thread in the net process.

NET033 **)

SU

Error when creating the threads for the shared waiting point in the net process.

NET034 **)

SU

Error when creating the receive socket for the shared waiting point in the net process.

NET035 **)

SU

Error when setting the socket attribute REUSEADDR for the receive socket in the net process.

NET036 **)

SU

Error on bind() call for the receive socket in the net process.

NET037 **)

SU

Error when detecting the listener port for the receive socket in the net process.

NET038 **)

SU

Error when initializing the socket environment in the net process.

NET039 **)

A

On the computer there is not installed the socket library version that is necessary for the net process.

NMTE00

M

XAP-TP component.
Module KCOCOHF, function NewMemTabEntry().
The function RequestBuffer() issued the return code LB_NOMEM.

NMTE02

M

XAP-TP component.
Module KCOCOHF, function NewMemTabEntry().
The macro mGetBufferSpace() issued the return code LB_NOMEM.

NQATT1 *)

F

The status of the application is TERM APPLICATION. The task is thus also terminated (= continuation dump).

NQCAT1 *)

F

(see NQATT1)
The status of the application is TERM APPLICATION. The task is thus also terminated (= continuation dump).

NQKAT1 *)

F

(see NQATT1)
The status of the application is TERM APPLICATION. The task is thus also terminated (= continuation dump).

NQPCT1 *)

F

(see NQATT1)
The status of the application is TERM APPLICATION. The task is thus also terminated (= continuation dump).

NRDBER

A

Cluster application.
The node recovery needs to be terminated abnormally due to an error during database recovery. No UTM-dump is initiated.

ODIA00

SX

XAP-TP component.
Module KCOCOHF, function OssDiagInfo().
The OSS function o_error() returned the return code O_ERROR.

ODIA01

SX

XAP-TP component.
Module KCOCOHF, function OssDiagInfo().
The OSS function o_error() returned the return code O_INVEREF.

ODIA02

SX

XAP-TP component.
Module KCOCOHF, function OssDiagInfo().
The OSS function o_error() returned the return code O_INVEREF.

OREA00

SX

XAP-TP component.
The OSS function o_reason() returned the return code O_ERROR.

OREA01

SX

XAP-TP component.
The OSS function o_reason() returned the return code O_INVEREF.

OREA02

SX

XAP-TP component.
The OSS function o_reason() returned an invalid return code.

OSAFT2

F

Return code APEXT_TERMAPPL from XAP-TP.

OSGO01

SX

XAP-TP component.
Module KCOCOHF, function OssGo().
The OSS function o_go() returned the return code O_INVCREF.

OSGO02

SX

XAP-TP component.
Module KCOCOHF, function OssGo().
The OSS function o_go() returned the return code O_ERROR.

OSGO03

SX

XAP-TP component.
Module KCOCOHF, function OssGo().
The OSS function o_go() returned an unexpected return code.

OSS002 **)

ASU

Error number nnn when calling shmget() in s_rqshm().
Error nnn: See message K078.
Note: See ALGxxx.

OSS003 **)

ASU

Error number nnn when calling shmat() in s_rqshm().
Error nnn: See message K078.

OSTM01

AS

Serious error during interaction with database system.

OSTM05

AU

Task-specific buffer for restart information is too small.
Action: Increase the size of MAX RECBUF=(...,length) in the KDCDEF generation.

OSTM06

AS

Serious error during interaction with database system.

OSTM07

A

A log record cannot be backed up, since the page pool is full.
Action: Increase the size of the page pool. Do this by increasing MAX PGPOOL=(number,...) in the KDCDEF generation.

OSTP01

SX

XAP-TP component.
Module KCOCOHF, function OssStop().
The OSS function o_stop() returned the return code O_INVCREF.

OSTP02

SX

XAP-TP component.
Module KCOCOHF, function OssStop().
The OSS function o_stop() returned the return code O_ERROR.

OSTP03

SX

XAP-TP component.
Module KCOCOHF, function OssStop().
The OSS function o_stop() returned an unexpected return code.

PCMM05

AU

For KCSPCMM with the opcode Get Pagechain, the NR_PAGES parameter is invalid or larger than the number of all page pool pages.
Action: Increase MAX PGPOOL=number in KDCDEF generation.

PCTR00

M

XAP-TP component.
Module KCOCOHF, function PrepareCtrlReq().
The macro mGetBufferSpace() issued the return code LB_NOMEM.

PEND02

A

No further TACB can be written for "System PEND ER" because the page pool on KDCFILE is full.
Action: Increase page pool by increasing MAX PGPOOL=(number,...) in KDCDEF generation.

PEND03

AS

The DB system has reported a serious error, see DB-DIAGAREA in UTM dump.

PEND04

S

The DB system supplied an impermissible return code, see DB-DIAGAREA in UTM dump.

PEND05

AS

(see PEND03)
The DB system has reported a serious error, see DB-DIAGAREA in UTM dump.

PEND07

ASU

STXIT between writing of a confirmatory record and the (temporary) end of the UTM transaction (KCSEXPI call END_TA).
Possible cause: error in the DB connection module. A timer STXIT during this period is ignored.

PEND11

S

Inconsistent XID

PEND26

A

in case of "System PEND ER" for a socket application, it is not possible to write a K017 message for a KDCDISP that may be required later, since the page pool on KDCFILE is full.
Action: Increase page pool by increasing MAX PGPOOL=(number,...) in KDCDEF generation.

PEND97

A

(see PEND26)
in case of "System PEND ER" for a socket application, it is not possible to write a K017 message for a KDCDISP that may be required later, since the page pool on KDCFILE is full.
Action: Increase page pool by increasing MAX PGPOOL=(number,...) in KDCDEF generation.

PEND98

A

(see PEND02)
No further TACB can be written for "System PEND ER" because the page pool on KDCFILE is full.
Action: Increase page pool by increasing MAX PGPOOL=(number,...) in KDCDEF generation.

PENDER

ADU

Dump is not caused by the application being aborted, but by a user-specified PEND ER, or a UTM-internal PEND ER following KCRCCC >= 70Z or 

STXIT

.

PENDT1

F

Another task has terminated the application abnormally (= follow-up dump before KCSBRSE call).

PENDT2

F

(see PENDT1)
Another task has terminated the application abnormally (= follow-up dump before KCSBRSE call).

PENDT3

F

Another task has terminated the application abnormally (= follow-up dump after call by KDCROOT with PEND ER).

PIPE39 **)

AU

Error setting up an instance of a named pipe to the Windows system.
Possible cause: There are two UTM applications of the same name on the system..(on Windows systems only)

PLCA00

SX

XAP-TP component.
Module KCOXFPL, function ActivateCmxCallback().
The CMX function t_callback() returned the return code T_ERROR.

PLCC00

SX

XAP-TP component.
Module KCOXFPL, function CmxCallback().
The system function select() returned an unexpected return code.

PLCC01

S

XAP-TP component.
Module KCOXFPL, function CmxCallback().
The system function select() returned an unknown return code.

PLCD00

SX

XAP-TP component.
Module KCOXFPL, function DeactivateCmxCallback().
The CMX function t_callback() returned the return code T_ERROR.

PMIO20

ASU

Integrity IDs of page inconsistent both in original and also in duplicate file.
Possible cause: KDCFILE files were overwritten during live operation by copying in the start procedure.
Action in this event: Correct start procedure. If this is not the cause, write PR.
The following documentation is required for diagnosis: UTM dump, KDCFILE files, start procedure and task/process log. In the case of cluster applications, the cluster page pool files are also required.

PMIO22

ASU

The page type specified in the cache control table and the page typein the header of the scanned page do not match.
Possible cause: see PMIO20
Action in this case: As for PMIO20

PMIO23

ASU

The page pool page to be read or written is not allocated.
Cause and action: As for PMIO20

POLL03

MX

XAP-TP component.
Module KCOXFPL, function ap_poll().
The return code of the macro mGetBufferSpace() was not equal to LB_OK.

POLL05

SX

XAP-TP component.
Module KCOXFPL, function ap_poll().
The OSS function o_event() reports an ACSE event and the user data were not yet received completely on the o_event() call.

POLL07

SX

XAP-TP component.
Module KCOXFPL, function ap_poll().
The OSS function o_event() returned the return code O_ERROR.

POLL08

SX

XAP-TP component.
Module KCOXFPL, function ap_poll().
The OSS function o_event() returned the return code O_INVEREF.

POLL09

SX

XAP-TP component.
Module KCOXFPL, function ap_poll().
The OSS function o_event() returned the return code O_TIMEINT.

POLL10

SX

XAP-TP component.
Module KCOXFPL, function ap_poll().
The OSS function o_event() returned the return code O_WAKEINT.

POLL11

SX

XAP-TP component.
Module KCOXFPL, function ap_poll().
The OSS function o_event() returned the return code O_SYSTEM.

POLL12

SX

XAP-TP component.
Module KCOXFPL, function ap_poll().
The OSS function ap_poll() returned the return code O_LOOK.

POLL13

SX

XAP-TP component.
Module KCOXFPL, function ap_poll().
The OSS function o_event() returned the return code O_TRANSPORT.

POLL14

SX

XAP-TP component.
Module KCOXFPL, function ap_poll().
The OSS function o_event() returned the return code O_SESSION.

POLL15

SX

XAP-TP component.
Module KCOXFPL, function ap_poll().
The OSS function o_event() returned the return code O_SHUTDOWN.

POLL16

SX

XAP-TP component.
Module KCOXFPL, function ap_poll().
The OSS function o_event() returned an unexpected return code.

PPMM10

ASU

UTM cluster application
Timeout in the lockFile routine during attempt to lock a cluster page pool file.
Action: See CCFG19.

PPMM12

SU

UTM cluster application
Timeout in the unlockFile routine during attempt to unlock a cluster page pool file.
Action: See CCFG19.

PPMM14

SU

UTM cluster application
Bad return code from KCSBFMM in routine readControlPage.

PPMM15

ASU

UTM cluster application
Control page of the cluster page pool has an invalid page header in the readControlPage routine.

PPMM41

SU

UTM cluster application
Error when reading or writing the first CONS page of a cluster page pool file.

PPMM42

SU

UTM cluster application
Bad return code from KCSBFMM when requesting a buffer.

PRIV02 *)

SU

The attempt to set a system privilege failed.

PRIV03 *)

SU

The attempt to reset a system privilege failed.

PUTR01 **)

AU

Not enough bytes could be written in KCSPUTR.
Possible cause: disk storage bottleneck.

PWRT03

AMU

KCSPWRT has requested memory (via KCSALME), but did not get it.
Action: Check memory requirements operating system generation.

PWRT06

F

With KCSPWRT, term application was called during the Periodic Write by another UTM task of the application (= continuation dump).

RALC01

AU

Index is outside the permitted range when KCSRALC is called

RCV009

MX

XAP-TP component.
Module KCOXFRV, function ap_rcv().
The return code of the function CopyElement() was not equal to DM_OK.

RCV012

MX

XAP-TP component.
Module KCOXFRV, function ap_rcv().
Inconsistency in the Boolean variables <bSwitchToNextTtnid> and <bClearTtnid>.

REME01 **)

SU

Illegal system return code on KCSREME call.

RESTRT

D

The dump is only created during a warm start and in the debugging mode. It is used to diagnose any eventual errors in the warm start.

RQOB00

M

XAP-TP component.
Module KCOCOHF, function ReqOssInBuff().
The function RequestBuffer() issued the return code LB_NOMEM.

RTXA01 **)

A

Error using dynamic XA registration in function ax_reg(). The Version of libwork does not match to rootdata version of the utmwork process.
Check registry key "HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\OraClientnnHome1"

RVCS03

M

XAP-TP component.
Module KCOXFRV, function CheckSaRetc().
The return code issued by the function SetAttribute() was SA_NOMEM.

SACT14

MX

XAP-TP component.
Invalid return code after calling PutElement() to request a dynamic memory area for the SACF action COPY.

SACT27

M

XAP-TP component.
Invalid return code after calling PutElement() to perform save in SACF action FLUSHALL or FLUSHPAR.

SACT28

M

XAP-TP component.
Invalid return code after call of ReAllocElement() or PutElement() in SACF action QUEUE.
Action: Increase the value of the KDCDEF parameter MAX OSI-SCRATCHAREA.

SAT002 *)

S

Internal SAT error.

SAT003 *)

A

Subsystem SATCP not available.
Please inform the BS2000 security officer.

SAT004 *)

A

SAT function not currently executable.
Please inform the BS2000 security officer.

SAT005 *)

A

SAT record not written.
Please inform the BS2000 security officer.

SC0005

SU

The half session is generated as PLU. An RU request arrived but the request code is not SDT, STSN or CLEAR.

SC0006

SU

The half session is generated as PLU. An RU response arrived but the request code is not RQR.

SC0007

SU

#FSM.SESS is not in "ACTIVE" status.

SC0008

SU

The half session is generated as SLU. An RU request arrived but the request code is not RQR.

SC0009

SU

The half session is generated as SLU. An RU response but the request code is not SDT,STSN or CLEAR.

SC0010

SU

Protocol error for at least one of the FSMs #FSM_DT, #FSM_STSN or #FSM_RQR.

SC0011

SU

Sense code is set by at least one of the FSMs #FSM_DT or #FSM_CNTL_IMMED_EXP.

SC0014

SU

FSM_SESS_LU_LU returned an invalid return code.

SC0019

ADU

Protocol error reported by FSM.
Action: Check whether both partners are generated as DTP partners in the KDCDEF generation.

SC0020

ADU

The status of the PLU-FSM is not permitted.
Action: Check whether both partners are generated as DTP partners in the KDCDEF generation.

SC0021

ADU

The status of the SLU-FSM is not permitted.
Action: Check whether both partners are generated as DTP partners in the KDCDEF generation.

SC0023

DSU

When checking UNBIND-RSP for FSM_SESS_LU_LU an error has been found

SC0024

DSU

When switching UNBIND-RSP for FSM_SESS_LU_LU an error has occurred

SC0025

DSU

When checking UNBIND Request for FSM_SESS_LU_LU an error has been found

SC0026

DSU

When switching UNBIND Request for FSM_SESS_LU_LU an error has occurred (diagnostic dump)

SC0027

DSU

FSM_STSN_SEND returns S,RQ,STSN

SC0028

DSU

Unauthorized STSN-REQ for PLU_TO_SLU

SC0029

DSU

Unauthorized STSN-REQ for SLU_TO_PLU

SC0030

DSU

ACT_SC_RECEIVE could not set any return code

SC0032

A

The session cannot be activated since there are no connections available.
Action: Change KDCDEF generation, include more CON statements.

SC0034

DSU

The partner has made a protocol error on setting STSN response

SDCS02

M

XAP-TP component.
Module KCOXFSD, function CheckSaRetc().
The SetAttribute() return code was SA_NOMEM.

SDUI01

M

XAP-TP component.
Module KCOXFSD, function UserDataIn().
The macro mGetBufferSpace() issued the return code LB_NOMEM.

SEND05

SU

Severe BCAM error when processing a BCAM SENDLET calls. Error when cancelling a timer for output terminals.

SENDT1

F

Another task has terminated the application abnormally (= follow-up dump).

SG-nnn

D

Diagnostic dump generated on the basis of a KCRSIGN1/2 return code after a SIGN ON call. The prefix SG- is followed by the return code (e.g. SG-U17).
Activation and deactivation via the message dump function.

SHCxxx **)

SU

Error number xxx when calling shmctl() in KCSSHMF.

SHM002 **)

A

An attempt was made to generate a shared memory area that already exists.
Action: Check UTM generation.

SIGxxx **)

AU

Signal with signal number xxx has occurred.
Note: If the application terminates with SIG010/SIG011 (SIGBUS/SIGSEGV), the reason may be incorrect or missing parameters with KDCS call.
Whether this is case can be ascertained by way of the Stack Traces in the gcore dump or Automatic Storages in the UTM dump. In this situation the function KCSAVAL may be found on the stack.

SIGND1 *)

DU

The call of the Kerberos interface returned an unexpected return code. Only if test mode is active.

SIGND2 *)

DU

(see SIGND1)
The call of the Kerberos interface returned an unexpected return code. Only if test mode is active.

SIGND3 *)

DU

(see SIGND1)
The call of the Kerberos interface returned an unexpected return code. Only if test mode is active.

SIGND4 *)

DU

(see SIGND1)
The call of the Kerberos interface returned an unexpected return code. Only if test mode is active.

SLOG05

SU

KCSLKLC returned a bad return code when attempting to lock the message buffers (possibly TIMEOUT).

SLOG06

SU

KCSLKLC returned a bad return code when attempting to unlock the message buffers.

SLOG07

SU

KCSLKLC returned a bad return code when attempting to lock the SYSLOG file (possibly TIMEOUT).

SLOG08

SU

KCSLKLC returned a bad return code when attempting to unlock the SYSLOG file.

SLOG09

SU

Attempt to write message buffer to current SYSLOG file failed (the DMS error code in the preceding K043 message may provide information about the cause of the error).

SLOG10

SU

The attempt by a follow-up task to switch to the current SYSLOG file generation failed (please refer to any preceding K043 message).

SLOG21

ASU

In the administration call KDCSLOG INFO or in the call to the program interface for administration with the opcode KC_SYSLOG and the subopcode1 KC_INFO, KCSSLOG called the component KCSFST in order to determine the attributes of the file generation group of the SYSLOG (only when the SYSLOG is created as a FGG).KCSFST gave a DMS error (also take note of preceding K043 message).

SLOT07

AM

The address of a slot must be calculated in KCSSLOT. The task does not yet know the shared memory that contains the slot. The attempt to link up with Memory Pool failed due to insufficient address space.
Action: Check memory requirements and ADDRESS-SPACE-LIMIT of the BS2000 userid.

SM2001 *)

SU

Call of KCSSM2 with incorrect opcode.

SM2002 *)

SU

Call of KCSSM2 with opcode SM2_CONNECT when KAA.STATE.SM2 = SM2_OFF

SM2003 *)

SU

Call of KCSSM with write data opcode, but KAA.SM2.RECORD_ADDR = NULL.

SM2004 *)

SU

Incorrect parameters with DSSM call CONNECT_SS.

SM2005 *)

SU

Incorrect parameters with DSSM call DISCONNECT_SS

SM2006 *)

SU

DSSM call CONNECT_SS, but task is already connected.

SM2007 *)

SU

Call of KCSSM2 when KAA.STATE.SM2 = SM2_N

SMSG00

AUD

SMSG00 is a diagnostic dump and does not lead to the end of the application run; a SMSG00 dump is only taken when test mode is activated.
An SMSG dump is created if KCSSMSG wants to send a message to a message destination of the type MSG-DEST and receives a bad return code from KCSFPUT.
The return code can be taken from the NKB table of the UTM dump; the CC and DC codes of the DPUT call are at distance X'5C' in this table.
One possible reason is that the queue/TAC is locked.

SMSG03

ASU

The component KCSSLOG supplied a bad return code on writing a message to the SYSLOG.
Cause: See DMS return code in K043 message

SMSG09

D

SMSG09 is a diagnostic dump and does not cause the application run to terminate; an SMSG09 dump is only created if test mode is enabled.

SND005

M

XAP-TP component.
Module KCOXFSD, function ap_snd().
The UserDataIn() function returned the UDIN_NOMEM return code.

SND007

MX

XAP-TP component.
Module KCOXFSD, function ap_snd().
The return code of the function GetVarLthAttr() was not equal to GA_OK.

SSO002 *)

DSU

Diagnostic dump; created after a serious error when the SRPMSSO subsystem is called.

STnnnn

ADSU

Error when processing the start of a UTM task, where nnnn is the number indicating the error cause in the UTM message "K049 Error <nnnn> during application startup".

STPF10

SX

XAP-TP component.
Invalid indicator for HeurRep parameter in TP-HEUR-REP-RI.

STPF11

SX

XAP-TP component.
Invalid indicator for FuUnits parameter in TP-BEG-DIAL(dialogue)-RC.

STPF12

SX

XAP-TP component.
Invalid indicator for Result parameter in TP-BEG-DIAL(dialogue)-RC.

STPF13

SX

XAP-TP component.
Invalid indicator for Diagnostic parameter in TP-BEG-DIAL(dialogue)-RC.

STPF14

SX

XAP-TP component.
Invalid indicator for user data parameter in TP-BEG-DIAL(dialogue)-RC.

STPF15

SX

XAP-TP component.
Invalid indicator for Result parameter in TP-BEG-DIAL(channel)-RC.

STPF16

SX

XAP-TP component.
Invalid indicator for Diagnostic parameter in TP-BEG-DIAL(channel)-RC.

STPF17

SX

XAP-TP component.
Invalid indicator for HeurRep parameter in TP-(ABORT-AND-)HEUR-REP-RI.

STPT02

SX

XAP-TP component.
Invalid value for p_udt.p_udtnxt.

STPT10

SX

XAP-TP component.
Invalid indicator for InitTPSUT parameter in TP-BEG-DIAL(dialogue)-RI.

STPT11

SX

XAP-TP component.
Invalid indicator for RecTPSUT parameter in TP-BEG-DIAL(dialogue)-RI.

STPT12

SX

XAP-TP component.
Invalid indicator for FuUnits parameter in TP-BEG-DIAL(dialogue)-RI.

STPT13

SX

XAP-TP component.
Invalid indicator for BegTrans parameter in TP-BEG-DIAL(dialogue)-RI.

STPT14

SX

XAP-TP component.
Invalid indicator for Conf parameter in TP-BEG-DIAL(dialogue)-RI.

STPT15

SX

XAP-TP component.
Invalid indicator for LastPartId parameter in TP-BEG-DIAL(dialogue)-RI.

STPT16

SX

XAP-TP component.
Invalid indicator for user data parameter in TP-BEG-DIAL(dialogue)-RI.

STPT17

SX

XAP-TP component.
Invalid indicator for FuUnits parameter in TP-BEG-DIAL(channel)-RI.

STPT18

SX

XAP-TP component.
Invalid ChanUtil parameter in TP-BEG-DIAL(channel)-RI.

STPT19

SX

XAP-TP component.
Invalid indicator for LastPartId parameter in TP-BEG-DIAL(channel)-RI.

STPT20

SX

XAP-TP component.
Invalid indicator for CcrTokReq parameter in TP-BID-RI.

STPT21

SX

XAP-TP component.
Invalid indicator for LastPartId parameter in TP-BID-RI.

STPT22

SX

XAP-TP component.
Invalid indicator for Result parameter in TP-BID-RC.

STPT23

SX

XAP-TP component.
Invalid indicator for Conf parameter in TP-END-DIAL-RI.

STPT24

SX

XAP-TP component.
Invalid indicator for ConfUrg parameter in TP-HSK-RI.

STPT25

SX

XAP-TP component.
Invalid indicator for ConfUrg parameter in TP-HSK-AND-GRT-CTRL-RI.

STPT26

SX

XAP-TP component.
Invalid indicator for Type parameter in TP-DEFER-RI.

STPT27

SX

XAP-TP component.
Invalid indicator for Reason parameter in TP-TOKEN-GIVE-RI.

STPT28

SX

XAP-TP component.
Invalid indicator for Correlator parameter in TP-TOKEN-GIVE-RI.

STRT01

DU

When changing the application program the number of processes which still are to be changed is less than zero, i.e. the counter is inconsistent. The application is terminated abnormally if debug mode is activated, otherwise a diagnostic dump is written.

SYPM01

AU

Task-specific buffer for restart information is too small.
Action: Enlarge MAX RECBUF=(...,length) in KDCDEF generation.

SYPM03

AS

Serious error in communication with DB system (FITA).

SYPM11

AU

Task-specific buffer for restart information is too small.
Action: Enlarge MAX RECBUF=(...,length) in KDCDEF generation.

TADR03

SU

The so-called Application Reference in the announcement is invalid.

TC0040

DSU

The input message length supplied by the transport system does not match the length contained in the message.

TC0041

DSU

The input message length supplied by the transport system is shorter than the value in the Data Count Field (DCF) in the Transmission Header (TH).

TCPI13 *)

SU

Invalid length of the IP address (TCP_GET_HOST_BY_ADDR).

TCPI14 *)

SU

Invalid length of the IP address (TCP_CONNECTION_REQUEST).

TIEV19

DS

Inconsistence between the announced length and the actual length of data.

TIMR02

SU

Error on $NCANTI.

TIMR03

SU

Error on $NCHNGTI.

TIMR05 **)

AU

utmtimer process not present when sending to IUTMIPC in KCSTIMR

TINF01 *)

SU

Error when reading the task priority

TINF02 *)

SU

Error when setting the task priority

UATC02 **)

SU

(see UKAA02)
Unlock failed.

UATC03 **)

SU

(see UKAA03)
Maximum number of locks per task exceeded.

UCAC02 **)

SU

(see UKAA02)
Unlock failed.

UCAC03 **)

SU

(see UKAA03)
Maximum number of locks per task exceeded.

UKAA02 **)

SU

Unlock failed.

UKAA03 **)

SU

Maximum number of locks per task exceeded.

UMDT12

SU

KCCUMDT opcode UMDT_LOCK_ULS
Bad return code from KCSBFMM when reading a ULS administration file.

UMDT13

SU

KCCUMDT opcode UMDT_LOCK_ULS
Bad return code from KCCLKMT.

UMDT15

ASU

UTM cluster application
KCCUMDT opcode UMDT_UNLOCK_ULS:
Error on locking the ULS file.
Action: See section "Actions when locking UTM cluster files".

UMDT32

SU

UTM cluster application
KCCUMDT function readHdrPage
Bad return code from KCSBFMM when requesting a buffer.

UMDT33

ASU

UTM cluster application
KCCUMDT releaseFileLock function:
Timeout while unlocking the cluster ULS file.
Action: See UMDT15.

UMDT34

SU

UTM cluster application
KCCUMDT releaseFileLock function:
Incorrect return code from KCCGFLK when unlocking the cluster ULS file.
Action: See UMDT15.

UMDT42

SU

UTM cluster application
KCCUMDT function addrUlsEntry
Bad return code from KCSBFMM when requesting a buffer.

UMDT44

SU

UTM cluster application
KCCUMDT setFileLock function:
Incorrect return code from KCCGFLK when locking the cluster ULS file.
Action: See UMDT15.

UMDT52

ASU

UTM cluster application
KCCUMDT allocateUlsEntry function:
Incorrect return code from KCCUSF when locking the cluster user file.
Action: See UMDT15.

UMDT63

ASU

UTM cluster application
CUMDT entry KCCUGLI:
The cluster ULS file cannot be locked.
Action: See UMDT15.

UMDT73

SU

UTM cluster application
KCCUMDT function checkFile
Bad return code from KCSBFMM when requesting a buffer.

UMDT74

SU

UTM cluster application
KCCUMDT function checkFile
Bad return code from KCSBFMM when requesting a buffer.

UMDT77

SU

UTM cluster application
KCCUMDT function checkFile
Bad return code from KCSBFMM when requesting a buffer.

UMES02 *)

DSU

System error. For meaning see message K146.

UPCM02 **)

SU

(see UKAA02)
Unlock failed.

UPCM03 **)

SU

(see UKAA03)
Maximum number of locks per task exceeded.

USF002

ASU

UTM cluster application.
Module KCCUSF, opcode OPEN_FILE.
Timeout when initializing global file lock.
Action: Increase the value of the FILE-LOCK-TIMER-SEC or FILE-LOCKRETRY parameter in the CLUSTER statement of the KDCDEF generation.

USF003

SU

UTM cluster application
Module KCCUSF, opcode OPEN_FILE.
Invalid return code when initializing the global file lock.

USF009

ASU

UTM cluster application.
Module KCCUSF, opcode CUSF_RESET_PTC_FLAG.
Five timeouts on locking the cluster user file.
Action: See USF002.

USF013

ASU

UTM cluster application.
Module KCCUSF, opcode CUSF_SIGNOFF_USER_WITH_CONTEXT.
Five timeouts on locking the cluster user file.
Action: See USF002.

USF018

ASU

UTM cluster application.
Module KCCUSF, opcode CLOSE_FILE.
Timeout when destroying file lock.
Action: See USF002.

USF019

SU

UTM cluster application
Module KCCUSF, opcode CLOSE_FILE.
Invalid return code from KCCGFLK when destroying the file lock.

USF021

SU

UTM cluster application
Module KCCUSF, function setFileLock
Invalid return code from KCCGFLK when requesting the exclusive lock.

USF023

ASU

UTM cluster application.
Module KCCUSF, function releaseFileLock.
Timeout when releasing file lock.
Action: See USF002.

USF024

SU

UTM cluster application
Module KCCUSF, function releaseFileLock
Invalid return code from KCCGFLK when releasing the file lock.

USF025

ASU

UTM cluster application.
Module KCCUSF, function readPage.
Timeout when requesting shareable file lock.
Action: See USF002.

USF026

SU

UTM cluster application
Module KCCUSF, function readPage
Invalid return code from KCCGFLK when requesting the shareable file lock.

USF027

ASU

UTM cluster application.
Module KCCUSF, function readPage.
Timeout when releasing file lock.
Action: See USF002.

USF028

SU

UTM cluster application
Module KCCUSF, function readPage.
Invalid return code from KCCGFLK when releasing the file lock.

USF051

SU

UTM cluster application
Module KCCUSF, function writePage
Error when writing the cluster user file.

USF052

SU

UTM cluster application
Module KCCUSF, function readPage.
Error when reading the cluster user file.

VTSUER *)

ADS

VTSU-B reports an error connected with the applied character set or the encryption. The application is not aborted.
The Dump serves the diagnosis of the error reported by VTSU-B. The Dump contains only KDCROOT and KTA data.

WAI102

DU

Diagnostic Dump

WAI112 *)

DU

When switching the system protocol file the number of processes which still are to be switched is less than zero, i.e. the counter is inconsistent.
The application is terminated abnormally if test mode is activated, otherwise a diagnostic dump is written.

WAI113

DU

When changing the application program the number of processes which still are to be changed is less than zero, i.e. the counter is inconsistent.
The application is terminated abnormally if test mode is activated, otherwise a diagnostic dump is written.

WAI114

DU

see WAI113

WAI120

DU

When administering the diagnostic trace settings the number of processes which still have to update the settings is less than zero, i.e. the counter is inconsistent.
The application is terminated abnormally if debug mode is activated, otherwise a diagnostic dump is written.

WAIT01

SU

Bad return code when calling KCSBRSE for the work bourse in action block ENQUEUE_WORKBOURSE of KCSWAIT.

WAIT02

DS

Invalid timer announcement type (action block ENQUEUE_WORKBOURSE).

WAIT03

DS

Invalid type in announcement and no timer announcement (action block ENQUEUE_WORKBOURSE).

WAIT55

SU

Invalid code for an internal timer announcement (action block ANALYSE_INTERNAL_TIMER).

WAIT78

ASU

Severe error when calling the BCAM socket functionality.

WAITT1

F

Another task has terminated the application abnormally (= follow-up dump before calling KCSBRSE).

WAITT2

F

Another task has terminated the application abnormally (= follow-up dump after calling KCSBRSE).

XATT02

F

XAP-TP component.
Module KCOXFEX, function apext_att().
The function bCheckAndSetState() issued a bad return code and the application status was WAITING_DUMP_APPL. A different task had already caused the application to abort.

XATT04

MX

XAP-TP component.
Module KCOXFEX, function apext_att().
The return code of the function EstablishBuffer() was not equal to LB_OK.

XATT12

MX

XAP-TP component.
Module KCOXFEX, function apext_att().
The return code of the function EstablishBuffer() was not equal to LB_OK.

XATT13

MX

XAP-TP component.
Module KCOXFEX, function apext_att().
The return code of the function RequestBuffer() was not equal to LB_OK.

XFGA07

SUX

XAP-TP component.
Module KCOXFHF, function GetAttribute().
The function AllocUserMem() returned an unexpected return code when reading the attribute AP_DTNID in the single task mode.

XFGA11

M

XAP-TP component.
Module KCOXFHF, function GetAttribute().
The macro mGetBufferSpace() issued the return code LB_NOMEM.

XFGE01

F

XAP-TP component.
Module KCOXFHF, function bCheckAndGetCallEnv().
The function bCheckAndSetState() issued a bad return code and the application status was WAITING_DUMP_APPL. A different task had already caused the application to abort.

XFSA07

MX

XAP-TP component.
Module KCOXFHF, function SetAttribute().
The function PutElement() issued a return code other than DM_OK when setting the AP_DTNID attribute.

XFTM01

SX

XAP-TP component.
Module KCOXFHF, function TraceMgmt().
The OSS function o_tron() returned the return code O_ERROR.

XFTM02

SX

XAP-TP component.
Module KCOXFHF, function TraceMgmt().
The OSS function o_tron() returned the return code O_INVEREF.

XFTM03

SX

XAP-TP component.
Module KCOXFHF, function TraceMgmt().
The OSS function o_tron() returned an unknown return code.

XFTM04

SX

XAP-TP component.
Module KCOXFHF, function TraceMgmt().
The OSS function o_troff() returned the return code O_ERROR.

XFTM05

SX

XAP-TP component.
Module KCOXFHF, function TraceMgmt().
The OSS function o_troff() returned an unknown return code.

XINI06

ASX

XAP-TP component.
Module KCOXFEX, function apext_init().
The OSS function o_create() returned the return code O_ERROR.
Possible causes:

  • If the in insert XPFUNC has the value o_create() and the insert XPRET the value -1in the corresponding UTM message P001, then the error may be that the OSS subsystem has not been started.
  • A further OSI TP application was started in the dialog in the same task. However, OSS is still reserving resources of a previously terminated application and this is the reason for termination.
    Occurs in particular if the application has previously been started in two tasks in the dialog and then terminated again.
    Remedy: The resources are freed after a LOGOFF BUT.

XINI07

SX

XAP-TP component.
Module KCOXFEX, function apext_init().
The OSS function o_create() returned an unknown return code.

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


Actions when locking UTM cluster files

The following workaround is recommended for all errors that occur when requesting or releasing locks for UTM cluster files.

>

In the CLUSTER statement of the KDCDEF generation, increase the value of the FILE-LOCK-TIMER-SEC parameter or FILE-LOCK-RETRY parameter.

Powered by Atlassian Confluence and Scroll Viewport.