Service restarts

A service restart is generally performed if:

• a client signs on under a user ID that was generated with RESTART=YES,

• and an open service is still known for this user ID in the application.

If a message was sent to the client at the last synchronization point then openUTM sends this message to the client again. The user can then restart the service. Otherwise the open service is continued immediately.

Depending on the type of client and on the sign-on process involved, the following apply to the service restart:

• Standard sign-on process for terminals and TS applications:
  openUTM performs the service restart automatically.

• Standard sign-on process for UPIC clients and OSI TP partner:
  The client must start a specific conversation, which requests the restart using the UTM user command KDCDISP (see the manual „openUTM-Client for the UPIC Carrier System”, for example). A service cannot be restarted from OSI TP clients if the “commit” functional unit was selected.If an open service exists for the user but no service restart is requested the open service will be terminated abnormally.

• Signing on using a sign-on service:
  The sign-on service must initiate the restart or terminate the open service abnormally.

In an application with user IDs, a service is linked to the user ID. This means that the user can continue an interrupted service even on a different client, provided the LTERM partner of the client has the correct authorization and the client type remains the same.