05/26/87 complete_dump Syntax as a command: complete_dump {ctl_file {operator {ntapes}}} {-control_args} Function: begins a complete hierarchy dump. It dumps all storage system segments and directories, regardless of their modification dates. The complete_dump command calls the backup_dump command to do the actual dumping. The complete_dump command requires a dump control file, containing the full pathnames of the objects to be dumped. It calls backup_dump once for each line in the control file. See "Notes on Format of a Dump Control File" below. A map of all objects dumped is created in the working directory, with the name .dump.map. The complete_dump command is one of the commands used to control hierarchy dumping of storage system segments and directories to magnetic tape. The other commands are: backup_dump catchup_dump end_dump start_dump wakeup_dump You should note that argument processing for all of the hierarchy backup commands is performed by a common argument processing procedure. The values of all arguments are remembered in static storage and remain in effect for the life of the process, unless changed by arguments given in subsequent invocations of backup commands. It should also be noted that the dumping commands and the reloading/retrieving commands are all part of the same hierarchy backup system, and argument values set by the dumping commands remain in effect for the reloading/retrieving commands and vice versa, unless overridden. However, dumping and reloading cannot be done in the same process; use the new_proc command between dumping and reloading. See "Notes on Default Arguments" below. You may define certain frequently used arguments to the complete_dump command in two different ways. The first way is to precede the argument with an identifying control argument. The second way is to place the argument in a certain position on the command line. In the first case, the combination of control argument and argument may appear anywhere on the command line after any positional information. In the second case, the argument must appear at the beginning of the command line, before any control argument-argument combinations or any control arguments which stand alone. For the complete_dump command, the frequently used arguments are the control file, the operator's name, and the number of tape copies. When defined to the command positionally, i.e., without identifying control arguments, these arguments must appear in the following positions: complete_dump {ctl_file {operator {ntapes}}} {-control_args} The control file and the operator's name must be specified, in one way or the other. Arguments: ctl_file is the pathname of the dump control file (see the -control control argument). operator is the operator's name or initials (see the -operator control argument). ntapes is the number of copies to be made of each hierarchy dump tape (see the -tapes control argument). Control arguments: -all causes all directory entries (in the specified subtree) to be dumped, regardless of their dates modified or dates dumped. This argument overrides a previously given -dtd control argument or DATE argument. This is the default. -brief_map, -bfmap creates a map file that lists the processed entries. -control path indicates that path is the pathname of a dump control file. The suffix "dump" is assumed. For example, "-control sys_dirs" specifies a control file named sys_dirs.dump, in the working directory. See "Notes on Format of a Dump Control File" below. -debug disables those phcs_ and hphcs_ calls that deactivate dumped segments and set quotas. -destination STR, -ds STR specifies a destination for printing maps and error files. The default is "incremental" for maps and "error file" for error files. -dtd tests and dumps each segment only if the segment or its branch has been modified since the last time it was dumped. -error_of writes error messages into a file rather than online. The name of the error file is printed when the first error is encountered. This is the default. -error_on writes error messages on the user's terminal. -header STR, -he STR specifies a heading for dprinting maps and error files. -hold leaves the current hierarchy dump tape or tapes mounted and inhibits rewinding after the current hierarchy dump cycle is completed. -map writes a list of the segments and directories processed into a file. This is the default. -nodebug enables hphcs_ calls to set quotas and the transparency switches. This is the default. -nodprint, -no_dprint, -ndp causes the start_dump command not to dprint maps and error files. The default is -dprint. This control argument cannot be used with the backup_dump command. -nohold rewinds and unloads the hierarchy dump tape or tapes at the end of the current dump pass. This is the default. -nomap inhibits listing of the names of processed segments and directories and turns the tape switch on (see -tape below). -nooutput inhibits writing hierarchy dump information even if the tape switch is on. This is used for a test run or debugging. -noprimary, -npri uses each pathname as given. The default is -primary. -notape inhibits writing of a hierarchy tape. This argument also causes a map to be created even if it was previously inhibited. (See -map above.) -only indicates that only the requested segment or directory and its branch are to be dumped. This is the opposite of -sweep. -operator STR indicates that STR is the user's name or initials (up to 16 characters in length). -output writes hierarchy dump information onto the tape if the tape switch is on. This is the default. -primary, -pr replaces all directory names in each pathname with the primary names. This is the default. -pvname STR indicates that segments and directories may only be dumped if they reside on the physical volume specified by STR. -queue N, -q N specifies a queue number for any maps and error files that are dprinted. The default is queue 1. -request_type STR, -rqt STR specifies an output request type for printing maps and error files. Available request types can be listed by using the print_request_types command. The default is "printer." -restart path indicates that path is the pathname of a segment or directory where hierarchy dumping is to be restarted. Use of this feature assumes that there is a dump control file. It is normally used to restart a hierarchy dump that was interrupted by a system failure. -sweep indicates that the whole subtree beginning with the given directory is to be dumped, subject to the criteria of the -dtd control argument or the DATE argument if either has been invoked. This is the default. -tape allows writing of a tape. This is the default. -tapes N indicates that N is the number of output tape copies to be made where N can be either 1 or 2. The default is 1. -1tape sets the number of tape copies to 1 as an alternative to the -tapes argument. -2tapes sets the number of tape copies to 2 as an alternative to the -tapes argument. -wakeup N indicates that N is the wakeup interval between incremental hierarchy dump passes, in minutes. The default is 60 minutes. DATE an argument beginning with a character other than "-" or ">" is assumed to be a date, in a format acceptable to the convert_date_to_binary_ subroutine. If the argument can be converted to a date, then only segments and directories modified after that date are dumped. Notes on default arguments: The values of arguments given to any of the hierarchy backup commands are remembered in static storage and remain in effect for the life of the process, unless explicitly changed during the invocation of a subsequent backup command. The following defaults are in effect for the dumper before any backup commands are given; they are not, however, reset to these values at the start of each backup command, except as noted. -all -contin -error_of -map -nodebug -nohold -output -primary -sweep -tape The following defaults are set automatically at the time the respective commands are executed: catchup_dump -tape (default date yesterday at midnight) complete_dump -all -tape start_dump -dtd -hold -tape -wakeup 60 Notes on format of a dump control file: The control file specified by "-control path" is an ASCII segment containing absolute pathnames of entries (segments, MSFs, and directory subtrees) to be dumped, each on a separate line. ----------------------------------------------------------- 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