10/25/84 dm_system_shutdown Syntax as a command: dm_system_shutdown {-cargs} Function: This command schedules a Data Management system (DMS) shutdown. The DMS can be specified by the pathname of the its per-system directory, i.e., the directory in which it resides. By default, the DMS which this process is currently using is scheduled to be shut down. Processes using the DMS are notified of the scheduled shutdown via the dm_shutdown_scheduled_ IPS signal. The system shutdown process consists of five events executed at the following five points in time, usually, but not necessarily, in the given order: 1) At user-warning-time: a warning message is printed in each process using the DMS as follows: DM is shutting down; no new transactions will be allowed after 9:00. Please use the dm_user_shutdown_command, or 9:15, a forced shutdown will be done. Shutdown reason: {REASON} 2) At begin-shutdown-time: the Data Management daemon puts the DMS in a state wherein no new transactions can be created. This is considered the beginning of the DMS shutdown. 3) At user-shutdown-time: for each user process still using the DMS, a DM user shutdown is executed in the process. A message is printed informing the user, as follows: The Data Management system is shutting down; starting DM user shutdown. Shutdown reason: {REASON} 4) At user-bump-time: the Data Management daemon bumps each process still using the DMS. 5) At daemon-logout-time: the shutdown is made complete by logging out the Data Management daemon. The time of each event is determined according to the following rules: 1) If the time is specified with a control argument ending in "_time" the event is scheduled to occur at that time. 2) Starting from each specified time, the times for subsequent events are calculated using the specified or default delays, until an event is reached which has a specified time. 3) If the first event is not scheduled, then starting from the first specified time, calculate the times for previous events using specified or default delays, until the first event is reached. 4) If no times are specified, the user-bump-time defaults to the scheduled Multics shutdown time, and other times are calculated from there. 5) If no times are specified and there is no Multics shutdown scheduled, an error message is returned. Control arguments: -dm_system_directory PATH, -dmsd PATH is the pathname, PATH, of the DM per-system directory in which the DMS resides. Several DMSs may reside in the DM per-system directory. The one selected is the one for the current bootload at the AIM authorization of the caller. If not specified, the default DMS is the DMS the process is currently using. If not specified and the process is not currently using a DMS, an error message is printed and no action is performed. -reason STRING is the reason, STRING, why the DMS is being shut down. This reason is ultimately part of the messages received by users of the DMS. If not specified, a prompt is issued for the reason. STRING can be no longer than 64 characters. STRING must be quoted if it contains whitespace. -user_warning_time TIME, -uwtm TIME specifies the user-warning-time. TIME may be absolute or relative to the time at which the dm_system_shutdown command is invoked. TIME must be acceptable to the convert_date_to_binary_ subroutine. If no user-warning-time is specified, the default is to use the config file begin_shutdown_delay to determine the user-warning-time, calculating backwards in time. -begin_shutdown_delay DELAY, -bsd DELAY specifies the time period between the user-warning-time and the begin-shutdown-time. DELAY must be in a form acceptable to the convert_date_to_binary_ subroutine. If no begin-shutdown-time is specified, the default is to use the config file begin_shutdown_delay to determine the begin-shutdown-time. -begin_shutdown_time TIME, -bstm TIME specifies the begin-shutdown-time. TIME may be absolute or relative to the time at which the dm_system_shutdown command is invoked. TIME must be acceptable to the convert_date_to_binary_ subroutine. If no begin-shutdown-time is specified, the default is to use the config file begin_shutdown_delay to determine the begin-shutdown-time. -user_shutdown_delay DELAY, -usd DELAY specifies the time period between the begin-shutdown-time and the user-shutdown-time. DELAY must be in a form acceptable to the convert_date_to_binary_ subroutine. If no user-shutdown-time is specified, the default is to use the config file user_shutdown_delay to determine the user-shutdown-time. -user_shutdown_time TIME, -ustm TIME specifies the user-shutdown-time. TIME may be absolute or relative to the time at which the dm_system_shutdown command is invoked. TIME must be acceptable to the convert_date_to_binary_ subroutine. If no user-shutdown-time is specified, the default is to use the config file user_shutdown_delay to determine the user-shutdown-time. -user_bump_delay DELAY, -ubd DELAY specifies the time period between the user-shutdown-time and the user-bump-time. DELAY must be in a form acceptable to the convert_date_to_binary_ subroutine. If no user-bump-time is specified, the default is to use the config file user_bump_delay to determine the user-bump-time. -user_bump_time TIME, -ubtm TIME specifies the user-bump-time. TIME may be absolute or relative to the time at which the dm_system_shutdown command is invoked. TIME must be acceptable to the convert_date_to_binary_ subroutine. If no times are specified via a -..._time control argument, the user-bump-time defaults to the scheduled Multics shutdown time. If a time other than the user-bump-time is specified, the default is to use the config file user_bump_delay to determine the user-bump-time. -daemon_logout_delay DELAY, -dld DELAY specifies the time period between the user-bump-time and the daemon-logout-time. DELAY must be in a form acceptable to the convert_date_to_binary_ subroutine. If no daemon-logout-time is specified, the default is to use the config file daemon_logout_delay to determine the daemon-logout-time. -daemon_logout_time TIME, -dltm TIME specifies the daemon-logout-time. TIME may be absolute or relative to the time at which the dm_system_shutdown command is invoked. TIME must be acceptable to the convert_date_to_binary_ subroutine. If no daemon-logout-time is specified, the default is to use the config file daemon_logout_delay to determine the daemon-logout-time. Access required: 're' permission to dm_admin_gate_ is required to execute this command. Examples: Given: Multics shutdown scheduled for 8:00. All default delays are five minutes. dm_system_shutdown -bsd 20min Schedules shutdown with following times: user-warning: 7:30 (specified delay) begin-shutdown: 7:50 (default delay) user-shutdown: 7:55 (default delay) user-bump: 8:00 (default time) daemon-logout: 8:05 (default delay) dm_system_shutdown -uwtm 5:00 -ustm 6:10 -ubtm 6:00 Schedules shutdown with following times: user-warning: 5:00 (specified time) begin-shutdown: 5:05 (default delay) user-shutdown: 6:10 (specified time) user-bump: 6:00 (specified time) daemon-logout: 6:05 (default delay) ----------------------------------------------------------- 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