Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Order of the control statements

Apart from the following exceptions, the control statements can be entered in any order. Apart from END and UTMD, all control statements can be entered several times.

  • The END statement is always specified last, and concludes the sequence of control statements.

  • In the OPTION statement, the last parameter value specified always applies.

  • The order of the AREA statements indicates the order in which these areas must be specified in the parameter list and declared in the program unit (e.g. in the LINKAGE-SECTION in COBOL). See the openUTM manual „Programming Applications with KDCS”.

  • The sequence of the EXIT statements with USAGE=START and USAGE=SHUT defines the sequence in which the programs of the event exits START and SHUT are executed when the application is started or shut down.

  • The master LTERM of a LTERM bundle must be generated before the slave LTERMs of this LTERM bundle.

  • The primary LTERM of a LTERM group must be generated before the alias LTERMs of this LTERM group.

  • The defined subnets are checked against the IP address of a connection request externally in the same order as that in which the SUBNET statements are entered.

BS2000 systems:

  • The DEFAULT statement refers only to the control statements entered thereafter.

  • Load modules are loaded in the same order as that in which the LOAD-MODULE statements are entered. Refer to the LOAD-MODULE statement in section "LOAD-MODULE - define a load module (BLS, BS2000 systems)" and openUTM manual “Using UTM Applications on BS2000 Systems”.

Unix, Linux and Windows systems:

  • Shared objects/DLLs are loaded in the same order as that in which the SHARED-OBJECT statements are entered.