In order for an OSI TP partner to sign on to the UTM application, the partner must know the the address of the OSI TP access point of the UTM application. This data is configured in the OSI TP partner.
In the case of OSI TP partner, the connection setup initiative can come from either the partner or openUTM. This means that several parallel connections, known as associations, can be established via one logical connection. An association name is assigned to each association.
Following a successful connection setup, the client first signs on under its association name. This name is made up of the name specified in OSI-LPAP ...,ASSOCIATION-NAMES= and a serial number, e.g. ASSOC03.
Once an application context containing the abstract syntax UTMSEC has been generated for OSI TP communication between the two partners (in case of openUTM in the APPLI-CATION-CONTEXT parameter of the OSI-LPAP statement), the communication partner can pass a genuine user ID and authorization data in the relevant log fields. openUTM then signs on with the user ID that has been passed. This sign-on then applies for the duration of the OSI TP dialog. The user is then signed off again at the end of the OSI TP dialog.
If no genuine user ID is passed, the client remains signed on under its association name.