1 01/24/84  copy_registry
 2 
 3 Syntax:  copy_registry from_path {to_path} {-control_arg}
 4 
 5 
 6 Function:  is used by the system administrator to make checkpoint
 7 copies of RCP Resource Management registries.  These copies can be used
 8 as a basis for the reconstruction of registries destroyed by
 9 catastrophic system failure.
10 
11 
12 Arguments:
13 from_path
14    is the pathname of the registry to be copied.  The star convention
15    is accepted.  If the suffix rcpr is not given, it is assumed.
16 to_path
17    is the pathname of the copy to be created.  The equals convention is
18    accepted.  If the suffix rcpr is not given, it is assumed.  If
19    to_path is not supplied, the copy will be placed in the working
20    directory and will have the same name as the original.  (See "Notes"
21    below.)
22 
23 
24 Control arguments:
25 -reset
26    specifies that the contents of the registry journal are to be
27    discarded after the copy operation has been successfully completed.
28    (See "Notes" below.)
29 
30 
31 Notes:  It is strongly recommended that the RCP Administrator NOT copy
32 registries into >sc1>rcp (for reconstruction purposes or otherwise)
33 except under special session.
34 
35 The registry journal contains a record of all operations performed
36 against all registries since the time its contents were last reset via
37 the use of the -reset control argument described above.  Since a
38 successful reconstruction operation depends on the journal containing a
39 record of all operations performed since the copies of the registries
40 were created, it is important that the -reset control argument only be
41 specified for invocations which result in the copying of all
42 registries.
43 
44 
45 The copying of any number of registries and the resetting
46 of the journal within one invocation of the copy_registry command is
47 performed as an indivisible operation, which guarantees that no
48 operations can be performed against any of the registries involved
49 until the copying operation is complete and the journal has been reset.
50 Since this cannot be guaranteed between multiple invocations of the
51 copy_registry command, the -reset control argument should never be used
52 without copying all active registries.
53 
54 When -reset is specified, the journal is reset only if the copy
55 operations are completed successfully.
56 
57 Copies of system registries are automatically made each night by the
58 system accounting facility (crank) using this command.
59 
60 
61 Access required:  This command requires access to the rcp_admin_
62 gate.