1 02/27/85 reconfigure, rcf
 2 
 3 Syntax as a command:  rcf operation type name {-control_args}
 4 
 5 
 6 Function:  adds or deletes selected reconfigurable entities to or from
 7 the current configuration.
 8 
 9 
10 Arguments:
11 operation
12    is one of the functions listed below under "List of Operations."
13 type
14    is one of the reconfigurable entities listed below under "List of
15    Reconfigurable Entities."
16 name
17    is the name of the item being reconfigured.  Examples of names are
18    given under "List of Reconfigurable Entities."
19 
20 
21 Control arguments:
22 -add_all_attachments
23    used only after an add operation.  This control argument causes all
24    reconfigurable entities which are newly accessible to be added.
25 -brief, -bf
26    does not print out a list of every item which is added or removed.
27    This is the default.
28 -delete_all_attachments
29    used only after a delete operation.  This control argument causes
30    all reconfigurable entities which will become inaccessible to be
31    deleted.
32 -long, -lg
33    prints out a list of every item which is added or removed.
34 
35 
36 List of operations:
37 add
38    the specified item is to be added to the current configuration.  It
39    will thus become available for use.
40 delete, dl
41    the specified item is to be deleted from the current configuration.
42    It will thus become unavailable for use.
43 
44 
45 List of reconfigurable entities:
46 channel, chan, chnl
47    a logical channel.  A channel's name is the name by which IOI knows
48    it (e.g., a9, b23).
49 cpu
50    a Central Processing Unit.  A processor's name is its tag as it
51    appears on a cpu card in the config deck (e.g., a, b).  Only
52    processors that are defined in the configuration deck can be added.
53    You must set all of the switches correctly and initialize the
54    processor before you issue this command.
55 device, dv, prph
56    a peripheral device.  A device's name is the name by which RCP knows
57    it (e.g., tapa_03, dskb_13, fnpc, opca).
58 
59 
60 iom
61    an Input/Output Multiplexer.  An IOM's name is its tag as it appears
62    on an iom card in the config deck (e.g., a, b).
63 link_adapter, la
64    a link adapter or physical channel.  This is a shorthand way of
65    specifying a collection of logical channels.  A link adaptor's name
66    is the name of its lowest numbered channel (e.g., b28).
67 mpc
68    a Microporgrammed Peripheral Controller.  This is a shorthand way of
69    specifying a collection of link adapters (and thus, a collection of
70    logical channels).  An MPC's name is its name as it appears on an
71    mpc card in the config deck (e.g., mspa, mtpb).
72 
73 
74 page
75    a page of memory.  A page's name is its number.  Pages are numbered
76    starting at 0.  Numbers may be given in any form acceptable to the
77    cv_integer_string_ function.  A range of pages may be specified by
78    an expression of the form <low>:<high>.  Pages to be added must
79    reside within system controllers already in the Multics
80    configuration.  Pages to be removed must reside within a single
81    system controller.
82 mem, scu
83    a System Control Unit.  An SCU's name is its tag as it appears on a
84    mem card in the config deck (e.g., a, b).  Only system controllers
85    that are defined in the configuration deck can be added.  You must
86    set all of the switches on the system controller correctly before
87    you issue this command.
88 
89 
90 Access required:  Use of the reconfigure command requires re access to
91 the hphcs_gate.
92 
93 
94 Notes:  When you add an SCU, all of its pages are also added.  However,
95 when you delete all of an SCU's pages, the SCU itself is not deleted.
96 
97 For more details on the dynamic reconfiguration, see the Multics System
98 Maintenance Procedures manual, Order No.  AM81, and the Operator's
99 Guide to Multics, Order No.  GB61.