Google
 

Trailing-Edge - PDP-10 Archives - bb-bt99p-bb - readme.022
There are no other files named readme.022 in the archive.


1.0  INTRODUCTION

This is the twenty-second Autopatch set.  It allows the patching of
ALGOL-10-V10B, ANF10-V704, APLSF-10-V2, COBOL-10-V12C,
CUSTOMER-SUPPORTED-10-V704, DBMS-10-V5A, DECNET-10-V704, FORTRAN-10-V11,
GALAXY-10-V704, IBMCOM-10-ET-V4, IBMCOM-10-HASP-V1, MCB-10-V704,
MONITOR-10-V704, MPE-10-V704, MS-SOURCES-10-V11, MX-SOURCES-10-V1A,
SORT-10-V4D, and UTILITIES-10-V704.  To install Autopatch for the first
time, you must first restore the second save set and follow the
instructions found in the Autopatch Procedures/Reference Manual and the
INSTAL.DOC file.  Information specific to each product is recorded in
section 5.0 of this document.



2.0  EXCEPTIONS


     1.  The following product(s) are no longer Autopatched:  ANF10-V23,
         ANF10-V703, APL-10-V2, COBOL-10-V12B,
         CUSTOMER-SUPPORTED-10-V703, DECNET-10-UTILITIES-V702,
         DECNET-10-V703, FORTRAN-10-V6, FORTRAN-10-V7, FORTRAN-10-V10
         GALAXY-10-V4-1, GALAXY-10-V702, GALAXY-10-V703, LINK-10-V5-1,
         MCB-10-V702, MONITOR-10-V703, MPE-10-V702, MPE-10-V703,
         MS-10-V10, MS-EXE-10-V11, NFT-10-V1, RMS-10-V1, SORT-10-V4C,
         TOPS-10-DN6X-V701A, TOPS-10-KI-V701A, TOPS-10-KL-V701A,
         TOPS-10-KL-V702, TOPS-10-KS-V701A, TOPS-10-KS-V702,
         TOPS-10-MCB-V703, TOPS-10-MPE-V701A, TOPS-10-TSK-V701,
         UTILITIES-10-V701A, UTILITIES-10-V702, and UTILITIES-10-V703.

         *NOTE* It is strongly suggested that you DESELECT any of these
         products before proceeding with processing any currently
         supported products.

     2.  The following products are supported for the first time with
         this tape:  MX-SOURCES-10-V1A.

     3.  The following Autopatched product(s) do not have any new edits
         delivered with this patch set:  ALGOL-10-V10B, ANF10-V704,
         APLSF-10-V2, DBMS-10-V5A, DECNET-10-V704, MCB-10-V704,
         MPE-10-V704, and SORT-10-V4D.

     4.  The Autopatch updates are delivered on two tapes.  The first
         tape (BB-BT99x-BB) Contains the current patch save-set, the
         installation save-set, and the Documentation Update save-set.
         If you are at the current tape level and are not Autopatching
         any 'old' products for the first time, this first tape is the
         only one you need to use.  Procedures for using this tape are
         identical to those for use of the former single-tape format.

         The second tape (BB-JR93x-BB) contains historical patch
         save-sets.  This tape is needed if you are not up to the
         current tape level or you are Autopatching, for the first time,
         a product which was supported by previous tapes.
                                                                  Page 2


         In essence, the old tape format was split with the first two
         save-sets of the old format now being written to a separate
         tape.  The BACKUP CCL files are still found in the current
         patch save-set (first save-set of the first tape).  The ALL.Pnn
         CCL file restore files from the current (first) tape and the
         ALL.Ann CCL file restore files from the historical (second)
         tape.

     5.  (*new*) A bug in the PEP utility has caused an error in the
         Patch Data Base file (.PDB) for the Monitor product.  In order
         to correct the problem you must use the new MON704.PDF file in
         the second saveset of the CURRENT tape to DESELECT and SELECT
         the MONITOR product.  You need the previously delivered Monitor
         patch files (.X21) to reautopatch the product.  If these files
         have been deleted you can get them from this autopatch tape.
         You can create a temporary version of the LAP.DEF file which
         only defines LAPMON:  and use the ALL.P22 file (first saveset
         of CURRENT tape) on the HISTORICAL tape.  Alternatively, you
         can skip 21 savesets on the HISTORICAL tape and restore *.X21
         files.

         Be sure the new MON704.PDF file is in PAT:  before selecting
         the Monitor product.

     6.  (*new*) The new MX product is provided in the fourth saveset of
         this tape.  This product is supported by Autopatch.  The
         previous release of MX was supported as a component of MS V11.
         No adjustment to the existing MS Source product is needed.  You
         may want to delete all files except .MAC files from the MS
         Source distribution area.  Do this BEFORE loading the area with
         new MX sources.  Be sure to read the README.MEM file in the MX
         distribution save-set of this tape.

     7.  (tape 21) The D8EINT.MAC file was missing from the 7.04
         release.  It is provided on the second save-set of the CURRENT
         tape.

     8.  (tape 21) A copy of MACREL.REL, needed to build the SMFILE
         component of the UTILITIES product, is supplied in the first
         save-set of the CURRENT tape.

     9.  (tape 21) Be sure to delete files for the previous monitor from
         the common patching area before installing the new monitor.
         This includes *.FIL and D36PAR.*.

    10.  (tape 20) BACKUP %6(700) and DIRECT %7A(504) implement tape
         blocking.  A single switch controls the use of blocking factors
         and its meaning in both programs is identical.  The new switch
         is /BLOCKINGFACTOR:n, where "n" is an optional decimal number.

         The /BLOCKINGFACTOR switch sets the number of disk blocks per
         tape block read or written on tape.  The default value is 4 for
         compatibility with tapes written by BACKUP without blocking
         factor capability.  The specified value must be in the range of
         4 to 96, and be a multiple of 4 disk blocks.  Due to KS10
                                                                  Page 3


         UNIBUS adapter limitations, the maximum blocking factor on a
         KS10 is 56.

         Tape blocking is defined as writing a tape block that contains
         more than one disk block.  Versions of BACKUP prior to %6(700)
         write 4 disk blocks per tape block.  Thus, older versions of
         BACKUP may be said to use a blocking factor of 4.  The
         advantage of using higher blocking factors is to permit BACKUP
         to fit more information on a tape than it could writing a tape
         with the standard blocking factor of 4.  This is possible
         because the number of gaps between tape blocks is reduced.
         Note that INTERCHANGE mode forces a blocking factor of 4 for
         compatibility with other programs such as TOPS-20 DUMPER.

    11.  (tape 19) We no longer need to provide 'empty' .MKL files or
         null .SUP files for products with no edits.  Use of the new
         PEP.EXE and PEPB.EXE in the second save-set as well as modified
         Patch and Build control files from the same save-set will
         prevent use of old patch command files.

    12.  (tape 19) We have eliminated the product-specific BACKUP ccl
         files.  There are now two files.  The ALL.Pnn file will restore
         files for all desired products from the CURRENT patch tape.
         The ALL.Ann file will restore ALL files for all desired
         products from the HISTORICAL patch tape.  The loading process
         depends on the definition of product-specific logicals.  Each
         file will use the definitions in the LAP.DEF file.  A default
         LAP.DEF file is supplied in the first save-set.  This LAP.DEF
         defines logicals for all products.  It is intended that you
         only have logicals defined in LAP.DEF for those products that
         are being Autopatched at your site.  You must be pathed to the
         common patching directory (PAT:) when you invoke the ALL files.
         The recommended procedure for Autopatching a product for the
         first time is to create a temporary version of LAP.DEF that
         defines the logical for only that product.  Use of ALL.Ann will
         then restore all files for that product.

    13.  (tape 18) Some of the base-building files are maintained via
         Autopatch in the Utilities product.  When an INSTALL is done
         the updated components are copied to INS:  and deleted from
         PAT:.  This may cause problems if other products have not yet
         been built.  Do not INSTALL UTILITIES until all other products
         have been built.

    14.  (tape 17) We are no longer providing edit documentation files
         by product (.Dnn).  The cumulative edit list (APEDIT.RPT) is
         still provided.  Symptom, Diagnosis and Cure information is
         still available in The Software Dispatch.  Also provided is
         another edit list (APEDIT.nnn) which is a subset of the
         APEDIT.RPT file.  The new file contains only the edits which
         are new with the current tape.

    15.  (tape 17) We have implemented the DEFINE-LOGICAL-NAMES command
         in PEPB.  This command defines PAT:,DIS:,INS:  and ASL:  for a
         product.  Now batch jobs can be segmented and checkpointed
                                                                  Page 4


         without re-use of the INITIALIZE command.  The product that
         this immediately changes is GALAXY-10-V703.  The GALAXY control
         files on the second save-set of the CURRENT tape have been
         modified to take advantage of this new command.  The use of
         multiple batch streams to run concurrently the jobs submitted
         by GAL703.CTL will no longer have file contention problems.
         Also note that the GAL703.CTL file will now be the only one
         which actually renames the patch files.

    16.  (tape 17) The third saveset of the CURRENT tape contains a
         complete copy of the revised 'Monitor Calls Manual - Volume 2'
         in the MONCAL.MEM file.  Please read the MCINFO.MEM file for
         more information.  These files were first delivered on tape 16.

    17.  (tape 17) DBMS must be Autopatched every time there is an
         update to the product which uses it (COBOL or FORTRAN),
         regardless of whether there are any DBMS edits.  The reason for
         this requirement is that PEP will delete the updated components
         from the common patching area at the end of INSTALLation.  This
         requirement can be avoided if the DBMS distribution area is
         part of the PAT:, DIS:  or INS:  definition for FORTRAN or
         COBOL.

    18.  (tape 16) We have included the DCRYPT program in the second
         save-set.  This tool is not a supported part of Autopatch.
         DCRYPT may be used to decrypt the replacement EXE/REL files for
         COBOL-REP-V12C and FORTRAN-10-REP-V11 without using Autopatch
         procedures.  The README file details the relationship between
         Patch files and End-user files.  The KEY files from the
         distribution tapes are required.  A help file for DCRYPT is
         also provided.

    19.  (tape 11) The Autopatch build for source-patched products will
         delete source files in PAT:  to prevent problems if a build is
         re-started.  This process may fail if PAT:  is defined with
         SFDs.  Either do not use SFDs when defining PAT:  or manually
         delete the source files in the SFD before re-starting the
         Autopatch build.

    20.  (tape 10) If you are using DBMS with FORTRAN or COBOL, do not
         INSTALL DBMS with PEP until FORTRAN and/or COBOL has been
         built.  A feature of PEP which was new with tape 9 deletes the
         autopatched files from PAT:  upon successful installation.  The
         COBOL and FORTRAN products depend on the necessary DBMS files
         being in PAT:.

    21.  (tape 10) There are three .REL modules for DBMS (FML10, INF10
         and MND10) which are null.  This causes a %CGV error message at
         the end of the batch job and when PEP is checking the results
         of the batch job.  These messages should be ignored.

    22.  (tape 9) There are two new features of PEP and PEPB which are
         worthy of note.  First, the new PEP will automatically delete
         copies of files in PAT:  which have been successfully installed
         with the INSTALL command.  Second, the definition of ASL:  has
                                                                  Page 5


         been changed to be PAT:,DIS:,INS:.  The old definition was
         PAT:,DIS:,REL:,UNV:,SYS:.  This change was made to obtain
         better control over all files used in the build process.  We
         have delivered what we believe to be a complete set of base
         building software on the Autopatch tape.  If your procedure has
         problems you may have to copy certain files into PAT:, DIS:, or
         INS:.  The following files are required for Autopatch use, not
         put in place by Autopatch, and may have been previously found
         in SYS:.

                        IBMCOM HASP and ET

                DDT11.EXE       GALCNF.UNV      MACDLX.EXE

                        FORTRAN

                BLIS10.EXE      BLIS10.ERR

         If these files are currently found in SYS:  they must be copied
         or moved to PAT:, DIS:, or INS:.

    23.  (tape 9) The IBMCOM products have a module named MACROS.P11
         which conflicts with a module by the same name with different
         contents in the ANF10 product.  The IBMCOM MACROS module has
         been renamed as MACRO.P11.  For users of Autopatch on the
         IBMCOM products for the first time, if the IETV04 or IHSV01
         .CCL file is used to load the distribution directory then no
         action is required by the user.  Otherwise, the distributed
         MACROS.P11 file must be renamed to be MACRO.P11 or the
         MACRO.P11 file on the Autopatch tape must be put in DIS:.  The
         UTILTY.UPD file will update the Patch Database file.

    24.  (tape 7) Changes have been made to the PEP utility.  It is
         MANDATORY that PEP.EXE and PEPB.EXE be restored to SYS:  from
         the installation (second) save-set.  Due to a limited amount of
         space in some of PEP's internal tables, we are now declaring
         some products to be "obsolete".  These products will be removed
         from PEP's internal tables.  For the most part this process is
         transparent to you, unless the obsolete product has previously
         been SELECTed.  Suppose FORTRAN-10-V6 is one of your SELECTed
         products.  In that case, the following message would be
         displayed the first time you run the new PEP:

             [FORTRAN-10-V6 is now obsolete.
              Edits are no longer being delivered.
              You should DESELECT this product.]

         This message will only appear ONCE PER SELECTED OBSOLETE
         PRODUCT.  Use the DESELECT command to purge the obsolete
         product from your database.
                                                                  Page 6


                                      NOTE

             The PEP101.PDF file is NOT compatible with earlier
             versions of PEP.


         There is now a short version of the INFORMATION command called
         STATUS.  It displays the status information and logical name
         definitions, but does not list any files or their checksums.
         For example, you might see the following:

             PEP>status LINK-10-V5-1

             LINK-10-V5-1 is ready to be SETUP for patch and rebuild
              Patches retrieved through patch tape 7

              Logical names:
                PAT: (autopatching directory) defined as DSKP:[7,6]
                DIS: (distribution directory) defined as DSKP:[7,6,LINK]
                BAK: (backup directory) defined as DSKP:[7,6,BACKUP]
                INS: (installation directory) defined as SYS:
                ASL: (autopatch search list) defined as PAT:,DIS:,INS:


    25.  (tape 7) Edit 612 to DBMS-10-V5A eliminates the need for the
         DBSINF.REL module which was introduced on Autopatch tape 5.
         Users who have Autopatched DBMS previously are urged to be sure
         that the new version of the DBINF1.CMD file is restored from
         the patch set 7 save set on this tape.  Use of the DBMV5A.Ann
         file will accomplish this task.

    26.  (tape 7) The second chapter of the TOPS-10/TOPS-20 Autopatch
         Procedures/Reference Manual suggests a quota of 20,000 blocks
         for the [7,6] PPN on page 2-2.  Because of additional product
         support, it is now suggested that you use a figure of 150000.

    27.  (tape 6) The patch directory files (.DPD) have been
         re-formatted;  the same number of edits, but less 'patches',
         are described.  Also, intermediate checkpointing has been
         suppressed during the execution of the PEP 'AUTOPATCH' command.
         Checkpoint processing time has been SIGNIFICANTLY reduced.
         These changes will improve PEP performance, but will cause
         minor variations from the examples provided on pages 2-7, 2-17
         and 3-8 of the Autopatch Procedures/Reference Manual.

    28.  (tape 6) Users of FORTRAN with DBMS MUST create a file - read
         the INSTAL.DOC file.

         If you have previously SELECTed DBMS for Autopatch and
         indicated that FORTRAN was being used than you may want to 're
         do' DBMS.  FORTRAN V6 is no longer supported by Autopatch.
         With FORTRAN V7 and later the FORLIB.REL file is not modified
         for DBMS and the DBMSF.EXE file is autopatched by FORTRAN.

         The suggested procedure is to use the DBMV5A.Ann file to
                                                                  Page 7


         restore all files for DBMS from this tape and issue the
         DESELECT and SELECT commands for DBMS-10-V5A to PEP before
         Autopatching DBMS.  Otherwise, the DBMS Autopatch process will
         'install' copies of FORLIB.REL and DBMSF.EXE which is also done
         by the FORTRAN Autopatch process.

    29.  (tape 6) There are three warning messages seen during the
         patching of REL libraries of the DBMS product.  Newer edits are
         trying to remove edits which were suppressed.  This condition
         is non-fatal and has no impact on the success of DBMS updating.
         Ignore the messages.

    30.  (tape 6) BATCH time limits for FORTRAN and COBOL should be high
         to ensure that the product build BATCH jobs do not abort due to
         CPU time overrun.  Use a figure of 5 hours to cover all
         possibilities.

    31.  (tape 6) Some products can optionally use other products.  This
         means that one product may have to be patched and rebuilt
         before another product.  For example, COBOL can optionally use
         the DBMS product.  The COBOL Autopatch process requires that
         DBMS and SORT be updated before COBOL.  In order to apply all
         patches correctly you must SUBMIT the Patch and Build Control
         file for SORT and DBMS before the COBOL Control file.  The MPE,
         Customer-supported and Decnet options to the TOPS-10 Monitor
         must be Autopatched before the Control file to build the
         monitor is submitted.

    32.  (tape 5) Before selecting the ALGOL product for Autopatching be
         sure to read the note in the INSTAL.DOC file regarding a
         required rename of the OTS.

    33.  (tape 4) When PEP is run, the default directory must be PAT:.

    34.  (tape 4) It is advised that all desired products be SELECTed
         for Autopatching before entering the AUTOPATCH or RETRIEVE
         command for the first time.  The patch retrieval process is NOT
         product specific.  This process can be invoked with the
         RETRIEVE command or the AUTOPATCH command.  PEP will then read
         the entire patch directory file (.DPD) and update the patch
         database file (.PDB) for all SELECTed products.  If the
         AUTOPATCH command is entered for a product which was SELECTed
         at the time of a prior retrieval process, a statement will be
         made indicating that all patches have already been retrieved.




3.0  RELATED DOCUMENTS

TOPS-10/TOPS-20 Autopatch Procedures/Reference Manual (AA-H729A-TK)
INSTAL.DOC      (in Installation Save Set on this tape)
                                                                  Page 8


4.0  FILE INDEX

Patch Set 022

File            Description

README.022      Patch Set 022 Master Documentation File
TAP022.DIR      Directory with Checksums of Patch Set 022
PAT122.DPD      Patch Directory File for Patch Set 022
APEDIT.RPT      Autopatch Edit Report
APEDIT.022      Autopatch Edit Report for Patch Set 022
PATCLN.CMD      Directory Cleanup Command File
UTILTY.UPD      Utility checksum and version update file

COBVER.C22      COBVER.MAC Patch FIle    COBOL-10-V12C
IFGEN.C22       IFGEN .MAC
CBL74.X22       CBL74 .EXE
CBL74C.X22      CBL74C.EXE
CBL74D.X22      CBL74D.EXE
CBL74E.X22      CBL74E.EXE
CBL74F.X22      CBL74F.EXE
CBL74K.X22      CBL74K.EXE
CBL74O.X22      CBL74O.EXE
68274.X22       68274 .EXE
68274C.X22      68274C.EXE
68274D.X22      68274D.EXE
68274E.X22      68274E.EXE
68274F.X22      68274F.EXE
68274K.X22      68274K.EXE
C74LIB.X22      C74LIB.REL
C74O12.X22      C74O12.EXE


CMPLEX.C22      CMPLEX.BLI Patch File   FORTRAN-10-V11
DEFPT.C22       DEFPT .BLI
REVHST.C22      REVHST.BLI
DORTB.X22       DORTB .EXE
DORTC.X22       DORTC .EXE
DORTD.X22       DORTD .EXE
DORTE.X22       DORTE .EXE
DORTF.X21       DORTF .EXE
DORTG.X22       DORTG .EXE
DORTRA.X22      DORTRA.EXE
FORTB.X22       FORTB .EXE
FORTC.X22       FORTC .EXE
FORTD.X22       FORTD .EXE
FORTE.X22       FORTE .EXE
FORTF.X22       FORTF .EXE
FORTG.X22       FORTG .EXE
FORTRA.X22      FORTRA.EXE
SINGLE.X22      SINGLE.EXE

                                                                  Page 9


LPTTTY.X22      LPTTTY.MAC Patch File  GALAXY-10-V704
OPR.X22         OPR   .MAC
LPTMAC.X22      LPTMAC.MAC
OPRPAR.X22      OPRPAR.MAC
ORNMAC.X22      ORNMAC.MAC


IBMSPL.C22      IBMSPL.MAC Patch File   IBMCOM-10-ET-V4


IBMSPL.C22      IBMSPL.MAC Patch File  IBMCOM-10-HASP-V1

AUTCON.X22      AUTCON.MAC Patch File   MONITOR-10-V704
CLOCK1.X22      CLOCK1.MAC
COMDEV.X22      COMDEV.MAC
COMMON.X22      COMMON.MAC
CTXSER.X21      CTXSER.MAC
DCRSER.X22      DCRSER.MAC
D36COM.X22      D36COM.MAC
DEVPRM.X22      DEVPRM.MAC
ERRCON.X22      ERRCON.MAC
FILUUO.X22      FILUUO.MAC
MACSYM.X22      MACSYM.MAC
MONPFH.X22      MONPFH.MAC
NETSER.X22      NETSER.MAC
ONCMOD.X22      ONCMOD.MAC
PTYSER.X22      PTYSER.MAC
ROUTER.X22      ROUTER.MAC
S.X22           S     .MAC
SCNSER.X22      SCNSER.MAC
SEGCON.X22      SEGCON.MAC
T78KON.X22      T78KON.MAC
TAPSER.X22      TAPSER.MAC
TAPUUO.X22      TAPUUO.MAC
TD2KON.X22      TD2KON.MAC
TM2KON.X22      TM2KON.MAC
TX1KON.X22      TX1KON.MAC
UUOCON.X22      UUOCON.MAC
VMSER.X22       VMSER .MAC



RX2SER.X22      RX2SER.MAC  Patch File  CUSTOMER-SUPPORTED-10-V704
TCXKON.X22      TCXKON.MAC
TMXKON.X22      TMXKON.MAC
TS1KON.X22      TS1KON.MAC


                                                                 Page 10


ACTDAE.X22      ACTDAE.MAC       Patch File     UTILITIES-10-V704
DDT.X22         DDT   .MAC
DECLAR.X22      DECLAR.MAC
F1EDDT.X22      F1EDDT.MAC
F1FDDT.X22      F1FDDT.MAC
F1UDDT.X22      F1UDDT.MAC
F1VDDT.X22      F1VDDT.MAC
FAL.X22         FAL   .MAC
FILCOM.X22      FILCOM.MAC
HELP.X22        HELP  .MAC
INITIA.X22      INITIA.MAC
INTCUS.X22      INTCUS.MAC
INTPRM.X22      INTPRM.MAC
MIC.X22         MIC   .MAC
REACT.X22       REACT .MAC
RMS.X22         RMS   .EXE
RMS.Y22         RMS   .REL
RMSCOB.X22      RMSCOB.EXE
RMSUTL.X22      RMSUTL.EXE
RMSINT.X22      RMSINT.UNV
RMSSYM.X22      RMSSYM.LUS
SCAN.X22        SCAN  .MAC
UUOSYM.X22      UUOSYM.MAC


Base Building Software

ACTLIB.REL      ACTPRM.UNV      ACTSYM.UNV      B361LB.REL      BTSPRM.UNV
C74SHR.REL      CATPRM.UNV      CATTAB.REL      CHRFRM.REL      COMPIL.EXE
CREF.EXE        D60JSY.REL      D60UNV.UNV      DIRECT.EXE      DXMCA.ADX
EDDT.REL        FILEX.EXE       FORDBM.REL      GALCNF.UNV      GALGEN.EXE
GLOB.EXE        GLXINI.REL      GLXLIB.REL      GLXMAC.UNV      HELPER.REL
JOBDAT.REL      JOBDAT.UNV      KLPCOD.ULD      KNICOD.ULD      LINK.EXE
LNK999.EXE      LNKERR.EXE      LNKLOD.EXE      LNKMAP.EXE      LNKOV1.EXE
LNKOV2.EXE      LNKSCN.EXE      LNKXIT.EXE      MACDLX.EXE      MACRO.EXE
MACSYM.UNV      MACTEN.UNV      MAKLIB.EXE      MONSYM.UNV      NCPTAB.REL
OPRPAR.REL      ORNMAC.UNV      OVRLAY.REL      PATH.EXE        PIP.EXE
QSRMAC.UNV      RMSINT.UNV      S.MAC           SCAN.REL        SCNMAC.UNV
SWIL.REL        SWIL.UNV        TECO.EXE        TGHA.EXE        UFDPRM.UNV
UFDSET.REL      UUOSYM.REL      UUOSYM.UNV      VNP36.EXE       WILD.REL

                                                                 Page 11


5.0  PRODUCT DOCUMENTATION

Information on which edits are provided on the CURRENT tape can be found
in the APEDIT.0nn file in the first save-set.  You may use the ALL.Pnn
file to restore files for the latest update from the CURRENT tape, and
the ALL.Ann file to restore files from the HISTORY tape.

If you are patching a product for the first time, you must define a
distribution area and obtain some files from the distribution tape.
This process is described in the INSTAL.DOC file in the second save-set
on the CURRENT tape and in the Autopatch Procedures/Reference Manual.
The Dist.  CCL file found in the Installation save-set may be used for
this purpose.

Below is a list which identifies these files and the Distribution tape
for each product.
                                                                 Page 12



Product         Dist. tape      Dist. CCL

ALGOL-10-V10B   BB-D608D-SB     ALG10B.CCL

ANF10-V704      BB-X140C-SB     MON704.CCL

APLSF-10-V2     BB-D476E-BB     APL1S2.CCL

COBOL-10-V12C   BB-H580E-SB     CBL12C.CCL

COBOL-REP-V12C  BB-H580E-SB     CBR12C.CCL

CUSTOMER-SUPPORTED-10-V704
                BB-X130C-SB     CUS704.CCL

DBMS-10-V5A     BB-D478D-BB     DBMV5A.CCL

DECNET-10-V704  BB-X116C-SB     DEC704.CCL

FORTRAN-10-V11  BB-D480G-SB     FTN111.CCL

FORTRAN-10-REP-V11
                BB-D480G-SB     FTN1X1.CCL

GALAXY-10-V704  BB-FP63B-SB)    CSP704.CCL
                BB-X128C-SB)

IBMCOM-10-ET-V4 BB-J992D-SB     IETV04.CCL

IBMCOM-10-HASP-V1
                BB-V552B-SB     IHSV01.CCL

MCB-10-V704     BB-X116C-SB     MCB704.CCL

MONITOR-10-V704 BB-X140C-SB     MON704.CCL

MPE-10-V704     BB-X133C-SB     MPE704.CCL

MS-SOURCES-10-V11
                BB-FP63B-SB)    CSP704.CCL
                BB-X128C-SB)

SORT-10-V4D     BB-H580E-SB     CBL12C.CCL*

UTILITIES-10-V704
                BB-FP63B-SB)    CSP704.CCL
                BB-X128C-SB)

* The SORT product may also be setup for Autopatching with the use of
the SRTV4D.CCL file against the BB-D489F-SB Sort Distribution tape