A program unit can use up to 99 other areas, which you define with the KDCDEF statement AREA (see the openUTM manual “Generating Applications”). AREAs are shared storage areas available to the UTM application. The structure of these areas is not predefined by openUTM and you can define them as you wish.
The addresses of such storage areas are passed along with SPAB and KB as additional parameters at the start of the program. These areas are not subject to the transaction concept: openUTM does not save these areas, nor does it roll back them with an RSET or lock them. This means that the application program alone is responsible for managing these storage areas.
For information about how you define such an area in your programming language, refer to "Other data areas (AREAs)" for C/C++ and "COBOL program units as subroutines" for COBOL.
When program units which use AREAs are transferred from one application to another, the use of AREAs may cause problems, for example because of differences in parameters. Alternatives to the use of AREAs are described on "Other data areas (AREAs)" for the C/C++ programming language and "COBOL program units as subroutines" for COBOL.
Unix, Linux and Windows systems
AREAs in a UTM cluster application are always node-specific, i.e. one node cannot access the AREAs in another node.