1 10/31/92 GB58 Multics Common Commands
2 Errata Information for MR12.5
3
4
5 pg 3-6: for the "add_name" command, add a CONTROL ARGUMENTS
6 section after the ARGUMENTS section containing the
7 following.
8
9 -brief, -bf
10 suppresses the error message "Name already on entry"
11
12 -interpret_as_extended_entry -inaee
13 interprets the selected entry as an extended entry type
14
15
16 -interpret_as_standard_entry -inase
17 interprets the selected entry as a standard entry type
18
19 -long, -lg
20 does not suppress the error message "Name already on
21 entry" Default
22
23
24 pg 3-22: for the "calc" command, under NOTES ON ASSIGNMENT
25 STATEMENTS replace the sentence that begins "The name of the
26 variable must be..." with the following.
27
28 The name of the variable must be from one to eight
29 characters in length and must be made up of letters
30 uppercase and/or lowercase, digits if not at the
31 beginning of the name, and the underscore character _.
32
33
34 pg 3-27: for the "cancel_output_request" command, in the NOTES
35 section replace "If the request is already running,...
36 ...are ignored by the system" two paragraphs with the
37 following.
38
39 If the request is already running, the running request will
40 not be stopped and the request's entry will not be removed
41 from the queue. A warning message will be displayed to warn
42 the user of this action.
43
44
45 pg 3-32: for the "copy" command, under NOTES add the paragraph
46 below.
47 pg 3-34; for the "copy_dir" command, under NOTES add the
48 paragraph below.
49 pg 3-126; for the "move" command, under NOTES add the paragraph
50 below.
51
52 If copying a non-empty mailbox requires that the max_length
53 characteristic of the source be applied to the target, then
54 the target max_length value will take on the default value
55 that was given to it when created.
56
57
58 pg 3-45: for the "delete_name" command, add the following under
59 the CONTROL ARGUMENTS section.
60
61 -interpret_as_extended_entry -inaee
62 interprets the selected entry as an extended entry type
63
64 -interpret_as_standard_entry -inase
65 interprets the selected entry as a standard entry type
66
67
68 pg 3-55: for the "enter_abs_request" command, under ARGUMENTS
69 change the description of "path" to the following.
70
71 path
72 specifies the pathname of the absentee control segment
73 associated with this request. The absin suffix is
74 assumed. If a pathname is given, it identifies the
75 absin segment. If only an entryname is given, the absin
76 segment is located using the exec_com search list.
77
78
79 pg 3-55: for the "enter_abs_request" command, add the following
80 to the CONTROL ARGUMENTS section.
81
82 -authorization STR, -auth STR
83 sets the authorization of the process to that specified
84 by STR. STR is a character string composed of level and
85 category names for the desired authorization, separated
86 by commas. STR cannot contain any embedded blank or tab
87 characters. The short names for each level and
88 category always contain no blanks or tabs and can be
89 used whenever the corresponding long names contain
90 blanks or tabs. STR must represent an authorization
91 that is within the range of minimum and maximum
92 authorization of Person_id on the Project_id.
93
94
95 If -authorization is omitted, your current login
96 authorization is used. See the Programmer's Reference
97 Manual for more information about process
98 authorizations. Allowed authorization range can be
99 displayed via the "user auth_range" command.
100
101
102 -home_dir path, -hd path
103 sets the home directory of the absentee process to the
104 path specified, if the project administrator allows such
105 changes. The "user attributes" command displays allowed
106 attributes. The vhomedir attribute is required to use
107 the -home_dir control argument. The specified home dir
108 cannot exceed 64 characters and must be specified as an
109 absolute pathname.
110
111 -no_start_up, -ns
112 instructs the standard process overseer not to execute
113 the start_up.ec segment in the absentee process, if the
114 project administrator allows it. The "user attributes"
115 command displays allowed attributes. The nostartup
116 attribute is required to use this control argument.
117
118
119 -process_overseer path, -po path
120 sets the process overseer for the absentee process to
121 the procedure given by path if the project administrator
122 allows this. If path ends in the characters ",direct",
123 the specified procedure is called directly during
124 process initialization rather than by the standard
125 system-provided procedure. This means that the program
126 used by path must perform the tasks that would have been
127 performed by the standard procedure. The length of the
128 process_overseer path should not exceed 64 characters.
129 The "user attributes" command displays allowed
130 attributes. The vinitproc attribute is required to use
131 this control argument.
132
133
134 -ring N, -rg N
135 sets the initial ring to N if this ring number is within
136 the range of the registered minimum ring and maximum
137 ring. This range may be displayed via the "user
138 ring_range" command.
139
140 -start_up
141 instructs the standard process overseer to execute the
142 start_up.ec segment if it exists. Default
143
144
145 pg 3-57: for the "enter_abs_request" command, add the following
146 to the NOTES section.
147
148 When -proxy is given, no attempt is made by ear to validate
149 attribute dependent control arguments. Since the job is
150 submitted on behalf of another user, the attributes for the
151 proxy user will be validated only by the answering service
152 when it attempts to run the job. Attribute dependent
153 control arguments are:
154
155 -no_start_up
156 -home_dir
157 -authorization
158 -process_overseer
159 -ring
160
161
162 pg 3-64: for the "exec_com" command version 2, under LIST OF
163 LITERALS add the following after the description of &NL.
164
165 &CR, &CRN
166 expands to a single carriage return character ASCII
167 015 or to N carriage returns.
168
169
170 pg 3-72: for the "exec_com" command version 2, under LIST OF
171 CONTRUCTS replace the line
172
173 &&NL, &QT, &SP, &VT List of literals
174 with
175 &&NL, &CR, &QT, &SP, &VT List of literals
176
177
178 pg 3-101: for the "link" command, under the "-chase" control
179 argument, replace "ia" with "is".
180
181
182 pg 3-121: for the "memo" command, under LIST OF MEMO OPTIONS
183 delete the following sentence under the description of the
184 "-repeat_when_processed" control argument.
185
186 This is useful for memos that are only significant within a
187 single process.
188
189
190 pg 3-139: change the documentation for the "program_interrupt"
191 command to the following.
192
193 NAME
194
195 program_interrupt, pi
196
197 SYNTAX AS A COMMAND
198
199 pi -control_arg
200
201
202 FUNCTION
203
204 informs a suspended invocation of an interactive subsystem
205 that you wish to abort a subsystem request and reenter the
206 subsystem.
207
208
209 CONTROL ARGUMENTS
210
211 -no_restore, -ns
212 does not restore the standard I/O attachments see
213 "Notes".
214
215
216 NOTES
217
218 The program interrupt command is used with interactive
219 subsystems. Interactive subsystems are commands that accept
220 user requests from the terminal. To abort a subsystem
221 request, the user uses the quit or break key to interrupt
222 execution, and then gives the program_interrupt command. If
223 the subsystem supports the use of the program_interrupt
224 command, it will abort the interrupted request and ask the
225 user for a new one. If the subsystem does not support the
226 use of program_interrupt, the command will print an error
227 message. The user may then either restart the interrupted
228 operation with the "start" command, or abort the entire
229 subsystem invocation with the "release" command.
230
231
232 This command restores the attachments of the user_input,
233 user_output, and error_output switches and the mode of
234 user_i/o to their values at the time of interruption unless
235 you give -no_restore.
236
237 If there is more than one suspended command in your stack,
238 the stack is searched for a program that supports
239 program_interrupt and any intervening programs are released.
240
241
242 pg 3-150: for the "query" command, add the following to the
243 CONTROL ARGUMENTS section.
244
245 -no_trim
246 does not trim trailing spaces from the question
247 argument.
248
249 -trim
250 trims trailing spaces from the question argument.
251 Default
252
253
254 pg 3-150: for the "query" command, add the following to the
255 CONTROL ARGUMENTS section.
256
257 -no_trim
258 does not trim trailing spaces from the question
259 argument.
260
261 -trim
262 trims trailing spaces from the question argument.
263 Default
264
265
266 pg 3-157: for the "rename" command, add the following to the
267 CONTROL ARGUMENTS section.
268
269 -interpret_as_extended_entry, -inaee
270 interprets the selected entry as an extended entry type.
271
272 -interpret_as_standard_entry, -inase
273 interprets the selected entry as a standard entry type.
274
275
276 pg 3-181: for the "status" command, replace the description of |
277 the "-author" control argument with the following: |
278 |
279 -author, -at |
280 prints the author of the entry. The author is the name |
281 of the user who created the segment or directory. This |
282 attribute cannot be modified. |
283
284
285 pg 3-182: for the "status" command, under LIST OF TYPE-SPECIFIC |
286 CONTROL ARGUMENTS, replace the description of "-bc_author" |
287 with the following: |
288 |
289 -bc_author, -bca |
290 prints the bit count author of the entry. The bit count |
291 author is the name of the user who last set the bit |
292 count of the segment or directory. This attribute is |
293 automatically updated when the bit count is set. Not |
294 valid for DM files. |
295
296
297 pg 3-195: replace the documentation for the "working_dir"
298 command with the following.
299
300 SYNTAX AS A COMMAND
301
302 wd LOCATIONS -control_arg
303
304 SYNTAX AS AN ACTIVE FUNCTION
305
306 wd LOCATIONS
307
308
309 FUNCTION
310
311 prints or returns the pathname of the current working
312 directory. Optional arguments can be given to print or
313 return entries on the stack of working directories. Refer
314 to the change_wdir command for a description of the working
315 directory stack.
316
317
318 ARGUMENTS
319
320 LOCATIONS
321 selects entries on the working directory stack to be
322 printed or returned. LOCATION can be an integer
323 position N from the top of the stack; or a text LABEL
324 associated with a stack entry; or one of the reserved
325 words first f, last l or all a. The reserved word
326 first identifies the current working directory which is
327 not on the stack of prior working directories and is
328 displayed above stack position 1; last identifies the
329 bottom stack entry; and all identifies the current
330 working directory plus all stacked directories.
331
332
333 More than one LOCATION can be given to select several
334 entries. Individual locations are separated by a space.
335 A LOCATION_RANGE is given by a starting and ending
336 LOCATION separated by a colon. For example, f:2
337 identifies the current working directory and the top two
338 directories on the stack, and 1:XXX identifies stack
339 entries from the top of the stack to the entry with
340 label XXX.
341
342
343 CONTROL ARGUMENTS
344
345 -header, -he
346 displays a heading of the form: LOC LABEL PATHNAME.
347 The default is to print a heading when more than one
348 directory is displayed.
349
350 -no_header, -nhe
351 suppresses the heading before the stack contents are
352 displayed. default
353
354
355 NOTES
356
357 Since the working_dir is returned in quotes, the command
358 processor treats it as a single argument regardless of
359 special characters in the name.
360
361
362 The current working directory is located at location zero.
363 The most recent prior working directory is at the stack
364 position 1 and the least recent prior working directory is
365 at the Nth last position. If a stack of prior working
366 directories is empty then only the current working directory
367 is printed. For the case when the current working directory
368 has been deleted, an attempt to print it out will display
369 the "directory has been deleted" message in square brackets,
370 separated from the directory pathname by a blank space.
371 This does not apply when one or more prior working
372 directories on the stack have been deleted. See also the
373 change_wdir cwd command for stack features.
374
375
376 Examples: Assume the stack looks like the following:
377
378 0 >udd>m>tai>archive_dev
379 1 >udd>m>tai>abbrev_dev
380 2 XXX >udd>m>tai>cwd_dev
381 3 >udd>m>tai
382
383 then
384
385 ! wd XXX
386 2 XXX >udd>m>tai>cwd_dev
387
388 ! wd 2 -he
389 LOC LABEL PATHNAME
390
391
392 2 XXX >udd>m>tai>cwd_dev
393
394 ! wd f:XXX
395 LOC LABEL PATHNAME
396
397 0 >udd>m>tai>archive_dev
398 1 >udd>m>tai>abbrev_dev
399 2 XXX >udd>m>tai>cwd_dev
400
401 ! string wd XXX
402 >udd>m>tai>cwd_dev
403
404 ! string wd 2
405 >udd>m>tai>cwd_dev
406
407
408 ! string wd a
409 >udd>m>tai>archive_dev >udd>m>tai>abbrev_dev
410 >udd>m>tai>cwd_dev >udd>m>tai
411
412 ! dd >udd>m>tai>archive_dev
413 ! wd a
414 LOC LABEL PATHNAME
415
416 0 >udd>m>tai>archive_dev directory has been deleted
417 1 >udd>m>tai>abbrev_dev
418 2 XXX >udd>m>tai>cwd_dev
419 3 >udd>m>tai
420
421
422 ! string wd a
423 >udd>m>tai>archive_dev >udd>m>tai>abbrev_dev
424 >udd>m>tai>cwd_dev >udd>m>tai
425