In performing some types of repairs, you may have to stop one or more processes. You can choose from several methods.
If the process' principal device is not available, or the process does not respond to pressing <CTRL-C>, use MUPIP STOP. This allows GT.M to disengage the process from all shared resources, such as I/O devices and open database files.
The DSE command CRITICAL /INITIALIZE /RESET causes GT.M to terminate all images that are actively accessing the target database. This DSE command has a similar effect on processes to that of the DCL command STOP, except that it simultaneously terminates all processes actively using a database. However, DCL STOP should not, by itself, damage database contents.
Finally, if the process does not respond to MUPIP STOP, use the DCL command STOP. This terminates the process abruptly and may leave database files improperly closed and require a MUPIP RUNDOWN. However, DCL STOP should not, by itself, damage database contents.
When you have terminated all processes, do a MUPIP RUNDOWN on all database files:
To preserve database integrity, always verify that all GT.M images have terminated and all GDS databases are RUNDOWN before shutting down your system.