z/OS Security Server RACF Command Language Reference
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


RESTART (Restart RACF subsystem functions)

z/OS Security Server RACF Command Language Reference
SA23-2292-00

Purpose

Use the RESTART command to restart a function in the RACF® subsystem address space. The RESTART command can be used after you apply maintenance and to recover from failures.

The RESTART command ends the current subtask and starts a new one. Only one function can be restarted with a single RESTART command, but that function might involve multiple subtasks.

Note: All users or applications that update the RACF database should be completed before issuing the RESTART command.

Issuing options

The following table identifies the eligible options for issuing the RESTART 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 stop the RACF subsystem address space, see STOP (Stop RACF subsystem).
  • To restart the RACF subsystem address space after it has been stopped, use the MVS START command.

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

For the key to the symbols used in the command syntax diagrams, see Syntax of RACF commands and operands. The complete syntax of the RESTART command is:

   
subsystem-prefixRESTART
 

{ COMMAND
| CONNECTION [ NODE(nodename | * )
  [ SYSNAME(sysname | * ) ] ]
| MESSAGE
| OUTPUT
| RACLINK
| RECEIVE
| SEND
}

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.

Subsystem prefix is a required keyword for RACF operator commands.

COMMAND | CONNECTION | MESSAGE | RACLINK | RECEIVE | SEND
Specifies the restartable function. The RESTART command signals the specified function to stop and then restart.

Specify only one function per RESTART command. If more than one function is specified, only the first is processed and the rest are ignored.

For a list of the modules associated with each restartable function, see "Restarting a function in the RACF subsystem" in z/OS Security Server RACF System Programmer's Guide.

NODE(nodename | *)
Restarts the RRSF connection to the specified node only when the connection is in an operative state. When you specify a single node name, the handshaking and communication subtasks for specified node are stopped and restarted. When you specify an asterisk (*), the handshaking and communication subtasks for all nodes with operative connections are stopped and restarted.

The NODE operand applies only to the CONNECTION function. If NODE is specified with any other function, it is ignored.

If NODE is not specified with CONNECTION, all modules associated with the CONNECTION function are stopped and restarted.

SYSNAME(sysname | *)
Restarts the RRSF connection to the specified system in the specified multisystem node only when the connection is in an operative state. When you specify a single system name, the handshaking and communication subtasks for specified system are stopped and restarted. When you specify an asterisk (*), the handshaking and communication subtasks for all systems in the node with operative connections are stopped and restarted.

The SYSNAME operand is positional and must follow NODE.

Examples

     
Example 1 Operation A maintenance PTF has been applied to module IRRSSC01 and user DNP2 wants to load a new copy to put the change in effect.
Known Module IRRSSC01 resides in load module IRRSSC00.

The RACF subsystem prefix is @.

Command @RESTART COMMAND
Defaults None.
Results The command handler is shut down and restarted. A new copy of load module IRRSSC00 is loaded including the updated copy of IRRSSC01.
Example 2 Operation Restart the connection to the single-system node NODE1
Known NODE1 is a single-system node. If it were not a single-system node, RACF would issue an error message and not execute the command.
Command RESTART CONNECTION NODE (NODE1)
Defaults None.
Results The command restarts the connection to NODE1
Example 3 Operation Restart the connections to all single-system nodes, and to all member systems of multisystem nodes
Command RESTART CONNECTION NODE (*)
or RESTART CONNECTION NODE (*) SYSNAME(*)
Defaults None.
Results The command restarts the connection to all single-system nodes and to all member systems of multisystem nodes.
Example 4 Operation Restart the connections to the specific member system SYS1 on the multisystem node MULTNODE.
Command RESTART CONNECTION NODE (MULTNODE) SYSNAME(SYS1)
Defaults None.
Results The command restarts the connection to SYS1 on MULTNODE. If MULTNODE is a single-system node, RACF issues an error message.
Example 5 Operation Restart the connections to all member systems of the multisystem node MULTNODE.
Command RESTART CONNECTION NODE (MULTNODE) SYSNAME(*)
Defaults None.
Results The command restarts the connection to all member systems of MULTNODE. If MULTNODE is a single-system node, RACF issues an error message.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014