The ULS is a long-term storage area which is assigned to each user ID (USER), LU6.1 session (LSES) and OSI-TP association (ASSOCIATION-NAMES of the OSI-LPAP statement). This long-term storage may consist of multiple blocks whose names you define in the ULS statements. A separate ULS statement is used to define each ULS block name. The defined block names are the same for all user IDs. A particular block can be identified by its block name and the name of the associated user ID (see the openUTM manual “Generating Applications”).
You can, for example, use the ULS to record statistics about user IDs.
Without administrator privileges, a program unit can only access the ULS blocks of the user ID under which it was started. To access ULS blocks of other user IDs, the program unit must have administrator privileges.
You use the SGET call to read and the SPUT call to write a ULS block. openUTM locks a ULS bock from the time of access to the end of a transaction. You can specify the maximum wait period at generation (KDCDEF statement MAX, Operand RESWAIT, value time1). If a ULS block has only been read, you can use the UNLK call to unlock the block explicitly (see also section "Action with locked storage areas (TLS, ULS and GSSB)").
The ULS is used for storing information that has to be available independently of the life of the services and the operating time of the application. It is thus again made available to a UTM application after an interruption of operation, provided that, in the case of a standalone application, the same KDCFILE is used as before the interruption or if the user data has been transferred to a new KDCFILE using the KDCUPD tool.
Unix, Linux and Windows systems
In UTM cluster applications, user-specific, long-term storage is supported throughout the cluster. I.e. the data is stored in the cluster page pool and is therefore available for all users in all node applications. This means that all the node applications have the same view of the data in the storage area, see also “Storage location for user data” (KDCS storage areas in openUTM).
The ULS is used for storing information that has to be available independently of the life of the services and the operating time of the application. It is thus again made available to a UTM application after an interruption of operation, provided that, in the case of a UTM cluster application, the same cluster page pool is used as before the interruption or if the user data has been transferred to the new cluster page pool using the KDCUPD tool.