Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

obj_type=KC_PROGRAM

To add a new program unit or VORGANG exit to the configuration you must place the data structure kc_program_str in the data area.

The table below shows you how to supply data to the fields in the data structure kc_program_str.


Field name 1

Meaning

m

pr_name[32]    

Name of the program unit. The name may be up to 32 bytes long.
You must observe the conventions in section "Format and uniqueness of object names" when specifying a name. The name of a program unit that has been deleted from the configuration cannot be used.
In UTM applications on BS2000 systems you specify the ENTRY or CSECT name of the program unit.

(m)

compiler

Compiler or ILCS-capability of the compiler used to compile the program unit.

In UTM applications on BS2000 systems the compiler specification is mandatory.
For all program units that support ILCS you must specify 'I' for ILCS for the compiler.

In UTM applications on BS2000 systems the following settings are possible:
'I' for ILCS (Inter Language Communication Services)
'A' for the assembler compiler ASSEMB
'C' for the C compiler (UTM sets this to 'I')
'1' for the COBOL compiler (COB1)
'F' for the FORTRAN compiler (FOR1)
'X' for PASCAL-XT
'P' for PLI1
'S' for SPL4

In a UTM application on a Unix, Linux and Windows system the following values are possible:
'C' for the C compiler
'+' for the C++ compiler
'2' for the COBOL compiler of Micro Focus
'3' for the NetCOBOL compiler from Fujitsu

m

load_module[32]

                                

Name of the load module (BS2000 systems) or of the shared object/DLL (Unix, Linux and Windows systems) into which the program unit is linked.
The name can be up to 32 characters long.

BS2000 systems:
The load module must be statically configured using the KDCDEF control statement LOAD-MODULE. It may not be statically linked to the application program.

Unix, Linux and Windows systems:
The shared object must/DLL be statically configured using the KDCDEF command SHARED-OBJECT.

1

All fields in the data structure kc_program_str that are not listed and all fields that are not relevant to the operating system you are using are to be set to binary zero. The data structure is described in full in chapter "kc_program_str - Program units and VORGANG exits".