The objects of a UTM application are combined in shared name spaces which are defined for specific object types. The names and address of objects of the permitted types must be unique throughout the name class. A name or address must only be assigned once within the name class. There are three name classes:
Name class 1
LTERM partners (statement LTERM ltermname)
LTERM partners created by openUTM for the LTERM pools
(statement TPOOL ...,LTERM=ltermprefix, NUMBER=number)transaction codes and TAC queues (statements TAC tacname)
LPAP or OSI-LPAP partners for server-to-server communication
(statements OSI-LPAP osi_lpap_name and LPAP lpapname)
Name class 2
user IDs (statement USER username)
sessions for distributed processing based on LU6.1 (statement LSES sessionname)
connections and associations for distributed processing based on OSI TP (statement OSI-LPAP..., ASSOCIATION-NAMES=, ASSOCIATIONS=)
Name class 3
clients and printers (PTERM statement)
Clients are terminals, UPIC-clients, transport system applications (DCAM, CMX and socket applications), and UTM partner applications that do not use a higher-level protocol (LU6.1, OSI TP) during communication.name of the partner application for distributed processing based on LU6.1 (CON statement)
name of the partner application for distributed processing based on OSI TP (OSI-CON statement)
multiplex connections of a UTM application on BS2000 systems (MUX statement)
The objects listed in name class 3 are communication partners of the UTM application. openUTM must be able to uniquely identify these objects and the connections to them. For this purpose, it assigns a name triplet to each communication partner. This name triplet must be unique within the UTM application and consists of the following components:
the name of the communication partner.
This is specified in ptermname in the PTERM statement, in remote_appliname in the CON statement, in TRANSPORT-SELECTOR= in the OSI-CON statement and in name in the MUX statement.
On BS2000 systems the BCAM name of the communication partner must be specified.the name of the system on which the communication partner is located.This is specified in the PRONAM= operand of the PTERM, CON and MUX statements and in the NETWORK-SELECTOR= operand of the OSI-CON statement.
the name of the local application via which the connection to the communication partner is established. This is specified in the BCAMAPPL= operand of the PTERM, MUX and CON statements and in the LOCAL-ACCESS-POINT= operand of the OSI-CON statement.