1 :Info: copy_mrds_data: cpmd:  1986-06-16  copy_mrds_data, cpmd
 2 
 3 Syntax as a command:  cpmd input_db_path output_db_path {-control_args}
 4 
 5 
 6 Function:  This command copies data from one MRDS data base to another.
 7 
 8 
 9 Arguments:
10 input_db_path
11    is the pathname of the data base from which data is copied.  If the
12    pathname does not have a suffix of db, then one is assumed.
13    However, the db suffix must be the last component of the name of
14    the input segment.
15 output_db_path
16    is the pathname of the data base to which date is copied.  The data
17    base must already exist.  If the pathname does not have a suffix of
18    db, then one is assumed.  However, the db suffix must be the last
19    component of the name of the output segment.
20 
21 
22 Control arguments:
23 -input_prevent_ops OPS
24    specifies the prevent scope on the input relation(s), where OPS is
25    the set of operations that the user wishes to deny other openers of
26    the input data base for the relation(s) being copied.  (Default is
27    "dms" -- refer to Notes for a list of scope mode abbreviations.)
28 -output_prevent_ops OPS
29    specifies the prevent scope on the output relation(s), where OPS is
30    the set of operations that the user wishes to deny other openers of
31    the output data base for the relation(s) being copied.  (Default is
32    "dms" -- refer to Notes for a list of scope mode abbreviations.)
33 
34 
35 -relation RELNAME, -rel RELNAME
36    specifies that RELNAME be copied.  Only one relation at a time can
37    be copied using this control argument.  If this control argument
38    appears more than once in a command line, the previous occurrence
39    is overridden.
40 -transaction_group_size N
41    specifies copying N tuples within the confines of a single
42    transaction.  If this control argument is omitted, or if N is equal
43    to 0, then each access to a protected data management file is
44    completed as a separate transaction.
45 
46 
47 Notes:  The abbreviations used for prevent scope operations (for either
48 input or output) are as follows:
49    a     append_tuple
50    s     append_tuple (same as a)
51    d     delete_tuple
52    m     modify_attr
53    n     null
54    r     read_attr
55    u     update (same as dms)
56 
57 
58 If "n" prevent scope is given, then no other mode may be specified for
59 that prevent.  Each of the other modes may be used only once in the
60 same prevent scope.
61 
62 
63 Relations that are copied must be identical in their makeup, having the
64 same attributes, attribute names, indexes, etc.  It is suggested, where
65 possible, that both data bases be created using the same create_mrds_db
66 source.  When using the -relation control argument however, it is
67 possible to copy from data bases with differing models, as long as the
68 relation being copied is the same in both data bases.
69 
70 
71 :hcom:
72 
73 
74 
75 
76 /****^  HISTORY COMMENTS:
77   1) change(2020-04-21,GDixon), approve(2021-02-22,MCR10088),
78      audit(2021-05-27,Swenson), install(2021-05-27,MR12.6g-0056):
79      Add missing subroutine introduction block to info segment.
80   2) change(2020-12-14,GDixon), approve(2021-02-22,MCR10088),
81      audit(2021-05-27,Swenson), install(2021-05-27,MR12.6g-0056):
82       A) Change "Syntax:" to "Syntax as a command:" in command info seg
83          last changed after 1984.
84                                                    END HISTORY COMMENTS */
85 
86 
87