In UTM cluster applications, a service restart is possible in all node applications for all genuine user IDs that have been generated with USER ..., RESTART=YES. Any genuine user generated with USER ...,RESTART=YES is always signed on exclusively, i.e. the user can only be signed on once to the UTM cluster application at any given time. Furthermore, such users can have no more than one open dialog service throughout the entire cluster.
The open services of such users can be continued in any node application provided that the open service is not bound to a node application, see below. A bound service can only be continued in the node application to which it is bound.
When a node application is terminated service data is lost for all services bound to this node. See next section "Node-bound services".
Node-bound services
The following services are always node bound:
Services that have started communications with a job receiver via LU6.1 or OSI TP and for which the job-receiving service has not yet been terminated
Inserted services in a service stack
Services that have completed a SESAM transaction
In addition, 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.
If a user who wants to sign on at another node application even though his service is bound to a 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 (prepare to commit),
or the UTM cluster application was generated with CLUSTER ... ABORT-BOUND-SERVICE = NO.
Connection user IDs
The service restart for connection user IDs of TS applications is bound to the connection and therefore to the node application. If a connection user ID has been generated by a TS application with RESTART=YES then it can have a service context that permits restarts in every node application.