You must create the upicfile yourself. This file has the following format:
In Unix, Linux and Windows systems the file must contain only text and must be called upicfile. If you choose a different name, you must also set the UPICFILE environment variable accordingly.
On BS2000: You must create a SAM file with the name
upicfile. If you choose a different file name, you must set the job variable link *UPICFIL accordingly.
This file is used by all client programs, e.g. in the Initialize_Conversation() or Enable_UTM_UPIC() calls.
- On Linux Unix and Windows systems: The environment variable UPICPATH determines the directory; std = current directory
- On BS2000: the job variable linkname * UPICPAT determines a partially qualified file name; std = expiration identifier of the UPIC client
The upicfile can contain the following types of entries:
communication partner entries which are addressed in the client program using the symbolic destination name:
Entries for the direct addressing of UTM applications (identifier HD or SD)
Entries for a list of communication partners (identifier ND) from which the client program selects an available UTM partner via the load balancer. These
communication partners must be standalone UTM applications.Entries for a list of communications partners in an openUTM cluster (identifier CD) from which the client program selects an available cluster node via the load balancer.
Side information entries for the local application which are addressed in the client program using the local application name (identifier LN). These entries are optional.
To make the layout of the upicfile legible, the file may also contain blank lines and/or comment lines. Comment lines are identified by an asterisk („*“) in column 1. Note that a semicolon is always interpreted as an end-of-line character, even within a comment line.