STOP terminates a GT.M image. The image executes an orderly rundown of all databases that are currently open, and then exits. A MUPIP STOP performs an OpenVMS FORCEX system service and therefore may also be used to stop non-GT.M images

The format of the STOP command is:

     
            ST[OP] /N[AME]=process-name | /ID=process-id
     
     
         

At least one of the qualifiers must appear. If both qualifiers appear, they must refer to the same process or STOP rejects the command.

Use the DCL command SHOW SYSTEM to display a list of active process names and process identifiers (PIDs). PIDs appear as hexadecimal numbers on a SHOW SYSTEM display, which is how they are specified to MUPIP STOP.

To STOP a process belonging to its own account, a process requires no privileges. To STOP a process belonging to another account in the same group, a process requires GROUP privilege. To stop a process belonging to an account in a different group, a process requires WORLD privilege and must use /ID=.

/I[D]=process-id

STOP interprets the /ID qualifier as a hexadecimal number that corresponds to the form displayed by the DCL command SHOW SYSTEM.

/N[AME]=process-name

Specifies the name of the process to stop. The maximum length of the name is 15 characters. Use the /ID qualifier if the process belongs to an owner in a different group.

/UP[GRADE] /N[AME] = file-name

Upgrades a GT.M version 3.x database file to the GT.M version 4 format. Ensure that there is a backup copy of any file that is being upgraded, and that mupip integ with GT.M 3.x reports that the file is clean. Files must be upgraded one at a time. Pressing <CTRL-C> or experiencing a system crash while a file upgrade is in progress can leave the file damaged, and require that it be restored from the backup.