PATCH DECK STRUCTURE
PATCH DECK SYMBOL TABLES
The Delta format symbolic values that are recognized in patches are assembled by the system tape definition proces-sor, DEF, from the REF/DEF stacks of the patchable modules
In addition, two special symbols are available during the patching process. Executive Delta will automatically relocate the patch area.
Example:
The following two patch decks are equivalent:
/IORT+.F8/B @/ /IORT+.F8/B PATCH/
Example:
/MM+.64/LPSD,8 @@/
/@@/MM+.65+4**28/
/@/ .17000000/
New symbols may be added to the symbol table by including symbol definition patches in the patch deck. Symbol def-inition patches must have the format
# SYMBOL
=
value whereSYMBOL is any Delta format symbol. (The symbol can be no longer than eight characters.)
value is any evaluatable expression terminated by a blank.
Example:
tfoGRUNCH= .D87
/GRUNCH/B GRUNCH+.20/
/ .+l/B @/
/@/LW,3 TABLES+3/
t/JK=@
/@/CI,3 10/
i@/B GRUNCH+.50/
/55+.1E8/B JK/
In the above example, the patch at 55+. IE8 branches to the instruction Cl, 3 10.
RECONflGURATION AND PARTITIONING COMMANDS These commands provide a means of reconfiguring the system and partitioning devices and/or controllers at boot-time.
All of the commands begin with a colon (:) and must end with a period or a trailing blank by at least column 72.
The commands may be specified in any order with the ex-ception of :END which must appear last {if it is used}.
If no reconfiguration and partitioning commands are speci-fied, the system responds as if the :GO command had been specified.
26 Patch Deck Structure
Three of these commands (:TYPE, :PART, and :REMOVE) contain the following parameter as part of the command format:
value (sometimes referred to as value
l and value 2) The description of this parameter is quite detailed. To avoid repeating the description several times, it will be given here and references will be made back to this section in the command descriptions.
The format of value is dependent on the CPU being used.
For Sigma
6/7/9
systems, value must be in the format nddwhere
n represents a controller address and is specified as a letter. See Table B-2 in Appendix B.
dd specifies the device number. See Table B-3 in Appendix B.
For Xerox 560 systems, value may take one of two formats.
The first format is ndd
where
n represents a cI uster number and a un it number.
See Table B-4 in Appendix B.
dd specifies the device number. See Table B-3 in Appendix B.
The second format consists of four hexadecimal digits which represent a hardware address in the format
I~, I, : J ~ J . ""~,~ ,,,..J
where
c specifies the cluster number.
u specifies the unit number.
dd specifies the device number.
: GO This command specifies that the configuration speci-fied on the system tape is to be used as is. The format of the command is
:GO
If :GO is specified, : TYPE and :REMOVE commands are not meaningful and the following message is output on the LL device:
ALL :TYPE/:REMOVE COMMANDS IGNORED
If no reconfiguration and partitioning commands are speci-fied, the system responds as if the :GO command had been specified.
:SAVE This command specifies that all device addresses not changed by : TYPE commands are to remain as is, except according to restrictions listed in the following description.
The format of the command is ad-dresses which are different on the target machine from that of the SYSGENed system tape need be changed by the: TYPE specified by :TYPE commands.· Any SYSGENed devices for which addresses are not defined by :TYPE commands are
removed from the system configuration (and cannot be re-turned to the system configuration without rebooting).
:TYPE The :TYPE command defines a device type, its model number, and its new device address or addessses. The format of the command for single access device definitions is
: TYPE device, valuer, value]. ••
and the format for dual access device definitions is :TYPE device, (value last four characters specify the device model num-ber in hexadecimal.
value specifies the device address in the format de-scribed at the beginning of this section. The num-ber of addresses depends upon the numnum-ber of devi ces of thatdevicetype whichare on the target machine or which need address changes (when :SAVE is used). For dual access devices, value1 specifies the primary path address and value2 specifies the
alternate path address. When a device- address When found, its corresponding controller model number is obtained from the M:MODNUM table. Thedevice/controller model numbers are then used to check if this combination is the same as that which was originally SYSGENed for the given devi ceo If not the same, all similar device/controller model number combinations in M:MODNUM are used for this validation. As an example, if M:MODNUM contains the following entries:
Device Model Controller Model
Number Number
7120 7120
7120 7121
7121 7121
7121 7J20
and the SYSGENed combination is
7120 7121
then the command: TYPE CR7121, •••• will cause the fol-lowing device/controller combinations to be checked with the indicated results: from the system. The removed device or controller cannot be returned to the system without rebooting. (Although public disk packs are not partitionable, they can be re-moved from the system.) The format of the command is
In the following example, four disk packs were SYSGENed SYSCON processor description in the CP-V ISM Reference Manual, 90 16 74.) This is useful when a system is being
value specifies the address of thedevice or control-ler to be removed in the format described at the beginning of this section.
CONT specifies that a controller is to be parti-tioned. When a controller is partitioned, all de-vices on that controller are also partitioned.
A device partition request causes all devices which have identical device addresses to be paritioned.
Example:
A system was SYSGENed to have four 9-track tape drives but two are down for maintenance when the system is booted.
:TYPE 9T7322,A80,A81,A82,A83 :PART A82
:PART A83
28 Patch Deck Structure
: END The :END command defines the end of the set of reconfiguration and partitioning commands. The command is optional because the occurrence of either the first nonroot patch or an asterisk (*) command would also indicate the end of reconfiguration and partitioning commands.
The format of the command is :END
When the end of reconfiguration and partitioning commands is encountered, all : TYPE command definitions are processed first, then all :REMOVE requests, and finally all :PART requests.
RECONFIGURATION AND PARTITIONING EXAMPLE In the following example, a CP-V system was SYSGENed for four different hardware configurations. These config-urations are referred to as the 560X, 7T, 7D, and 7E • .A set of reconfiguration and partitioning commands was generated for each machine with the set of commands for each machine being bounded by a conditional patch control command.
The four sets of reconfiguration and partitioning commands exist in the patch deck. The one set that is to be used for recon-figuraction and partitioning commands which were ignored because they were for machines not being booted. Figure 9 lists the set of reconfiguration and partitioning commands which were used in the boot process because the 7D was selected. Figure 10 lists the set of devices for the 7D con-figuration. This information is listed on the line printer during a boot, but not necessarily in the order shown in the
Figures.
RECONFIGURATION AND PARTITIONING MESSAGES Table 5 lists the messages that may be output when recon-figuration and partitioning commands are being processed.
When an error is encountered, the error message is preceded by a message containing a dollar sign ($) beneath the char-acter position in the command at which the error was found.
Processing of the command in error is discontinued.