Sample automatic direction of application updates

Some examples of using profiles to control automatic application update direction follow. For each example, assume that no other profiles beginning with AUTODIRECT are present in the RRSFDATA class.

To disallow both automatic direction of commands and automatic direction of application updates for TAPEVOL and RRSFDATA profiles, disallow automatic updates for TAPEVOL and RRSFDATA profiles, disallow automatic direction of application updates for all DATASET profiles, and allow all other updates to propagate to all remote nodes:
```
AUTODIRECT.*.TAPEVOL.*     with UACC(NONE) and no users on access list
AUTOTAPE.*.DATASET.*       with UACC(NONE) and no users on access list

AUTODIRECT.**              with UACC(READ) and no users on access list
AUTODASD*.**               with UACC(READ) and no users on access list
```
The following RRSFDATA profiles allow both automatic direction of commands and automatic direction of application updates only to NODEA for the USER and GROUP classes. In this example, no AUTOTAPE or AUTODASD profiles are defined. This gives the same results as defining the profiles with a UACC of NONE (updates are not propagated):
```
AUTODIRECT.NODEA.USER.*    with UACC(READ) and no users on access list
AUTODIRECT.NODEA.GROUP.*   with UACC(READ) and no users on access list
```