Configuration without upicfile

For communication between UPIC and UTM, it is necessary for both the UPIC client and the UTM server to sign on to the local communication system with a name. UPIC signs itself on to the communication system with the local_name, UTM with the BCAMAPPL (application name). A communication relationship between the client and server is defined by UPIC addressing the UTM application in this case from BCAMAPPL and host name. UTM receives the local name of the client in order to be able to authenticate the client (PTERM statement).

openUTM only accepts the connection if a PTERM statement or a suitable TPOOL exists for the complete address consisting of local name, process name and BCAMAPPL.

UPIC addresses the UTM application using the partner_LU_name. A partner_LU_name is designated as single-part if it only contains the address information about the name of the UTM partner application. The two-part partner_LU_name is identified by the fact that it contains a dot (“.”). The part to the left of the dot is the application name, the part to the right of the dot is the system name. The dot itself does not form part of the address.

The values for TSEL and HOSTNAME are derived from the partner_LU_name. The left part, up to the period (".") i.e. the application name, is assigned to TSEL. The part to the right of the period, i.e. the host name, is assigned to HOSTNAME.

Address components

• local_name

  The local_name is set with the Enable_UTM_UPIC() call. A preset local_name is used if an empty local_name (8 blanks and/or length = 0) is passed with this call. The preset local_name is assigned the following default value:

  • On Unix, Linux and Windows systems:

    • UPICL with UPIC-L

    • UPICR with UPIC-R

  It is overwritten with the call Specify_Local_Tsel().

upicfile comparison

The value of local_name can be overwritten using a upicfile. The upicfile is described in section “The side information file (upicfile)”.

• partner_LU_name

  Following the Initialize_Conversation call, the partner_LU_name is assigned the following default value:

  • On Unix, Linux and Windows systems:

    • UTM with UPIC-L

    • UTM.local with UPIC-R

  It is overwritten with the Set_Partner_LU_Name() call.

  upicfile comparison

  The value of partner_LU_name can also be overwritten using a upicfile. The partner_LU_name in turn is addressed using the Symbolic Destination Name in the upicfile.
  The upicfile is described in section “The side information file (upicfile)”.

• Symbolic Destination Name

  The Symbolic Destination Name is precisely 8 characters in length and is passed in the Initialize_Conversation call. An empty Symbolic Destination Name consists of precisely 8 blanks.
  An empty Symbolic Destination Name must be passed as the Symbolic Destination Name in the Initialize_Conversation call.

  upicfile comparison

  When a upicfile is being used, an empty Symbolic Destination Name can be passed in the Initialize_Conversation call.
  The upicfile is described in section “The side information file (upicfile)”.