Automatic command direction, which is an extension of command direction, is useful primarily for keeping already-synchronized RACF® profiles synchronized between two or more remote nodes. Every automatically directed command is processed on the node that originates the command; profiles in the RRSFDATA class identify the other nodes where the command should also be processed. Your RACF security administrator sets up these profiles. No user ID associations are required for automatic command direction. If user ID associations are defined, they are ignored during processing for automatic command direction.

An installation decides who should be notified of results and output from automatically directed commands, so you might or might not see output or TSO SEND messages from automatically-directed commands.

If you get output or notification that an automatically directed command failed, notify your RACF security administrator. This is an indication that the RACF profiles are no longer synchronized.

The format of the output for automatic command direction is similar to the output from directed commands, with one additional line for automatic command direction. Figure 1 shows the format of output for an automatically directed ADDUSER command. Figure 2 shows the format of output for an automatically directed RDEFINE command.

ADDUSER issued at 10:42:33 on 04/03/98 was processed at NODEA.LAURIE
on 04/03/98 at 10:43:45
Command was propagated by automatic direction from NODEB.LAURIE

 COMMAND ISSUED:  ADDUSER (ANDREW) PASSWORD() NAME('####################')
 AUTHORITY(USE) NOSPECIAL UACC(NONE) NOOPERATIONS NOADSP NOGRPACC NOAUDITOR

 COMMAND OUTPUT:
 IRRR008I Command succeeded.  There are no messages.

RDEFINE issued at 12:33:41 on 04/03/98 was processed at NODEA.LAURIE
on 04/03/98 at 12:35:02
Command was propagated by automatic direction from NODEB.LAURIE

 COMMAND ISSUED:  RDEFINE AUTODIRECT.**  UACC(NONE)

 COMMAND OUTPUT:
 ICH10102I AUTODIRECT.** ALREADY DEFINED TO CLASS RRSFDATA.