Trailing-Edge - PDP-10 Archives - bb-l014r-bm_tops20_v6_1_atpch_18 - autopatch/readme.018
There is 1 other file named readme.018 in the archive. Click here to see a list.


This is the  eighteenth  Autopatch  tape.   It  supports  ALGOL-20-V1-2,
APL-20-V2,  APLSF-20-V2,  BASIC-PLUS-2-V2A, COBOL-20-V13, COBOL-REP-V13,
DBMS-V6-1,  DECNET-20-V4,  FTS-20-V1,  GALAXY-20-V5,  IBMCOM-20-ET-V2-1,
IBMCOM-20-HASP-V1-1,   MS-SOURCES-20-V11,   PASCAL-20-V1,   PSI-20-V1-1,
SORT-20-V5,    SORT-REP-V5,    TOPS-20-2060-V6-1,    TOPS-20-TCPIP-V6-1,
TRAFFIC-20-V4,  UTILITIES-20-V6-1,  and  UTILITIES-B-V6-1.   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.


     1.  The following products are no longer Autopatched because of new
         releases:   COBOL-20-V12B, DBMS-20-V6, DECNET-20-V3, DIL-20-V1,
         FORTRAN-20-V6, FORTRAN-20-V7, FORTRAN-20-V10,  FORTRAN-REP-V10,
         GALAXY-20-V4,    GALAXY-20-V4-2,    LINK-20-V5-1,    MS-20-V10,
         PSIMCB-20-V1-1,   PSIUTL-20-V1-1,    RMS-20-V1,    SORT-20-V4C,
         TOPS-20-2020-V4,        TOPS-20-2040-V4,       TOPS-20-2060-V4,
         TOPS-20-2060-V5-1,   TOPS-20-KL-ARPA-V4,    TOPS-20-KS-ARPA-V4,
         TOPS-20-KL-ARPA-V5-1, UTILITIES-20-V4, and UTILITIES-20-V5-1.


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

     2.  The following Autopatched product(s) do not have any new  edits
         delivered  with  this  patch  set:   ALGOL-20-V1-2,  APL-20-V2,
         APLSF-20-V2, DBMS-V6-1, FTS-20-V1, GALAXY-20-V5,  PASCAL-20-V1,
         SORT-20-V5, SORT-REP-V5, and TRAFFIC-20-V4.

     3.  (*new*) We have  eliminated  the  product-specific  DUMPER  cmd
         files.  There are now two files.  The ALL.P18 file will restore
         files for all desired products from  the  CURRENT  patch  tape.
         The  ALL.A18  file  will restore 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.   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.Pnn and ALL.Ann will then restore all
                                                                  Page 2

         files for that product.

     4.  (*new*) Most of the patch files for DECNET components  on  this
         tape  have  already been delivered on previous tapes.  They are
         here for the PSI product which should have  had  these  updates
         applied.  The only new items for the DECNET product are NFT and

     5.  (*new*) The DIL V2  components  have  been  part  of  both  the
         UTILITIES-20-V6-1  and the UTILITIES-B-V6-1 product sets.  This
         has  been  fixed.   You  must  Autopatch  the  UTILITIES-B-V6-1
         product to get the DIL edits delivered with this tape.

     6.  (*new*) We have provided null patch command files for APL, SORT
         and  PSI.   If  you build any of these products in spite of the
         fact that no edits are delivered  these  files  will  permit  a
         successful  build.  There will be checksum warnings about these
         files which may be ignored.

     7.  (tape 17) A recent change to PEP causes a  justifiable  failure
         during SELECT or BUILD if a BLD type file, described in the PDF
         file, is missing.  However, up  to  now,  the  DB2V61.PDF  file
         referenced   a  non-existent  DBMS.CMD  file.   This  has  been
         changed.  Users who select DBMS with  the  PDF  file  from  the
         second  save-set on this tape will not have the problem.  Users
         who currently are Autopatching DBMS will need a dummy  DBMS.CMD
         file.   Such  a file has been included on the first save-set of
         this tape.  This file should be restored  to  any  area  (PAT:,
         DIS:  or INS:) for DBMS.

     8.  (tape 17) Users of FORTRAN with DBMS are  advised  to  use  the
         DBCS2F.CMD  file  which  was delivered on the DBMS distribution
         tape and NOT the newer version on the FORTRAN V11  distribution
         tape.   The FORTRAN version references a file (DBSFG.REL) which
         was never released.

     9.  (tape 17) The same RMSINT.UNV replacement file was delivered on
         both  tape  15  and  tape  16.  However, due to an error in the
         Distributed Patch Directory file (DPD) for  tape  16,  the  L36
         file was renamed to be the UNV.  We have corrected this problem
         by again distributing the same update to the UNV file  on  this

    10.  (tape 16) There is a new version of PEP in the second save-set.
         PEP  has been modified to retain the correct size and byte size
         for copy operations.  This is important for the .EXB  files  of
         BOOT.   The  new  PEP  and  PEPB  will be restored if using the
         ALL.Pnn file.

    11.  (tape 16) The HELPER.MAC and HELPER.REL which were  distributed
         on  the latest "Tops-20 V4.1 Update tape" (BB-R775E-BM) are for
         use with EDT builds only.  These files have not been  validated
         as  replacements  for  the original HELPER distribution and are
         not to be used as such.
                                                                  Page 3

         If the EDT-only HELPER is retrieved from the  Update  tape  and
         used  in  place of the standard HELPER the UT2V61 product build
         will fail.

         Copies of the original release of HELPER.MAC and HELPER.REL are
         available  in  the first saveset of the Autopatch tape for your

    12.  (tape 16) Autopatch Tape 16 for TOPS-20 6.1 contains a software
         documentation  file  that  reflects  the  software on the tape.
         DIGITAL authorizes  you  to  make  up  to  two  copies  of  the
         documentation  for  use  at  your site, as long as you maintain
         DIGITAL's copyright page.  We request that you print  the  file
         and use one of the reply forms to send your opinions to us.

         On Autopatch Tape 16, you will find the following documentation

         1.  DDT44C.MEM contains the DDT Manual;  it uses  approximately
             118  pages  of  disk  space.   This  version  of the manual
             contains changes that we have made  since  the  manual  was
             printed for TOPS-20 DDT Version 43, in May 1985.

         2.  DDTINFO.MEM is a duplicate of this customer letter and  the
             reply form.

         DDT44C.MEM is about 155 line-printer pages  long  and  contains
         change bars to indicate the pages that have changed and bullets
         to indicate data deletions.   The  file  contains  non-printing
         control  characters  for  paging  and bolding effect, making it
         unsuitable for terminal display.  We recommend that  you  print
         the file on any supported line printer.

    13.  (tape 16) Be sure to read the T26A61.B16 and T26V61.B16  beware

    14.  (tape 15) This time the Autopatch updates are delivered on  two
         tapes.  The first tape (BB-L014x-BM) contains the current patch
         save-set and the installation save-set.  If you are at  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 previous Autopatch tape.

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

         In essence, the old tape format has been split with  the  first
         two save-sets of the old format now being written to a separate
         tape.  All of the DUMPER cmd  files  are  still  found  in  the
         current patch save-set (first save-set of the first tape).  The
         ALL.Pnn file restores files from the current (first)  tape  and
         the  ALL.Ann  file  restores files from the historical (second)
                                                                  Page 4


         If you are Autopatching ALGOL, for example, for the first  time
         and  want  to  use  the DUMPER cmd files, create a LAP.DEF file
         with the LAPALG:  logical defined and use the ALL.Pnn  file  on
         the CURRENT tape and the ALL.Ann file on the HISTORICAL tape.

    15.  (tape 15) 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-V13,   FORTRAN-20-REP-V11,  and  SORT-REP-V5  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.

    16.  (tape 15) Users of the new FORTRAN V11 must update RMS V3  with
         this  Autopatch tape in order to use the RMS interface with the
         new FORTRAN.  RMS is part of the UTILILITIES-B-V6-1 product.

    17.  (tape 15) The Distributed Patch Directory  file  as  originally
         delivered  on  Autopatch tape 12 had two entries for correction
         files to LINK.  These entries were made in error.  With tape 13
         and  subsequent  tapes  the  correct  PAT212.DPD  file has been
         provided.  Before autopatching UTILITIES with tape 12 edits  be
         sure that the PAT212.DPD file has a date of 30-MAY-86 or later.

    18.  (tape 15) A replacement RAM.ULD file has been put on the  first
         save-set  of  this  tape.   This file is used when building the
         KNILDR component of the UTILITIES product.  This file  contains
         several  edits  to  the  NI microcode.  The RAM.ULD file is not
         maintained as part of  the  UTILITIES  product  and  should  be
         simply  restored  to PAT:.  The restoration will occur normally
         with the use of the ALL.Pnn file.

    19.  (tape 14) This tape contains important  edits  for  COBOL  V13.
         The  edits  fix  the  way LIBOL does BLTs.  COBOL without these
         edits may  have  errors  when  used  with  the  new  micro-code
         2.1(442)  which  was delivered with the most recent update tape
         (6.1A).   Both  the  source-patched  and  the   Decrypted   EXE
         replacement updates contain these edits.

    20.  (tape 14) There are two files in the  second  save-set  of  the
         Autopatch   tape   which   are  required  for  UTILITIES.   The
         EDTHLP.RNO and MAKHLP.EXE files should be placed  in  the  DIS:
         area.   These files were omitted from the distribution tape and
         were previously designated as required  in  INS:.   The  UT2V61
         DUMPER control file will restore these files to PAT:.  You must
         copy these files to DIS:.

    21.  (tape 13) For the 6.1 monitor there  are  two  LINK  CCL  files
         (P6BLNK.CCL and P6MLNK.CCL).  These files were omitted from the
         TOPS-20  V6.1  distribution  but  are  included  on  the  first
         save-set  of this Autopatch tape.  Use of the ALL.Pnn file will
         put these files in PAT:.  Before building the monitor the  user
                                                                  Page 5

         must rename one of these files to be P6LNK.CCL.  The 'P6B' file
         is for a 'BIG' configuration and the 'P6M' file is for a  'MAX'

         Similary, replacement LINK CCL files have been provided for the
         TCP/IP  monitor  product.  Before building the ARPA monitor the
         user must rename one of these files to be ANLNK.CCL.  The 'ANS'
         file  is  for  a 'BIG' configuration, the 'ANM' file is a for a
         'MAX' configuration and the 'AND' file is  for  an  ARPA/DECNET

    22.  (tape 13) Be aware that the distributed PARAMS.MAC file  builds
         a  monitor  which  provides  NIA20 (Ethernet) support.  STG.MAC
         will not assemble correctly if this is changed because  of  the
         lack  of  the NIPAR.UNV file on the distribution.  This file is
         provided in the first save-set of this Autopatch tape.

         Also, be sure that there is not a 5.1 PARAMS.MAC file in  PAT:.
         This  file  was  delivered  on  Autopatch  tape 9 and should be

    23.  (tape 13) The COBOL V13 Autopatch Patch &  Build  control  file
         (CBL13.CTL)  has  been  changed  to  NOT  put DBMS support into
         COBLIB.REL.  The supported method of DBMS implementation is  to
         LINK DBMS.REL into the OTS (COBOTS-V13.EXE).  This procedure is
         accomplished by the DBMS  6.1  build  file  (DB2V61.CTL).   The
         DB2V61  product  should have been 'tracking' the DBMS.REL file,
         but has not.

         If you use Autopatch for DBMS/COBOL then you must take  one  of
         two  actions  to  correct  the  problem with DBMS.REL.  You may
         restore the revised DB2V61.PDF file from the second save-set of
         the  Autopatch  tape,  DESELECT  the  DBMS product with the PEP
         tool, SELECT DBMS with PEP, and  Autopatch  DBMS.   An  updated
         DBMS.REL  will  now  be  tracked  and  installed  as with other

         Alternatively, you may insert a copy  command  into  DB2V61.CTL
         after  a successful build is signalled to move the new DBMS.REL
         file from PAT:  to INS:.  However, a  later  RESTORE  with  PEP
         will not do the right thing with this file.

         Users who install DBMS for Autopatching for the first time with
         this  tape  do not need to be concerned with this problem.  The
         CBL13.CTL file will no longer implement DBMS support in the OTS
         - you must Autopatch DBMS to accomplish this.

    24.  (tape 13)  It  is  possible  to  use  DECNET  without  the  MCB
         front-end code.  At this time, the Autopatch process for DECNET
         requires you to build the MCB.  If you do not intend to use the
         MCB  then  you  may  SELECT  DECNET  for  Autopatching after 1)
         creating a null FOO.SYS file in the directory you intend to use
         as   INS:    and  2)  copying  the  CETAB.MAC,  NETPAR.MAC  and
         NMLACC.MAC files from the second save-set of the Autopatch tape
         into the area you intend to use as DIS:.
                                                                  Page 6

         When SELECTing DECNET answer the node name with FOO.SYS.

    25.  (tape 13) The EXEC building process for  tape  12  displayed  a
         warning  message  about  Multiply-defined global symbol STATSW.
         This message may be ignored and the problem is  corrected  with
         the  delivery  of  EXECDE.UNV  in  the  first  save-set of this
         Autopatch tape.

    26.  (tape 13) PEP reports a strange EDIT/VERSION  for  the  rebuilt
         COBOTS-V13.EXE  file.   An INFORMATION VERSION on the component
         reports no edit at all!  This is due to a flaw/bug in the COBOL
         product  and may be ignored.  Using DDT to display the contents
         of location 137 will show the correct EDIT/VERSION.

    27.  (tape 13) If you use tape drives other than the TU72,  be  sure
         to read the GALV50.B13 beware file regarding a MOUNTR edit.

    28.  (tape 12)  The  FTS-20  product  build  requires  some  DIL  V1
         modules.  Since DIL V2 has replaced DIL V1 these V1 modules are
         no longer Autopatched.  The modules (DAP2V1  and  XPN2V1)  have
         been  provided  on  the  second save-set of the Autopatch tape.
         The use of the ALL.Pnn file will restore  these  files  to  the
         patching  directory.  FTS-20 may now be Autopatched at any time
         without regard to the Autopatching of DIL V2 which is now  part
         of the UTILITIES-20 product set.

    29.  (tape 12) A normal customized installation of  DECNET-20-V4  or
         PSI-20-V1-1 MUST occur before the product can be Autopatched.

    30.  (tape 12) The use of  the  Monitor/EXEC  DDC  file  to  perform
         initial  distribution directory loading will also load required
         files for GALAXY and the UTILITY set into the common directory.
         Be  sure  to  specify  this  directory  name when SELECTing the
         products with PEP.  The use of  the  GALV50.DDC  or  UT2V61.DDC
         file  is  ONLY  required  if  you  do NOT use the T26V61.DDC or
         T26A61.DDC file.

    31.  (tape 12) The SELECTion  of  TOPS-20  Utilities  requires  that
         CHECKD.EXE,  6-1-SETSPD.EXE,  and  6-1-SYSJOB.EXE  exist in the
         installation directory specified.  This means you  either  have
         to  copy  these  files  to INS:, or DEFINE INS:  to include the
         SYSTEM:  logical.  Additionally, after each autopatch update of
         these  utilities,  they  must  be  copied  from  the  autopatch
         installation directory to a SYSTEM:  directory.

    32.  (tape  11)  The  DBMS-V6-1   Autopatch   build   control   file
         (DB2V61.CTL) clears ALL logical definitions.  If there are user
         logical definitions which must be in effect, these  definitions
         can  be  placed  in  a take command file named SETUP.CMD in the
         connected directory.

    33.  (tape 11) COBOL-20-V13 users should  be  sure  that  a  revised
         OTSDEL.CMD file from the second (installation) save-set on this
         tape is used.  The old version deleted C8XSHR.REL which  caused
         errors  when the build process then tried to copy that file for
                                                                  Page 7

         later use by the  DBMS  process.   The  revised  file  will  be
         restored from the Autopatch tape if the ALL.Pnn file is used.

    34.  (tape 11) Several products use external command files in  their
         build  procedure.  When a new version is provided, be sure that
         the newest versions  of  these  command  files  are  used.   In
         particular,  use  the  F20LIB.CCL and F20OTS.CCL files from the
         version 11 tape and not from previous releases.  Use of  normal
         Autopatch  procedures  will  put  the  new  files in the common
         patching directory where they will be used.  If,  however,  you
         are  using  a  customized  directory/logical setup, you must be
         sure that the correct files are being used.

    35.  (tape  10)  Revised  copies  of  DBCS24.CMD,   DBCS28.CMD   and
         DBCS2F.CMD  for  the  DBMS-V6  product  have  been delivered on
         previous Autopatch tapes.  Be sure that these files are NOT  in
         the common patching directory (PAT:).

    36.  (tape 10) If you are building either COBOL or FORTRAN with DBMS
         V6-1,  do  not  INSTALL  COBOL or FORTRAN before building DBMS.
         Unlike the V6 product, the V6.1  Autopatch  procedure  requires
         that  COBOL  and/or  FORTRAN  be  built  BEFORE  the  DBMS V6.1
         Autopatch  build  is  submitted.   The  DBMS   V6.1   Autopatch
         procedure will implement DBMS within COBOL and FORTRAN.

    37.  (tape 9) The COBOL-V13 product may now be updated with  REL/EXE
         replacement.  If you want to use this method the KEY files must
         be restored from the COBOL distribution tape, support files for
         CBL13R  restored from the Autopatch tape, and the COBOL-REP-V13
         product selected with PEP.  See the INSTAL.DOC  file  for  more
         information.  The COBOL-20-V13 product will continue to receive
         source-level patches and you may continue to use this method of
         Autopatching.  The SORT-V5 product may also be Autopatched with
         either source-level or EXE replacement.


             The REL/EXE replacement files have been  encrypted  and
             must  be  processed  via  Autopatch  before they can be

    38.  (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.   You  may  also  want  to use the
         PATCLN.CMD file in the first save set to delete other temporary
         files AFTER successful installation.

         Second,  the  definition  of  ASL:   has  been  changed  to  be
         PAT:,DIS:,INS:.     The    old    definition   of   ASL:    was
         PAT:,DIS:,SYS:.  This change was made to obtain better  control
         over  all  files  used in the build process.  We have delivered
                                                                  Page 8

         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:.


                SDDT.EXE        UDDT.EXE


                NMLACC.MAC      CETAB.MAC       NETPAR.MAC


                B362LB.REL      XPORT.REL

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

    39.  (tape 9) The ALGOL, COBOL, IBMCOM, and PASCAL Autopatch control
         files  redefine the local definition of SYS:  to ensure the use
         of provided Base Building Software items.

    40.  (tape 8) A required file for the IBMCOM products, PROD.P11,  is
         provided  on  the  Autopatch  tape.   Use  of any of the IBMCOM
         DUMPER control files to process the Autopatch tape will attempt
         to load this file into the default distribution areas.

    41.  (tape 8) Be  sure  to  read  the  IETV21.B08,  IHSV11.B08,  and
         PAS2V1.B08 beware files.

    42.  (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
         TOPS-20-2060-V4  is  one  of  your  SELECTed products.  In that
         case, the following message would be displayed the  first  time
         you run the new PEP:

             [TOPS-20-2060-V4 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 9


             The PEP201.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.

    43.  (tape 7) PA1050.EXE, unlike other  Base-building  Software,  is
         invoked  indirectly  from  SYS:.   In  order  to avoid checksum
         warnings from PEP, the PA1050.EXE program which is supplied  on
         this  tape and restored to PAT:  must be copied to SYS:  before
         invoking PEP.

    44.  (tape 7) The Autopatch process is designed to be  used  without
         privileges  enabled.   If  you  experience  protection failures
         check that all parameters of the directory  have  been  set  up
         properly  -  especially  PROTECTION,  DEFAULT  PROTECTION, USER
         GROUP, and DIRECTORY GROUP.  Also,  be  sure  that  appropriate
         ACCESS commands have been given for the structures in use.

    45.  (tape 7) The working and permanent quotas for the  distribution
         directory  for  TOPS-20 were given as 3000 pages in the manual.
         If you are using the TOPS-20 distribution directory  as  common
         to  GALAXY  and UTILITIES this figure should be doubled to 6000

    46.  (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.

    47.  (tape 6) The PA1050 program will automatically expunge  deleted
         files if the MAKLIB program causes an over quota situation.  Be
         aware that PA1050 will NOT expunge if the situation detected is
         that  the  disk  is  physically  full.   The build process will
         explicitly EXPUNGE the PAT:  area when the MAKLIB operation  is
         complete.   You  are  advised  not to use infinite quota if the
         disk used may run out of space.

    48.  (tape 6) The GALAXY and TOPS-20 DDC files may take longer  than
         the  default  five  minute  BATCH  time  limit  and  should  be
         submitted with a ten minute limit to be safe.

    49.  (tape 6) BATCH time limits for 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.
                                                                 Page 10

    50.  (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  DBMS Autopatch process requires that
         COBOL and/or FORTRAN be updated before DBMS.

    51.  (tape 6) Sites which Autopatch BASIC-PLUS-2 for the first  time
         may  notice  that  the LINKing of BASOTS generates some warning
         messages.  These messages are given because  the  new  LINK  is
         detecting  a  questionable  but  harmless  situation and may be

    52.  (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.

    53.  (tape 5) The Autopatch build process for ALGOL, COBOL, DBMS and
         SORT  redefines  DSK:.   It  is  MANDATORY  that a structure be
         specified when providing the  directory  specifications  during
         the initial SELECTion process.

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

    55.  (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.

    56.  (tape 3) Be sure to read the APL2B2.B03 beware file.


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

                                                                 Page 11

Patch Set 018

File            Description

README.018      Patch Set 018 Master Documentation File
TAP018.DIR      Directory with Checksums of Patch Set 018
PAT218.DPD      Patch Directory File for Patch Set 018
APEDIT.RPT      Autopatch Edit Report
APEDIT.018      Autopatch Edit Report for tape 018
ALGV12.SUP      Empty Patch command files
UTILTY.UPD      Utility checksum and version update file

 Patch Files

B20CMA.R18      B20CMA.REL      Patch File      BASIC-PLUS-2-V2A

COBVER.C18      COBVER.MAC      Patch File      COBOL-20-V13

DAPLIB.C18      DAPLIB.MAC      Patch File      DECNET-20-V4
NFT.C18         NFT   .MAC

ACT1.C18        ACT1  .BLI      Patch File      FORTRAN-20-V11
STA2.C18        STA2  .BLI

IBMSPL.C18      IBMSPL.MAC      Patch File      IBMCOM-20-ET/HASP
                                                                 Page 12

MS.X18          MS    .MAC      Patch File      MS-SOURCES-20-V11

DTE.X18         DTE   .TSK      Patch File       PSI-20-V1-1
DTE.Y18         DTE   .STB
NMS.X18         NMS   .TSK
NMS.Y18         NMS   .STB
NSP.X18         NSP   .TSK
NSP.Y18         NSP   .STB
TLI.X18         TLI   .TSK
TLI.Y18         TLI   .STB
TOP.X18         TOP   .TSK
TOP.Y18         TOP   .STB
XPE.X18         XPE   .TSK
XPE.Y18         XPE   .STB
XPT.X18         XPT   .TSK
XPT.Y18         XPT   .STB
FAL.C18         FAL   .MAC
NFT.C18         NFT   .MAC
NMLT20.X18      NMLT20.EXE

LN2061.X18      LN2061.REL      Patch File      TOPS-20-2060-V6-1
T20EX6.X18      T20EX6.REL
STG.MAC         Replacement files

T20AN.X18       T20AN .REL      Patch File      TOPS-20-TCPIP-V6-1
T20EX6.X18      T20EX6.REL
STG.MAC         Replacement files

DUMPER.C18      DUMPER.MAC      Patch File      UTILITIES-20-V6-1
INFO.C18        INFO  .MAC
                                                                 Page 13

DIL.X18         DIL   .REL      Patch Files     UTILITIES-B-V6-1
FFF.X18         FFF   .REL
MS.Y18          MS    .EXE
RMS.X18         RMS   .EXE
XRMS.X18        XRMS  .EXE
                                                                 Page 14

Base Building Software

                                                                 Page 15


Information on which edits are provided on the CURRENT tape can be found
in the APEDIT.018 file in the first save-set.

If you are patching a product for the first  time,  you  must  define  a
distribution  area  and  obtain  some  files from the dustribution 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.  DDC file found in the Installation save-set may be  used  for
this purpose.

You may use the ALL.Pnn file to restore files from the CURRENT tape, and
the  ALL.Ann file to restore files from the HISTORICAL tape.  Below is a
list which identifies the Dist.  DDC file and the Distribution tape  for
each product.

Product         Dist. tape      Dist. DDC

ALGOL-20-V1-2   BB-5471C-BM     ALGV12.DDC

APL-20-V2       BB-5135E-BM     APL2B2.DDC

APLSF-20-V2     BB-5137E-BM     APL2S2.DDC

                BB-5543F-BM     B20V2A.DDC

COBOL-20-V13    BB-Z795A-SM     CBL13.DDC


DBMS-V6-1       BB-4148F-BM     DB2V61-CBL.DDC

DECNET-20-V4    BB-H240E-BM     DEC2V4.DDC

FORTRAN-20-V11  BB-4157J-SM     FTN211.DDC

                BB-4157J-SM     FTN2X1.DDC

FTS-20-V1       BB-M251A-BM     FTS201.DDC

GALAXY-20-V5    BB-H137E-BM)    T26A61-BIG.DDC
                BB-H138E-BM)    T26A61-DCN.DDC

                BB-D351C-SM     IETV21.DDC

                BB-J724B-SM     IHSV11.DDC
                                                                 Page 16

                BB-JF18A-BM     MS211S.DDC

PASCAL-20-V1    BB-P557A-BM     PAS2V1.DDC

PSI-20-V1-1     BB-W661B-BM     PSIV11.DDC

SORT-20-V5      BB-Z795A-SM     CBL13.DDC

SORT-REP-V5     BB-Z795A-SM     CBL13R.DDC

                BB-H137E-BM)    T26A61-BIG.DDC
                BB-H138E-BM)    T26A61-DCN.DDC
                BB-EV83A-BM)    T26A61-MAX.DDC

                BB-H137E-BM)    T26V61-BIG.DDC
                BB-H138E-BM)    T26V61-MAX.DDC

TRAFFIC-20-V4   BB-5372E-SM     TFR2V4.DDC

                BB-H137E-BM)    T26A61-BIG.DDC
                BB-H138E-BM)    T26A61-DCN.DDC

                BB-JF18A-BM     --

* The SORT product may also be setup for Autopatching with  the  use  of
the  SRTV5.DDC  file or the SRTV5R.DDC file against the BB-Z761A-SM Sort
Distribution tape.

* The DBMS product may also be setup for Autopatching without updates to
the COBOL interface with the use of the DB2V61.DDC file.

* The GALAXY product may also be setup for Autopatching with the use  of
the  GALV50.DDC  file  and the UTILITIES product with UT2V61.DDC.  These
files are only needed if you do not use one of the monitor DDC files.

* The UTILITIES-B product does not use  a  distribution  area.   Updates
replace  the  end-user  files  which  are  installed as part of a normal