kc_utmd_par_str - Parameters for distributed processing

The data structure kc_utmd_par_str is defined for the parameter type KC_UTMD_PAR. In the case of KC_GET_OBJECT, UTM returns the basic settings for distributed processing via LU6.1 and OSI TP in kc_utmd_par_str.

Data structure kc_utmd_par_str

char application_process_title[10][8];

char maxjr[3];

char rset;

The fields in the data structure have the following meanings:

application_process_title

Only of relevance for distributed processing via OSI TP.
application_process_title contains the application process title of the local application (see the openUTM manual “Generating Applications”).

An application process title consists of at least two, but at most 10 components.
Each individual component is a positive integer and is a maximum of 8 characters long.

UTM returns one field element per component of the application process title, i.e. the number of field elements in application_process_title that contain data corresponds to the number of components generated. The rest of the field elements are set to binary zero.

If no application process title was generated, then all field elements of application_process_title are set to binary zero.

maxjr ( maximum number of job receivers)

Specifies the maximum number of remote job-receiving services that may be addressed at one time within the local application.

This value, in percent, corresponds to the total number of sessions and associations generated (=100%). The value must be between 0 and 200.

A value greater than 100 means that openUTM APRO calls for addressing remote services are accepted, even if no session or association is (yet) free for this job at this time.

rset

Specifies how rolling back a local transaction will affect the distributed transaction when distributed processing is utilized.

A local transaction can be rolled back by a RSET call from a program unit or by rolling back a database transaction that is involved in the local transaction.
rset can contain one of the following values:

'G'

(GLOBAL) After rolling back the local transaction the program unit must be terminated in such a manner that UTM rolls back the distributed transaction.

'L'

(LOCAL) Rolling back a local transaction has no influence on the distributed transaction. The distributed data can become inconsistent when some of the local transactions involved in a distributed transaction are rolled back and others continue as before. If rset='L', then global data consistency is not guaranteed by the system components involved. This task then becomes the responsibility of the application program units. They must decide in which situations the distributed transaction can be sensibly terminated and in which situations they must be rolled back.