KDCSHUT - Terminate an application run

KDCSHUT allows you to terminate a UTM application. You have the following options:

In UTM cluster applications, you can specify whether the application run is to be terminated at all nodes or only at the node at which the call is issued.

You have the following options:

• You can terminate the application run normally. UTM terminates the application run as soon as all running dialog steps have been completed (NORMAL).

• You can schedule the application to terminate after a specified period (WARN).

• You can terminate the application once all the UTM-D dialogs have been terminated and all the UTM-D connections have been disconnected and at the latest, however, after a specified period (GRACE).

• You can kill the application, i.e. perform an immediate abnormal termination (KILL).

You should note the following if you kill an application:

You cannot kill the application by means of an asynchronous service, i.e. the asynchronous transaction code KDCSHUTA KILL has no effect.

You should note the following when shutting down applications with distributed processing:

• You should preferably terminate applications with distributed processing with KDCSHUT GRACE or alternatively with a warning (KDCSHUT WARN).
  The use of KDCSHUT GRACE or WARN reduces the probability that services will be killed and distributed transactions will remain in transaction status P (preliminary end of transaction).

• An application with distributed processing is not terminated normally if, at shutdown time, there are still services with transaction status P (prepare to commit) or if acknowledgments are still outstanding for asynchronous messages to a partner server. In such cases, openUTM issues message K060 with ENDPET as the reason for termination. No dumps are generated.

  Consequently, for KDCSHUT WARN or GRACE, you should specify a time that is greater than the maximum period that a distributed transaction remains in the state PTC (i.e. transaction status P). This reduces the probability of distributed transactions still being in this state at the end of the application and of the application being terminated abnormally with ENDPET.

For further information about shutting down/terminating a UTM application, please refer to the openUTM manual “Using UTM Applications”..

---

KDCSHUT       { GRACE [ ,TIME=time_min ] | KILL | NORMAL |
                WARN [ ,TIME=time_min ] }

              [ ,SCOPE= { LOCAL | GLOBAL } ]

---

For administration using message queuing you must enter KDCSHUTA.

GRACE		All the active LPAP and OSI-LPAP connections are set to QUIET. The application is terminated as soon as all the UTM-D connections have been disconnected or, at the latest, when the defined time has expired. On BS2000 systems, at all active terminals, a note in the system line indicates the impending shutdown of the application. This is accompanied by an indication of the time remaining before shutdown (see TIME operand). After KDCSHUT GRACE has been entered, only users with administration authorizations may sign-on. It is then only possible to start services whose service TAC belongs to an administration program unit. All UTM user commands with the exception of KDCOUT are still executed. The application run is terminated, i.e. it is shut down immediately. Open services will not be terminated first. A UTM dump with the dump code='ASIS99' is created by all processes.
NORMAL		Termination of the application is initiated immediately. No more users can sign on to the application and users cannot start any new services. No new dialog entries are processed. If the new dialog entry is a multi-step transaction, the multi-step transaction is rolled back to the last synchronization point. All logical connections to clients and printers are shut down. Users can continue working on open services after the next application start.
WARN		All active connections from LPAPs and OSI-LPAPs are set to QUIET. On BS2000 systems, at all active terminals, a note in the system line indicates the impending shutdown of the application. This is accompanied by an indication of the time remaining before shutdown (see TIME operand). After KDCSHUT WARN has been entered, only users with administration authorizations may sign-on. It is then only possible to start services whose service TAC belongs to an administration program unit. All UTM user commands with the exception of KDCOUT are still executed.
TIME=time_min
		Only works together with WARN and GRACEFUL. Meaning for GRACE: time_min is the maximum time in minutes after which the application will be terminated. Meaning with WARN: time_min is the time in minutes after which the application is terminated. Maximum: 255 minutes Minimum: 1 minute openUTM rejects the entry TIME=0. Note for BS2000 systems At all active terminals, a note in the system line indicates the impending shutdown of the application. This is accompanied by an indication of the time remaining before shutdown. If a very large number of terminals are active (configurations with many terminals) then it takes a certain amount of time to issue the shutdown notification. You should therefore not choose too short a value for TIME. During KDCDEF generation, TAC KDCSHUT was assigned the maximum CPU time required by KDCSHUT to perform a shutdown. Select a sufficiently long period of time for applications involving numerous terminals. If this period of time is not long enough, openUTM terminates the process and issues the message K017.
SCOPE=		Specifies the scope of application of the command. This parameter is only relevant for UTM cluster applications.
	LOCAL	The command only applies to local node applications. Default value.
	GLOBAL	The command applies to all the node applications in the UTM cluster application. SCOPE=GLOBAL is rejected if the running node applications have not all been generated in the same way. This may occur, for example, if an update generation of the KDCFILE is performed without fully shutting down the UTM cluster application.

Output from KDCSHUT

The message "COMMAND ACCEPTED" is displayed on the administrator terminal. UTM displays the actual termination of the application in the following manner:

• BS2000 systems: The end of the application is only displayed on the console. The display appears as soon as the last process in the UTM application has finished.

• Unix and Linux systems: The end of the application is logged by the utmmain process after stdout and stderr.

• Windows systems: The end of the application is logged in stdout and stderr by the process utmmain. If the application is started as a service, messages are also entered in the event logfile of the Windows system.