The AT option is used to explicitly direct a command to a user
ID on a particular RRSF node. Although explicit command direction
using the AT option and automatic command direction are two distinct
forms of command direction, they can both occur when a command is
issued within an RRSF network, as shown in the following examples.
- Suppose:
- NODE1, NODE2, and NODE3 are RRSF nodes that are operative targets
of each other.
- NODE2 and NODE3 have automatic command direction activated between
them with the following RRSFDATA class profiles:
- On NODE2: AUTODIRECT.NODE3.* with UACC(READ)
- On NODE3: AUTODIRECT.NODE2.* with UACC(READ)
- CHARLIE1 on NODE1 has a peer user ID association with CHARLIE2
on NODE2.
- CHARLIE2 exists on NODE2 and NODE3, but with no user ID association
between nodes.
- CHARLIE1 on NODE1 issues the following command:
ADDUSER PREMA AT(NODE2.CHARLIE2)
- Because the AT option was specified, the command is explicitly
directed to NODE2.CHARLIE2.
- At NODE2, the ADDUSER PREMA command runs under the authority of
CHARLIE2.
- After the ADDUSER PREMA command runs successfully (under the authority
of CHARLIE2 at NODE2), it is automatically directed to NODE3.CHARLIE2.
Note: - The ADDUSER PREMA command does not run on NODE1.
- NODE1.CHARLIE1 receives output via the RRSFLIST data set for the
ADDUSER PREMA command that ran on NODE2.
- The destination of notification and output from the ADDUSER PREMA
command that ran on NODE3 is determined by what was specified on SET
AUTODIRECT command issued on NODE3.