1 01/07/87  load_from_tape, lft
  2 
  3 
  4 Syntax as a command:  lft tape_name {-control_args}
  5 
  6 
  7 Function:  loads MPC firmware, ITRs, MDRs, and T&D test pages from the
  8 Integrated, Firmware And Diagnostic (IFAD) tape into a tandd_deck_file.
  9 In addition, MPC firmware modules are loaded into individual segments
 10 in a form acceptable to the generate_mst command, in order that they
 11 may be written onto the Multics Boot Tape.  Also, a DN6670 Binary Deck
 12 Tape may also be loaded into the tandd_deck_file.
 13 
 14 
 15 Arguments:
 16 tape_name
 17    specifies the name of the tape to be used.  See "Notes on tape name"
 18    below.
 19 
 20 
 21 Control arguments:
 22 -brief, -bf
 23    suppresses messages from deckfile_manager specifying the
 24    deckfile.list and tandd_deck_file that will be used for this
 25    request.
 26 -copy <copy_vol> {-copy_args}, -cp <copy_vol> {-copy_args}
 27    produces a tailored copy of an IFAD tape for use with offline T&D.
 28    Only those modules applicable to Multics are written to the copy
 29    tape.  The -copy argument is mutually exclusive with the -deckfile,
 30    -firmware.  For a list of -copy_args, see "List of copy args" below.
 31 
 32 
 33 
 34 -density <value>, -den <value>
 35    specifies the initial density setting for tape attachment.  Although
 36    the density of the input tape is automatically determined, some tape
 37    subsystems may not have tape drives capable of handling the default
 38    density of 1600 bpi.  The allowable values for <value> are 6250,
 39    1600, 800, 556, or 200.  See "Notes on tape name" below.
 40 -firmware, -fw
 41    specifies that only firmware modules are to be loaded into
 42    individual segments; no deckfile or listing file is produced.  This
 43    argument is mutually exclusive with the -deckfile, -list, and -copy
 44    arguments.
 45 
 46 
 47 -patches
 48    allows patches with zero checksums to be accepted.  The checksum is
 49    adjusted before the record is written to the deckfile.
 50 -track <n>, -tk <n>
 51    where <n> is 7 or 9 (for 7- or 9-track tapes).  If the -track
 52    argument is not specified, 9-track is assumed.
 53 Notes
 54    The default action of this command, if no control arguments are
 55    specified, is to load all modules on the tape that are applicable to
 56    Multics into the deckfile and all firmware modules into individual
 57    segments.
 58 
 59 
 60    Firmware segments are created (in memory image format) using a four
 61    component entry name:
 62 
 63       fw.<name>.<ident>.<fw_rev>
 64 
 65    where name is the name of the device, ident is taken from the
 66    MPC-assembler IDENT pseudo-op card, and fw_rev is the firmware
 67    revision.
 68 
 69 
 70    Each module that is read from the tape and written to the deckfile
 71    is copied as-is in GCOS object deck format.  Each object deck
 72    occupies one record of the keyed sequential deckfile.  The record
 73    search key is formed from information obtained from the $!OBJECT
 74    card.
 75 
 76 
 77    Catalog records are built for all tape files while the respective
 78    tape files are being read.  These catalog records are merely a list
 79    of all of the search keys associated with each individual tape file.
 80    Each catalog record is written to the deckfile immediately following
 81    each tape file, and have record search keys in the form:
 82 
 83       cata.itr.<mpc_name>.<fw_rev> - for an ITR catalog
 84    or
 85 
 86       cata.mdr.<grp_name>.<file> - for an MDR catalog
 87    where:
 88       <mpc_name>  is the name taken from the ident pseudo-op card image
 89       <grp_name>  is the name of the generic peripheral group and can
 90                   be either tape, disk, print, or card
 91       <fw_rev>    is the revision of the mpc firmware in this file.
 92                   For the urcmpc itr/firmware file, it is the revision
 93                   of the common mpc firmware.
 94 
 95 
 96 
 97 Notes on tape name:  The tape name may be of any format, but it is
 98 recommended that the name used reflect the tape being read, ie an ifad
 99 tape would be ifad.b3 or for a FNP 6670 tape name would be 6670-a3.
100 This name is added to the tandd_deck_file and deckfile.list files and
101 can be used as a record of revision of the source used to create the
102 deckfile.  The convention of "tape_name,density" where density is the
103 density of the tape, is also supported.
104 
105 
106 List of copy args::
107  The copy_args pertain only to the <copy_vol> and may be chosen from
108 the following:
109 -density <value>, -den <value>
110     sets the density of the copy tape to <value>.  The allowable values
111    for <value> are 6250, 1600, 800, 556, and 200.  If the -density
112    argument is not specified, the copy tape is set to the density of
113    the input tape.
114 -track <n>, -tk <n>
115    where n is 7 or 9 (for 7- or 9-track tapes).  If the -track argument
116    is not specified, 9-track is assumed.
117 
118 
119