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


Command direction and automatic command direction

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

With command direction, some RACF® commands can be directed to run under the authority of a user ID on a remote node, or the same node. Use the AT keyword on your command for command direction. For information on command direction, see z/OS Security Server RACF Security Administrator's Guide. For information on the AT keywords, see the eligible command descriptions. For a complete list of RACF commands that are eligible for command direction, see Table 1.

A failure might occur while attempting to execute a command issued on one (uplevel) system and manually or automatically directed to another (downlevel) system through RACF remote sharing facility (RRSF) for any of the following reasons:

  • The command references a class unknown to the target system (for example, if the class descriptor tables are different),
  • The command references a segment or field unknown to the target system (for example, if the templates or dynamic parse definition are different)
  • The command uses a command keyword unknown to the target (for example, if the dynamic parse definitions or command processor code is different), or if it specifies a profile or member name that is unacceptable to the target system (for example, if the class descriptor tables have different syntax requirements for profile name length or syntax).

If an out-of-synchronization condition occurs while using automatic command direction, a RACF TSO command can be directed with the ONLYAT keyword to fix the condition. The command runs on the node specified on the ONLYAT keyword and are propagated to any other node. (Note that if the AT keyword is used, the command can be propagated by automatic command direction to other nodes.) For information on the ONLYAT keyword, see the eligible command descriptions. For a complete list of RACF commands that are eligible for automatic command direction, see Table 1.

Some RACF TSO commands can be automatically directed to remote nodes in order to keep profiles synchronized between the nodes. For information on automatic command direction, see z/OS Security Server RACF Security Administrator's Guide.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014