A side information file (upicfile) must be created for the carrier system UPIC. See figure 21 below to see which entries you must make in the upicfile, and how these correspond to the local configuration file and KDCFILE of the UTM partner. For more information, please refer to section “Side information for stand-alone UTM applications” .
Figure 21: Conformance considerations when configuring server and client
Unix, Linux and Windows systems
An entry must start with SD or ND (Unix, Linux and Windows systems) if the server is a stand-alone application on a Unix or Windows system. If the server is a UTM cluster application then the entries for the node applications must start with CD, see section “Side information for UTM cluster applications”.
utmappl is the name of the UTM application, as configured with the KDCDEF statements MAX APPLINAME or BCAMAPPL=. Address information, such as IP address and port number, must be specified in the upicfile. With UTM applications on BS2000 systems, no UPIC communication can be made via the application name defined with MAX APPLINAME, since this is defined with T-PROT = NEA.
The transaction code tac in the SVCU statement must be defined with a TAC statement in the UTM configuration.
If you specify the “upic” parameter for xatmigen, a upicfile is created in which the individual lines need only be extended to include the partner parameter (using an editor). If you do not specify the “upic” parameter, you must create the entire upicfile yourself.