1 04/07/86  dm_send_request
 2 
 3 Syntax as a command:  dm_send_request keyword {value}
 4 
 5 
 6 Function: enables administrators to intervene during data management
 7 operations by sending requests to the data management (DM) daemon to
 8 perform actions it normally performs through internal interfaces.  This
 9 is an efficient mechanism for administrators to activate operations
10 that require access to dm_daemon_gate_.
11 
12 
13 Arguments:
14    keyword can be any of the following:
15 adjust_tdt, adjtdt
16    calls on the DM daemon to scan the transaction definition table
17    (TDT) and abort those transactions associated with dead processes
18    and those that have been abandoned.  This is the same function that
19    the daemon performs as caretaker of Data Management System (DMS)
20    upon receiving a periodic wakeup call.
21 adjust_tdt_entry value, adjtdte value
22    calls on the DM daemon to check on the specified transaction and
23    abort it if it belongs to a dead process or if it has been
24    abandoned; value is the transaction index associated with the TDT
25    entry.
26 
27 
28 adjust_txn value, adjtxn value
29    calls on the DM daemon to check on the specified transaction and
30    abort it if it belongs to a dead process or if it has been
31    abandoned; value is the unique transaction identifier assigned when
32    the transaction was started.
33 kill_txn value, kill value
34    calls on the DM daemon to expunge the specified transaction from the
35    TDT without rolling it back or committing it; value is the unique
36    transaction identifier assigned when the transaction was started.
37    Any DM files modified by the transaction may be left inconsistent,
38    so use this request only as a last resort.
39 new_proc
40    calls on the DM daemon to do a new_proc.  This request is useful for
41    setting the daemon to use a newly installed version of DMS.
42 
43 
44 new_process_notifications, notify
45    calls on the DM daemon to send a dm_shutdown_scheduled_ IPS to the
46    process sending this request.  The implication is that the process
47    logged in after the Multics shutdown was scheduled.
48 shutdown
49    calls on the DM daemon to schedule a DM shutdown coinciding with the
50    scheduled Multics shutdown.  The times of each stage of the shutdown
51    are calculated according to the scheme described in  the
52    dm_system_shutdown command write-up.  Shutdown is included to enable
53    a Multics operator to shutdown Data Management via the reply
54    operator command.  Administrators should use the dm_system_shutdown
55    command to shutdown Data Management, as it affords the full range of
56    shutdown specifications.
57 
58 
59 Access required: You must have re access to dm_admin_gate_.