Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

Messages K071 - K101

K071

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

The inserts have the following meanings:

&DBCON

Name of the connection module to the DB system

&OPCD1

DB operation code, see section "DB Diagarea"

&ERCD3

KCRCDC error code with the possible values KU04 through KU24, see section "Internal return code KCRCDC"

&DBTRAC

DB trace information. The possible values and their meanings are described in the discussion of the relevant database system.
For UDS-DB system: Interpretation of DB trace information, see description of return codes in the manual “UDS/SQL Messages”.
For the SESAM-DB system: see the manual "SESAM/SQL Database Operation", section "Diagnostic information in the DB Diagarea of openUTM" in the chapter "Error recovery"

If the DB system is connected via the XA interface then the 4 DB trace information bytes have the following meanings:

Byte 1

Resource Manager index (cf sequence in the start parameters)

Bytes 2 and 3

Operation code of XA call, output hexadecimal and platform-dependent (EBCDIC or ASCII), e.g. in the BS2000 system: (EBCDIC) X'9697' = C'op'
op = xa_open, en = xa_end etc.

Byte 4

Return code of XA call, output hexadecimal and platform-dependent e.g. in the BS2000 system: FD = -3 = XAER_RMERR

K072

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

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

Response: regenerate ROOT and/or KDCFILE

K073

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

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

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

Response: regenerate ROOT and/or KDCFILE

K074

Program exchange completed; &CTYP &PROG &PVER

(see K075)

K075

Program exchange aborted by task &TASK; &CTYP &PROG &PVER

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

&TASK:

TSN of the task for which program exchange was aborted.

&CTYP:

APPL, Exchange of the entire application program
LMOD, Exchange of a load module

&PROG:

Name of the load module (only when CTYP=LMOD)

&PVER:

Version number of the load module (only when CTYP=LMOD)

K076

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

K077

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

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

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

&CLSIGT

Meaning

1

Check the availability of the monitored node application (check alive request).

2

Check for changes in the cluster configuration

4

Administration job

8

Job to wake up one of the tasks waiting at a GSSB or ULS

16

Response to an availability query from the monitoring node application (check alive response)

No action is required.

K078&ERRNAME &ERRCODE: in &REA3


Message K078 is output by UTM in several different variants, depending on the event that has occurred. The events can be subdivided into the following categories:


IlCS messages

K078

WRONG SPL-VERSION (NO ILCS)

This means that an incorrect SPL version has been linked in (<= V1.5): SPL does not establish ILCS-compliant stacks.

Response: Link the program again with SPL version >= 2.0

K078

subcode: ERROR HANDLING IN module, RC = return code

This means that an internal error occurred when managing the ILCS stacks or on calling ILCS-internal functions. The return code is also output if ILCS functions are called.
The subcode allows you to identify the phase in which the error occurred:

subcode = IL01 - IL09: Error during initialization

subcode = IL20 - IL29: Error during start/end of TP

subcode = IL30 - IL39: Error during stack management

The following table describes the errors for which subcode describes a user error. In all other cases, you must write a problem report (PR) and contact systems support.

subcode

Modul

Return
code
output?

Precise meaning of &ERCD2

IL02

IT0INIT

yes

Error initializing ILCS.
User error if ILCS code is executed before UTM start code.
Response: set the ENTRY-POINT of the application to KDCRTST.

IL08

KDCCILCI

no

An incorrect ILCS version was linked in. Version 1.5 or higher is required.

K078

xxxx : UNRECOVERABLE ILCS ERROR OCCURRED - ILCS FUNCTION WITHIN NON-ILCS PROGRAM UNIT.

xxxx = SEUB/SELB/ASID/AHID

Meaning:

This message is output on termination of a program unit run. In a program unit with COMP=ASSEMB/COB1, an ILCS object (source module) was compiled by an ILCS-compiler. However, the ILCS object changes one of the fields for which xxxx stands in the central ILCS data area (IT0PCD). openUTM can therefore no longer base itself on this data, and the application program is terminated.

Action:

You must either create an ILCS-capable program unit from your ASSEMB/COB1 program unit or adapt the ILCS-capable object so that it does not use the ILCS.


Message on establishing connection to the DB system

K078

Invalid DBCON-Adress in KDCRTDB:
KDCRTDB: application running in lower adress-space!Term in Start

While reloading the DBCON module, it is detected that the DBCON module was loaded in the upper address space, the application, however, is running in the lower address space.

K078
K078
K078

KDCRTDB ERROR : in SESAM : INSTALLATION-UNIT / VERSION = db-system / version
GETINSP 00400013: in KDCRTDB: error accessing pathname for logical-id yyyyyy
DCRTDB ERROR : in KDCRTDB - START OF APPLICATION WILL BE TERMINATED!

Error during dynamic loading of the DB connection module if the connection module was dynamically loaded with LIB=LOGICAL-ID (yyyyyy) via the IMON installation path. The specified name yyyyyy is incorrect.

K078

Variant of the message K078 for the verification of the Oracle interface that is linked to the application program:

"K078 *BIND -- MISMATCH -- : in KDCRTDB:
      old ORACLE IUTMDB interface linked in XA environment"
"K078 *BIND -- MISMATCH -- : in KDCRTDB:
      start of application will be terminated."

Meaning:
When a UTM Oracle XA application is started, a check is performed to determine whether the old IUTMDB interface has been linked by mistake. This check found the (old) ORADBCON connection module for the IUTMDB interface in the application program. openUTM terminates application start.

Action:
The application program must be linked again, see also Oracle® Database User's Guide (BS2000/OSD).

K078
K078
K078

*BIND 0C010600: in KDCRTDB ENTRYNAME = entryname
*BIND ERROR---: in KDCRTDB: LOAD-LIBRARY = : library-name
*BIND ERROR---: in KDCRTDB - START OF APPLICATION WILL BE TERMINATED!

Error during dynamic loading of the DB connection module if the connection module was dynamically loaded with LIB=LOGICAL-ID (SYSLNK) via the IMON installation path. The dynamically loadable module is not present in the library found via LOGICAL-ID(SYSLNK).

K078

RTIMER event A0 : in KDCRTDI - event in KDCRTDB while connecting to database

The establishment of the connection to the database system is aborted during UTM application start due to timer expiry (real-time). The task is then terminated.

The message is only output if the start parameter DB-CONNECT-TIME is set (minimum = 60 sec., maximum = 3600 sec.). In DB-CONNECT-TIME, you specify the timer which monitors the establishment of the connection to the DB system during the start phase of a UTM application.


Messages when loading or exchanging programs

K078

xxxxxxxx yyyyyyyy: IN module-name text

This message is output when dynamically loading or exchanging individual load modules.

Meaning of the inserts:

xxxxxxxxcontains a short ID of the error which occurred (see table "Values for xxxxxxxx" ). For errors with xxxxxxxx = (KDCS00,LDRTnn) the field yyyyyyyy is not output.
yyyyyyyycontains the return code of the BS2000 macro called. For further information, refer to the BS2000 manual “Executive Macros”. This insert does not apply in the case of internal UTM error codes.
module-name

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

contains additional information on certain errors; possible texts:

’ WRONG OPCODE IN KDCRTLD: WRONG OPCODE AT CALL OF KDCRTLD ’

’ LMOD: STAT ERR IN KDCRTLD: LMOD: <name> / <version> ’

These texts refer to internal errors in UTM.

’ LINK ERR OF AREAS in KDCRTLD: FOR AREA: <areaname> ’

In this case the specified area has not been linked in by the user (check UTM generation and load module creation).

Action: Link application program correctly.


xxxxxxxxx

Error cause

Action

ASHARE

Error when loading a load module into a memory pool. Further information is given by the insert ' LMOD: name / version '

See return code

BIND

  • Error when loading a load module. Further information is given by the insert ' LMOD: name / version ' or

  • Error when loading the linkage module to the DB system ( see insert ' ENTRYNAME = ' )

  • Error when dynamically loading the root table module (see inserts &object and &lib)

  • Error when dynamically loading the userspecific message module (see inserts &object and &lib)

See return code.

CSTAT

The status of an MP page cannot be changed to ' read only'. For further information see supplementary insert 'PAGENUMBER = '.

System error

DEQAR

Error when releasing a serialization ID.

See return code (pool name possibly locked; change UTM generation)

DMS

Error when interoperating with the DMS. For further information see supplementary insert 'FILENAME = ' .

See DMS error code

ENAMP

Error when creating a memory pool. SCOPE and NAME of the relevant memory pool are also specified.

See return code, e.g. pool name already in use by another task; change UTM generation

ENQAR

Error when accessing serialization ID.

See return code (e.g. DEQAR), change UTM generation where necessary and increase the value of MAX MP-WAIT.

ITABL

Error when determining addresses of shareable programs. May be caused by unresolved EXTRNS. For more information see supplementary insert ' ENTRYNAME = ' .

System error

JOINFOA

Error when querying the user entry.

See return code

KDCALME

Not possible to provide sufficient memory on request for KL6 memory (INSUFFICIENT MEMORY and number of bytes output).

An attempt may have been made to start the application in the lower address space (insufficient memory!).

KDCS00

CALL "KDCS" in START exit, in SHUT exit or in INPUT exit

Correct program unit.

LDRT00

TABLIB start parameter missing but no ROOT module linked

Adapt start parameter or definitively link ROOT

LDRT01

The version of the UTM macro library does not match that of the UTM modules or the message module.

Regenerate ROOT, link to current library SYSLNK.UTM.nnn or regenerate message module.

LDRT08

The parameter CATID was used even though the filebase operand was specified with catid.

Change start procedure

LDRT12

The root table module is to be dynamically loaded, but no load module has been generated.

Generate the application with at least one LOAD-MODULE.

LINK

Error when loading with LINK macro For further information see supplementary insert ' ENTRYNAME = ' .

Check UTM generation

MINF

The memory allocation table is not available.

System error

RELM

Error when releasing class 6 memory For further information see supplementary insert ' PAGENUMBER = '

System error

REQM

Error when allocating a memory pool.

System error

REQMP

Error when requesting class 6 memory.

Error code X'0C' can signify overlapping with a memory pool allocated by DSSM and defined with SCOPE=GLOBAL

Check BS2000 generation, possibly reduce UTM application
Release area with command:
/SET-SUBSYSTEM-OPTIONS SUBSYSTEM-NAME=NON-PRIVILEGED

SETIC

The interval timer could not be set.

System error

STXIT

Execution of the STXIT call failed.

System error

TMODE

Error when querying task characteristics.

System error

UNBIND

Error when unloading a load module

For further information see supplementary insert ' LMOD: name / version '

See return code

VSVI

Error in VSVI macro

See return code

VSVI1

Error when determining program addresses.
For further information see insert ' FOR PROGRAM: name'

See return code

$APCB

Error when transferring the TU-PC to UTM-TPR, possible return codes:

See return code

02: $APCB is not supported in this BS2000 version

UTM error

otherwise: see macro return code

See return code



STXIT messages

K078

K078

STXIT 01 STXIT(ILCS_STXIT_CONTROL) started at xxxxxxxx with IW=yyyyyyyy

STXIT 02 STXIT(STANDARD) started at xxxxxxxx with IW=yyyyyyyy

The messages "STXIT 01" and "STXIT 02" are output by UTM when the UTM STXIT routines start, and they record that an STXIT event has occurred.

STXIT 01

The STXIT routine was started for ILCS.

STXIT 02

The standard STXIT routine was started.

The insert xxxxxxxx contains the address of the STXIT routine, the insert yyyyyyyy contains the interrupt weight.

Example:
K078 STXIT 01 STXIT (ILCS_STXIT_CONTROL) started at 010A70FC with IW=00000064

An STXIT event generally causes the UTM service to abort.

STXIT events can occur that do not lead to the abortion of the service. This is the case when an STXIT event occurs, is passed to the ILCS runtime environment and handled there either by ILCS itself or a program unit, and the event is then not passed on to UTM.

If an STXIT event occurs due to the expiry of a timer (e.g. IW=A0), it is possible that the STXIT message is output without any STXIT routine being started since the program unit has already been terminated in the interim. You may therefore need to increase the timer value for this transaction code. The TAC can be taken from the K099 message which is subsequently output:

K099 STXIT occurred in TAC: tacname at date: xx-xx-xx time: xx:xx:xx

The date and time in the K099 message refer to the start of the program unit.

The event IW=90 (TERM) can occur when one of the application’s tasks terminates.

Action:

If the service aborts, analyze the dump created. If there is an error in UTM, store the documents and write a PR; otherwise, correct the error in the program unit.

If the service does not abort, the message merely indicates that the interruption is being handled by the runtime system or the program unit. There is no error.


Message (warning) on processing of start parameters

K078

WARNING : in KDCRTBF! Syntax-error in SYSPROT-Parameter!
Default value used!

K078

WARNING : in KDCRTBF! SYSPROT-Parameter: prefix too long!
Default value used!

In both cases an incorrect SYSPROT start parameter was detected and the default value is effective. You may need to improve the SYSPROT start parameter!

K079

Accounting problem - reason: &REA2
When attempting to write accounting information, the BS2000 accounting routine reports an error. openUTM thus deactivates the accounting for the application. The application continues to run.

The error cause is given in the insert &REA2:

&REA2

Meaning

04

BS2000 accounting is not active

08

in the BS2000 accounting the corresponding record type is not active (record
type UTMA or UTMK)

20

Error in BS2000 accounting: Slot shortage

28

Error in BS2000 accounting write task


If &REA2=X‘08‘, openUTM deactivates the accounting phase, the calculation phase or both, depending on the record type.
In all other cases, openUTM deactivates both phases.

Action: Inform BS2000 system administrator.

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

K080

KDCMON is not active.

Possible error reasons:

  • The KDCMON sub system is not started

  • The KDCMON event monitor is not started or has been terminated in the meantime

For details, please refer to the openUTM manual “Using UTM Applications on BS2000 Systems”, section „Starting KDCMON“.

K081

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

Inserts

Meaning

&IMSG1

Number of terminal input messages 1)

&OMSG1

Number of terminal output messages 1)

&CONU

Number of connected users

&ATAC2

Number of unprocessed ATACs 1)

&LWRT

Number of log writes

&HITR

Cache hit rate 1)

&WTBF

Cache waits for buffer

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

K082

Wrong file &FNAM

K083File &FNAM has been destroyed.

K084

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

K085

&FNKT functions are not available.

K086

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

Inserts

Meaning

&PTRM

Name of LU6.1 connection (CON)

&PRNM

Processor name

&BCAP

BCAM application name

&LTRM

Name of LPAP parameter

&USER

User ID

&SYSD

SNA sense code (system)

&USSD

SNA sense code (user)

&FMH7

Error message from the remote application

&AGUS

ID of job-submitting user

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

&SYSD&USSD

Meaning

08120000

Resource bottleneck (e.g. page pool full)

08130000
081B0000

Contention: A request to occupy a session was rejected by the contention loser application because the contention winner application had already occupied the session for a job.

08641003

Invalid or locked TAC

0864C5E2

PEND ER from UTM

0864C5D9

PEND ER from the application program unit

0864D9E2

PEND RS from UTM

0864D9E4

PEND RS from the application program unit

0866D9E2

PEND RS from UTM

0866D9E4

PEND RS from the application program unit

10030000

Invalid or locked TAC

K087

Error in interoperation of UTM and format handling system: opcode = &OPCD3, error code = &ERCD4 &ERCD5

&OPCD3

Meaning

STPA

Start parameter input

INIT

Initialize the formatting system

INPI

Create and enlarge the PI (Presentation Image)

ISOUT

Incorporate the output message section in the PI (in MPUT)

CRM

Generate output message (in PEND)

ISINP

Incorporate input message in the PI

RDMP

Read input message section from the PI (in MGET)

REST

Restart formatting for the screen restart

USER

User call to the formatting system

CUR

Cursor positioning

CRMA

Generate asynchronous output message


The insert &ERCD4 contains the error code KCRCDC of the form FHxx:

&ERCD4

Meaning

FH01

An error has occurred in the formatting. See supplementary return code from FHSCON or FHS in field KCRMF.

FH02

Hardware function not available.

FH04

Serious error during initialization of the formatting system FHS. openUTM aborts the start of the application.

The insert in &ERCD5 provides additional information on the errors that have occurred. You can find out the meaning of the supplementary information in the formatting system manual.

K088

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

UTM-D session start. The message contains diagnostic information

Inserts

Meaning

&LSES

LSES name

&RSES

RSES name

&LPAP

LPAP name

&SRFG

Status bits from the LSES table entry (SR)

&PSQN

PET sequence numbers
Two 2 byte numbers:

  • sequence number sent saved

  • sequence number sent current

&ESQS

Secured sequence numbers
Two 2-byte numbers:

  • SLU TO PLU

  • PLU TO SLU

&EBSS

Secured bracket state

  • "BETB" = BETween Bracket

  • "INBR" = IN Bracket Receive (local side without send authorization)

  • "INBS" = IN Bracket Send (local side with send authorization)

&ESQR

Current sequence numbers (from STSN request)
Total of 5 bytes:

  • SEC_TO_PRI_SQN (2 bytes)

  • PRI_TO_SEC_SQN (2 bytes)

  • ACTION_CODE_SEC_TO_PRI (2 bits)
    00: ignore
    01: set
    10: test
    11: set and test

  • ACTION_CODE_PRI_TO_SEC (2 bits)
    00: ignore
    01: set
    10: test
    11: set and test

  • RESERVED (4 bits)

&ESRR

Current sequence numbers RSP(STSN)
Total 5 bytes:

  • SEC_TO_PRI_SQN (2 bytes)

  • PRI_TO_SEC_SQN (2 bytes)

  • ACTION_CODE_SEC_TO_PRI (2 Bit)
    00: ignore
    01: set
    10: test
    11: set and test

  • ACTION_CODE_PRI_TO_SEC (2 bits)
    00: ignore
    01: set
    10: test
    11: set and test

  • RESERVED (4 bits)

&EBSR

Current bracket state

  • "BETB" = BETween Bracket

  • "INBR" = IN Bracket Receive (local side without send authorization)

  • "INBS" = IN Bracket Send (local side with send authorization)

K089

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

&CHAIN

Meaning

NO

No negative confirmation job of the deleted message was present.

DEL

The negative confirmation jobs should also be deleted.

ACT

The negative confirmation job should be activated, i.e. inserted in the message chain of its receiver.

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

K090

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

K091

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

This message additionally contains the following insert:

&REA7

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

K092

Please enter password
> &PAS1 <
If you wish to change the password, please enter new password
> &PAS2 <
and repeat new password
> &PAS3 <

K093

Service cannot be stacked.
See also KDCDEF control statement MAX, operand NRCONV. 

K094

Sequence of unsuccessful sign-on attempts

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

The message contains the following inserts:

Inserts

Meaning

&PTRM

Terminal name

&PRNM

Processor name

&BCAP

Application name

&LTRM

Logical terminal name

&USER

User ID

&RCF1B

Reason for the rejection

&REA4

Originator of the rejection (L=LTERM, U=USER, B=BOTH)

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

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

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

K095

Sign-off is effective - please enter <SEND>

K096

Return to interrupted service - please enter <SEND>

K097

Input for new password cannot be used - please sign on

K098

Input exit returned error information &RCF1C &RCF2B - input please

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

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

&RCF1C

Meaning

IN00

INPUT exit call okay from UTM standpoint

IN01

Error in calling up INPUT exit via IUTMHLL

IN02

KDCS call in INPUT exit

IN03

Output parameters do not match KCICCD

IN04

Illegal value in KCICCD

IN05

DB USER CALL in INPUT exit

IN06

Signal in INPUT exit

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

K099

&MSG

This message is output by openUTM when an STXIT event occurs, or as a supplement to message K078, or when the ENTER-PROC-INPUT start parameter is too long. In the first case the insert &MSG contains:

STXIT occurred in TAC: tacname at date: yy-mm-dd time: hh:mm:ss

In the second case the insert &MSG contains additional return codes.

In the third case the insert &MSG contains:

KDCRTBF: maximum length(2000 byte) of ENTER-PROC-INPUT exceeded!

This message is also output as an information message in the case of generated memory pools. In this case, it provides information about the actual allocation of the memory pool by the shared components of the application program loaded in this pool. Two K099 messages are output: The first indicates the relevant memory pool and the second the level of occupancy by generated shared components if this pool is generated with write-protection.

K101

Resource Bottleneck - please repeat last input

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

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

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

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

Powered by Atlassian Confluence and Scroll Viewport.