Result of the KDCDEF run

Depending on the entries made during generation, the KDCDEF generation tool creates the following:

• BS2000 systems:

  • the KDCFILE with the main file filebase.KDCA and, if dual-file operation is used, the duplicate file filebase.KDCB

  • the ROOT table source

  • the page pool filebase.PnnA, possibly with the duplicate filebase.PnnB

  • the restart area filebase.RnnA, possibly with the duplicate filebase.RnnB

• Unix, Linux and Windows systems:

  • the main file KDCA in the filebase directory and, if dual-file operation is used, the duplicate file KDCB, also in the filebase directory

  • the ROOT table source in the form of a C/C++ source

  • the page pool PnnA, possibly with the duplicate PnnB, in the filebase directory

  • the restart area RnnA, possibly with the duplicate RnnB, in the filebase directory

• Additionally, if a UTM cluster application is being generated, see also the section "Notes on generating a UTM cluster application on Unix, Linux and Windows systems":

  • the cluster configuration file

  • the cluster user file

  • the cluster page pool files (a control file and one or more files for the user data)

  • the cluster GSSB file

  • the cluster ULS file

The format of the KDCFILE is described in detail in section "The KDCFILE".

KDCDEF outputs a message to SYSOUT (BS2000 systems) or stderr (Unix, Linux and Windows systems) indicating whether the KDCFILE was created successfully and specifying the size of the KAA (KDC Application Area) occupied by the application. It also outputs a log containing the control statements and any error messages to SYSLST (BS2000 systems) or stdout (Unix, Linux and Windows systems).

Note for KDCDEF on BS2000 systems

If the KDCDEF generation tool terminates abnormally due to an error, it sets process switch 3 (as occurs with all UTM tools). In this case, no files are generated apart from those created by the CREATE-CONTROL-STATEMENTS statement.