SOFTWARE HONEYWELL

HONEYWELL

MULTICS

ADMINISTRATION,

MAINTENANCE,

AND OPERATIONS

COMMANDS

SUBJECT

MULTICS ADMINISTRATION, MAINTENANCE, AND OPERATIONS COMMANDS

Description of Multics Commands Available for Use by System Administrators, System Maintainers, and System Operators

SPECIAL INSTRUCTIONS

This document contains Multics commands consolidated from the following Multics manuals: MAM System Administrator (AK50), MAM Project Administrator (AK51), MAM Registration and Accounting Administrator (AS68), IvIAivI Resource Control (CC74), ivfAivl Communications (CC75), Bulk I/O (CC34), Multics Operator's handbook (AM81), Multics System Metering (AN52), and Multics System Diagnostic Aids (AR97).

Throughout this' manual, marginal change indicators (change bars and asterisks) only indicate technical information added (or deleted) to support Multics Release 11.0. Marginal change indicators are not used to indicate information shifted from another manual.

SOFTWARE SUPPORTED

M:ultics Software Release 11.0

ORDER NUMBER

GB64-00 June 1985

PREFACE

This document describes those Multics Commands specifically designed for use by individuals filling the roles of (1) system administrators, (2) system maintainers, or (3) system operators.

System administrators provide their sites with a particular Multics operating environment.

They are responsible for such tasks as controlling and allocating resources; registering projects and users; creating load control groups; setting prices on resources; setting limits on, and billing for, resource usage; scheduling system activities such as hours of operation, shift change times. and unattended service; describing site parameters and setting site options; and assuring system security.

System maintainers configure and tune the operating system to make it comply with the special requirements of their sites. They are responsible for such tasks as backing up and recovering the system, salvaging and scavenging, analyzing crashes, balancing

disks~ setting up I/O daemons and the message coordinator, metering and tuning, and maintaining system databases.

Operators are responsible for everyday central site services such as system startup and shutdown, mounting and demounting of storage devices. operation of the I/O daemons.

communication with remote users, and first-level maintenance.

A detailed description of the procedures associated with each of the three user groups (administrators, maintainers, and operators) is found in the following three manuals:

System Administration Procedures (Order No. AK50) System Maintenance Procedures (Order No. AM81) Operator's Guide to Multics (Order No. GB6l)

This manual is designed as a reference work to be uSed together with one of the procedural manuals specified above. Those manuals function

as

"how to" documents, making reference.

as

needed, to the specific commands required to implement the various procedures. This manual complements the procedural manuals by providing a detailed description of the commands.

Each command description in this manual provides. minimally, the long and short name, syntax line, and function of the program. Standard headings. in the order in which they appear, when present, are

as

follows:

SYNTAX AS A COMMAND

SYNTAX AS AN ACTIVE FUNCTION FUNCTION

ARGUMENTS

CONTROL ARGUMENTS ACCESS REQUIRED NOTES

EXAMPLES

Syntax lines give the order of required and optional arguments accepted by a command or active function. Optional portions of syntax are enclosed in braces ({}).

The syntax for active functions is always shown enclosed in brackets ([]), which are required for active function

use.

To indieate that a command accepts more than one of a specific argument, an "s" is added to the argument name (e.g., paths, {paths} ,

{-control_args} ).

A series of arguments enclosed in nested braces (e.g., {argl {arg2 {arg3}}}) indicate that, while you can omit all the arguments, if you give anyone of them, you must also give the ones preceding it in the list. .

Siruificant Changes

in

GB64-00A

In the following lists, the number in parentheses is the section where the command is, or was, documented.

The following commands are new; they contain no change indieators.

adddev (4) copy_disk (9) debu!Lfnp (2) deldev (4)

display _lo!Lsegment (2) display _proc_audit_flags (2) edit_process_audit_flags (2)

edit_project (2)

lock_mea (2, 4, and 9) restore (9)

save (9)

set_process_audit_flags (2) unlock_mea (2, 4, 9)

The following commands are not privileged; they have been removed from the manual.

They belong in the Commands manual (AG92).

compare_configuration_deck (2) print_configuration_deck (2)

The following commands were accidentally left out for MR11.0:

display _disk_label (2) read_cards (6)

The following command is obsolete:

bos (9)

Section 10 and its 36 commands are obsolete.

Section

1

Section

2

CONTENTS

Introduction . . . . Organization of the Commands . . . . Moving From One Command Environment to Another BCE Command Environment . . . . Initializer Command Environment . . . . User Command Environment . . . . Registration and Accounting Command

Environment . . . . Daemon Command Environment . . . . Getting Online Help with Commands . . . . Privileged Multics Commands . . . _. . . . add_mail_table_entry . . . . . . . add_ volume_registration (avr) . . . . admin_mode_exit (arne) . . . . admin_util . . . . adopt_seg . . . . alarm_clock_meters . . . . analyze_multics -(azm) . . . . as_who . . . .

~kup __ dumJt . . . . backup __ load . . . . bind_fnp . . . . before.,joumal_meters (bjmt) . . . . bootload_fs . . . . cache_meters . . . . change_kst_attributes . . . . . . . change_tuninLparameters (ctp) . . . . change_volume_registration (cvr) . . . . channel_comm_meters . . . '. . . .. . . . charge_disk . . . . check_cpu __ speed. . • • . . . • • • • • . . . . • • check_dir . . . . check_mdcs . . . . check_IDSt . . . . check_sst_size . . . . check_tc_data_size . . . . clea.n._C&,iQ_'pool • • • • • • • • • • • • • • • • • • • • clear_partition . . . . clear-Pl'ojfile . . . . clear_reqfile . . . . . . . clear_resource (cIt) . . . . . . . . command_usage_count (cuc) .. . . . . compact_mail_table (salvage_mail_table) . . . . compare_configuration_deck . . . . . compare_IDSt . . . .

1-1

1-1

1-2

1-2

1-2

1-3

1-5

1-5

1-5

2-1

2-2

1,-7

2-4

2-7

2-11

2-12

2-14

2-45

2-49

2-53

2-58

2-59

2-63

2-67

2-69

2-70

2-71

2-75

2-80

2-81

2-82

2-82

2-83

2-86

2-87

2-88

2-89

2-90

2-90

2-91

2-91

2-94

2-95

2-98

compute_bill . . . . console_report . . . . convert_con figuration_deck . . . . copy _as_meters . . . . copy _deadproc . . . . copy _dump . . . ^{= • • • •} copy_mst (cpm) . . . . copy_registry . . . . create_daemon_queues (cdq) . . . . create_mail_table . . . . create_pnt . . . . . . . create_urf . . . . cv_cmf . . . . cv_dmcf . . . . cv_pmf . . . . cv _prt_rqti . . . . cv_rtmf . . . . daily_summary . . . . deactivate_seg . . . . debug,.Jnp (db_fnp) . . . . define_ work_class (dwc) . . . . delete_mail_table_entry . . . . delete_old_pdds . . . . delete_proj . . . . delete_registry . . . . delete_volume_registration (dvr) . . . . deregister_resource (drr) . . . . disk_meters . . . . disk_queue (dq) . . . . disk_stat_print . . . . disk_usage_stat . . . . disklow . . . . display _account_status (das) . . . . display _anst . . . . display _aste . . . . display_aut . . . . display_branch . . . . display _cache_threshold . . . . display_edt . . . . display _cpu_error . . . . display _disk_label (ddl) . . . . display _dut . . . . display _fnp_idle . . . . display _ioi_data . . . . display_kst_entry . . . • . . . display _loLsegment . . . . display _mstb . . . . display _process_audit_flags . . . . display

_prt_fqti . . . .

display -l>SP • • • • • • • . • • • • • • • • • . • . • . display _pvte . . . .

2-98 2-100 2-104 2-104 2-105 2-106 2-106 2-106 2-108 2-109 2-109 2-110 2-111 2-112 2-115 2-117 2-118 2-119 2-120 2-121 2-122.11 2-122.12 2-123 2-124 2-124 2-125 2-126 2-126 2-131 2-132 2-134 2-134 2-135 2-138 2-139 2-141 2-143 2-143 2-144 2-145 2-147 2-148.1 2-148.3 2-150 2-152 2-153 2-154 2-154.1

'"

..

^~

..

^'"

~-~~

....

^~

2-154.2

2-155

display _ vtoce . . . . dm_Iock_meters . . . . dm_Iock_status . . . . dm_send_request . . . . dm_set.Journal_stamps . . . . . . . dm_set_system_dir . . . . dm_system_shutdown . . . . . . .

dump~firmware . . . • . . . dump_mpc . . . . dump_partition . . . . ed_installation_parms . . . . ed_mgt . . . . edit_process_audit_flags . . . . edit_proj . . . ' . . . . edit-Pl"oj$change_all . . . . eis_tester (et) . . . . enter_Iss . . . . excerpt_mst . . . . exercise_disk . . . . file_system_meters (fsm) . . . . fim_meters . . . . fix_quota_used . . . . flush . . . . . . fnp_data_summary . . . . fnp_throughput . . . . format_disk_pack (fdp) . . . .

generate~mst(gm) . . . . get_flag'box . . . . get_uid_with_lastname . . . . hc_pf_meters . . . . hp_delete (hpdI) . . . . bp_delete_acl (hpda) . . . . hp_delete_ vtoce . . . . hp_set_acl (hpsa) . . . . hpset_dir_rinLbrackets (hpdsrb) . . . . hpset_rinLbrackets (hpsrb) . . . . idump . . . . inhibi t_pv . . . '. . . install . . . . instr_S})eed . . . . interrupt_meters (intm) . . . . io_error_summary . . . . iod_command . . . . iod_tables_compiler . . . . iod_val . . . . is_he_user . . . . is_Iegal_proj . . . . link_meters . . . . list_as_requests . . . . list_delegated_projects • . . . • . . . . list_extra_personids . . . .

list~t . . • . . . • . . • . . . list_partitions . . . . list_proc_required . . . .

2-158 2-161 2-163 2-164 2-166 2-167 2-168 2-171 2-172 2-174 2-175 2-191 2-208 2-208.1 2-208.5 2-210 2-240 2-240 2-241 2-243 2-252 2-254 2-255 2-255 2-257 2-258 2-262 2-270 2-272 2-272 2-274

'" ",,,,r

~-~/;]

2-277

2-279

2-280

2-281

2-282

2-283

2-283

2-285

2-285

2-288

2-289

2-290

2-291

2-292

2-292

2-293

2-295

2-295

2-296

2-297

2-297

2-298

list_vols . . . . list_volume_registration (Ivr) . . . . load_ctl_status . . . .

1", ... ^~ ... _

lVUW_llJ.}"W • • • • • • • • • • • • • • • • • • • • • • • •

lock_mea . . . . make_commands . . . . make_volume_labels . . . . map355 . . . . mc_trace (mct) . . . . mcs_ version . . . . meter_fnp_idle . . . . meter-sate (mg) . . . . meter_rcp . . . . meter _sigIlal . . . . . . . monitor_cache . . . . monitor_sys_log (msI) . . . . mos_edac_summary . . . . move_dir_quota . . . . move_los-segments . . . . mpe_data_summary . . . . ms_create (mscr) . . . . new_user . . . . patch_firmware . . . . pdt_copy . . . .

:P011_fnp . . . • . . . • . . •

:POll_mos_memory . . . .

:P011_mpe . . . • . . • . . . • . . .

post_purge_meters (ppm) . . . . print_apt_entry (pae) . . . . print_devices . . . . print_disk . . . . print_iod_tables . . . . print_line_ids . . . . print_meters . . . . print_pdt . . . . prin t-Pll t . . . . print_projfile . . . . print_req.file . . . .' . . . print_sat . . . . print_spoolinLtape . . . . prin t_sys_Iog (psI) . . . • . . . . • . . . print_tuninLparameters (ptp) . . . . print_urf . . . . priv _move_quota . . . . process_id . . . . proLusage_report (pur) . . . . read_early _dump_tape (redt) . . . . reclassify _dir . . . .

reclassify _seg . . . .

reclassify _sys_seg . . . . reconfigure . . . .

2-299 2-304 2-305

"'" """,

~--,uo

2-307 2-307 2-309 2-311 2-313 2-325 2-325 2-326 2-331 2-333 2-335 2-336 2-346 2-347 2-348 2-350 2-351 2-352 2-358 2-359 2-360 2-361 2-362 2-363

2-365

2-369 2-370 2-370 2-371 2-371 2-372 2-373 2-374 2-375 2-375 2-377 2-381 2-389 2-391 2-391 2-392 2-394 2-396 2-396

"_,,n..,

~-:J:11

2-398 2-399

register _mdir . . . . register_resource (rgr) . . . . reload . . . . remove_registry . . . . retIlove_user . . . . reset_edt_meters . . . . reset_disk_meters . . . • . . . reset..:.,.soos • • • • • • • • . • • • • • • . • • • • • • • reset_usage . . . . reset_use_totals . . . .

r~nse_meters

. . . . restore_pdt_access . . . . retrieve . . . . rinLzero_dump (rzd) . . . . salvage_dir . . . • . . . . . . . . salvage_mstb . . . . save_history _registers . .. . . . . sc_command . . . . scavenge_vol . . . . sector_to_record . . . . send_adMin_command (sac) . . . . send_daemon_command . . . . send_ips . . . . send_wakeup . . . . set_dir_quota . . . . set_flag'box . . . . set_loLhis-tory:..,.dir . . . . set_mc_message_limits . . . • . . . set_mos_pollinLtime . . . . set_proc_required (sprq) . . . . set_process_audit_flags . . . . set_Quota

(sq) . . . • . • . . . . • . . . . .

set_SODS_ volume . . . • . . . . set_special_password . . . . set_system ... audit_flags . . . . set_systeM_console . . . .

seL~stem_priv

. . . . set_system_search_rules • . . . . set_ timax (stm) . . . . set_tpp (stpp) . . . . set_ work_class (swc) . . . . set_x25_packet_threshold . . . . sort_projfile . . . . sort_reqfile . . . . summarize_sys_log (ss1) . . . .

C!U7_'"

., .... 'WW',t' • • • • • • • • • • • • • • • • • • • • • • • • • •

sweep_pv . . . . sys_fu1l_report . . . • . . . . systen1_comm_meters .. . . . . system_daily _report . . • . . • • • ;, • . • . . . .

~tem_link_meters

. . . . system_monthly_report . . . .

~tem_performance..sraph

(spg) . . . . system_total . . . • . . .

2-407 2-408 2-416 2-421 2-421

2~422

2-422

2-423

2-424

2-425

2-426

2-431

2-432

2-437

2-441

2-443

2-443

2-444

2-445

2-441

2-447

2-449

2-451

2-451

2-452

2-453

2-454

2-455

2-456

2-456

2-458

2-458.1

2-459

2-459

2-460

2-462

2-463

2-465

2-466

2-467

2-469

2-470

2-471

2-472

2-472

2-480

2-482

2-484

2-485

2-487

2-488

2-491

2-492

2-496

test_cpu . . . . test_dcw . . . ^{0 0 0 • • •} test_fnp . . ^{0 • 0 • 0 • 0 • • 0 0 0 0 0 0 • 0 • 0 0 0 0}

+~+ : ... ...:I~ ... - - -

~"_lU_U4Cl11U1J. • • • 0 0 0 • 0 0 0 0 0 • 0 0 • • 0 0 •

test_taJ)e . . . ^{0 0 0 • • • • • • 0 0 0 0 0 0 0 • 0 • • •} total_time_meters (ttm) . . ^{0 0 • • 0 0 0 0 • 0 • 0 0} traffic_control_meters (tern) ^{0 • • • • • • • • • • • •} traffic_control_queue (tcq) ^{0 0 • • • 0 • • • • • 0 0 •} tty_dump . . . ^{0 • • 0} • • • • • • • • • 0 • • • • •

tty_lines . . . ⁰ • • • • • 0 • • • • 0 0 • • • 0 0 •

tune_disk . . . ^{0 • • 0 • 0} • • • • • • • 0 • •

tune_work_class (twc) . ^{0 • 0 • • 0 • • • 0 0 0 0 0 •} unlock_mca . . ^{0 • • • • 0 • 0 0 • • 0 0 • 0 0 • • 0 •} unwire_pages ^{0 • 0 • • • • • • 0 • • • • • • • • • • • •} up_ctr . ^{0 • • • 0 • 0} • • • • • • • • • 0 • • 0 • • • •

update_mail_table_entry . ^{0 • • • • • 0 • • • 0 0 • •} usage_and_revenue . ^{0 • • • • • 0 • • 0 • • 0 0 • • 0} usage_total ^{0 0 • • • 0 0 • 0 • • • • • • • • • 0 0 0 0 •} vtoc_buffer_meters . . . . ^{0 0 • 0 0 • • • • 0 0 0 0 •} vtoc_pathname ^{0 • 0 0 • 0 0 0 0 0 0 • 0 0 • ' . 0 0 0 0 0} vtocx_ to_record ^{0 • • • • • • 0 0 0 0 0 • 0 • • 0 0 0 •} wire_pages . . . ⁰ • • • • • • • • • • 0 0 • • 0 0 • • 0

work_class_meters (wcm) . . . ^{0 • • 0 0 • • 0 • •} write_acct_bill ^{0 0 0 0 • • • 0 • • • 0 • 0 • 0 0 • 0 0 0} write_billin&-summary . ^{0 • • • • 0 • • • • 0 0 • • •} write_notify _test . . . ^{0 • 0 • • 0 • • 0 •} write_user_usage_report . ^{0 • • • 0 • • • • • • 0 • •} Section 3 Accounting Commands· . . . .

add_anon . . . ⁰ • • • • 0 • 0 • • • • • • 0 • •

bill . . . ^{0 • 0 • •}

chaddr . . . ^{0 •}

chalias . . . ⁰ • • • • • • • • 0 • 0 • • • change . . ⁰ • • • • 0 • • • • • • • • • • • • 0 • • • • charge . . ' . . . ⁰ • • • • • • • • • • • • • • • •

chcJ)8SS . . . ' . . . ⁰ • • • • •

chdf -Pl'o j . . . ^{0 • • • • • • • • • • • • • • • •}

check_log . . . . chname . . . ^{0 • • •}

chJ)aSS . . . ⁰ • • • • • • • • •

chprog . . . ^{0 • •}

credit . . . ⁰ • • • • • • • • • • • • • • • • • •

cu . . . ⁰ • • • • • • • • • • • • •

day . . . . delegate . . . ⁰ • • • • • • • • • • • • • • • •

disk_report (drp, disk_auto) . . . . dmisc . . . . dptIlf . . . . dproj . . . . edit_proj . . . • . . . install . . . ⁰

2-497

2-504

2-519

2-520

2-524

2-526

2-530

2-535

2-539

2-541

2-543

2-545

2-546

2-546.1

2-547

2-547

2-549

2-551

2-552

2-555

2-556

2-556

2-557

2-561

2-561

2-562

2-564

3-1

3-3

3-4

3-5

3-6

3-6

3-9

3-9

3-10

3-11

3-13

3-14

3-15

3-16

3-16

3-17

3-18

3-19

3-20

3-20

3 ... 21

3-22

3-24

Section 4

pmisc . . . • . . . . . 3-36 proLmtd . . . . . 3-38 recov . . . . . 3-39 register . . . . . 3-39 rename_proj . . . . . 3-41 rqm . . . . . 3-42 setcrank . . . 3-43 setdisk . . . ~ . . . ... . . . . 3-43 undelegate . . . 3-44 upmf . . . • . . . .. 3-45 who_delg . . . . . 3-46 Initializer Commands . . . .

abs • . • • • • • • • • • • • • • • • • • . • • • • . ••

accept . . . . add_Iv (alv) . . . . add_pdir _volume . . . . adddev (addd) . . . . add_vol (av) . . . . adddev (addd) . . . . admin . . . . attach . . . . 'bee • • • • • • • • • • • • • • • • • • • • • • • • • • • bump . . . . cripple . . . . . . • . . . debug . . . . define . . . . del_Iv (dlv) . . . . del_pdir_ volume . . . . del_vol (dv) . . . . deldev (deld) . . . .

deroute . . . .

detach . . . . disconnect . . . . display_volume_log . . . . down . . . • . . . drop . . . . dump_mpx . . . .

exec (x) . . . .

force_reset . . . . go . . . . help . . . . hmu . . . . init_ vol . . . . intercom . • . . . . list_disks (ld) • . . . load_mpx • . . .

lock_mea . . . • . . .

log . . . • • • . . . login (logi) . . . .. . . .. . . . logout (logo) . . . . maxunits (maxu) • . • • • • • • • • • . • • • • • . . • mc_list . • . . . • . . • . . . .

message

(motd) . . . • . . .

4-1 4-2 4-10 4-11 4-12 4-13 4-13 4-14 4-15 4-15 4-16 4-17 4-19 4-19

4-20

4-20 4-21 4-21 4-22

4-22

4-23 4-24 4-25 4-25.1 4-26 4-27 4-27

4-29

4-29 4-30

4-30

4-31

4-34 4-34 4-36

4-37 4-37 4-38 4-40 4-41 4-41 4-42

Section 5

multics (mult) . . . . . 4-43 no_start (ns) . . . . . 4-44 preload . . . . . 4-44 quit . . . 0 0 • 0 • • • • • • • • • • 4=45 rep . . ^{0 • 0 0 • • • • • • • • • • • • • • • • • • • • •} 4-45 rebuild_disk . . . ^{0 0 0 0 0 0 0 0 0 • • • • • • • •} 4-47 reconfigure (ref) . . . ^{0 • • • • • • • • • • • • •} 4-48 recover_volume_log . . . . ^{0 • • • • 0 • • • • • • • •} 4-51 redefine . ^{0 • • • • • • • • 0 0 0 0 0 0 0 0 0 • 0 • 0 0} 4-52 release 0 . . . 0 • 0 0 0 • 0 • 0 0 0 4-53 reload . ^{0 • • 0 • 0 0 0 0 • • • • • • • • • • • • • • •} 4-54 reload_system_release . . . . . 4-58 reload_volume . . . . ^{0 0 • • • 0 • • • •} 4-62 remove . . ^{0 • • • • • • • • 0 • • 0 • • 0 • • 0 0 0 • 0} 4-65 reply (d . ^{0 0 • • 0 0 • • 0 • • 0 • 0 • • • 0 • • •} o. 4-65 reregister . . ⁰ • • • • • • • ' 0 • • • • • • • • • • • • 4-66 reroute ^{0 0 0 • • • • • 0 0 • 0 • 0 0 • • • • • • • • • 0} 4-67 reset ^{0 0 0 0 0 0} o. ⁰ • • • • • 0 • 0 • 0 0 • 0 • • 0 • • 4-68 route . . . ^{0 • • 0 • 0 0 0 0 0 0 0 • • • 0 0 • 0 • • • •} 4-68 salvage_dirs (salv) . . . .. . . . . 4-69 salvage_vol ^{0 • 0 0 • • • 0 0 • • • • • 0 • • 0 • • • • •} 4-69 set_drive_usage (sdu) ⁰ • • • • • • • • • • • • 0 0 • • 4-70

set-Pdir~volumes . . . . ^{0 • • • • • • 0 0 • 0 • • • •} 4-71 shift . ⁰ • • • • 0 0 • • 0 • • • • • • 0 • 0 • 0 • 0 O . 4-72 shutdown (shut) . . . . ^{0 0 0 0 • • 0} 4-74 sign_off

0... 0

4-75 sign_on . . . . . 4-75 standard (stan) . . . 4~ 76 start_mpx . " . . . 4-76 startup (star) . . . . . 4-77 stop . . . . . 4-77 stop_mpx . . . . ^{0 0 • 0 • • • • • 0 • 0 • • 0 • •} 4-78 sUbstty . ^{0 0 0 0 • 0 0 • 0 0 0 • 0 0 • 0 0 0 0 0 0 • 0 0} 4-79 sysid ^{0 0 0 • • 0 • 0} • • • • • • • • • • • • • • • 0 0 0 4-80 terminate (term) . . . ⁰ • • • • • 0 0 0 • • 0

o.

4-81 unbump

0... o.

4-82 undefine . . . . ⁰ • • • • • 0 0 • • • • • • • • 0 0 O . 4-82 unload . . . ^{0 • 0 • • • • • • • • • 0 0 0} 4-83 unlock_mea . . . ^{0 • 0 • • • •} o. 4-84 vacate-Pdir _volume . . . ^{0 • • • 0 0 0 • • • • • •}

o.

4-84 warn (w) . . ^{0 0 • 0 0} • • • • 0 • • • 0 • 0 0 • 0 • O . 4-85

who ^{0 • • 0 • 0} • • • • • 0 • • 0 • 0 • • • • • • • • 0 0

4-86

word . . ^{0 • 0 0 • 0 • 0 • 0 • 0 • 0 • • 0 • • 0 • 0 • •} 4-88 Initializer

Exec Commands . . .

⁰ • • • • •

attended (attend) . . . ^{0 • • • • • • • • • • • • •} auth . . . ⁰ • • • • • • 0 • • • • • • 0 • • • • • •

auto . ^{0 • • • • • • • • 0 0} • • • • 0 • • • 0 • • • • •

cat . . . ; : : ; ; ; . . . complete_volume (vcomp) . . . . .; . . . . consolidated_volume (vcons) . . . . ^{0 0 • • • • • • •}

5-1 5-2 5-2 5-4

<-<

., ., 5-6 5-6

echoplex . . . 5-8 end_dump . . . " . . . . 5-9 inc . . . 5-9 incremental_volume (vinc) . . . 5-10 io . . . . . 5-11 iol . . . 5-11 meter . . . . . 5-11 print_queues (pq) . . . . . 5-12 punch (puna) . . . 5-12 punch_end (end_punch) . . . 5-12 punch_restart . . . 5-13 read_cards (cards. rc) . . . 5-13 repair . . . . . 5-13 reprint (rep) . . . . . 5-14 reset_phcs_access (rpa) . . . . . 5-15 reset_tabs (tabs, rt) . . . . . 5-15 scav . . . . . 5-16 set_fdump_number (set_fdump, sfdn) . . . 5-16 set_phcs_access (spa) . . . 5-17 unattended (unattend) . . . . . 5-17 wakeup_dump . . . . . . . 5-18 Section 6 I/O Daemon Commands . . . . . 6-1

auto_queue . . . . . 6-2 auto_start ... delay . . . . . 6-2 banner_bars . . . 6-3

banner~type . . . "6-3 cancel . . . 6-4 clean_pool . " . . . . . . . . 6-5 copy . . . 6-5 ctl_term . . . 6-6 deier . . . . . 6-7 defer_time . . . . . 6-7 go . . . . . 6-8 halt . . . . . 6-8 hasp_host_operators_console (hhoc) . . . . . 6-9 help . . . 6-11 help . . . 6-11 hold . . . 6-11 inactive_limit . . . 6-12 kill . . . 6-12 list . . . 6-13 listen . . . . . . . 6-13 logout . . . 6-13 logout . . . 6-14

master . . .

6-14 new_device . . . . . 6-14 next. . . . . 6-15 paper _info. . . . . 6-16 J)3.use_time . . . ~ . . . . . 6-17 print (pr) . . . 6-17 print_devices. . . . . 6-17 print_devices . . . . . 6-18 print_line_ids . . . 6-18

Section 7

prt_control . . . . pun_control . . . . punch . . . .

rpJtd_cards . . . •

ready . . . . receive . . . . reinit . . . . release . . . . . . . re<l-status . . . . . . . request_type (rqt) . . . . restart . . . . . . . restart_q . . . . restart_status . . . . runout_spa.cing . . . . sample . . . . sample_f orm . . . . sample_hs . . . . save . . . . sep_cards . . . . single . . . . slave . . . . slave_term . . . . start . . . . start . . . . station . . . . status . . . . step . . . . term . . . .

wait_status .". . . . x (xxxx) . • . . • • • . • • • • • . • • . • • . . .

Volume Backup Daemon Limited Service Subsystem

Commands . . . . complete_volume_dump . . . . consolidated_volume_dump . . . . delete_volume_log . . . . display _pvolog . . . . display_volume_log . . . . dmpr_unlock_pv . . . . end_volume_dump . . . . incremental_volume_dump . . . . list_retrieval_requests (Irr) ., . . . . merge_volume_log . . . . preattach_dump_ volumes . . . . purge_volume_log . . . . rebuild_pvolog . . . . recover_volume_log . . . • . . . . reloa.d_ volume . . . . retrieve_from_ volume . . . .

^{= = •}

set_volume_log . . . ; . . . set_volume_wakeup_interval . . . .

6-19

6-20

6-21

6-21

6-22

6-22

6-23

6-23.1

6-24

6-25

6-25

6-26

6-27

6-27

6-28

6-28

6-29

6-29

6-30

6-31

6-31

6-32

6-33

6-33

6-33

6-34

6-35

6-36

6-36

6-37

7-1

7-3

7-5

7-8

7-8

7-9

7-10

7-11

7-11

7-14

7-16

7-16

7-17

7-18

7-19

7-20

7-22

7-24

7-25

Section 8

Section

9

Appendix A

Figure

1-1.

volume_dump_trace_on ^{0 • • • 0 • 0 0 • 0 0 • • • • •}

7-27

wakeup._volume_dump . . .

7-28

Hierarchy Backup Daemon Limited Service Subsystem

Commands . . . . catchup_dump . . . . complete_dump . . . . end_dump . . . . start_dump . . . . wakeup_dump . . . . BCE Commands . . . . ^I

alert . . . . bce . . . . bee_state (bees) • . . • . . . • . . • • • • • • • • . • boot . . . . confis-edit (config) . . . . continue (go) . . . . copy_disk . . . . delete (d}) . . . . . . die . . . . display _disk_label (ddI) . . . . dump . . . .

emergency_shutdown.

(esd) . . . • • . . . exec_com (ec) . . . .

fwload (fw) ~...

get_flagbox (gfb) . . . . . . . init_files . . . . list (Is) . . . . • . . . . • . . • • . . . . • • . • . . . list_requests (Ir) . . . . • . • . . • . . . • . lock_mca . . . . print (pr) . . . • . . . • . . . probe (pb) . . . • . . . . qedx (qx) . . . . reini tialize (reini t) . . . . rename (rn) . . . . restore . . . ' . . . . save . . . . set_flagbox (sfb) . . . . severity . . . . shutdown_state (sds) • • • . • • • • • . • • • . • . . test_disk (td) . . . • • . . . • . . .

unlock_mea . . . .

Configuration

Deck

Description

8-1 8-3 8-8 8-13 8-14 8-20 9-1 9-2 9-2 9-2 9-3 9-5

9-6

9-7 9-9 9-9 9-10 9-12 9-15.1 9-15.1 9-15.2 9-16 9-17

9-17

9-17

9-17

9-18

9-18

9-24

9-25

9-26

9-27

9-30

9-33

9-34

9-35

9-36

A-1

Illustrations Moving from One Command Environment to Another

1-7

Table 1.

Index

Rep Effective Access . . . .

Tables 2-414

i-I

SECTION 1 INTRODUCTION

ORGANIZATION OF THE COMMANDS

The commands in this document are organized into eight sections (Section 2 through Section 9), as described below.

The commands in Section 2 do not require you to be in a "special"

environment They do, however, require that you have access to the segments and directories they reference. At most sites, required access are set only for those individuals on the SysAdmin, SysMaint, or Opr projects.

The commands in Section 3 are entry points (labels) in master.ec. The registration and accounting administrator issues a limited set of entry points in master.ec. The system administrator can act in the role of registration and accounting administrator.

The commands in Section 4 can

Pe

used only when communicating with the initializer process.

The commands in Section 5 can be used only when communicating with the initializer process. These commands are also contained within admin.ec and require that you type "exec" (x) prior to typing the command.

The commands in Section 6 can be used only when communicating with the I/O daemons (i.e., the I/O daemon coordinator and drivers).

The commands in Section 7 are contained within a Honeywell-provided limited-service subsystem and are used for communicating with the Volume_Dumper. Daemon, the Volume_Reloader.Daemon, or the Volume_Retriever . Daemon.

The commands in Section 8 are contained within a Honeywell-provided limited-service subsystem and are used for communicating with the Backup.SysDaemon and the Dumper.SysDaemon.

•

The commands in Section 9 can be executed only within the restricted environment of the Bootload Command Environment (BeE).

COMMAND ENVIRONMENTS

The Multics system "handles" each command by first interpreting the request and then invoking the necessary system software components to perform the required function. The commands in this manual are organized according to the system software components (the environment) required for execution.

It is the presence of the different software components that forms the

"command environment" The way in which you enter a specific command environment is described at the beginning of each command-specific section. The system software components required for command execution are automatically made available when you perform the required actions.

MOVING FROM ONE COMMAND ENVIRONMENT TO ANOTHER

In some cases you can log in in one environment and move to another environment The Multics system includes various transitional commands that permit you to enter two or more command environments while logged in at a single session.

Figure 1-1 shows the commands that you can issue to move from one command environment to another; that process is described below.

BCE Command Environment

The first activity in starting or bringing up a Multics system involves the

• loading of the BCE (Bootload Command En:vironment) software. While BCE is running, you can enter and execute only BCE commands.

Once the Multics operating system software is bootloaded and the initializer process is active, it is not possible, without executing the shutdown command, to

• reenter the BCE command environment

Initializer Command Environment

The initializer process is the system control process for Multics. The initializer process is created automatically as a result of a successful Multics bootload operation.

The initializer process can be active in ring 1 or 4. If the "star" argument was

• used with the BCE boot command, then the initializer process moves directly to ring 4 without pausing in ring 1. The system is also made ready for normal user sessions (users can log in from remote terminals).

If Multics is not booted with the boot star command, the initializer is first brought to command level in ring 1. The initializer remains in ring 1 until the operator moves it to ring 4 using the standard command or the multics command.

The operator must then issue the startup command or the go command to make the system available for normal user sessions (users can log in from remote terminals).

You use the initializer commands and the initializer exec commands to communicate with the initializer process. Certain initializer commands can be used only when the initializer process is operating in ring 1. Others can be used only when the initializer process is operating in ring 4. Some can be used at either time. The description of the initializer commands in Section 4 indicates when the individual command can be used. The initializer exec commands can be used only when the initializer is operating in ring 4.

The initializer process remains active as long as the system is running. In its normal mode of operation the initializer responds only to initializer commands or initializer exec commands. Sometimes, however, it is desirable to use the initializer process to execute a "normal" Multics command (i.e., any command that is not an initializer command, an initializer exec command, or a BCE command). To use the

*

initializer to execute a "normal" command you must enter the initializer admin mode by issuing the admin command. When in admin mode the initializer process responds to "normal" commands instead of to the initializer commands or the initializer exec commands.

Once in admin mode you can- -shift -back to the -- initializer command environment by issuing the admin_mode_exit command. Alternatively, if you want to remain in admin mode but want to execute a single initializer command from time to time, you can do the following:

1. if you want to enter an initiaiizer commana \excepting the exec commands), you must use the sc_command together with the desired initializer command, as in

2. If you want to enter an initializer exec command, you must use the ec admin command together with the desired exec command, as in

ec admin attended

While in the initializer command environment, you can communicate with the system daemon process(es) by the initializer reply command. You use the reply command together with the daemon driver label and the daemon command, as in

reply prta go

If you want to interrupt daemon execution while in the initializer process, you must issue the initializer quit command (and not press the A TIN or INTERRUPT key).

User Command Environment

Once the bootload/initialization sequence is complete the system becomes available for normal user sessions. Users log in at remote terminals to perform assigned work. in a normal session you can use a wide variety oi commands, including the privileged commands (see Section 2) as well as the commands described in the Commands manual (AG92).

While in the user command environment, you can't use any of the "special"

environment commands described in this manual; you can, however, move to those special environments by using transitional commands:

1. If you want to enter an initializer command (excepting the exec commands), you must use the send_admin_command command (which enters initializer admin mode) and the sc_command command together with the desired initializer command, as in

sac sc_command maxu auto

2. If you want to enter an initializer exec command, you must use the send_admin_command command and the ec admin command together with the desired exec command, as in

sac ec admin attended

3. If you want to submit a "normal" command to the initializer process, you must enter initializer admin mode by using the send_admIn_command command together with the selected "normal" command, as in

sac set_system_consoie -reset·

4. If you want to enter a daemon command, you can use the send_daemon_command command, as in

Alternatively, you can use the send_admin_command command and the sc command command together with the initializer reply command, the daemon driver label, and the desired daemon command, as in

sac sc_command reply prta go

5. If you are a system administrator, you can enter an accounting command by changing your working directory to >udd>SysAdmin>admin (see Section 3) and using the ec master command together with the selected accounting command, as in

ec master bill prepare

Registration and Accounting Command Environment

A registration and accounting administrator is restricted by a special process overseer to a limited set of commands and cannot move to another command environment If you are a system administrator. you can move into. or out of, the registration and accounting command environment by changing your working directory (see Section 3).

Daemon Command Environment

The I/O daemon command environment uses a special process overseer Hod-overseer) and a special set of search rules; you can't shift from this environment to another. The commands in the volume backup daemon command environment are contained within a Honeywell-supplied limited-service subsystem; you can't shift from this environment to another. The commands for two of the hierarchy backup daemons (Backup.SysDaemon and Dumper.SysDaemon) are also contained within a Honeywell-supplied limited-service subsystem; you can't shift from this environment to another.

GETTING ONLINE HELP WITH COMMANDS

There are information segments (info segs) for the commands in this manual in the following directories:

Commands Directories

Commands in Section

2

>doc>pr i v i 1 eged Commands in Section 3 >doc>ss>accounting

COiin"iiands in e __ . : __

J. >doc>ss>Operator

~C"'LIUII

...

(Ring 4 commands only)

Commands in Sect

i

on 4 >doc>ss>rl in it

i

ali zer (Ri ng

1

commands onl y)

Commands in Section 5 >doc>ss>operator Commands in Section 6 >doc>ss>io_daemon Commands in Section

7

>doc>pr i vi 1 eged Commands in Section 8 >doc>pr i v i 1 eged Commands

in Section ^Q ,.,

>doc>ss>bce

*

If you're in the user command environment, the volume backup limited-service subsystem, or the hierarchy backup limited-service subsystem, you can use the user help command to look at the above info segs. When using the help command, however, you must specify the absolute pathname of the info seg, as in the following

example.

help >doc>privileged>set_system_console

Alternatively, you can add one or more directories to your info search list by adding a line to your start_up.ec; for example,

asp info >doc>privileged

Then, you can look up info segs in the directories without having to specify the absolute pathname; for example,

If you're in the ring 4 initializer command environment, you can look at info segs for ring 4 initializer commands by using the initializer help command; for example,

help down

If the info seg you want to look at is for an exec command, you must specify the name in the format "x. command , " as in

help x.attended

If you're in the ring 1 initializer command environment, the registration and

*

accounting command environment, the I/O daemon command environment, or the BeE command environment, you can't look at info segs.

BCE

l

^boot

MULTICS RING 1

l

standard or multics MULTICS RING 4

boot startup

sc_command or arne admin

..

t

sac ed admin DAEMON sac sc_command reply" USER / ' COMMANDS ...

11---

^COMMANDS

ecadmin

~

^{exec, x} tiO(LCOmmand

I

accounts_overseer or

+

^{ec master}

DAEMON EXEC COMMANDS

ACCOUNTING COMMANDS

INITIALIZER ADMIN MODE

Figure 1-1. Moving From One Command Environment to Another

SECTION 2 PRIVILEGED MUL TICS COMMANDS

The commands in this section do not require you to be in a "special"

environment. You can use these commands while logged in at a remote terminal in a normal user session. However. these commands do perform operations on "privileged"

data bases and tables and. consequently. can be used only by selected personnei (administrators. operators. and maintainers). Thus, while these commands are potentially available to all users, they can be executed only by personnel who have previously been given access to the segments and directories referenced by the commands. Before using any of these commands. you should check with your system administrator to determine if you are permitted to perform the desired operation.