Examples

   1.$ ! Command sequence used on system 1 at site 1:
     $ MOUNT/SYSTEM DSA0:/SHADOW=($1$DGA0:,$1$DGA1:) TEST
     $ SET SHADOW/SITE=1  DSA0:
     $ !
     $ ! Command sequence used on system 2 at site 2:
     $ MOUNT/SYSTEM DSA0:/SHADOW=($1$DGA0:,$1$DGA1:) TEST
     $ SET SHADOW/SITE=2  DSA0:
     $ !
     $ ! Commands used on both system 1 and system 2:
     $ SET SHADOW/SITE=1  $1$DGA0:
     $ SET SHADOW/SITE=2  $1$DGA1:

     In this example, the system at site 1 will perform reads from
     $1$DGA0, which is located at that site, while the system at
     site 2 will perform reads from $1$DGA1, which is located at
     site 2.

   2.$ SET SHADOW DSA1: /POLICY=HBMM=  -
     _$      (MASTER_LIST=(NODE1,NODE2,NODE3), COUNT=2, -
     _$      RESET_THRESHOLD=75000)

     This command defines an HBMM policy for shadow set DSA1:. The
     policy specifies that no more than two systems of the three
     systems listed can have an HBMM master bitmap. Once 75000
     blocks have been modified on DSA1:, any existing HBMM bitmaps
     are zeroed.

   3.$ SET SHADOW /POLICY=HBMM=(MASTER_LIST= -
     _$ (NODE1,NODE2,NODE3), RESET_THRESHOLD=75000, COUNT=2) -
     _$ /NAME=HONESTY_IS_BEST

     This command defines the named policy HONESTY_IS_BEST. This
     policy is available to all cluster members, but is not applied
     to any specific shadow set.

   4.$ SET SHADOW DSA1: /POLICY=HBMM=HONESTY_IS_BEST

     This command associates the named policy HONESTY_IS_BEST with
     shadow set DSA1.

   5.$ SET SHADOW /POLICY=HBMM=( -
     _$       (MASTER_LIST=(NODE1,NODE2,NODE3), COUNT=2), -
     _$       (MASTER_LIST=(NODE4,NODE5,NODE6), COUNT=2), -
     _$               RESET_THRESHOLD=150000) -
     _$               /NAME=POLICY_2

     This command defines the HBMM named policy POLICY_2, which has
     two master lists.

   6.$ SET SHADOW DSA2: /POLICY=HBMM=POLICY_2

     This command associates the named policy POLICY_2 with shadow
     set DSA2.

   7.$ SET SHADOW /POLICY=HBMM /DELETE /NAME=POLICY_2

     This command deletes the named policy POLICY_2. Note that
     any shadow set that had acquired the attributes of POLICY_
     2 by execution of a SET SHADOW DSAn: /POLICY=HBMM=POLICY_2
     command is not affected. Changes made to a named policy are
     not retroactive to a mounted shadow set that was assigned the
     characteristics of a previous version of that named policy.

   8.$ SET SHADOW  DSA1: /POLICY=HBMM /DELETE

     This command deletes the existing HBMM policy from DSA1:. If
     this HBMM policy is enabled on DSA1:, you must first execute
     the following command to disable the policy before you can
     delete it:

       $ SET SHADOW  DSA1: /DISABLE=HBMM

   9.$ SET SHADOW /DEMAND_MERGE/CONFIRM
     Allow merge of _DSA721:? [N]:y
     Allow merge of _DSA850:? [N]: TRUE
     Allow merge of _DSA1010:? [N]:N
     $

     In this example, a merge operation is initiated on DSA721: and
     DSA850: but not on DSA1010:.

10$ SET SHADOW DSA1/POLICY=HBMM=(MASTER=*,COUNT=12,MULTIUSE=12,DISMOUNT=1)

     In this example, a policy is set in which all 12 bitmaps can
     be used as multiuse bitmaps. When you execute the command
     DISMOUNT/POLICY=MINICOPY, 1 minimerge bitmap is converted to
     multiuse bitmap. You can use this multiuse bitmap with the
     MINICOPY command to add the dismounted member back to the
     shadow set. In other words, it specifies that 12 bitmaps can
     be used during the automatic and 1 bitmap during the manual
     removal of the shadow set member.

   11$SET SHADOW DSA42 /STALL=WRITES

     In this example, the writes are stalled to the shadow set for a
     period of SHADOW_MBR_TMO seconds.

   12$SET SHADOW DSA42 /STALL=WRITES=60

     In this example, the writes are stalled to the shadow set for a
     period of 60 seconds.

   13$SET SHADOW DSA42 /NOSTALL=WRITES=30

     In this example, the writes are allowed to the shadow set after
     a period of 30 seconds.