Each communication partner from the list of UTM partner applications is addressed using an identical symbolic destination name in the client program. This name is specified when initializing a conversation (call Initialize_Conversation). For each symbolic destination name used in the program, you must create entries in the upicfile.
To enable a UPIC client to access all communication partners, you create an entry in the upicfile for each partner. When doing this, please observe the following rules.
Rules for configuring a list of communication partners
For a symbolic destination name, you must create a separate entry in the upicfile with the identifier ND for each partner application. For example, if the list consists of three UTM applications, you must create three entries with the same symbolic destination name.
All entries for a particular symbolic destination name must immediately follow one another, see example below.
The communication end points can belong to one specific UTM application or to different UTM applications. In this case, the UTM applications should be running on the same platform in order to avoid code conversion problems.
Example list of partner applications
You want to configure a list of three application names for a symbolic destination name (service1). The application names are distributed over two different standalone UTM applications running on the computers HOST01 and HOST02. In the UTM application on HOST01 the two application names (BCAMAPPL) UTMAPPL1 and UTMAPPL2 are configured, and in the UTM application on HOST02 the application name UTMAPPL1.
The entries could, for instance, be as follows:
* entries for list of three communication end points in two UTM standalone applications NDservice1 UTMAPPL1.HOST01 TAC1 NDservice1 UTMAPPL2.HOST01 TAC1 NDservice1 UTMAPPL1.HOST02 TAC1