Effects of the KDCDEF statements on the generation objects

Not all statements of the KDCDEF generation tool have the same effect on the KDCFILE and ROOT table source. The table below shows which control statements affect which generation objects during the KDCDEF run:

KDCDEF control statement	KDCFILE	ROOT tables	KDCDEF control	Distributed processing via
				LU6.1	OSI TP
ABSTRACT-SYNTAX	X				X
ACCESS-POINT	X				X
ACCOUNT	X
APPLICATION-CONTEXT	X				X
AREA	X	X
BCAMAPPL	X			X
CON	X			X
CREATE-CONTROL-STATEMENTS1
EJECT			X
END			X
EXIT	X	X
KSET	X
LPAP	X			X
LSES	X			X
LTAC	X			X	X
LTERM	X
MASTER-LU61-LPAP	X			X
MASTER-OSI-LPAP	X				X
MAX2	X	X			X
MESSAGE	X	X
MSG-DEST	X
OPTION3	X	X	X	(X)	(X)
OSI-CON	X				X
OSI-LPAP	X				X
PROGRAM	X	X4
PTERM	X
QUEUE	X
REMARK			X
RESERVE	X	X5
ROOT		X
SESCHA	X			X
SFUNC	X
SIGNON	X
SUBNET	X
TAC	X
TACCLASS	X
TAC-PRIORITIES	X
TLS	X
TPOOL	X
TRANSFER-SYNTAX	X				X
ULS	X
USER	X
UTMD	X			X	X
BS2000 specific statements
DATABASE	X	X
DEFAULT6	X	X	X
EDIT	X
FORMSYS	X	X
LOAD-MODULE	X	X7
MPOOL	X	X8
MUX	X
SATSEL	X
TCBENTRY		X
Unix, Linux and Windows system specific statements
CLUSTER	X
CLUSTER-NODE	X
RMXA	X	X
SHARED-OBJECT	X	X

¹Based on the configuration information defined in an existing KDCFILE, the CREATE-CONTROL-
STATEMENTS statement generates an input file containing KDCDEF control statements for a new KDCDEF run.

²The operands CLRCH=, KB=, NB= and SPAB= only affect the generation of the ROOT table source. The other operands only affects the generation of the KDCFILE.

³The effect of the OPTION statement on the KDCFILE and the ROOT table source depends on the values entered for OPTION ...,GEN=.

⁴Only when generating a UTM application without load modules (on BS2000 systems), shared objects (on Unix and Linux systems) or DLLs (on Windows systems).

⁵Only when generating without the operand PROGRAM= and without load modules, shared objects or DLLs.

⁶The effect of the DEFAULT statement on the KDCFILE and the ROOT table source depends on the specified substatement.

⁷Only when extending the generation by n load modules.

⁸Only when generating without load modules.

The KDCDEF control statement OPTION...GEN= is used to define which objects (the KDCFILE, ROOT table sources and UTM cluster files) are to be generated by the KDCDEF generation tool.

When a new ROOT table source is created, this must be compiled (assembled on BS2000 systems) and relinked to your application. Relinking of an application program is only necessary if the table module is not dynamically loaded.
This is not necessary if you merely modify the KDCFILE. You can run the application with the new KDCFILE and the old main routine KDCROOT if no generation parameters that also affect KDCROOT have been changed when creating the new KDCFILE.

The MAX, ULS, CLUSTER and CLUSTER-NODE statements also affect the UTM cluster files during generation of UTM cluster applications. If you change parameters of the ULS, CLUSTER and/or CLUSTER-NODE statement when performing a new generation of a UTM cluster application, you must specify OPTION GEN=CLUSTER in order for the changes to take effect, see also "OPTION - manage the KDCDEF run".