STOP (Stop RACF subsystem)

Purpose

Use the STOP command to allow the MVS operator to stop the RACF subsystem address space if restarting a subtask is not sufficient to recover from a failure. This command shuts down the RACF subsystem address space and prevents the loss of any outstanding requests that are waiting for completion.

The STOP command can also be used to stop the RACF subsystem address space before an IPL.

Guidelines:

If you are directing work to the RACF subsystem, stop the RACF subsystem address space before IPLing to prevent the loss of outstanding requests.
If you are using automatic direction or password synchronization, do not stop the address space except immediately before an IPL. If you stop it at other times, updates that are made to the local node might not be sent to the other nodes.
Ensure that all users or applications that update the RACF database are finished before issuing the STOP command.

Issuing options

The following table identifies the eligible options for issuing the STOP command:

As a RACF TSO command?	As a RACF operator command?	With command direction?	With automatic command direction?	From the RACF parameter library?
No	Yes	No	No	No

For information on issuing this command as a RACF® operator command, see RACF operator commands.

Related commands

To restart the RACF subsystem address space, use the MVS START command.
To restart a function in the RACF subsystem address space, see RESTART (Restart RACF subsystem functions). You must restart the RACF subsystem address space before restarting functions within the RACF subsystem address space.

Authorization required

You might require sufficient authority to the proper resource in the OPERCMDS class. For details about OPERCMDS resources, see "Controlling the use of operator commands" in z/OS Security Server RACF Security Administrator's Guide.

Syntax

The complete syntax of the STOP command is:

subsystem-prefixSTOP

For information on issuing this command as a RACF operator command, see Rules for entering RACF operator commands.

Parameters

subsystem-prefix: Specifies that the RACF subsystem is the processing environment of the command. The subsystem prefix can be either the installation-defined prefix for RACF (1 - 8 characters) or, if no prefix has been defined, the RACF subsystem name followed by a blank. If the command prefix was registered with CPF, you can use the MVS command D OPDATA to display it or you can contact your RACF security administrator.
The subsystem prefix is a required keyword for RACF operator commands.

Examples


Example 1	Operation	User AMT02 wants to shut down the RACF subsystem address space in an orderly manner without losing any remote RRSF requests.
	Known	The RACF subsystem prefix is `@`.
	Command	`@STOP`
	Defaults	None.