The data structure kc_system_par_str is defined for the parameter type KC_SYSTEM_PAR. In the case of KC_GET_OBJECT, UTM returns following information in kc_system_par_str:
The basic settings of the application, for example if the application is generated for server-server communication.
The openUTM version together with its update information.
The application name and functionality.
The operating system and the name, platform and operating mode of the computer on which the application runs.
Data structure kc_system_par_str |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The fields in the data structure have the following meanings:
appliname | ||
The name of the application specified in the KDCDEF generation in MAX APPLINAME. | ||
utm_version | ||
The openUTM version used, including the update information, for example V07.0A00. | ||
applimode | ||
Specifies if the UTM application is a UTM-S or UTM-F application. | ||
'S' | The application is generated as a UTM-S application (Secure). | |
'F' | The application is generated as a UTM-F application (Fast). | |
system_type | ||
The operating system of the computer on which the application runs. | ||
'B' | BS2000 systems | |
'X' | Unix and Linux systems | |
'N' | Windows systems | |
hostname | ||
The name of the computer on which the application runs. Note for Unix, Linux and Windows systems If this name is longer than 8 characters, the computer name, up to 64 characters long, can be taken from the hostname_long field. In this case, the hostname field contains the first 8 characters of the long name. | ||
destadm | ||
Contains the receiver to which UTM sends the results of KDCADM administration calls that were processed asynchronously (KDCADM asynchronous transaction codes). destadm may contain the following:
If destadm contains blanks, then no receiver is defined. The results of the KDCADM asynchronous transaction code are lost. | ||
tacclasses | ||
Specifies if the application was generated with TAC classes, i.e. if TAC classes were created during the KDCDEF generation. | ||
'Y' | The application was generated with TAC classes. | |
'N' | The application was generated without TAC classes. | |
pgwt | ||
Specifies whether program units containing blocking calls are allowed in the application (for example the KDCS call PGWT). | ||
'Y' | Blocking calls are allowed, i.e. there is at least one transaction code or one TAC class with the property pgwt='Y' (see kc_tac_str.pgwt in "kc_tac_str - Transaction codes of local services" and kc_tacclass_str.pgwt in "kc_tacclass_str - TAC classes for the application"). | |
'N' | Blocking calls are not allowed, i.e. the application contains neither transaction codes nor TAC classes for which pgwt='Y'. | |
kdcload (only on BS2000 systems) | ||
This field always contains 'N'. | ||
load_module_gen | ||
Specifies if the application was generated with load modules (BS2000 systems) or shared objects/DLLs (Unix, Linux and Windows systems), i.e. if at least one LOAD-MODULE statement or SHARED-OBJECT statement was specified for the KDCDEF generation. | ||
'Y' | The application was generated with LOAD-MODULE or SHARED-OBJECT statements. | |
'N' | The application was not generated with LOAD-MODULE or SHARED-OBJECT statements. | |
prog_change_running | ||
Specifies if UTM is currently executing a program change for the application. | ||
'Y' | A program change is currently being executed. | |
'N' | No program change is currently being executed. | |
inverse_kdcdef_state | ||
Specifies whether an inverse KDCDEF is currently running, i.e. if a KC_CREATE_STATEMENTS call is being processed. | ||
'N' | No inverse KDCDEF is currently running. | |
'A' | An inverse KDCDEF run is being prepared. It will be started asynchronously as soon as all transactions that change configuration data have terminated. | |
'Y' | An inverse KDCDEF is currently running. | |
utmd | Specifies if the application is generated for distributed processing using a higher level communication protocol (LU6.1 or OSI TP). | |
'Y' | The application was generated for distributed processing. | |
'N' | The application was not generated for distributed processing. | |
osi_tp | Specifies if the application is generated for distributed processing using OSI TP. | |
'Y' | The application was generated with statements for OSI TP. | |
'N' | The application was not generated with statements for OSI TP. | |
certificate_gen (only on BS2000 systems) | ||
This parameter is no longer supported. | ||
os | Indicates the system platform of the computer, e.g. 'Windows Intel' or 'Solaris Sparc'. | |
bit_mode | ||
Mode in which the operating system runs: '32 bit' 32-bit mode '64 bit' 64-bit mode | ||
cluster_appl | ||
Specifies whether the application belongs to a UTM cluster application. | ||
'Y' | The application is a node application in a UTM cluster application. | |
'N' | The application is a standalone UTM application. | |
hostname_long | ||
The name of the computer on which the application runs. |