The restart function for a client is linked to the user ID that the client has used to sign on to the UTM application.
Restart function for real user IDs
The restart function for real user IDs is specified in the RESTART operand of the USER statement.
USER userid-name...RESTART=YES | NO
If this is generated as RESTART=YES then the type of client and any generated sign-on services will also play a role in service restart:
If a sign-on service has been generated for a client that signs on using this user ID, then this service will control whether a service restart is performed or whether an open service is terminated abnormally, see the description of the sign-on service in the openUTM manual „Programming Applications with KDCS”.
If a terminal or TS application does not sign on via a sign-on service, then openUTM always initiates a service restart.
If a UPIC client does not sign on via a sign-on service then the UPIC client must explicitly initiate a service restart, otherwise an open service is terminated abnormally see the manual „openUTM-Client for the UPIC Carrier System”.
When using OpenCPIC clients, restart is only possible with cooperative processing (functional unit not equal to "Commit"). The OpenCPIC client must explicitly initiate a service
Restart function for connection user IDs
If individually generated TS applications sign on via implicit (created by openUTM) connection user IDs, then the restart function is controlled by the RESTART operand in the LTERM statement:
LTERM ltermname ... RESTART=YES | NO
This parameter of the LTERM statement is irrelevant for the service restart if the TS application is signed on via an explicitly generated connection user ID or a real user ID.
Explicitly generated connection user IDs to UPIC clients are generated in any case and without any message with RESTART=NO.