Return codes

In addition to the return codes listed in section "Return codes", the following codes can also occur. Some of these return codes may occur independently of the specified object type; others occur only for certain object types.

Type-independent return codes:

Main code = KC_MC_DATA_INVALID

Information is missing from the data structure in the data area or a field contains an invalid value.

Subcodes:

KC_SC_DATA_MISSING

Data is missing from the data structure. Possible causes:

• The field to be modified was not specified.

• Several fields must be specified together for the requested modification, and one of these values is missing (e.g. obj_type=KC_TPOOL: state and state_number).

KC_SC_INVALID_MOD

A field in the data structure which can be modified was completed with an invalid value.

KC_SC_NOT_NULL

A field in the data structure which cannot be modified was not completed with binary zero.

Main code = KC_MC_REJECTED_CURR

The call cannot be processed at the present time.

Subcode:

KC_SC_INVDEF_RUNNING

An inverse KDCDEF is currently running and configuration data cannot be changed during the run.

Main code = KC_MC_NOT_EXISTENT

No object of the type specified in obj_type exists under the name or name triplet passed in the identification area.

Subcode:

KC_SC_NO_INFO

Main code = KC_MC_DELETED

The specified object has been deleted. Its properties cannot be modified.

Subcode:

KC_SC_NO_INFO

Main code = KC_MC_REJECTED

The call was rejected by UTM.

Subcode:

KC_SC_NOT_GEN

No explicitly generated object of the object type specified in obj_type exists. Implicitly generated objects might, however, exist, e.g. user IDs for clients with ptype='APPLI'.

KC_SC_JCTL_RT_CODE_NOT_OK

Only in UTM cluster applications:
An internal UTM error occurred during the global modification of an object.
Please contact system support.

KC_SC_NO_CLUSTER_APPLI

This action is only possible in a UTM cluster application.

KC_SC_NO_GLOB_CHANG_POSSIBLE

No global administration changes are possible since the generations of the node applications are not consistent at present.

KC_SC_NOT_ALLOWED_IN_CLUSTER

The administration action is not permitted in a UTM cluster application.

Main code = KC_MC_RECBUF_FULL

The buffer with recovery information is full (see KDCDEF control statement MAX, operand RECBUF).

Subcode:

KC_SC_NO_INFO

Return codes for obj_type=KC_CLUSTER_NODE:

Maincode = KC_MC_REJECTED

The call was rejected by UTM.

Subcode:

KC_SC_CCFG_NO_CLUSTER_APPLI

The specified application is not a UTM cluster application

KC_SC_CCFG_FILE_NOT_OPEN

Internal UTM error.
Please contact system support.

KC_SC_CCFG_RT_CODE_NOT_OK

Modification was not performed. Possible cause, e.g. timer expired.

KC_SC_CCFG_FILE_LOCK_ERROR

Cluster configuration file is locked.

KC_SC_CCFG_FILE_READ_ERROR

Error reading the cluster configuration file.

KC_SC_CCFG_FILE_WRITE_ERROR

Error writing the cluster configuration file.

KC_SC_CCFG_INVALID_BUFFER_LTH

Internal UTM error.
Please contact system support.

KC_SC_CCFG_INVALID_NODE_INDEX

Internal UTM error.
Please contact system support.

KC_SC_CCFG_INVALID_NODE_STATE

Invalid node application status.
Note: You may not make any modifications for a running node application.

KC_SC_CCFG_INVAL_FILEBASE_NAME

Base name of UTM cluster invalid.

KC_SC_CCFG_INVALID_HOSTNAME

The host name is invalid.

Return codes for obj_type = KC_DB_INFO:

Maincode = KC_MC_REJECTED

The call was rejected by UTM.

Subcode:

KC_SC_NOT_GEN

No database is generated for the application.

KC_SC_INVALID_TYPE

The database selected in the identification area is not an XA database.

KC_SC_NO_INFO

Internal error in UTM when encoding the new password.

Maincode = KC_MC_NOT_EXISTENT

The object specified in the identification area does not exist.

Subcode:

KC_SC_NO_INFO

Return codes for obj_type=KC_KSET:

Maincode = KC_MC_REJECTED

The call was rejected by UTM.

Subcodes:

KC_SC_NOT_ALLOWED

It is not permissible to modify the KDCAPLKS or MASTER key set.

Return codes for obj_type=KC_LOAD_MODULE (program exchange):

Main code = KC_MC_REJECTED_CURR

The call cannot be processed at the present time.

Subcode:

KC_SC_CHANGE_RUNNING

A program exchange is running.

Main code = KC_MC_REJECTED

The call was rejected by UTM.

Subcodes:

KC_SC_NOT_CHANGEABLE

The load module / shared object / DLL specified in the identification area is not interchangeable.
Possible reasons include, for example:

• the load module has the load mode STATIC.

• the load module contains TCB entries.

KC_SC_SAME_VERSION

load_mode !='U' (not STARTUP):
The currently loaded version of the load module was specified in version.

KC_SC_LMOD_NOT_EXISTENT (only on BS2000 systems)

No module with the specified version could be found in the library.

KC_SC_INVALID_VALUE (only on BS2000 systems)

The load module is generated with LOAD-MODE=POOL, (POOL,STARTUP) or (POOL,ONCALL) and with version *HIGHEST-EXISTING, but in version was specified a value not equal *HIGHEST-EXISTING.

Return codes for obj_type=KC_LPAP:

Main code = KC_MC_REJECTED

The call was rejected by UTM.

Subcodes:

KC_SC_CONNECTED

state = 'N': There is a connection to the partner application. The partner application thus cannot be disabled. Before the partner application is disabled, all connections to it must be shut down.

KC_SC_NOT_ALLOWED

Possible causes:

• you have attempted to establish a connection to a disabled partner application (state = 'N') with connect_mode = 'Y', or

• you have set state = 'N' together with connect_mode = 'Y', or

• you have specified connect_mode and quiet_connect together, or

• the value specified in bcam_trace is not permissible.

KC_SC_NOT_EXISTENT

The specified object does not exist.

Return codes for obj_type=KC_LSES:

Main code = KC_MC_REJECTED

The call was rejected by UTM.

Subcodes:

KC_SC_NOT_ALLOWED

Possible causes:

• The combination of the specified modifications is not permitted, i.e. both connect_mode and quiet_connect were set.

• There is no connection to the partner application and it is not possible to establish one because the LPAP partner of the partner application is disabled. The LPAP partner must first be enabled in a separate transaction.

KC_SC_INVALID_CON

The connection specified by (con, pronam, bcamappl) is invalid. It does not exist or is intended for another partner application (LPAP partner).

KC_SC_CONNECTED

A connection to be established was specified in (con, pronam, bcamappl). However, the session already has another connection.

Maincode = KC_MC_NOT_EXISTENT

The specified object does not exist.

Subcode:

KC_SC_NO_INFO

No LU6.1 connection was created or generated.

Return codes for obj_type=KC_LTAC:

There are no type-specific return codes for KC_LTAC. 

Return codes for obj_type=KC_LTERM:

Main code = KC_MC_REJECTED

The call was rejected by UTM.

Subcodes:

KC_SC_POOL_LTERM

The LTERM partner specified in the identification area belongs to an LTERM pool. The requested modification is not permissible for this LTERM partner.

KC_SC_NO_PTERM

connect_mode = 'Y' was set:
UTM cannot establish a connection because no client/printer is currently assigned to the LTERM partner or the associated client/printer is disabled.

KC_SC_NOT_ALLOWED

Possible causes:

• an attempt was made to define a start format for an LTERM partner with usage_type='O'.

• format_attr='E' (#format) was specified, but no sign-on service is defined.

• an inadmissible value was specified in bcam_trace.

• The replacement of two master LTERMs was rejected because one of the LTERMs is not a master LTERM or the same master was specified for both. The replacement of two master LTERMs is not permitted in a UTM cluster application.

KC_SC_NO_FORMAT_ALLOWED

Values specified in format_name and format_attr (modifying the start format) are not permitted as no formatting system has been generated for the application.

KC_SC_INVALID_ALIAS

The primary LTERM is itself an alias LTERM.

KC_SC_INVALID_ALIAS_CTERM

The primary LTERM is a CTERM.

KC_SC_INVALID_ALIAS_BUNDLE

The primary LTERM is a slave LTERM in an LTERM bundle.

KC_SC_ALIAS_STATE_ILL

The primary LTERM has been generated with RESTART=NO or QAMSG=NO.

Return codes for obj_type=KC_MUX (BS2000 systems):

Main code = KC_MC_REJECTED

The call was rejected by UTM.

Subcodes:

KC_SC_CONNECTED

state='N': There is a connection to the multiplex connection. It therefore cannot be disabled.
connect_mode = 'Y': There is already a connection to the multiplex connection.

KC_SC_NOT_ALLOWED

You have tried to establish a connection to a disabled multiplex connection, or the value specified in bcam_trace is not permitted.

Return codes for obj_type=KC_OSI_CON:

Main code = KC_MC_REJECTED

The call was rejected by UTM.

Subcode:

KC_SC_CONNECTED

There is a connection to the partner application. It is only possible to switch to a replacement connection if no active association to the partner application currently exists.

Return codes for obj_type=KC_OSI_LPAP:

Main code = KC_MC_REJECTED

The call was rejected by UTM.

Subcodes:

KC_SC_CONNECTED

Specified value state = 'N': a connection to the partner application exists. The OSI-LPAP partner of the partner application therefore cannot be disabled. All connections to the partner application must be shut down before the disable operation.

KC_SC_NOT_ALLOWED

Possible causes:

• you have attempted to establish a connection (connect_number>0) to a disabled partner application (OSI-LPAP partner) or to a partner application for which no connection is set to active (see kc_osi_con_str field active)

• you have set state = 'N' together with connect_number, or

• you have set state = 'N' together with quiet_connect, or

• you have set quiet_connect together with connect_number.

Return codes for obj_type=KC_PTERM:

Main code = KC_MC_REJECTED

The call was rejected by UTM.

Subcodes:

KC_SC_NOT_ALLOWED

Possible causes:

• an attempt was made to establish a connection to a disabled client/printer, or

• connect_mode = 'R' is not permitted for the client specified in the identification area, or

• the fields lterm and connect_mode were specified together.

• state = 'N' and auto_connect = 'Y' were specified together.

KC_SC_POOL_PTERM

The requested modification is not permitted for clients connected via an LTERM pool.

KC_SC_UPIC_PTERM

The requested modification is not permitted for clients with ptype= 'UPIC-R' or 'UPIC-L' (on Unix, Linux and Windows systems).

KC_SC_TTY_PTERM (only on Unix, Linux and Windows systems)

The requested modification is not permitted for a terminal (ptype='TTY').

KC_SC_MUX_DIS_PENDING (only on BS2000 systems)

The specified client is connected to the application via a multiplex connection and the session is in the state DISCONNECT PENDING.
An attempt was made either to establish or shut down the session (connect_mode='Y' or 'N‘) or to release the session explicitly while the timer was still running (connect_mode='R').

KC_SC_LTERM_NOT_EXISTENT

The client/printer assignment to the LTERM partner cannot be modified as the LTERM partner specified in lterm does not exist.

KC_SC_LTERM_DEL

The client/printer assignment to the LTERM partner cannot be modified as the LTERM partner specified in lterm has been deleted.

KC_SC_LTERM_NOT_ALLOWED

The client/printer assignment to the LTERM partner cannot be modified.
Possible causes:

• The LTERM partner specified in lterm belongs to an LTERM pool.

• The specified LTERM partner has been configured for connection to a client with ptype='UPIC-...' and cannot be assigned to any other client.

• KDCMSGLT was specified in lterm. KDCMSGLT is generated internally by UTM for the event service MSGTAC. It cannot be assigned to any client/printer.

KC_SC_CONNECTED

The client/printer assignment to the LTERM partner cannot be modified.
Possible causes:

• The client/printer which is to be assigned to the LTERM partner is currently connected to the application.

• A client which is connected to the application is currently assigned to the LTERM partner.
  The old assignment of the LTERM partner cannot be cancelled as one of the two clients is entered as a dialog partner (usage_type='D').

KC_SC_OUT_PTERM_DIAL_LTERM

The name of an output medium (usage_type='O') was stated in the identification area, but the LTERM partner specified in lterm is configured as a dialog partner.
An output medium cannot be assigned to a dialog LTERM partner.

KC_SC_DIAL_PTERM_TO_BUNDLE

The new client/printer assignment to the LTERM partner cannot be created.
The name of a dialog partner (usage_type='D') was passed in the identification area, but the LTERM partner specified in lterm belongs to a printer pool.

KC_SC_PTYPE_APPLI

The new client/printer assignment to the LTERM partner cannot be created.
The name of a client having ptype='APPLI' or 'SOCKET' was specified in the identification area.
The LTERM partner specified in lterm is not suitable for this client because no user ID has been generated for the LTERM partner.

KC_SC_PTERM_WITHOUT_CID

The new client/printer assignment to the LTERM partner cannot be created.
The specified LTERM partner is assigned to a printer control LTERM, but no printer ID (CID) has been defined for the specified printer.

KC_SC_CID_AMBIGUOUS

The new client/printer assignment to the LTERM partner cannot be created.
The specified LTERM partner is assigned to a printer control LTERM, but the printer ID defined for the specified printer is not unambiguous at the level of the printer control LTERM.

KC_SC_NO_LTERM

connect_mode = 'Y' is not permitted: no LTERM partner is assigned to the specified client/printer, so no connection can be established.

KC_SC_INVALID_PROTOCOL_USAGE

PTYPE and protocol cannot be combined.

KC_SC_BUNDLE_NOT_ALLOWED

It is not possible to make the new assignment between the client and the LTERM partner because the LTERM partner belongs to an LTERM bundle.

KC_SC_GROUP_NOT_ALLOWED

It is not possible to make the new assignment between the client and the LTERM partner because the LTERM partner belongs to an LTERM group.

KC_SC_NOT_ALLOWED_IN_CLUSTER

This function is not permitted in a UTM cluster application, e.g. KDCSWTCH or replacement of two bundle masters

Return codes for obj_type=KC_TAC:

Main code = KC_MC_REJECTED

The call was rejected by UTM.

Subcode:

KC_SC_NOT_ALLOWED

Possible causes:

• An attempt was made to modify state and to reset statistics values at the same time.

• It is possible that an attempt was made to modify the lock_code and access_list parameters.
  It is not permitted to modify access_list if lock_code is generated.

• It is not permitted to modify access_list in the case of the TACs KDCBADTC, KDCMSGTC and KDCSGNTC.

• An attempt was made to disable KDCTAC.

• A TAC generated with the NEXT property should be disabled with state='N'. This is not permissible. Disabling it has no effect.

• In the case of a TAC that is not of the type 'Q', an attempt was made to modify 'q_read_acl' or 'q_write_acl'.

• An attempt was made to set dead_letter_q = 'Y' for an interactive or asynchronous TAC with CALL=NEXT or for a KDCDLETQ or KDCMSGTC TAC.

KC_SC_INVALID_READ_ACL

The key set specified in q_read_acl does not exist.

KC_SC_INVALID_WRITE_ACL

The key set specified in q_write_acl does not exist.

KC_SC_INVALID_ACL

The key set specified in access_list does not exist.

KC_SC_READ_ACL_DEL

The key set was deleted.

KC_SC_WRITE_ACL_DEL

The key set was deleted.

Return codes for obj_type=KC_TACCLASS:

Main code = KC_MC_REJECTED

The call was rejected by UTM.

Subcodes:

KC_SC_NOT_ALLOWED

• An invalid number of processes was specified in tasks or tasks_free.

• Both tasks and tasks_free were specified.

KC_SC_NOT_CHANGEABLE

tasks and tasks_free cannot be modified because the application was generated with priority control (TAC-PRIORITIES).

Return codes for obj_type =KC_TPOOL:

There are no type-specific return codes for KC_TPOOL.

Return codes for obj_type=KC_USER:

Main code = KC_MC_REJECTED

The call was rejected by UTM.

Subcodes:

KC_SC_TOO_SIMPLE

The requested password change was not performed as the new password is not of the complexity level (protect_pw_compl) defined for the user ID.

KC_SC_OLD_PW

The requested password change was not performed as the old password was specified in password16 and a limited period of validity is defined in the user ID for the password (protect_p-w_time!='0'). The old password cannot be specified as the new password for this user ID.

KC_SC_NOT_ALLOWED

The requested modification was not performed. Possible causes:

• state='N': you have attempted to disable a user ID that has administration privileges (permit='A' or 'B').

• you have attempted to modify a user ID which is assigned to a client having ptype='APPLI', 'SOCKET' or 'UPIC-...'.

• you have attempted to modify the user ID KDCMSGUS which UTM has generated internally for the event exit MSGTAC.

• you have specified format_attr='E' (#format), but no sign-on service has been defined.

• It is only permitted to enable or disable the BCAM trace if the BTRACE module is set to SELECT mode.

KC_SC_NO_FORMAT_ALLOWED

It is not permitted to specify information in format_name and format_attr (modifying the start format), as no formatting system has been generated for the application.

KC_SC_INVALID_READ_ACL

The key set specified in q_read_acl does not exist.

KC_SC_INVALID_WRITE_ACL

The key set specified in q_write_acl does not exist.

KC_SC_READ_ACL_DEL

The referenced key set was deleted.

KC_SC_WRITE_ACL_DEL

The specified key set was deleted.

KC_SC_KSET_DEL

The referenced key set was deleted.

KC_SC_KSET_NOT_EXISTENT

The specified key set does not exist.

KC_SC_INVALID_PRINCIPAL (only on BS2000 systems)

Error on sign-on with principal.

Return codes for obj_type=KC_CLUSTER_PAR: 

Maincode = KC_MC_REJECTED

The call was rejected by UTM.

Subcodes:

KC_SC_CCFG_NO_CLUSTER_APPLI

The application is not a UTM cluster application.

KC_SC_CCFG_RT_CODE_NOT_OK

Modification was not performed.
Internal UTM error.
Please contact system support.

KC_SC_CCFG_FILE_LOCK_ERROR

Cluster configuration file is locked.

KC_SC_CCFG_FILE_WRITE_ERROR

Error writing the cluster configuration file.

KC_SC_CCFG_FILE_READ_ERROR

Error reading the cluster configuration file.

KC_SC_INVALID_BUFFER_LTH

Internal UTM error.
Please contact system support.

KC_SC_CCFG_FILE_NOT_OPEN

Internal UTM error.
Please contact system support.

Return codes for obj_type=KC_DIAG_AND_ACCOUNT:

Main code = KC_MC_REJECTED

The call was rejected by UTM.

Subcodes:

KC_SC_NOT_AVAILABLE

The event monitor KDCMON cannot be activated. It is not available.

KC_SC_KDCMON_ERROR

Possible causes:

• The KDCMON sub system was not started

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

KC_SC_NOT_GEN

The OSI trace is to be activated although no objects have been generated for distributed processing through OSI TP.

KC_SC_SYSPROT_SWITCH_RUNNING

A log file is currently in the process of being switched over to the next log file. It is therefore not possible to execute a new switchover command.

KC_SC_TRCFILE_HANDLING_RUNNING

Trace files are currently being opened or closed, with the result that it is not possible to modify the trace settings at present.

Return codes for obj_type=KC_MAX_PAR:

Main code = KC_MC_REJECTED

The call was rejected by UTM.

Subcodes:

KC_SC_NOT_GEN

Data supply to openSM2 was not generated, i.e. it cannot be activated or deactivated.

KC_SC_NOT_AVAILABLE

openSM2 is currently unavailable.

KC_SC_NOT_ALLOWED

An invalid destination was specified when modifying destadm (recipient of results from KDCADM asynchronous TACs). Possible causes:

• an LTERM partner which has been disabled or deleted was specified in destadm.

• a transaction code which has been disabled or deleted was specified in destadm.

• a dialog TAC was specified in destadm, but only an asynchronous TAC or an LTERM partner may be specified as the recipient.

• an LTERM partner was specified in destadm to which a client of the type UPIC_... is assigned.

KC_SC_NOT_EXISTENT

Invalid information in destadm. The specified name belongs neither to an LTERM partner nor to a transaction code.

Return codes for obj_type=KC_TASKS_PAR:

Main code = KC_MC_REJECTED

The call was rejected by UTM.

Subcode:

KC_SC_NOT_ALLOWED

• The number of processes specified in mod_max_tasks, mod_max_asyntasks or mod_max_tasks_in_pgwt is greater than the value generated in the KDCDEF statement MAX.

• mod_max_tasks_in_pgwt='0' is not allowed, since the application allows blocking call, i.e. transaction codes or TAC classes with pgwt='Y' were generated.

Return codes for obj_type=KC_TIMER_PAR:

Main code = KC_MC_REJECTED

The call was rejected by UTM.

Subcode:

KC_SC_NO_UTMD

An attempt was made to set a timer for distributed processing through LU6.1 or OSI TP, although no objects have been generated for distributed processing.