Honeywell MULTICS POCKET GUIDE MULTICS'POCKET GUIDE COMMANDS AND ACTIVE COMMANDS AND ACTIVE FUNCTIONS FUNCTI·ONS SERIES 60 (LEVEL 68) SERIES 60 (LEVEL 68) SOFTWARE SUBJECT: Abbreviated Version of Multics Commands and Active Functions SPECIAL INSTRUCTIONS: This document is based on the contents of the Multics Programmers' Manual Commands and Active Functions, Order No. AG92. SOFTWARE SUPPORTED: Multics Software Release 3.1 DATE: Apri11976 CONTENTS PREFACE Page This pocket guide presents an abbreviated version of the commands and active functions described in detail in the Introduction . _ .. __ . _ ...... _ ................. _ . 1 Multics Programmers' Manual Commands and Active Func­ tions, Order No, AG92. Commands ................... _ . 3 Users of this document should be familiar with some of Listed by Function .... _ ................. _ , _ . 5 the concepts and terminology of the Multics System. The Individual Descriptions (Alphabetical) ..... _ . 8 following Multics user documentation should be consulted: Active Functions .............................. 59 Multics Users' Guide Order No. AL40 Listed by Function .......................... 60 Multics Programmers' Manual: Individual Descriptions (Alphabetical) ........... 61 Reference Guide Order No. AG91 Commands and Active Functions Order No. AG92 Multics ASCII Character Set. .. 73 Subroutines Order No. AG93 Subsystem Writers' Guide Order No. AK92 For detailed information on Multics programming lan­ guages, refer to the following manuals: APL Users' Guide Order No. AK95 BASIC Order No. AM82 COBOL Reference Manual Order No. AS44 COBOL Users' Guide Order No. AS43 FORTRAN Order No, AJ28 PLjI Language Manual Order No. AG94 PLjI Reference Manual Order No. AM83 © 1976, Honeywell Information Systems Inc. File No.: 1 Ll3 iii user's registered project identifier; a project is an arbitrary set of users grouped together for INTRODUCTION accounting and access control purposes. User id This document is intended to serve as a quick reference access control name of the form Person id and convenient memory aid for the user with some familiarity Project_id.tag; since the tag portion is r~el~ explicitly given, the term User id is often de­ with Multics command conventions. fined as a Person_id.Project_id pair. This guide presents an abbreviated description of the Multics commands and active functions described in detail in the Multics Programmers' Manual Commands and Active Functions (MPM Commands), Order No. AG92. The com­ mands are presented in alphabetical order, with each descrip­ tion showing the proper usage and a list of the control arguments and optional arguments that may be used. Control arguments are only listed; they are not defined in detail in this document. The reader is expected to be familiar with the Multics command environment conventions. The following terms are defined here and are not explained at each occurrence in this document. If the reader needs more information on termi­ nology than is given here, he should refer to "Glossary of Multics Terms" in Section I of the Multics Programmer's Manual Reference Guide, Order No. AG91. ACL access control list; it describes who may access a~ entry in the Multics storage system and in what way (see modes below). modes access identifiers; used to define the kind of access a user has to a storage system entry. The modes are: segments directories (read) s (status) e (execute) m (modify) w (write) a (append) Null access can also be specified for either seg­ ments or directories: " ", n, or null. path pathname of an entry; it can be relative or absolute. Person_id user's registered personal identifier; usually some form of the user's surname; unique at site. 2 COMMANDS If more information is needed about a particular value, the reader should consult the appropriate command descrip­ tion in the MPM Commands. The format of each command description in this docu­ The commands listed below are grouped according to ment is based on those found in the MPM Commands. The their function. An abbreviated description for each com­ command name, in boldface type, is shown first, followed by mand is given in the following pages, arranged in alphabetical the usage line. In the usage line, the following conventions rather than function order. apply: 1. If a command accepts more than one of a specific argument, an "s" is added to the argument name (e.g., paths, control_args). 2. To indicate one of a group of similar arguments, an ''1'' is added to the argument name (e.g., pathi, control_argi). 3. Multiple arguments that must be given in pairs are indicated by xxxI yyyl ... xxxn yyyn. 4. Pathnames that must be given in pairs are indicated by path 11 path21 ... pathln path2n. 5. Optional arguments are enclosed in braces (e.g., {path}, {-control_args}). All other arguments are required. To illustrate these conventions, consider the following usage line: command {paths} {-control_ args } The lines below are just a few examples of valid invocations of this command: command command path command path path -control_arg command path -control_arg -control_arg command -control_arg command -control_arg -control_arg For simplicity, when an argument takes a value other than a pathname (indicated by "path"), the value is indicated as follows: XX character string N number, decimal or octal DT date-time character string in a form acceptable to the converCdate_ to_binary _ subroutine described in the Multics Programmers' Manual Subroutines, Order No. AG93. 3 4 Access to the System Directory Manipulation Formatted Output Facilities Debugging and Perform­ (preaccess requests) add name cancel_ daemon_ request ance Monitoring Facilities dprint change _ error _ mode MAP create_dir dpunch 963 delete dir cum ula tive _ page _ trace 029 delete_name dump_segment debug list _ daemon_ req uests display _ pll io _ error dial fs chname print dump_segment enter link runoff page_trace enterp list runofCabs probe login rename safety _ sw _ off profile logout Language Translators, safety _ sw _ on progress Compilers, Assemblers, ready Creating and Editing Segments status and Interpreters ready_off adjust_ bit_ count unlink apl vfile status ready _on basic_system basic compare _ ascii reprint_ error Access Control basic_system edm trace delete acl bind indent trace stack delete iacl dir cancel_ co bol_ program program_interrupt delete_iacl_seg cobol Input/Output System Control qedx list acl display _ cobol_run_ unit assign_ resource runoff list iacl_dir format cobol_source cancel_ daemon_req ues.t runofCabs list_iacl_seg fortran close file set bit_count set acl fortran abs console_output sort_seg set iacl· dir indent copy _cards set_iacl_seg pH display _pllio_error Segment Manipulation pH_abs dprint adjust __ bit_ count Address Space Control profile dpunch archive add_search_rules qedx file _ ou tpu t compare change_default_ wdir run cobol io_call compare_ascii change _ wdir runoff line _lengt h copy delete search rules runofCabs list_ daemon_ req uests create initiate set_cc list_resources delete list ref_names stop_cobol_run print delete force new_proc print_attach_ table link print_default_ wdir Object Segmen t print_request_ types move print_proc_auth Manipulation set_cc set bit count print_search_rules archive set_ tty sort_seg print_ wdir bind unassign _ reso urce truncate set search rules vfile _adjust unlink terminate vfile status vfilc_adjust term ina te _ ref name terminate_segno terminate _ single _ refname where 6 5 Command Level Environment Communication with the abbrev, ab abbrev System provides the user with a mechanism for abbreviating add search rules check_info _segs parts of (or whole) command lines in the normal com­ answer help mand environ men t. basic_system how_many _ users Usage: abbrev change_default_ wdir print_motd change _ error _ mode who CONTROL REQUESTS change_ wdir .a <abbr> <rest of line> console _ output Accounting add the abbreviation <abbr> to the current profile delete _ search rules get_quota segment. move_quota do .ab <abbr> <rest of line> resource_usage exec_com add an abbreviation that is expanded only if found file _ ou tpu t Control of Absentee at the beginning of a line or directly following a geC com_line Computations semicolon (;) in the expanded line. line _length cancet.. abs_request .af <abbr> <rest of line> memo enter_abs_request add an abbreviation to the profile segment and new_proc fortran_abs force it to overwrite any previous abbreviation with print_default_ wdir how _many _ users the same name. print_search_rules list_abs_requests .abf <abbr> <rest of line> print_wdir pll_abs add an abbreviation that is expanded only at the program_interrupt runofCabs beginning of a line and force it to replace any pre­ ready who vious abbrevialion with the same name. ready _off ready _on GCOS Environment .d <abbrl> ... <abbrn> release gcos delete the specified abbreviations from the current reprint_ error gcos_ card_ utility profile. see com_line gcos_sysprint .f seC search rules gcos_syspunch enter a mode (the default mode) that forgets each start command line after executing it. Miscellaneous Tools Communication Among calc .I <abbrl> ... <abbrn> Users decode list the specified abbreviations with the things they accept_ messages encode stand for. defer _ messages memo .la <letterl> ... <lettern> immediate_messages progress list all abbreviations starting with the specified mail walk subtree letters. print_auth_names print_ messages .q send_message quit using the abbrev processor. who .r enter a mode that remembers the last line expanded byabbrev