1 04/05/85  config_edit, config
 2 
 3 Syntax as a command:  config {file_name}
 4 
 5 
 6 Function:  enters the config deck editor.  This editor is identical in
 7 function to the qedx text editor, except that buffer 0 contains a copy
 8 (in ASCII source form) of the config deck.  This command is not valid
 9 at the "crash" command level.
10 
11 
12 Arguments:
13 file_name
14    is the name of a file to be read into the config deck.
15 
16 
17 Notes:  If a file_name is supplied on the command line, the specified
18 file is read into the config deck without entering the config deck
19 editor.
20 
21 If a file_name is not supplied, the current config deck (that found in
22 the CONF partition on the RPV) is read into buffer 0.  It is converted
23 to a labeled ASCII form which is an expanded form of that used in the
24 configuration card description section.  Arbitrary text editing
25 operations may be performed on this buffer, as well as any other.
26 Performing a w (write) request on buffer 0 writes the edited buffer
27 back into the config deck.
28 
29 
30 The read (r) and write (w) requests (when used with a file name) may be
31 used to insert a file into the copy of the config deck or to make a
32 copy of the config deck in a file, respectively.  When used with a file
33 name, these two requests do not change the default file name of
34 config_edit's copy of the config deck.  When used without a file name,
35 these two requests always refer to config_edit's copy of the config
36 deck.
37 
38 The qedx request line 1,$dr can be used to restore the original config
39 deck if no write request has been performed.  If a write request has
40 been performed, this request line will only discard those changes made
41 since the most recent write.
42 
43 
44 In the labeled format, each field on a config card, except for the card
45 name, may be optionally preceded by a label.  Labeled fields may appear
46 in any order.  The interpretation of a card in labeled form is that all
47 labeled fields are placed into their proper places; any unlabeled
48 fields then fill in the missing spaces.  Thus,
49 
50       iom -state on -port 1 a nsa
51 
52 becomes
53 
54       iom a 1 nsa on
55 
56 in its standard format.
57 
58 
59 The various labeled formats are described in the Multics System
60 Maintenance Procedures manual, Order No.  AM81.  If a card is to be
61 entered whose format has been locally changed or whose format or type
62 is otherwise unknown, a "."  may be placed in front of the card name to
63 avoid errors during parsing of the card.  Such a card may not have any
64 labeled fields.
65 
66 Refer to the discussion under "Config Deck and Device Accessibility" in
67 the Multics System Maintenance Procedures manual, Order No.  AM81, for
68 details on the implications of the use of this command.
69 
70 See the description of the qedx command in the Multics Commands and
71 Active Functions manual, Order No.  AG92, for complete information on
72 qedx requests and their options.