In UTM cluster applications, service restarts are supported globally throughout the cluster for all genuine user IDs generated with RESTART=YES. This means that after signing off at the node application, a user is able to continue an open dialog service at another node application provided that the service is not a node-bound service.
Node-bound services
The following services are node-bound:
Services that have started communication with a job receiver via LU6.1 or OSI TP and the job receiver service has not yet been terminated
Inserted services in a service stack
In addition, a service associated with a user is node-bound as long as the user is signedon at a node application. Hence, following abnormal termination, an open service is bound to a node application if the user was signed on at the node application at the time the application was terminated.
Node-bound services can only be continued at the node to which they are bound.
If a user who has a node-bound service wants to sign on at another node application then the sign-on attempt is rejected if
the node application to which the service is bound is running, or
the bound service has a transaction in the state PTC, or
the UTM cluster application has been generated with ABORT-BOUND-SERVICE = NO.
If an attempt by a user with a node-bound service to sign on at another node application is accepted, then the open service is not continued but is instead terminated abnormally the next time the node application to which it is bound is started.
A connection user ID is bound to the connection. A connection user ID generated with RESTART=YES can have an open service in every node application.
In applications without USER, an LTERM generated with RESTART=YES can have an open service in every node application.
Service restarts in UTM-F applications
Although service restarts are also supported in UTM-F applications, the service data is not saved until the user signs off.
As a result, following an abnormal termination of a node application, no further service restart is possible if the user
was signed on at the node application at the time it was terminated abnormally or
has a service bound to the node application that has terminated abnormally.