The incompatible KDCS return code KCRCDC consists of four printable characters and contains more detailed information on the cause of the error than the compatible return code KCRCCC.
The incompatible return code can be set in the following situations:
if the KDCS call returns the compatible return code 40Z
if openUTM terminates a service abnormally with PEND ER (KCRCCC >= 70Z)
if a transaction is implicitly reset by openUTM.
The return code KCRCDC has the following structure:
s###
The first character (s) of KCRCDC specifies which part of openUTM reported the error:
A | Administration |
| H | HTTP functions |
K | UTM system code or ROOT code. |
U | UPIC (server part) |
The following table describes the error causes and, where applicable, the required recovery action. If TESTMODE=OFF, the PEND ER dump is suppressed in cases marked with (1). Dynamic loading is also suppressed. At the same time, loading is suppressed unless PGWT calls are permitted for the current TAC and the KDCS call in which the error occurred was not a PEND call.
Code | Module | Cause of error and action (if any) |
A010 *) | KCSSADM | User is no SAT administrator. |
A011 *) | KCSSADM | TAC has no SAT admission. |
A012 *) | KCSSADM | SAT subsystem is not available. |
A013 *) | KCSSADM | SAT version is not compatible. |
A015 *) | KCSSADM | An inverse KDCDEF is running or is to be started. |
A100 | KCSADMI | When calling the program interface for administration, the address specified for the parameter area is either inaccessible or cannot be accessed for the length of the parameter area or it is not on a word boundary. |
A101 | KCSADMI | An invalid return code was issued internally when calling the programming interface for administration. System error. |
ABTR *) | KCSENDE | The code is reported in UTM messages K017 or K055. It occurs whenever after an abnormal task termination (cp. ABNORMAL TASK TERMINATION in batch or TIAM timesharing mode) a service is terminated abnormally by UTM system code because UTM-STXIT handling has not run (STXIT switched off or STXIT code overwritten).Generally, this does not adversely affect application execution. |
EXIT **) | KDCROOT | - The exit() function was called illegally in a C program. |
FH01 *) | KDCRTFH | Error occurred during formatting. See additional return code from FHSCON or FHS in KCRMF field. 1 |
FH02 *) | KDCRTFH | Warning: hardware function not available. 1 |
FH04 *) | KDCRTFH | Serious error when initializing FHS Format Handling System UTM aborts start of application. |
FR00 *) | KDCRTFH | Error occurred during FORMAT-Exit-Function "CHECK_FOR_DOWNLOAD" |
FR01 *) | KDCRTFH | - A format ID with "-" was specified although the application was generated without FORMAT exit, or- a "*" or "+" format was specified but the utm generation does not contain a FORMSYS statement. 1 |
FR02 *) | KDCRTFH | KDCFOR not allowed for partial format. 1 |
FR98 *) | KDCRTFH | '-' Format, i.e. user-own formatting; the length of the input message was illegally set by the FORMAT EXIT (< 0). The return code is set by KDCRTFH. |
FR99 *) | KDCRTFH | '-' Format, i.e. user-own formatting; the length of the restart area was illegally changed by FORMAT EXIT. The return code is set by KDCRTFH. |
FRxx *) | KDCRTFH | Format in '-' Format, i.e. user-own formatting: xx is the return code entered in the ....MCRF field in the user-own control area MDCBL. The entry comes from the FORMAT exit.The values X'01' , x'02' , X'03' , X'04' , X'08' , X'10', X'98' and X'99' are not permitted for the format exit, because these return codes are reserved for UTM and FHS. |
| HT01 | KDCHTPF | Program for HTTP exit is missing. The service aborts with PEND ER. |
| HT02 | KDCHTPF | Language connection error when calling HTTP exit program. |
| HT03 | KDCHTPF | The HTTP exit program split the input message in more message parts than allowed. |
| HT04 | KDCHTPF | The total length of the accumulated input message parts is longer than the buffer for the input message. |
| HXxy | KDCHTPF | The user-specific HTTP exit program returned with error code xy (X'01' <= xy <= X'FF'). Therefore the service is abnormally terminated with PEND ER. |
K300 | KCSPEND | Invalid operation modification was used in the PEND call. |
K301 | KCSPEND | (see KA00) |
K302 | KCSPEND | The task-specific buffer area for restart information is too small (see UTM manual Generating applications: restart area). |
K303 | KCSPEND | An invalid operation modification was used in the PGWT call. |
K304 | KCSPEND | The DB system requests a CLOSE DB call prior to END RE/FI, but the call was not given. |
K305 | KCSPEND | A PEND KP or a PEND PA/PR with process switch was called, although the DB system with which the transaction was opened does not permit a PEND KP. |
K306 | KCSPEND | The transaction had to be rolled back and the service had to be terminated abnormally because the DB system has rolled back the DB transaction when closing down. |
K307 | KCSPEND | PEND PS is only permitted in the first part of the sign-on service. |
K308 | KCSPEND | The DB transaction was closed prior to PEND KP or PEND PA/PR with process switch. |
K309 | KCSPEND | The TAC specified in KCRN is not permitted as a follow-up TAC. |
K310 | KCSPEND | Error when storing the MPUT message during PEND PA/PR with process switch. |
K311 | KCSPEND | A temporary end of transaction (PTC) was reached with PEND RE/FI, but the DB system where the transaction is open does not permit the transaction status. |
K312 *) | KCSPEND | A formatted message cannot be output because it is too long. |
K313 | KCSPEND | A SIGN OF/OB was issued in a program unit run, but the output message is for the job-receiver or the program run was terminated with an PEND variant that is not permitted. |
K314 | KCSPEND | A program unit run of a sign-on service was not terminated with PEND PS following a successful SIGN ON. |
K315 | KCSPEND | With service stacking, an MPUT PM was issued with KCLM/kclm > 0 prior to PEND FI. The last output from the preceding service was a LINEMODE message and can only be output in unmodified form. |
K316 | KCSPEND | PEND RS was called in the program unit or a situation (e.g. loss of connection) has occurred which requires UTM to roll back the transaction. However, PEND RS is not permitted because no service restart is possible. This is the case if:
No PENDER dump is written. |
K317 *) | KCSPEND | The actual size of the service memory (SQL) to be saved is greater than the permitted maximum value limited by VGMSIZE. |
K318 | KCSPEND | PGWT was called in a program unit where for this TAC
Action: Correct generation with KDCDEF. |
K319 | KCSPEND | There are not enough processes to use the PGWT or PGWT was called from an UTM system process (only possible via a privileged LTERM). |
K320 | KCSPEND | After a RSET in a distributed transaction, the transaction was not rolled back, although UTMD RSET = GLOBAL was generated |
K321 *) | KCSPEND | The edit profile name of the saved message of the stacked service is not generated. |
K322 | KCSPEND | The operation modification FC is not permitted in asynchronous services or job-receiving services. |
K323 | KCSPEND | The operation modification FC is not permitted in the sign-on service if a service restart is required. |
K324 | KCSPEND | KCRN does not contain blanks when calling PEND RS or PEND FR. |
K325 | KCSPEND | The operation modification RS is not permitted in the sign-on service or in the MSGTAC program, or the Resource Manager of the XA connection requires a rollback of the transaction in the case of an xa_end of the sign-on service or the MSGTAC service. |
K326 | KCSPEND | Switch between dialog transaction code and asynchronous transaction code is not permitted, or the follow-up TAC in PEND FC is not a service TAC, or the follow-up TAC in PEND PA/PR, PS, KP, RE or SP is not a follow-up TAC. |
K327 | KCSPEND | The operation modification FC is not allowed in the sign-on service if the last sign-on attempt failed. |
K328 | KCSPEND | The sign-on service cannot be terminated normally when the validity period of the password has expired but the password has not been changed. |
K329 | KCSPEND | The sign-on service cannot be terminated normally when the password transferred with KDCUPD does not meet the complexity level requirement or is too short and the password has not been changed with SIGN CP. |
K330 | KCSPEND | A SIGN OB in the sign-on service for terminals is only allowed in conjunction with an MPUT NT/NE. |
K331 | KCSPEND | If a sign-on service with a service restart is terminated without the user signing off, then no MPUT NT/NE is allowed. |
K332 | KCSPEND | If a sign-on service with a service restart is terminated with PEND FI without a preceding MPUT, then UTM terminates the open service. |
K333 | KCSPEND | The service should wait for a DGET message, but the follow-up program unit is not in a TAC class. |
K334 | KCSPEND | The service should wait for a DGET message; only PEND PA/PR/RS/ER/FR and PGWT RB are permitted. |
K335 | KCSPEND | The process waiting in PGWT is terminated abnormally because it was noted that not enough processes are active to continue the service. No PENDER dump is written. |
K336 | KCSPEND | Although required, no MPUT call was made prior to PEND KP/RE/FI/FR/ER or PGWT KP. |
K337 | KCSPEND | An MPUT call was made prior to PGWT PR. |
K338 | KCSPEND | The transaction was rolled back because the application is being terminated. |
K339 | KCSPEND | The MSGTAC program unit was terminated without reading a message with FGET. |
K340 | KCSPEND | On transaction rollback, the database reported an error which makes it necessary to dynamically load the application program. |
K341 **) | KCSPEND | Only in UTM cluster applications: A user was generated or deleted in the current transaction. The user file could not be locked because it is currently being accessed by a KDCDEF run. |
K342 **) | KCSPEND | Only in UTM cluster applications: |
K343 **) | KCSPEND | Only in UTM cluster application: PTC state rejected because the service is locked be administration. |
K344 **) | KCSPEND | Only in UTM cluster applications: CR could not be written because a global ADM lock is set. |
K345 | KCSPEND | The page pool in KDCFILE is full.Action: Change generation with KDCDEF, enlarge page pool with MAX PGPOOL=(number,...). 1 |
K346 | KCSPEND | The sign-on service is not permitted to terminate an open service if a transaction in the open service is in the "prepare to commit" (PTC) state. The sign-on service is terminated abnormally. |
K347 **) | KCSPEND | Only in UTM cluster applications: The transaction has to go to the status "prepare to commit" (PTC) but an error occurred while writing the status to the cluster user file. |
K348 **) | KCSPEND | The cluster page pool in the KDCFILE is full. |
K349 | KCSPEND | The connection to the partner has been terminated. |
K350 | KCSPEND | Invalid operation modification after the abnormal termination with CTRL AB of a OSI TP dialog in which the functional unit commit was selected. |
K351 | KCSPEND | The transaction is marked to be rolled back but a PEND/PGWT call was used to commit the transaction. |
K360 | KCSPEND | The transaction was rolled back with PGWT RB because KCSPEND was called from KDCROOT with PGWT RB. |
K361 | KCSPEND | The transaction was rolled back with PEND RS because KCSPEND was called by KDCROOT with PEND RS. |
K362 | KCSPEND | The transaction was rolled back and the service terminated abnormally with PEND ER because KCSPEND was called by KDCROOT with PEND ER. |
K363 | KCSPEND | The transaction was rolled back with RSET because KCSPEND was called by KDCROOT with RSET. |
| K370 | KCSPEND | A service initiated by an HTTP client must issue an MPUT call to a job-receiving service before issuing a PEND call that does not end the service. |
K601 | KCSMPUT | Buffer for dialog messages generated too small. |
K602 *) | KCSMPUT | MPUT call requires format output but formatting was not generated. 1 |
K603 *) | KCSMPUT | MPUT with screen function KCCARD, but terminal does not have an ID card reader. |
K604 *) | KCSMPUT | MPUT with screen function KCCARD and user ID has operand CARD=(position, string): the ID card reader cannot be used for KDCSIGN checks and data input at the same time. |
K605 *) | KCSMPUT | MPUT with screen function KCCARD and output in formatted mode. |
K606 *) | KCSMPUT | Caused by a MPUT call with KCDF not equal to binary zero and one of the following conditions:- follow-up partial message in formatted mode- KCMF = name of an #-format- KCMF = name of an edit profile. |
K607 | KCSMPUT | The MPUT message specified by address and length partly covers an internal ROOT buffer area (the MPUT buffer) |
K608 | KCSMPUT | (see K345) |
K609 *) | KCSMPUT | With a follow-up message segment, the edit profile name is different to that entered for the first message segment. |
K610 | KCSMPUT | The ES operation modification of the MPUT call is only permitted for UPIC and SOCKET partners. |
K611 | KCSMPUT | In the case of the MPUT ES call, the KCRN field is not filled with blanks. |
K612 | KCSMPUT | MPUT was called in the MSGTAC program unit. |
K613 | KCSMPUT | Operation modification illegal. |
K614 | KCSMPUT | MPUT PM in the asynchronous service. |
K615 | KCSMPUT | MPUT PM in the first part of the sign-on service. |
K616 | KCSMPUT | MPUT PM with KCLM/kclm not equal to 0 in the sign-on service. |
K617 | KCSMPUT | MPUT PM, but the service is neither inserted nor a sign-on service. |
K618 | KCSMPUT | MPUT PM in the sign-on service for a UPIC connection user. |
K701 | KCSFPUT | UTM refuses an asynchronous message because level 2 has already been reached in the page pool. |
K702 | KCSFPUT | The name of a dialog TAC was specified in KCRN. Action: new utm generation or change the program. |
K703 *) | KCSFPUT | (see K602) |
K704 | KCSFPUT | (see K302) |
K705 | KCSFPUT | An asynchronous message is to be sent with FPUT to an LTERM or (OSI-)LPAP partner, for which LTERM ...,QAMSG=N is specified in the KDCDEF generation. UTM therefore rejects the message. |
K706 | KCSFPUT | An asynchronous line mode message is to be sent to an dialog terminal with FPUT/DPUT. The message is longer than the buffer area defined in the MAX NB= parameter in the generation. UTM does not accept the message. |
K707 | KCSFPUT | The target time specified in a DPUT call exceeds the limits set by the generation (MAX DPUTLIMIT1=, DPUTLIMIT2=). |
K708 | KCSFPUT | An asynchronous message is to be sent to an LTERM or (OSI-)LPAP partner, an asynchronous TAC, a TAC queue, a user queue, a temporary queue or an (OSI) LPAP with FPUT/DPUT. The number of asynchronous messages for this LTERM partner or TAC has already reached the maximum value defined at generation (parameter QLEV of KDCDEF statement LTERM, TAC, USER, QUEUE, LPAP oder OSI-LPAP). |
K709 *) | KCSFPUT | With a follow-up message segment, the edit profile name is different to that entered for the first message segment. |
K710 *) | KCSFPUT | Caused by FPUT/DPUT call with KCDF not equal to 0 and one of the following conditions:- KCMF/kcfn = name of an #-format- KCMF/kcfn = name of an edit profile. |
K711 | KCSFPUT | A DPUT was issued with a new destination in KCRN although the preceding DPUT to another destination is not yet completed. |
K712 | KCSFPUT | The name of a UTM-D partner, a MUX connection, a UPIC client or a HTTP client was specified in KCRN. |
K713 *) | KCSFPUT | Caused by an FPUT/DPUT call to an ID card reader |
K714 | KCSFPUT | The name of a message complex was specified in KCRN in an FPUT call. |
K715 | KCSFPUT | The name of a message complex was specified in KCRN, but this name does not match the message complex currently open. |
K716 | KCSFPUT | The name of a message complex was specified in KCRN, but no message complex is currently open. |
K717 | KCSFPUT | The name of a TAC was specified in KCRN, but the specification is incompatible with the specification in KCOM. |
K718 | KCSFPUT | An asynchronous service running under a deleted LTERM partner attempted to issue an FPUT or DPUT. |
K719 | KCSFPUT | An asynchronous service running under a deleted user attempted to issue an FPUT or DPUT. |
K720 | KCSFPUT | In case of a DPUT call to a USER queue: There is no USER with the name specified in KCRN, or the USER was deleted. |
K721 | KCSFPUT | In case of a DPUT call to a USER queue: The KSET of the user and the write ACL of the USER queue do not have a common key. |
K722 | KCSFPUT | Time-controlled DPUT calls for USER queues are not possible (KCMOD not, equal to blank). |
K723 | KCSFPUT | In case of a DPUT call to a QUEUE object: There is no QUEUE object with the name specified in KCRN. |
K724 | KCSFPUT | In case of a DPUT call to a USER queue: The KSET of the LTERM and the write ACL of the USER queue do not have a common key. |
K725 | KCSFPUT | Time-controlled DPUT calls are not possible for QUEUE objects. (KCMOD not equal to blank) |
K726 | KCSFPUT | Invalid value in KCQTYP. |
K727 *) | KCSFPUT | The current RSO version does not support this function. |
K728 *) | KCSFPUT | The message target is not a RSO printer. |
K729 *) | KCSFPUT | The message target is not a LTERM. |
K730 *) | KCSFPUT | A message for which a message segment has already been written may not be extended with an FPUT RP or DPUT RP. |
K731 | KCSFPUT | No asynchronous messages can be sent to a TAC generated with CALL=NEXT. |
K732 | KCSFPUT | No asynchronous messages may be sent to KDCMSGLT. |
K733 **) | KCSFPUT | No asynchronous message may be sent to an LTERM that has been implicitly generated for the internal cluster communication. |
K801 | KCSSSB | (see K345) |
K802 | KCSSSB | (see K302) |
K804 | KCSSSB | No GSSBs were generated or more GSSBs were created than permitted in the utm generation. |
K805 | KCSSSB | SPUT created more LSSBs than specified in the utm generation. |
K810 | KCSSSB | When accessing a GSSB, TLS or ULS: The storage area cannot be accessed by the transaction following a certain wait period. |
K811 | KCSSSB | When accessing a GSSB, TLS or ULS: The storage area is currently locked by another transaction for an "indeterminate" period, i.e. it has locked the area and then issued PEND KP or PGWT KP call. |
K812 | KCSSSB | When accessing a ULS: The user ID for the user whose ULS is to be accessed is being deleted. |
K813 | KCSSSB | The application is being terminated. |
K820 | KCSSSB | Waiting for a global secondary storage area would lead to a deadlock. |
K822 **) | KCSSSB | (see K348) |
K823 **) | KCSSSB | Only in UTM cluster applications: A timeout occurred on a request for a file lock for the administration file for GSSB or ULS. |
K824 | KCSSSB | When accessing a GSSB, TLS or ULS: The storage area is currently locked and the task cannot wait for the lock to be released because there are already too many tasks waiting.
For information on how to distribute UTM services that use GSSB or ULS memory areas to the tasks in a UTM cluster application, see openUTM manual "Using openUTM Applications under BS2000 Systems". |
K825 **) | KCSSSB | Only in UTM cluster applications when accessing a GSSB or ULS: The queue at the requested area has already reached the maximum length; the service cannot currently wait for this storage area. |
K826 **) | KCSSSB | Only in UTM cluster applications when accessing a GSSB or ULS: A transient error occurred on a request for an internal resource; access to the requested area is not currently possible. |
K827 **) | KCSSSB | Only in UTM cluster applications when accessing a GSSB or ULS: The area is currently locked by a failed node; there is at present no point in waiting for this area. |
K901 | KCSLPUT | K901 KCSLPUT UTM rejects an LPUT call because level 2 has already been reached in the page pool. |
K902 | KCSLPUT | (see K302) |
K903 | KCSLPUT | UTM rejects an LPUT call because a DMS error occurred during the last write procedure to the user log file(s). The DMS error was output with message K043. The records buffered in the page pool remain. |
KA00 | KCSWAIT | The buffer is too small for the input message. |
KA01 | KCSWAIT | A serious error ocuured during communication between job submitter and job receiver (UTM-D). Communication cannot be continued; UTM aborts the jobreceiving service with PEND ER.
Diagnostic aids:
|
KA02 | KCSWAIT | The page pool in the KDCFILE is full, consequently the messages could not be passed to the task waiting in the PGWT. |
KA03 | KCSWAIT | UTM has received an unencrypted message although an encrypted message was expected. |
KA04 | KCSWAIT | The connection to the partner was disconnected. |
KA05 | KCSWAIT | A transaction in PTC state was rolled back following an administration request. |
KB01 | KCSDGET | DGET calls are not permitted in the first part of the sign-on service. |
KB02 | KCSDGET | A DGET message must be waited for; no further DGET calls are therefore permitted. |
KB03 | KCSDGET | Invalid value of KCQTYP. |
KB04 | KCSDGET | There is no object for the name of the type KCQTYP specified in KCRN, or this object has been deleted. |
KB05 | KCSDGET | Messages to dialog or asynchronous TACs cannot be read by means of a DGET call. |
KB06 | KCSDGET | The read ACL or the TAC or USER queue and the KSET of the user's LTERM do not have a common key. |
KB07 | KCSDGET | The read ACL or the TAC or USER queue and the KSET of the user do not have a common key. |
KB08 | KCSDGET | (see K302) |
KB10 | KCSDGET | Negative wait time in case of a DGET FT /BF call, or wait time is not equal to zero in case of a DGET NT/BN/PF/PN call. |
KB11 | KCSDGET | DGET calls with waiting are not permitted for the MSGTAC program. |
KB12 | KCSDGET | In case of the call DGET NT/BN/PN, the name or type of the specified queue does not suit the previous DGET call of the current program unit run. |
KB13 | KCSDGET | An attempt was made to read from a USER queue although the application was generated without any users. |
KB14 | KCSDGET | An attempt was made to read from a TAC queue with STATUS = HALT or KEEP. |
KB15 | KCSDGET | An attempt was made to read from a TAC queue with ADMIN=Y, but the user is not an administrator. |
KB16 | KCSDGET | Operation modifier in KCOM is invalid. |
KB17 | KCSDGET | For DGET BF/PF: Value in KCDPID does not contain a valid DPUT ID. |
KB18 | KCSDGET | For DGET FT/NT: KCMF/kcfn does not contain blanks. |
KB19 | KCSDGET | For DGET NT/BN/PN (next): KCOM does not match the preceding DGET call, or no DGET FT/BF/PF (first) has been issued yet in this program run, or a PGWT call was made in the intervening period. |
KB20 | KCSDGET | For DGET NT/BN/PN: Since the last DGET call the DGET queue deleted and regenerated. |
KB21 | KCSDGET | For DGET BN/PN (next): Since the last DGET call the USER specified in the KCRN and KCQTYP or the temporary queue was deleted and regenerated. |
KB22 | KCSDGET | For DGET BN: There is no message with the creation time specified in KCGTM, or processing has taken place in the meantime. |
KB23 | KCSDGET | For DGET PF: There is no message with the creation time specified in KCGTM, or processing has taken place in the meantime. |
KB24 | KCSDGET | For DGET BF/PF: KCDPID does not match the specifications in KCRN and KCQTYP. |
KB25 | KCSDGET | DGET calls with waiting are not permitted in the sign-on service. |
KB26 | KCSDGET | Attempts were made with DGET FT/NT/PF/PN to read from the dead letter queue KDCDLETQ. |
KC01 | KCDCTRL | UTM-D has not been generated. |
KC02 | KCDCTRL | The first character in the service ID specified in KCRN is not '>'. |
KC03 | KCDCTRL | The call was issued for an asynchronous service, i.e. the service ID specified in KCRN was defined with an APRO AM call. |
KC04 | KCDCTRL | The VGID specified in KCRN is invalid. |
KC06 | KCDCTRL | The CTRL call was addressed to a partner which is not communicated with via the OSI TP protocol |
KC07 | KCDCTRL | CTRL PR was intended for a partner for which the functional unit commit has not been selected. |
KC08 | KCDCTRL | CTRL PE was intended for a partner for which the functional unit commit has not been selected. |
KC09 | KCDCTRL | CTRL AB was intended for a partner to whom a message has already been sent with MPUT. |
KC10 | KCDCTRL | The operation modification OM is nether PR nor PE nor AB. |
KC11 | KCDCTRL | KCLA/kcla is not zero. |
KC12 | KCDCTRL | KCLM/kclm is not zero. |
KC13 | KCDCTRL | KCMF/kcfn is not filled with spaced (blanks). |
KC14 | KCDCTRL | KCDF/kcdf does not contain binary zeros. |
KC15 | KCDCTRL | The extended parameter area (EXTENT) does not contain binary zeros. |
KC16 | KCDCTRL | The call was intended for a partner for whom an MPUT HM has already been issued. |
KC17 | KCDCTRL | The call CTRL PR was intended for a partner in a middle node, but the local service had not already received a Prepare from its job submitter. |
KC18 | KCDCTRL | The call CTRL PE was intended for a partner in a middle node, but the local service had not already received a Prepare from its job submitter. |
KC19 | KCDCTRL | The CTRL AB call was intended for a partner for which the functional unit commit has not been selected and the service status is not O. |
KC20 | KCDCTRL | The CTRL AB call was intended for a partner for which the functional unit commit has not been selected and the service status is neither O nor C. |
KC21 | KCDCTRL | The CTRL PR call is not permitted because the service status is not O. |
KC22 | KCDCTRL | The CTRL PE call is not permitted because the service status is not O. |
KC23 | KCDCTRL | The CTRL PR call is not permitted because the transaction status is P. |
KC24 | KCDCTRL | The CTRL PE call is not permitted because the transaction status is P. |
KC25 | KCDCTRL | Binary zeros have not been entered for the unused part of the extended parameter area (EXTENT). |
KC26 | KCDCTRL | The KCNORPLY field does not have either the value Y or binary zero. |
KD00 | KCDAPRO | KCRN does not contain a valid service ID (MGET, MPUT, FPUT, DPUT). |
KD01 | KCDAPRO | LTAC is not defined. |
KD02 | KCDAPRO | LTAC cannot be used; LTAC is locked. |
KD03 | KCDAPRO | User does not have a key in his/her key set for the lock on the LTAC. |
KD04 | KCDAPRO | APRO DM was called, but the LTAC is generated as an asynchronous LTAC, or APRO AM was called and LTAC is generated as a dialog LTAC. |
KD05 | KCDAPRO | APRO created more job-receiving services than specified at generation time (KDCDEF generation: UTMD MAXJR= ). |
KD06 | KCDAPRO | MPUT to job-receiving service and KCDF not binary 0. |
KD08 | KCDAPRO | (see K345) |
KD09 | KCDAPRO | APRO DM was called, but the virtual connections to the remote application were cleared down with the administration command KDCLPAP ACT=QUIET. |
KD10 | KCDAPRO | APRO DM was called, but no virtual connection was set up to the remote application. |
KD11 | KCDAPRO | APRO DM was called, but the remote application was generated as "contention winner" and the wait period for session occupancy is 0 (only for LU6.1). |
KD12 | KCDAPRO | Following an MPUT NE/HM to a job-receiving service, another MPUT was issued to the job-receiving service. |
KD13 | KCDAPRO | No connection exists to the remote application with FPUT (or DPUT with KCMOD='_') to a job-receiving service and the wait period for session or association occupancy is 0. |
KD14 | KCDAPRO | An asynchronous service in another application is to be addressed with APRO. The number of asynchronous jobs for this application has already reached the maximum value defined at generation (LPAP QLEV= or OSILPAP QLEV=). |
KD15 | KCDAPRO | With an MPUT EM or MPUT HM the destination in KCRN/kcrn is not an OSI TP communication partner. |
KD16 | KCDAPRO | No MPUT NT was given prior to an MPUT HM. |
KD17 | KCDAPRO | The RTAC was generated for an OSI TP partner. |
KD18 | KCDAPRO | A selected functional unit is not supported by this UTM version. |
KD22 | KCDAPRO | The functional unit commit was selected, but the abstract syntax CCR was not generated for the partner. |
KD23 | KCDAPRO | Mixed operation of LU6.1 and OSI TP within a distributed transaction. |
KD24 | KCDAPRO | (see KD23) |
KD25 | KCDAPRO | More than one ACCESS-POINT was used in a distributed transaction with OSI TP. |
KD26 | KCDAPRO | An abstract syntax which has not been generated was specified for an OSI/TP partner for MPUT/FPUT/DPUT in KCMF/kcfn. The syntax names "CCR" and "OSITP" are not permitted. |
KD27 | KCDAPRO | KCLM/kclm must be 32. |
KD28 | KCDAPRO | KCLM/kclm must be zero. |
KD29 | KCDAPRO | KCLM/kclm must be equal to the length of the data structure in COPY KCAPROC or include kcapro.h. |
KD30 | KCDAPRO | Illegal values in the APRO data area. |
KD31 | KCDAPRO | KCFUCHN must contain blanks for KCFUCOM = 'N'. |
KD32 | KCDAPRO | Security type "Same" or "Program" was selected, but the abstract syntax UTMSEC has not been generated for the partner. |
KD33 | KCDAPRO | An invalid length was specified for the user ID or the password with the security type "Program". |
KD34 | KCDAPRO | Error on encoding the security data. |
KD35 | KCDAPRO | KCFUHSH = 'Y' is only permitted in the case of dialog partners. |
KD36 | KCDAPRO | After a CTRL PR or PE, an MPUT HM was issued to the same partner. |
KD37 | KCDAPRO | After a CTRL AB, an MPUT was issued to the same partner. |
KD38 | KCDAPRO | MPUT to job submitter, but KCSEND = NO. |
KD39 | KCDAPRO | The unused fields for the security function when KCSECTYP is not equal to 'P' are not deleted. (CHAR fields to blank, numeric fields to 0). |
KD40 | KCDAPRO | There is no active connection assigned to the OSI-LPAP in the APRO call. |
KD41 | KCDAPRO | The master (OSI-)LPAP is locked. |
KD42 **) | KCDAPRO | (see K348) |
KE01 | KCSPADM | No authorization for the call: |
KE02 | KCSPADM | No printer (PTERM) is assigned to the printer control terminal. Check utm generation. |
KE03 | KCSPADM | A PADM call for printer acknowledgment or print repeat (KCOM = OK/PR) was issued even though there was no printout to be acknowledged for the specified printer. |
KE04 | KCSPADM | (see K302) |
KE05 | KCSPADM | A printer is to be assigned to another LTERM (KCOM = CA), but is linked with the application. |
KE06 | KCSPADM | Connection to a printer is to be set up, but the printer is locked. |
KE07 | KCSPADM | An inverse KDCDEF is running or is to be started. |
KE08 **) | KCSPADM | Administration applying globally to the cluster is not currently possible because node applications with different utm generations are running. |
KF01 | KCSINFO | The user has been generated without an ID card and no Kerberos dialog was executed for the LTERM client (INFO CD). |
KF02 *) | KCSINFO | The information is no longer available, e.g. because of a loss of connection (INFO CD). |
KF03 *) | KCSINFO | The Kerberos dialog returned an error, but Kerberos information is possibly transferred anyway (INFO CD). |
KF04 *) | KCSINFO | The Kerberos information is not complete because it exceeds the length generated in MAX PRINCIPAL-LTH (INFO CD). |
KG01 | KCSDADM | No authorization for the call: |
KG02 | KCSDADM | (see K302) |
KG03 | KCSDADM | A DADM call to delete all asynchronous messages was made (KCOM = DA) even though messages were being processed for the specified destination. |
KG04 | KCSDADM | An attempt was made to administer a message currently being processed. |
KG05 | KCSDADM | A call to delete messages (KCOM = DL/DA) was followed by another delete job or a job to modify concatenation of a message (KCOM = DL/DA/CS). |
KG06 | KCSDADM | An attempt was made to modify the concatenation of a time-driven message (KCOM = CS), although its start time had not yet been reached. |
KG07 | KCSDADM | A call to read information about messages was issued (KCOM = RQ), although there were no messages for the specified destination (or only messages currently being processed). |
KG08 | KCSDADM | KCQTYP invalid |
KG09 | KCSDADM | In the case of DADM MV with blanks in KCLT/kclt, the original destination of the message in the dead letter queue no longer exists. This message must be assigned a new destination. |
KG10 | KCSDADM | In the case of DADM MV, the destination specified in KCLT/kclt no longer exists. |
KG11 | KCSDADM | In the case of DADM MV, the type of destination specified in KCLT/kclt does not match the type of the original destination of the message. |
KH01 | KCSSIGN | (see K302) |
KH02 | KCSSIGN | With SIGN CP: The new password does not satisfy the requested complexity level. |
KH03 | KCSSIGN | With SIGN CP: The new password is too short. |
KH04 | KCSSIGN | With SIGN CP: The new password is identical to the old password or to a password in the password history. |
KH05 *) | KCSSIGN | With SIGN CL: The specified language identifier is invalid. |
KH06 *) | KCSSIGN | With SIGN CL: The specified territorial identifier is invalid |
KH07 *) | KCSSIGN | With SIGN CL: The specified character set name is invalid |
KH08 | KCSSIGN | An inverse KDCDEF is running or is to be started. |
KH09 | KCSSIGN | With SIGN CP: The password may not be changed because the minimum validity period has not been exceeded yet. |
KH10 *) | KCSSIGN | With SIGN CP: A password cannot be assigned or changed for a user generated with a Kerberos authentication. |
KH11 **) | KCSSIGN | The service was terminated abnormally because the page list for the cluster service data could not be written when the user signed off due to the fact that the cluster page pool was full. |
KH12 **) | KCSSIGN | An open cluster service cannot be continued because the sequence of TAC statements has changed following a regeneration of the node KDCFILE, or the properties of the follow-up TAC have been changed, or the follow-up TAC or the service TAC no longer exist. |
KI01 *) | KCSISLP | VTSU recognizes that editing of dialog output message with format exit contains an error.. |
KI02 *) | KCSISLP | VTSU reports invalid edit options for the dialog output message. |
KI03 *) | KCSISLP | VTSU recognizes that a dialog output message is to be sent with an invalid character set or one which is not supported by the terminal. |
KJ01 | KCCUSF | The service was terminated abnormally because it was marked for abnormal termination by another node application. This may have been performed via the administration functions or could be due to the fact that, even though there is a service bound to this node application, the user has signed on at another node application. |
KK01 | KCSSVCS | The second parameter in the KDCS call is missing. |
KK02 | KCSSVCS | Address validation of the second parameter in the KDCS call failed. |
KK03 | KCSSVCS | The KDCS call was issued from a program unit in an asynchronous service. |
KK04 | KCSSVCS | The KDCS operation code is unknown. |
KK07 | KCSSVCS | The KDCS operation code APRO is not permitted. |
KK08 **) | KCSSVCS | The call is not permitted in UTM cluster applications. |
KL00 | KCSSTRT | During warm start of the application no job-receiver session in the PTC state was found. |
KL01 | KCSSTRT | During warm start of the application no valid NODE table entry was found for the OSI TP service. |
KL02 | KCSSTRT | The user who started this service has been deleted. |
KL03 | KCSSTRT | During warm start it was determined that the service cannot be continued. OSI TP job receiving services are possibly terminated only after the association to the OSI TP partner has been established and the subsequent recovery has been processed. |
KL04 | KCSSTRT | PEND ER triggered by KCSSTRT |
KL05 | KCSSTRT | PEND ER triggered by KCSSTRT |
KL06 | KCSSTRT | PEND ER triggered by KCSSTRT |
KL07 | KCSSTRT | PEND ER triggered by KCSSTRT |
KL08 | KCSSTRT | PEND ER triggered by KCSSTRT |
KM01 | KCSTRHD | TAC is not defined. 1 |
KM02 | KCSTRHD | TAC cannot be used, TAC locked. 1 |
KM03 | KCSTRHD | There is no key in the key set of the LTERM or (OSI-)LPAP partner for the lock on the TAC. 1 |
KM04 | KCSTRHD | The user does not have a key in his/her key set for the lock on the TAC. 1 |
KM05 | KCSTRHD | The TAC is generated as an administration TAC, but the user is not an administrator. 1 |
KM07 | KCSTRHD | The program unit associated with the transaction code is not linked or could not be loaded. 1 |
KM08 | KCSTRHD | The transaction code is completely locked. It cannot be specified as a following TAC in a PEND call, nor can new jobs be specified for this TAC. 1 |
KM09 | KCSTRHD | The transaction code is protected by an encryption level and the caller does not support this encryption level or the input message was not encrypted with the appropriate level. |
KM99 | KCSTRHD | A TAC which is generated with XOPEN-API may only be used by a job submitter with whom communication takes place via the OSI TP, LU6.1 or UPIC protocol. |
KN01 | KCSDLO | The user who started the service has been deleted. |
KQ01 | KCSCRO | For a QCRE WN call the name in KCRN starts with a digit. |
KQ02 | KCSCRO | For a QCRE NN call KCRN does not contain blanks. |
KQ03 | KCSCRO | (see K302) |
KQ04 | KCSCRO | The tables for temporary queues reserved at utm generation by means of the QUEUE statement have been used up. |
KQ05 | KCSCRO | For a QCRE WN call KCRN contains an invalid character or is not filled with blanks. |
KR01 | KDCRTMM | A dialog program unit with which a service was meant to continue is missing (not linked). 1 |
KR02 | KDCRTMM | An asynchronous program unit for which a message is awaiting processing is missing (not linked). 1 |
KR04 | KDCRTMM | A program unit run prior to the last KDCS call continued writing beyond the end of the KB. |
KR05 | KDCRTMM | A program unit run prior to the last KDCS call continued writing beyond the end of the SPAB. |
KR06 | KDCRTMM | A KDCS call was made by the VORGANG exit program. The service aborts with PEND ER. |
KR07 *) | KDCRTMM | A KDCS call was issued by the FORMAT exit program unit. The service aborts with PEND ER. |
KR08 *) | KDCRTMM | Illegal DB USER call in sign-on service. The service aborts with PEND ER. |
KR09 | KDCRTMM | Error when loading a program unit. The service aborts with PEND ER. |
KR10 | KDCRTMM | Program for VORGANG exit is missing. The service aborts with PEND ER. |
| KR12 | KDCRTMM | Program for HTTP exit is erroneous. The service aborts with PEND ER. |
| KR13 | KDCRTMM | A KDCS call was issued by the HTTP exit program. The service aborts with PEND ER. |
KS00 | KCDSEFU | Prior to a transaction end request MPUTs were issued to two or more partners. |
KS01 | KCDSEFU | At the time of a transaction end request at least one partner has an illegal transaction or service status. |
KS02 | KCDSEFU | At the time of a transaction end request at least one session was not used (too many APRO calls). |
KS03 | KCDSEFU | The job submitter issued a MPUT call to a service ID and the transaction was subsequently terminated with PEND RE even though not all job submitters have yet reported PEND RE/FI. |
KS04 | KCDSEFU | PEND KP has been issued after a message was sent to an LU6.1 partner which has already initiated end transaction. |
KS05 | KCDSEFU | If a session is both job receiver and job submitter, then it may not send PEND RE to its job receiver until after receiving a PEND RE message from its job submitter. |
KS06 | KCDSEFU | Following an APRO AM no asynchronous message was issued for the addressed service. |
KS07 | KCDSEFU | PEND SP was issued even though there is at least one partner with an open transaction. |
KS08 | KCDSEFU | The OSI TP client sent a message to the OSI TP server without terminating the transaction, or has requested the OSI TP server to terminate the transaction although the server has already initiated transaction termination. |
KS09 | KCDSEFU | The OSI TP server has not terminated the transaction even though it was requested to do so by the OSI TP client. |
KS10 | KCDSEFU | Contrary to the request of the OSI TP client, the OSI TP server terminated the transaction with PEND SP. |
KS11 | KCDSEFU | The OSI TP client sent a message to the OSI TP server and terminated the transaction, although it does not have the right to send at transaction termination, since it is itself an OSI TP server on a different dialog and its OSI TP client has not transferred the right to send at transaction termination. |
KS12 | KCDSEFU | Contrary to the request of the OSI TP client, the OSI TP server terminated the transaction with PEND RE. |
KS13 | KCDSEFU | The OSI TP client terminated the service with PEND FI although it still has an open server conversation without functional unit commit. |
KS14 | KCDSEFU | Contrary to the request of the OSI TP client, the OSI TP server terminated the transaction with PEND FI. |
KS15 | KCDSEFU | The OSI TP client terminated the service with PEND FC although it still has an open server conversation without functional unit commit. |
KS16 | KCDSEFU | The OSI TP server sent a message to the OSI TP client although it does not possess the right to send to this dialog. |
KS17 | KCDSEFU | The OSI TP server terminated the dialog step, but did not send a message to the OSI TP client although it possesses the right to send on this dialog. |
KS18 | KCDSEFU | The OSI TP client transferred the right to send at transaction termination to more than one OSI TP server. |
KS19 | KCDSEFU | The OSI TP client issued CTRL PR or PE to request the OSI TP server to terminate the transaction or service, sent a message to this partner, but then initiated transaction termination itself. |
KS20 | KCDSEFU | The local service has called PGWT CM or PGWT RB although a partner is involved in the distributed transaction for whom the LU6.1 protocol is used for communication. |
KS21 | KCDSEFU | The OSI TP server has terminated the transaction with PGWT CM contrary to the request of the OSI TP client. |
KS22 | KCDSEFU | The OSI TP client terminated the service with PEND FI although it had issued CTRL PR before to request a server conversation to just terminate the transaction. |
KS23 | KCDSEFU | The OSI TP client terminated the service with PEND FC although it had issued CTRL PR before to request a server conversation to just terminate the transaction. |
KS24 | KCDSEFU | The OSI TP client issued CTRL PR/PE to request a server to terminate the transaction or service, even though no message has been sent to this server. |
KS25 | KCDSEFU | Session restart has failed. |
KT01 | KCDOSTM | (see K302) |
KT02 | KCDOSTM | (see K345) |
KT03 | KCDOSTM | (see K306) |
KT04 | KCDOSTM | A log record is too large for the input buffer. |
KT05 | KCDOSTM | The transaction must be rolled back because the database transaction was rolled back. |
KT06 | KCDOSTM | The database reported that the transaction was rolled back when the transaction was rolled terminated after a Prepare statement. |
KT07 | KCDOSTM | An OSI TP server reported a heuristic decision (heuristic mixed). |
KT08 | KCDOSTM | An OSI TP server reported a heuristic decision (heuristic hazard). |
KU04 | KDCRTDB | The DB transaction had to be rolled back. UTM also rolls back the UTM transaction: Control is returned to the program unit run, as with the UTM call RSET. |
KU08 | KDCRTDB | UTM has to terminate the service with PEND ER. The message K017 or K055 includes the first 4 bytes of the DB error message. |
KU0C | KDCRTDB | The DB system (the DBH) is not or no longer available. UTM terminates the application abnormally or aborts application start-up. |
KU10 | KDCRTDB | The DB system is no longer available due to DB administrator action. UTM terminates application abnormally. |
KU14 | KDCRTDB | The DB system is currently not available. A new attempt to set up the connection is made after 5 seconds. 1 |
KU18 | KDCRTDB | A (possibly recoverable) DB system error occurred. |
KU1C | KDCRTDB | An unrecoverable DB system error occurred. UTM terminates the application abnormally. |
KU20 | KDCRTDB | The DB system detected a user error. The error occurs at application start-up when the DB-specific start parameters are checked. |
KU24 | KDCRTDB | UTM behavior unexpected by the DB system. The application is terminated with PEND06. |
KU99 *) | KDCRTDB | With multi-DB systems: After a PETA call, the DB system cannot execute the FITA call. |
KV02 | KCSTUTM | (see K345) |
KV03 **) | KCSTUTM | (see K348) |
KW01 | KCDOSSF | TP-HANDSHAKE-IND received. |
KW02 | KCDOSSF | TP-BEGIN-DIALOGUE-CNF received (negative). |
KW03 | KCDOSSF | TP-U-ERROR-IND received from a partner which does not have the right to send. |
KW04 | KCDOSSF | Timer expired. |
KW05 | KCDOSSF | TP-U-ABORT-IND or TP-P-ABORT-IND received. |
KW06 | KCDOSSF | TP-ROLLBACK-IND received. |
KW07 | KCDOSSF | openUTM does not support reception of TP-END-DIALOGUE-IND from a client. |
KW08 | KCDOSSF | The dialog with the client was not terminated with the first transaction in the functional unit unchained functions. |
KY00 | KCDSYPM | A negative acknowledgment was received from the partner. |
KY01 | KCDSYPM | Timeout when reserving a session. |
KY02 | KCDSYPM | The job-receiving service was terminated with PEND ER. |
KY03 | KCDSYPM | The job-submitting service was terminated with PEND ER. |
KY04 | KCDSYPM | Mismatch with the partner, or the local service is in the PTC status. |
KY05 | KCDSYPM | Mismatch with the partner. |
KY06 | KCDSYPM | Mismatch with the database. |
KY07 | KCDSYPM | Loss of connection to the partner. |
NOTA | KCDRTDB | Transaction is unknown at the XA Resource Manager. (May occur, for example, after timeouts with the Oracle database). |
UPCP **) | KCSUPIC | (see K348) |
UPDE | KCSUPIC | The UPIC partner has required a service abort. |
UPPG | KCSUPIC | (see K345) |
UPRS | KCSUPIC | The UPIC partner has suppressed a service restart. This occurs when a service restart would have been possible, but was not required by the UPIC partner. UTM then terminates the service abnormally. |
UPXC | KCSUPIC | In a program unit using the X/OPEN-API, the message to the UPIC job submitter is to be completed even though a message to a job receiver service has already been completed. |
UPXM | KCSUPIC | In a program unit using the X/OPEN-API, the message to the UPIC job submitter is to be completed even though a message to the UPIC job submitter has already been completed. |
XTnn | KDCROOT | The signal routine in KDCROOT was called, nn = signal number (see header file signal.h). If nn is the value of SIGALRM, the maximum permissible program runtime has been exceeded (see KDCDEF generation TAC RTIME=<rtime>) |
1When TESTMODE=OFF, these PENDER dumps are suppressed. Dynamic loading is suppressed at the same time unless for the current TAC, PGWT calls are permitted and the KDCS call at which the error occurred was not a PEND call.
*) the values appear only on BS2000 systems.
**) the values appear only on Unix, Linux and Windows systems.