The TLS is assigned to a connection point (LTERM, LPAP or OSI-LPAP partner) and is used to store information that is to be available independently of the life of the services and the operating time of the application. This long-term storage may consist of multiple blocks whose names you define in the TLS statements. A separate TLS statement is used to define each TLS block name. You can specify multiple TLS statements. The defined block names are the same for all LTERM/LPAP/OSI-LPAP partners. A particular block can be identified by its block name and the names of its LTERM/LPAP/OSI-LPAP partners (see the openUTM manual “Generating Applications”).
For example, you can use a TLS
to generate statistics for an LTERM, LPAP or OSI-LPAP partner or
to log access violations, for a example for an MSGTAC exit, see "Example of a MSGTAC program unit" (Asynchronous service MSGTAC).
A program unit of a dialog service can only access blocks belonging to its "own" TLS, i.e. only the TLS of the LTERM, LPAP or OSI-LPAP partner via which the service was started.
A program unit run of an asynchronous service can read blocks from all the LTERM, LPAP or OSI-LPAP partners of the UTM application.
You use GTDA to read and PTDA to write a TLS block. openUTM locks a TLS block from the time of access to the end of the transaction. You can specify the maximum wait period at generation (KDCDEF statement MAX, Operand RESWAIT, value time1). If a TLS has only been read, you can use the UNLK call to explicitly unlock the TLS (see also the section "Action with locked storage areas (TLS, ULS and GSSB)").
The TLS is used to store 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 the UTM application after an interruption of operation provided that the same KDCFILE as before is used or if the KDCUPD tool is used to transfer the user data to a new KDCFILE.
Unix, Linux and Windows systems
In UTM cluster applications TLSs are only supported locally in the nodes , i.e. each node application has its own TLSs.