1.0;mrgrgy (merge_registries), revision 1.0, 85/05/15
MRGRGY (MERGE_REGISTRIES) -- Merge two network registries.
usage: MRGRGY rgy1_path rgy2_path
FORMAT
MRGRGY rgy1_path rgy2_path
MRGRGY merges two previously independent network registries. This command
merges each network's site directories. Thus, all site directories' person,
project, organization, full name, and account files are merged.
MRGRGY selects one master registry file to be the merged master. It then
merges the master registry files from each network into the merged master.
The merged master contains the name of the new master registry file and the
names of the site directories that were in each of the original master
registry files. The other master registry file (i.e., the file that is not the
merged master) is backed up and then deleted.
The MRGRGY command completes in four phases:
Phase Description
1 MRGRGY creates the new merged PPO and account files and saves
them in temporary files. Some .bak files are changed, but no
changes are made to the original PPO and account files. If
Phase 1 fails because MRGRGY detects duplicate entries in the
PPO and account files, fix the problem and rerun MRGRGY. If
Phase 1 fails due to a network problem, rerun MRGRGY.
2 MRGRGY saves the merged PPO and account files in the site
directories listed in the first master registry file. If
Phase 2 fails due to a network problem, rerun MRGRGY.
3 MRGRGY creates the merged master registry file and saves it in
the first master registry file. MRGRGY deletes the second
master registry file. If Phase 3 fails due to a network
problem, recreate the original master registry files from your
backup copies. Then rerun MRGRGY.
4 MRGRGY performs a SALRGY to copy the merged PPO and account
files to all site directories in the merged master registry.
(Some sites already have these files; they will get new
copies.) If Phase 4 fails due to a network problem, run
SALRGY.
Before you use MRGRGY, use CMPPO and CMACCT to check for all name and account
collisions that would prevent MRGRGY from running to completion.
MRGRGY is for use in a DOMAIN/BRIDGE internet. For more information on
merging registries, see Managing DOMAIN Internets.
ARGUMENTS
rgy1_path
(required) Specify the master registry file of one of the registries
to be merged; this file will become the new, merged
registry's master file.
The master registry file may be specified by its pathname,
(//node/REGISTRY/RGY_MASTER), by a node's copy of the
master registry file (//node/REGISTRY/REGISTRY), or simply
by a node entry directory (//node). If a node's
/REGISTRY/REGISTRY file or a node entry directory is
specified, the //node/REGISTRY/REGISTRY file is used to
locate the registry's master file.
rgy2_path
(required) Specify the master registry file of the other registry to
be merged.
EXAMPLES
The following command merges two registries. The registry masters are
//alpha/registry/rgy_master and //beta/registry/rgy_master.
$ mrgrgy //alpha/registry/rgy_master //beta/registry/rgy_master
Phase 1:
Merging the person files
Merge completed
Merging the project files
Merge completed
Merging the org files
Merge completed
Merging the full names files
Merge completed
Merging the account files
Merge completed
Phase 2:
Merged person file saved in registry //alpha/registry/rgy_master's sites
Merged project file saved in registry //alpha/registry/rgy_master's sites
Merged org file saved in registry //alpha/registry/rgy_master's sites
Merged full_names file saved in registry //alpha/registry/rgy_master's
sites
Merged account file saved in registry //alpha/registry/rgy_master's sites
Phase 3:
Creating the new registry's master file in "//alpha/registry/rgy_master"
New master file completed
Phase 4:
Merged person file saved in all new registry's sites
Merged project file saved in all new registry's sites
Merged org file saved in all new registry's sites
Merged full_names file saved in all new registry's sites
Merged account file saved in all new registry's sites
$