Messages of the KDCDEF generation tool

K400	KDCDEF &DEFTYP &VERS started
K401	Please enter control statements
K402	Syntax error: &SYNERR.
K403	Illegal value entered for parameter &PARAM15.
K404	DMS error &ERROR for file &FNAM. The DMS error codes are described on "Error codes during file processing (DMS errors)" .
K405	&ERROR error.
K406	Illegal value entered for operand &PARAM15. &PARVAL8 assumed
K407	Unable to create entry for user "&PARVAL8" in cluster user-file
K408	&STMTNAME name &UTMNAME must not start with "KDC".
K409	LTERM parameter is mandatory for PTERM statements with PTYPE=APPLI, SOCKET, UPIC-L or UPIC-R.
K410	Warning: LTERM is assigned to a PTERM with PTYPE=APPLI, SOCKET, UPIC-L or UPIC-R and an illegal USER or USAGE=O was specified.
K411	Mandatory parameter &PARAM15 has not been declared in any &PARAM15 control statement.
K412	DESTADM &UTMNAME is not defined as asynchronous TAC or as LTERM. No DESTADM assumed
K413	Ambiguous definition of &STMTNAME &OPERAN32 &STRING64
K414	No LSES control statement assigned to LPAP &UTMNAME.
K415	Illegal parameter for MAX DPUTLIMIT1 or DPUTLIMIT2. Default assumed
K416	&PARAM30 defined more than once.
K417	&PARAM10 but type is not "&PARAM30".
K418	CID parameter is mandatory for a PTERM controlled by a printer control terminal.
K419	Printer pool defined but type is not "OUTPUT".
K420	LTERM with USAGE=D must not be assigned to a PTERM with USAGE=O.
K421	&PARAM30 and &PARAM50 are mutually exclusive.
K422	Mandatory parameter &PARAM10 has not been specified.

K423	Warning: size page pool (PGPOOL) is not greater than size LPUT buffer (LPUTBUF).
K424	Invalid key value: &KEYVALUE. Valid key values are: 0 <= key <= MAX KEYVALUE.
K425	&STMTNAME name &PARAM32 has not been defined.
K426	&STMTNAME control statement missing
K427	Event exit &EXITNAME has already been defined.
K428	Invalid CARD parameter: &CARDINFO or POSITION = 0.
K429	Too many database types
K430	Too many &STMTNAME control statements
K431	User "&PARVAL8" from cluster user-file is missing in KDCFILE.
K432	No &STMTNAME with &PARAM32 .
K433	Filebase name is too long. The configuration run will be aborted.
K434	Minimum length of buffer for recovery data, RECBUF parameter, is 1024. 1024 assumed
K435	The event exit &PARAM8 must be assigned to an ASSEMBLER program unit.
K436	MAX statement is missing. The configuration run will be aborted.
K437	Program error in KDCDEF; reason: &TERMREAS. TERMREAS describes the cause that lead to the abnormal termination of the utility. The description of UTM message K060 also helps to clear the error. Action: Proceed as described for K060. In the other cases, there is an error in KDCDEF. Store the documents and write a PR.
K438	More LSES statements than CON statements have been assigned to LPAP &UTMNAME.
K439	In parameter KDCFILE the file base name was specified with a catalogue ID.
K440	&PARAM8 is not allowed in &STMTNAME statements with &PARAM10.
K441	SHARE table &UTMNAME is empty.
K442	Inclusion of &PARAM8 is only meaningful if the &STMTNAME is assigned to a &PARVAL8 program unit.
K443	Inclusion of ULS control statements is only meaningful if USER statements were generated.

K444	OPTION control statement is only effective when reading from stdin.
K445	&PARAM30 no longer supported.
K446	Parameter ignored.
K447	Control statement ignored.
K448	KDCFILE generated with warnings; KAA size: &KAASIZE K
K449	There was at least one ERROR. Configuration run aborted.
K450	KDCFILE generated; KAA size: &KAASIZE K
K451	File &FNAM generated.
K452	Too many &PARAM10 names. The configuration run will be aborted.
K453	BCAMAPPL name different from APPLINAME is only allowed for a &STMTNAME with PTYPE=APPLI, SOCKET or UPIC-R.
K454	Length of LTERM parameter &UTMNAME incompatible with NUMBER parameter.
K455	TAC assigned to STACK parameter may not be defined with TYPE=A or CALL=NEXT.
K456	It is not possible to assign a group-LTERM to a PTERM
K457	Warning: &PARAM10 larger than &PARAM10A
K458	LTERM &PARAM8 has been assigned as CTERM for LTERM &PARAM8A. "USAGE = OUTPUT" is not meaningful.
K459	The LTERM specified at GROUP must not be a group-LTERM itself.
K460	File &FNAM processed.
K461	&STMTTP30 &STMTNM30 not supported by &UTMVAR
K462	Only one OSI-CON connection group is allowed to be active with local partner application &PARAM8.
K463	&PARAM30 set to &PARAM30.
K464	Length of session names + length of associations > 8.
K465	&STMTNAME control statement is mandatory if &PARAM30 is generated.
K466	Parameter &PARAM30 is mandatory if &PARAM30 is generated.
K467	Error: Multiple entries for user "&PARAM8" found in cluster user-file
K468	Password parameter does not fit security level.
K469	Parameter &PARAM32 only allowed if &PARAM32.
K470	No user is able to call KDCSHUT.

K471	&OPERAND&PARAM10 already set.
K472	&PARAM32 too long.
K473	Parameter &PARAM10 used more than once for &PARAM30
K474	Parameter &PARAM30 is illegal if &PARAM30 is generated.
K475	Parameter &PARAM30 not needed if &PARAM30 is generated.
K476	In &STMTNAME control statements &OPERAND is given more than once for PRONAM=&PARAM8 and BCAMAPPL=&PARAM8 .
K477	Parameter &PARAM30 is illegal if any &PARAM30 is given.
K478	Control statement &STMTNAME is illegal if &PARAM30 is given.
K479	&STMTNAME &PARAM50 not used.
K480	Too many &STMTNAME control statements for this &PARAM30.
K481	The primary LTERM of a group must not be slave of a bundle.
K482	EXIT and TAC must be in the same LOAD-MODULE if the exit program is referencing a LOAD-MODULE with LOAD-MODE=ONCALL.
K483	&PARAM32 must not reference a &STMTNAME with &PARAM32 .
K484	&PARAM32 with &PARAM32 not generated.
K485	Control statement too long.
K486	Different libraries given for same DATABASE TYPE.
K487	Cannot assign a master LTERM of bundle to PTERM.
K488	All slave LTERMs of bundle must be assigned to PTERMs with identical PTYPE (APPLI or SOCKET).
K489	Master LTERM of bundle must not be a slave itself.
K490	Master LTERM must be generated with QAMSG=YES and RESTART=YES. Parameters changed.
K491	&OPERAND &PARAM32 &PARAM20 will not be supported in the next UTM version.
K492	Note: multiple ACCESS-POINT statements may cause problems.
K494	Operand &PARAM30 is mandatory if &STMTNAME control statement is given more than once.
K495	Standard message module not found in any MESSAGE control statement or not defined by MAX control statement.

K496	File &FNAM corrupted or not a KDCFILE.
K497	KDCDEF &VER1 / &OST1/ &BMD1cannot read KDCFILE &VER2 / &OST2/ &BMD2
K498	There are no &STMTNAME control statements to be created.
K499	&PARAM30 in &STMTNAME control statement and &PARAM30 do not match.

K500	No file(s) generated.
K501	Illegal character "&CHAR1" in string: &STRING64
K502	Number of free &PARAM10 entries:&PARAM11
K503	The referenced ACCESS-POINT &PARAM8 must include an APPLICATION-ENTITY-QUALIFIER because the referenced OSI-LPAP &PARAM8 includes an APPLICATION-CONTEXT with the ABSTRACT-SYNTAX CCR.
K504	OSI-CON &PARAM8 references same OSI-LPAP but different ACCESS-POINT.
K505	The operand &PARAM32 is mandatory if the referenced APPLICATION-CONTEXT includes the ABSTRACT-SYNTAX CCR.
K506	An APPLICATION-CONTEXT including the ABSTRACT-SYNTAX CCR must not be used because the UTMD control statement does not specify an APPLICATION-PROCESS-TITLE.
K507	Too many &PARAM32
K508	Error occurred during generation of RSA-Keys.
K509	OSI-CON &PARAM8 references same LOCAL-ACCESS-POINT and an OSI-LPAP with identical APPLICATION-ENTITY-QUALIFIER and APPLICATION-PROCESS- TITLE.
K510	Operand &PARAM32 requires at least &PARAM8 parameters.
K511	At most &PARAM11 concurrent stacked services will be possible.
K512	At most &PARAM11 concurrent sign on and/or stacked services will be possible.
K513	KDCDEF will now generate new RSA-Keys. Depending on key length and system configuration this process can take a considerable amount of time. Please wait ...
K514	Generation of RSA-Keys completed

K515

Warning: For proper operation the application needs RSA-keys. However, no RSA-keys have been generated.

If objects are generated with encryption levels, the application requires RSA keys in order to run correctly. If no RSA keys are available in the application, the application can be operated but with certain restrictions. TACs with encryption levels cannot be called and no connection can be set up to PTERMs or TPOOLs with encryption levels. Three responses are possible.

• The RSA keys can be transferred from an old KDCFILE to the new KDCFILE using KDCUPD before the application is started, or

• the KDCDEF run can be repeated with the GEN-RSA-KEYS=YES operand in the OPTION statement, or

• the application can be started and the required RSA keys can be created and activated by administration (e.g. using WinAdmin/WebAdmin).

K516

Error &DIAG1 for cluster user-file &STRING64

The insert &DIAG1 describes the cause of the error; the insert &STRING64 contains the file name.

The insert &DIAG1 can have the following values:

Value	Meaning
1	OPEN_ERROR Error opening the file.
2	CLOSE_ERROR Error closing the file.
3	FILE_ERROR The file is inconsistent.
4	LOCK_ERROR Error requesting the file lock.
5	UNLOCK_ERROR Error releasing the file lock.
6	USER_NOT_FOUND KCCUFUE sends an incorrect return code on an update to a user entry; the second insert contains the name of the user
7	UNEXPECTED_RETURNCODE An unexpected return code was returned by a called function; the second insert contains the value of the return code
8	KDCDEF_RUNNING The cluster user file is already locked by a KDCDEF run
9	FILE_IS_EMPTY The cluster user file is cataloged but empty
10	Error on getLocalHostName call The second insert contains the error code.
11	NO_XCS_GROUP The computer does not belong to an XCS cluster; the "distributed lock" function is not therefore available.

K517	&PARAM30 not supported for &PARAM30
K518	File &FNAM already exists. The configuration run will be aborted.
K521	MAX PRIVILEGED-LTERM=&UTMNAME is not defined as Dialog-LTERM.
K522	Note: No privileged LTERM generated (see MAX PRIVILEGED-LTERM=)
K523	K523 The LISTENER-PORT &PORT has already been assigned the LISTENER-ID &LISTENID.