02/27/85 reconstruct_registry Syntax as a command: reconstruct_registry registry_names {-control_args} Function: recovers a current copy of RCP Resource Management registries after a catastrophic system failure causing the loss of one or more registries. It assumes that the registry to be reconstructed is a consistent earlier copy of the registry desired, and that the RCP Resource Management journal contains a record of all operations performed on the registry since the time represented by the earlier copy. Arguments: registry_names are the entrynames of the registries to be reconstructed. The star convention is accepted. If the suffix .rcpr is not given, it is assumed. Control arguments: -pathname path (-pn path) to specify the directory in which the registries reside. If this control argument is not specified, the registries are sought in >sc1>rcp. Notes: An explanation of the creation and maintenance of checkpointed registry copies can be found in the documentation of the copy_registry command. The prescribed sequence of operations is to delete the damaged registries; copy the desired checkpointed registries into place; and invoke the reconstruct_registry command to update the registries. The command locates the RCP Resource Management journal relative to the directory in which the registries to be updated reside. If an online checkpoint copy of a system registry is not available, a copy of the registry may be retrieved from a system backup tape. In this case, the file retrieved must be from a time that is more recent than the last time the RCP Resource Management journal was reset (see the documentation of the copy_registry command). The reconstruction of system registries must only be performed from the Initializer, in the "standard" environment, before the answering service is activated. Access required: This command requires access to the rcp_sys_ gate. ----------------------------------------------------------- Historical Background This edition of the Multics software materials and documentation is provided and donated to Massachusetts Institute of Technology by Group BULL including BULL HN Information Systems Inc. as a contribution to computer science knowledge. This donation is made also to give evidence of the common contributions of Massachusetts Institute of Technology, Bell Laboratories, General Electric, Honeywell Information Systems Inc., Honeywell BULL Inc., Groupe BULL and BULL HN Information Systems Inc. to the development of this operating system. Multics development was initiated by Massachusetts Institute of Technology Project MAC (1963-1970), renamed the MIT Laboratory for Computer Science and Artificial Intelligence in the mid 1970s, under the leadership of Professor Fernando Jose Corbato. Users consider that Multics provided the best software architecture for managing computer hardware properly and for executing programs. Many subsequent operating systems incorporated Multics principles. Multics was distributed in 1975 to 2000 by Group Bull in Europe , and in the U.S. by Bull HN Information Systems Inc., as successor in interest by change in name only to Honeywell Bull Inc. and Honeywell Information Systems Inc. . ----------------------------------------------------------- Permission to use, copy, modify, and distribute these programs and their documentation for any purpose and without fee is hereby granted,provided that the below copyright notice and historical background appear in all copies and that both the copyright notice and historical background and this permission notice appear in supporting documentation, and that the names of MIT, HIS, BULL or BULL HN not be used in advertising or publicity pertaining to distribution of the programs without specific prior written permission. Copyright 1972 by Massachusetts Institute of Technology and Honeywell Information Systems Inc. Copyright 2006 by BULL HN Information Systems Inc. Copyright 2006 by Bull SAS All Rights Reserved