in the retcode field UTM outputs the return code of the call. In addition to the return codes listed in section "Return codes", the following codes can also be returned. Some of these return codes may arise independently of the object type specified; others only occur for certain object types.
Main code = KC_MC_DATA_INVALID A field in the data structure in the data area contains an invalid value. Subcodes: |
KC_SC_NOT_NULL A field in the data structure that should contain a binary zero contains something else. |
KC_SC_NO_INFO A field in the data structure contains an invalid value. |
Main code = KC_MC_REJECTED The call was rejected by UTM. Subcodes: |
KC_SC_NAME_MISSING No name was specified for the object to be configured. |
KC_SC_TAB_FULL No more objects of the specified object type can be created because the table spaces reserved during KDCDEF generation are already filled or because no table spaces for this object type have been reserved. Please note that the table spaces occupied by objects deleted with delay are not released. |
KC_SC_EXISTENT An object with this object name class already exists with the object name specified (see section "Format and uniqueness of object names"). Please note that the names of deleted objects should not be reused. |
KC_SC_OBJ_DEL The object to be configured was deleted with delay. |
KC_SC_INVALID_NAME The object name begins with 'KDC'. |
KC_SC_NO_GLOB_CHANG_POSSIBLE Only in UTM cluster applications: |
KC_SC_GLOB_CRE_DEL_LOCKED Only in UTM cluster applications: |
KC_SC_JCTL_RT_CODE_NOT_OK Only in UTM cluster applications: |
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 or an inverse KDCDEF run is being prepared (asynchronous), see KC_CREATE_STATEMENTS in chapter "KC_CREATE_STATEMENTS - Create KDCDEF control statements (inverse KDCDEF)". |
Main code = KC_MC_RECBUF_FULL The buffer containing restart information is full. The buffer size is set using the KDCDEF control statement MAX, operand RECBUF. Subcode: |
KC_SC_NO_INFO |
Return codes for obj_type = KC_CON:
Maincode = KC_MC_REJECTED The call was rejected by UTM. Subcodes: |
KC_SC_PROCESSOR_MISSING (only on BS2000 systems) A processor name was not specified in pronam_long. It is mandatory to specify pronam_long in UTM applications on BS2000 systems. |
KC_SC_PROCESSOR_NOT_ALLOWED In pronam_long a computer name has been specified that is longer than 8 characters and contains no full stops (‘.') which means it cannot be a DNS name. |
KC_SC_LPAP_MISSING No LPAP partner was specified. |
KC_SC_LPAP_NOT_EXISTENT The specified LPAP partner does not exist. |
KC_SC_BCAMAPPL_NOT_EXISTENT The application name specified in bcamappl does not exist. |
KC_SC_TPROT_NOT_ALLOWED (only on Unix, Linux and Windows systems) A BCAMAPPL is referenced with t_prot=socket. |
KC_SC_INVALID_LISTENID (only on Unix, Linux and Windows systems) The number specified in listener_port is impermissible. |
KC_SC_LISTENER_PORT_MISSING (only on Unix, Linux and Windows systems) No listener_port was specified. |
KC_SC_INVALID_BCAMAPPL_PORT (only on Unix, Linux and Windows systems) The specified port number is invalid. |
Return codes for obj_type = KC_KSET:
Maincode = KC_MC_REJECTED The call was rejected by UTM. Subcode: |
KC_SC_INVALID_KEY_VALUE An attempt was made to create more keys than are permitted by the maximum value generated in the application. |
Return codes for obj_type = KC_LSES:
Maincode = KC_MC_REJECTED The call was rejected by UTM. Subcode: |
KC_SC_LPAP_MISSING |
Return codes for obj_type = KC_LTAC:
Maincode = KC_MC_REJECTED The call was rejected by UTM. Subcodes: |
KC_SC_INVALID_WAITTIME A negative wait time was assigned to the waittime parameter. |
KC_SC_INVALID_LTACUNIT A value less than 0 or greater than 4095 was assigned to the ltacunit parameter. |
KC_SC_INVALID_LOCK The lockcode specified in the LTAC statement is less than 0 or greater than the permitted maximum value (KDCDEF statement MAX, KEYVALUE operand). |
KC_SC_NOT_ALLOWED lock_code and access_list cannot be specified together. |
KC_SC_INVALID_ACL The specified key set does not exist. |
KC_SC_INVALID_RTAC When code=INTEGER: The value for recipient_TPSU_title exceeds the max. permitted value. |
KC_SC_LPAP_NOT_EXISTENT The specified LPAP, OSI-LPAP or master LPAP partner does not exist. |
KC_SC_KSET_DEL The key referenced via access_list was deleted. |
KC_SC_NAME_TOO_LONG The name assigned to the rtac parameter is too long. |
KC_SC_NAME_TOO_SHORT The name assigned to the rtac parameter is too short. |
KC_SC_INVALID_CHAR_IN_STRING The RTAC name is incorrect. |
Return codes for obj_type = KC_LTERM:
Main code = KC_MC_OK The call was processed without errors. Subcode: |
KC_SC_INVALID_LEVEL You have specified values in plev and/or qlev that exceed the maximum value allowed. The value specified is replaced by the default value. |
Main code = KC_MC_REJECTED The call was rejected by UTM. Subcodes: |
KC_SC_INVALID_NAME The name specified for the object begins with "KDC". See section "Format and uniqueness of object names" for information on object names. |
KC_SC_NAME_EXISTENT The name specified for the object to be created already exists as a TAC name. |
KC_SC_INVALID_FORMAT The format specified in format_name is a #Format, but no sign-on service was generated (there is no TAC with the name KDCSGNTC). |
KC_SC_NO_FORMAT_ALLOWED A start format was specified in format_name and format_attr but no formatting system was generated (KDCDEF control statement FORMSYS). |
KC_SC_INVALID_FORMAT_USAGE A start format was specified in format_name, format_attr although usage_type ='O' has been specified. |
KC_SC_INVALID_PLEV_RESTART plev > '0' and restart ='N' has been set. |
KC_SC_INVALID_PLEV_QAMSG plev > '0' and qamsg = 'N' has been set. |
KC_SC_INVALID_PLEV_USAGE plev > '0' and usage_type = 'D' has been set. |
KC_SC_INVALID_RESTART_QAMSG restart = 'N' and qamsg = 'Y' have been set. |
KC_SC_KSET_NOT_EXISTENT No key set exists for the name specified in kset. |
KC_SC_INVALID_USAGE_CTERM The LTERM partner is to be assigned a printer control LTERM (specified in cterm), although usage_type = 'D' has been specified (dialog partner). |
KC_SC_CTERM_NOT_EXISTENT The name specified in cterm (printer control LTERM) does not exist. |
KC_SC_CTERM_DEL The LTERM partner belonging to the name specified in cterm has been deleted. |
KC_SC_INVALID_CTERM_USAGE The LTERM partner belonging to the name specified in cterm is not a dialog partner (usage_type='D'). |
KC_SC_INVALID_USER_USAGE The LTERM partner is to be assigned a user ID (specified in user_gen); however, usage_type is set to 'O' (printer). |
KC_SC_USER_NOT_ALLOWED A user ID is specified in the user_gen field, but the application was generated without user IDs. |
KC_SC_KSET_DEL The referenced key set was deleted. |
KC_SC_USER_NOT_EXISTENT The user ID specified in user_gen does not exist; the application was generated with user IDs. |
KC_SC_USER_DEL The user ID specified in user_gen has been deleted. |
KC_SC_USER_NOT_ADMINISTRABLE The user ID specified in user_gen cannot be administered because, for example, it is a user ID that was created internally by UTM. |
KC_SC_USER_ALREADY_EXISTS The application was generated without user IDs. |
KC_SC_CTERM_IS_TPOOL The object specified in cterm is an LTERM partner that belongs to an LTERM pool. It cannot be specified as a printer control LTERM. |
KC_SC_CTERM_IS_MUX (only on BS2000 systems) The object specified in cterm is an LTERM partner that belongs to a multiplex connection. It cannot be specified as a printer control LTERM. |
KC_SC_CTERM_IS_UTM_D The name specified in cterm belongs to an LPAP or OSI-LPAP partner for the purpose of connecting partner servers. |
KC_SC_INVALID_LOCK The lock code specified in lock_code does not lie in the range between 1 and the maximum value allowed for the application (KDCDEF command MAX, KEYVALUE operand). |
KC_SC_INVALID_BUNDLE_CTERM The specified CTERM is a master or slave of an LTERM bundle. |
KC_SC_PRINCIPAL_AND_KERBEROS The value 'Y' in kerberos _dialog is not permitted if both MAX PRINCIPAL-LTH and MAX CARDLTH have the value 0. |
Return codes for obj_type = KC_PROGRAM:
Main code = KC_MC_REJECTED The call was rejected by UTM. Subcode: |
KC_SC_LMOD_MISSING No load module / shared object / DLL was specified in load_module. |
KC_SC_COMP_MISSING (only on BS2000 systems) No compiler was specified in compiler. |
KC_SC_LMOD_NOT_EXISTENT The load module / shared object / DLL specified in load_module does not exist. |
KC_SC_LMOD_NOT_CHANGEABLE The load module / shared object / DLL specified in load_module cannot be exchanged. |
KC_SC_NO_LMOD The application was not generated with load modules / shared objects / DLLs. No program unit can be added dynamically to the configuration using KC_CREATE_OBJECT. |
KC_SC_COMP_NOT_GEN The application does not contain a language connection module that corresponds to the compiler specified in compiler. |
KC_SC_KDCADM_ONCALL_LMOD The default administration program KDCADM may not be created with the load mode set to ONCALL. |
KC_SC_MFCOBOL_AND_NETCOBOL (only on Unix, Linux and Windows systems) It is not permitted to use programs for MFCOBOL (Micro Focus COBOL) and NETCOBOL simultaneously in a UTM application. |
KC_SC_LANG_ENV_MISSING (only on Unix, Linux and Windows systems) No language environment is available for MFCOBOL or NETCOBOL |
Return codes for obj_type = KC_PTERM:
Main code = KC_MC_OK The call was processed without any errors. Subcodes: |
KC_SC_INVALID_USAGE_APPLI_UPIC The values specified in ptype and usage_type are not compatible. ptype = 'UPIC-...' was specified with usage_type = 'O'. The value in usage_type was automatically set to 'D'. |
KC_SC_INVALID_IDLETIME The value of the idletime parameter was changed because you entered a value between 1 and 59. UTM has set idletime to the smallest valid value. |
KC_SC_INVALID_PROTOCOL The values specified in ptype and protocol are not compatible. The following cases can arise:
|
KC_SC_INVALID_USAGE_AND_PROT The values specified in ptype, protocol and usage_type are not compatible. ptype = 'UPIC-...' was specified with usage_type = 'O' and protocol = 'S'. The value in usage_type was automatically set to 'D', the value in protocol was set to 'N'. |
Main code = KC_MC_REJECTED The call was rejected by UTM. Subcodes: |
KC_SC_PROCESSOR_MISSING (only on BS2000 systems) No computer name was specified in pronam_long. It is mandatory to specify pronam_long in UTM applications on BS2000 systems. |
KC_SC_PTYPE_MISSING (only on BS2000 systems) No partner type was specified in ptype. It is mandatory to specify it for UTM applications on BS2000 systems. |
KC_SC_PROCESSOR_NOT_ALLOWED In pronam_long a computer name has been specified that is longer than 8 characters and contains no full stops (‘.') which means it cannot be a DNS name, or - on Unix, Linux and Windows systems - a computer name has been specified in pronam_long although ptype='TTY', 'PRINTER' or 'UPIC-L' has been set. |
KC_SC_INVALID_NAME The object name specified begins with "KDC". This name is reserved for UTM. See section "Format and uniqueness of object names" for information on the format of object names. |
KC_SC_INVALID_STATUS_CONNECT state = 'N' was specified together with auto_connect = 'Y'. |
KC_SC_INVALID_PROTOCOL_USAGE protocol = 'N' was specified together with usage_type = 'O', and ptype was not assigned to 'RSO' or 'APPLI' or 'SOCKET'. |
KC_SC_INVALID_CID_USAGE A printer ID was specified in cid although usage_type = 'D' (on BS2000 systems) or ptype='tty' (on Unix, Linux and Windows systems) was specified. |
KC_SC_BCAMAPPL_NOT_EXISTENT The application name specified in bcamappl does not exist. |
KC_SC_INVALID_BCAMAPPL_PORT (only on Unix, Linux and Windows systems) Invalid listener port |
KC_SC_INVALID_BCAMAPPL_PTYPE The name specified in bcamappl is not identical to the application name (APPLINAME) defined in the KDCDEF control statement MAX, although ptype |
KC_SC_LTERM_NOT_EXISTENT The LTERM partner specified in lterm does not exist. |
KC_SC_PTYPE_NO_LTERM ptype = 'APPLI', 'SOCKET' or 'UPIC-...' was specified, but no LTERM partner was specified in lterm. |
KC_SC_INVALID_USAGE_LTERM The value specified in usage_type is not compatible with the LTERM partner specified in lterm. |
KC_SC_INVALID_BUNDLE_USAGE usage_type='O' not permitted for bundle |
KC_SC_INVALID_BUNDLE usage_type='D' was specified and an LTERM partner was specified in lterm that already has been assigned a client. |
KC_SC_INVALID_GROUP_USAGE usage_type='O' not permitted for group |
KC_SC_INVALID_PROV_BUNDLE usage_type='D' was specified and an LTERM partner was specified in lterm that already has been assigned a client in this transaction. |
KC_SC_LTERM_DEL The LTERM partner specified in lterm has been deleted. |
KC_SC_CID_MISSING No data was specified in cid: |
KC_SC_INVALID_CID The printer ID specified in cid already belongs to another printer that has been assigned to the same printer control LTERM. |
KC_SC_CTERM_DEL The printer control LTERM of the LTERM partner specified in lterm has been deleted. |
KC_SC_USRT_TAB_FULL For ptype = 'APPLI', 'SOCKET' or 'UPIC-...': UTM cannot create a connection user ID because all table spaces reserved for user IDs during generation have been used. |
KC_SC_PROCESSOR_NOT_ALLOWED (only on Unix, Linux and Windows systems) The name of a computer was specified in pronam although ptype = 'TTY', 'PRINTER' or 'UPIC-L' was specified. |
KC_SC_INVALID_MAP_PTYPE (only on Unix, Linux and Windows systems) map |
KC_SC_INVALID_MAP_AND_PROT (only on BS2000 systems) map |
KC_SC_INVALID_CONNECT_PTYPE (only on Unix, Linux and Windows systems) auto_connect='Y' was specified together with ptype = 'TTY' or 'UPIC-...'. |
KC_SC_INVALID_AUTOUSER_PTYPE ptype = 'APPLI', 'SOCKET' or 'UPIC-...': |
KC_SC_INVALID_LTERM_PTYPE ptype= 'APPLI', 'SOCKET' or 'UPIC-...': |
KC_SC_LTERM_IS_TPOOL The LTERM partner specified in lterm belongs to an LTERM pool. |
KC_SC_LTERM_IS_MUX (only on BS2000 systems) The LTERM partner specified in lterm belongs to a multiplex connection, i.e. it has been created implicitly by UTM for a multiplex connection. |
KC_SC_LTERM_IS_UTM_D The name specified in lterm belongs to an LPAP or OSI-LPAP partner for connecting partner servers. |
KC_SC_LTERM_IS_MASTER The specified LTERM is a master Lterm. |
KC_SC_LTERM_IS_ALIAS The specified LTERM is an alias Lterm. |
KC_SC_INVALID_GROUP_PTYPE The specified LTERM is a primary Lterm and the PTYPE is not APPLI or SOCKET. |
KC_SC_INVALID_LTERM_SLAVE_PTYP The specified LTERM is a slave Lterm and the PTYPE is not APPLI or SOCKET. |
KC_SC_INVALID_APPLI_USER ptype = 'APPLI', 'SOCKET' or 'UPIC-R': |
KC_SC_INVALID_LISTENID (only on BS2000 systems) The number specified in listener_port is invalid. |
KC_SC_PRONAM_NOT_RSO (only on BS2000 systems) '∗RSO' was specified in ptype, but pronam_long was not set to '*RSO'. |
KC_SC_PTYPE_NOT_RSO (only on BS2000 systems) '∗RSO' was specified in pronam_long, but ptype was not set to '*RSO'. |
KC_SC_INVALID_USAGE_APPLI_UPIC ptype='APPLI', 'SOCKET' or 'UPIC-...' was specified with USAGE='O'. |
KC_SC_INVALID_IDLETIME_USAGE idletime was specified for an output station. |
KC_SC_INVALID_AUTOUSER_PTYPE ptype ='APPLI', 'SOCKET' or 'UPIC-...' was specified, but the USER with the name of the specified LTERM is not created by the same transaction. |
KC_SC_PRINTER_NT_NOT_SUPPORTED (only on Windows systems) ptype='PRINTER' was specified in the UTM application on Windows systems, however, openUTM on Windows systems does not support printers. |
KC_SC_INVALID_PTYPE_AND_PROT The PTERM has not been generated with ptype='SOCKET' and the referenced BCAMAPPL has been generated with TCP/IP. BS2000 systems: The PTERM has been generated with ptype='SOCKET' and the referenced BCAMAPPL has not been generated with TCP/IP. |
KC_SC_INVALID_TPROT_AND_TPROT (only on Unix, Linux and Windows systems) The PTERM referenced with ptype='SOCKET' and the referenced BCAMAPPL is not generated with TCP/IP. |
KC_SC_INVALID_USP_AND_PROT A value not equal to NO is contained in the usp_hdr field, and the referenced BCAMAPPL does not have TCP/IP. |
KC_SC_TPROT_NOT_ALLOWED Transport protocol not permitted. |
KC_SC_KEY_NOT_GEN_CREA_IT An encryption level for which no RSA key pair was created at generation was selected in the encryption_level field. If a PTERM is to be created with this encryption level, you must first dynamically generate an RSA key pair with the desired encryption level. Note that this can take quite a long time for encryption levels 3 and 4. |
Return codes for obj_type = KC_TAC:
Main code = KC_MC_OK The call was processed without error. Subcode: |
KC_SC_INVALID_VALUE One or more of the following values were invalid or were set automatically:
|
Main code = KC_MC_REJECTED The call was rejected by UTM. Subcodes: |
KC_SC_NOT_ALLOWED The specification of lock_code and access_list together is not permitted. |
KC_SC_PROGRAM_MISSING No data was entered in program. |
KC_SC_INVALID_TYPE No queues are permitted in UTM-FF. |
KC_SC_INVALID_NAME You tried to generate an administration TAC without setting admin='Y' or the TAC name (tc_name) begins with "KDC". These names are reserved for UTM. See section "Format and uniqueness of object names" for information on the format of object names. |
KC_SC_TACUNIT_ILL Invalid value for tacunit. |
KC_SC_PROGRAM_NOT_EXISTENT The program unit specified in program does not exist. |
KC_SC_INVALID_EXIT_PROGRAM The VORGANG exit specified in exit_name belongs to a load module / shared object / DLL generated with the load mode set to ONCALL. However, this load module does not contain the program unit specified in program. |
KC_SC_NAME_EXISTENT The transaction code specified in tc_name is already defined as an LTERM partner. The names of transaction codes and LTERM partners belong to the same name class (see section "Format and uniqueness of object names"). |
KC_SC_EXIT_NEXT_TAC A VORGANG exit was specified in exit_name although the transaction code should have been configured as a follow-up (next) TAC (call_type='N'). |
KC_SC_PROGRAM_DEL The program unit specified in program has been deleted. |
KC_SC_EXIT_NOT_EXISTENT The VORGANG exit specified in exit_name does not exist. |
KC_SC_INVALID_TCBENTRY Specifying tcbentry is not allowed. |
KC_SC_EXIT_DELETED The VORGANG exit specified in exit_name has been deleted. |
KC_SC_XOPEN_NOT_ALLOWED A value not equal to 'K' (KDCS) was specified in api and the application was generated without X/Open TACs. You can only dynamically configure a transaction code for a program unit that uses the X/Open program interface functions if at least one transaction code of this type was statically generated with KDCDEF. |
KC_SC_INVALID_QMODE q_mode='W' is only permitted for TAC queues. |
KC_SC_INVALID_QMODE_QLEV q_mode='W' but qlev is not between 1 and 32766. |
KC_SC_INVALID_QMODE_FF Invalid q_mode for UTM-FF. |
KC_SC_KSET_DEL The key set referenced via kset or access_list was deleted. |
KC_SC_READ_ACL_DEL The key set referenced via q_read_acl was deleted. |
KC_SC_WRITE_ACL_DEL The key set referenced via q_write_acl was deleted. |
KC_SC_INVALID_LOCK The lock code specified in lock_code is not between 1 and the maximum value (KEYVALUE operand of the MAX command) allowed for the application. |
KC_SC_INVALID_TACCLASS The data specified in tacclass and tac_type is incompatible:
|
KC_SC_NO_TACCLASS_GENERATED Data was specified in the tacclass field, but the application was generated without TAC classes. |
KC_SC_PGWT_TACCLASS 'Y' was specified in pgwt. That is not allowed if the TAC-PRIORITIES statement was issued, during the KDCDEF generation. |
KC_SC_PGWT_NO_PGWT_TASKS 'Y' was specified in pgwt, but MAX TASKS-IN-PGWT=0 (default) was specified in KDCDEF generation of the application. |
KC_SC_ILLEGAL_STATUS 'K' (Keep) was specified in state, although tac_type='D' (i.e. the transaction code is not an asynchronous TAC) and/or call_type |
KC_SC_PGWT_YES_NO_TACCLASS You entered 'Y' for pgwt, although the application was generated without TAC classes. |
KC_SC_CALLTYPE_N_ENCRYPT encryption_level unequal 'N' was set, although the TAC is not a service TAC, i.e. call_type='N'. |
KC_SC_INVALID_READ_ACL The key set specified in q_read_acl does not exist. |
KC_SC_INVALID_WRITE_ACL The specified key specified in q_write_acl set does not exist. |
KC_SC_INVALID_ACL The specified key set specified in access_list does not exist. |
KC_SC_DLETQ_YES_NOT_ALLOWED Invalid value for dead_letter_q. |
Return codes for obj_type = KC_USER:
Main code = KC_MC_OK The call was processed without error. Subcode: |
KC_SC_INVALID_PROTECT_PW The value specified in protect_pw16_lth and/or in protect_pw_time were larger than the maximum value allowed. The value was set to the maximum value. |
Main code = KC_MC_REJECTED The call was rejected by UTM. Subcodes: |
KC_SC_CARD_TAB_FULL The table space reserved for CARD during KDCDEF generation is already occupied or no table spaces were reserved for CARD. |
KC_SC_NO_CARD_ALLOWED (only on Unix, Linux and Windows systems) card... was specified even though no formatting has been generated. |
KC_SC_INVALID_NAME The user ID (us_name) specified begins with "KDC". These names are reserved for UTM. See section "Format and uniqueness of object names" for information on the format of the object names. |
KC_SC_INVALID_FORMAT (only on BS2000 systems) The start format specified in format_name and format_attr is a #Format, but no sign-on service was generated (there exists no TAC with the name KDCSGNTC). |
KC_SC_NO_FORMAT_ALLOWED (only on BS2000 systems) A start format was specified in format_name and format_attr, but no formatting system was generated (KDCDEF control statement FORMSYS). |
KC_SC_COMPL_MISSING The password specified in password does not meet the complexity level required in protect_pw_- compl. |
KC_SC_KSET_NOT_EXISTENT No key set exists for the name specified in kset. |
KC_SC_INVALID_POSITION (only on BS2000 systems) The value specified in card_position is invalid. |
KC_SC_MIN_LTH_WITHOUT_PASSWORD No password was specified in password16 although protect_pw16_lth > '0' is set. |
KC_SC_APPLICATION_WITHOUT_USER You cannot create a user ID because the application was generated without user IDs. |
KC_SC_INVALID_READ_ACL The key set specified in q_read_acl does not exist. |
KC_SC_INVALID_WRITE_ACL The specified key specified in q_write_acl set does not exist. |
KC_SC_INVALID_QMODE_QLEV q_mode='W' but qlev is not between 1 and 32766 |
KC_SC_INVALID_QMODE_FF Invalid q_mode for UTM-FF |
KC_SC_KSET_DEL The key set referenced via kset was deleted. |
KC_SC_READ_ACL_DEL The key set referenced via q_read_acl was deleted. |
KC_SC_WRITE_ACL_DEL The key set referenced via q_write_acl was deleted. |
KC_SC_INVALID_PRINCIPAL (only on BS2000 systems) A principal was specified and at the same time the CARD or PASSWORD parameter was specified. |
KC_SC_INVALID_QLEV_FF Invalid qlev for UTM-FF |
KC_SC_PRINCIPAL_AND_PW (only on BS2000 systems) It is not possible to generate a USER with both a principal and a password. |
KC_SC_PRINCIPAL_AND_CARD (only on BS2000 systems) It is not possible to generate a USER with both a principal and a chip card. |
KC_SC_PRINCIPAL_TABLE_FULL (only on BS2000 systems) The table space reserved for PRINCIPAL during KDCDEF generation is already occupied or no table spaces were reserved for PRINCIPAL. |
KC_SC_PRINCIPAL_TOO_LONG (only on BS2000 systems) The principal is longer than the value specified in MAX PRINCIPAL-LTH. |
KC_SC_INVALID_CLUSTER_RESTART Only for UTM cluster applications: |