There are 2 other files named readme.020 in the archive. Click here to see a list.
This is the twentieth Autopatch tape. It contains patches for
ALGOL-20-V1-2, APLSF-20-V2, BASIC-PLUS-2-V2A, COBOL-20-V12C, DBMS-V6-1,
FORTRAN-20-V11, FTS-20-V1, GALAXY-20-V4-2, PASCAL-20-V1, SORT-20-V4D,
TOPS-20-2020-V4-1, TRAFFIC-20-V4, and UTILITIES-V4-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 product(s) are no longer Autopatched: APL-20-V2,
COBOL-20-V12B, DBMS-20-V6, DIL-20-V1, FORTRAN-20-V6,
FORTRAN-20-V7, FORTRAN-20-V10, FORTRAN-REP-V10, GALAXY-20-V4,
LINK-20-V5-1, LINK-20-V6, MS-20-V10, RMS-20-V1, SORT-20-V4C,
TOPS-20-2020-V4, TOPS-20-2040-V4, TOPS-20-2040-V4-1,
TOPS-20-2060-V4, TOPS-20-KL-ARPA-V4, TOPS-20-KS-ARPA-V4,
TOPS-20-KS-ARPA-V4-1 UTILITIES-20-V4, UTILITIES-20-KL-V4-1, and
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, APLSF-20-V2,
COBOL-20-V12C, DBMS-V6-1, FTS-20-V1, GALAXY-20-V4-2,
PASCAL-20-V1, and SORT-20-V4D.
3. (*new*) The DBMS control file will re-build the COBOL OTS in
PAT:. You should not INSTALL COBOL until after the DBMS build
has finished. Otherwise, you will have to manually copy the
COBOL files built by DBMS to INS:.
A similar circumstance exists with FORTRAN. If you will be
Autopatching DBMS for use with FORTRAN you may want to remove
the leading semi-colons associated with DBMSF from the
FTN211.PDF and/or FTN2X1.PDF file before SELECTing FORTRAN for
Autopatching. Then you should not INSTALL FORTRAN until after
the DBMS build has finished. Otherwise, you will have to
manually copy the DBMSF.EXE file built by DBMS to INS:.
The DBMS control file will create the following language
For COBOL-74 V12C support (KS only)
C74LIB.REL see notes 1 and 2
For COBOL V13 support (KL only)
COBLIB.REL see note 2
For FORTRAN V11 support
FORLIB.REL see note 3
Note 1: created when the DBMS-20 V6.1 stub is not detected
in the existing link-time library.
Note 2: created when DBMS-20 V6 support had previously been
added into the link-time library.
Note 3: created when the supplied FORLIB.REL does not contain
FORTRAN edit 3354.
4. (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 & Build control files from the same save-set will prevent
use of old patch command files.
5. (tape 19) We have eliminated the product-specific DUMPER cmd
files. There are now two files. The ALL.Pnn file will restore
files for all desired products from the CURRENT save-set of the
patch tape. The ALL.Ann file will restore ALL files for all
desired products from the 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.Ann will then restore all files for
6. (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.
7. (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.
8. (tape 17) Before submitting the UTLV41 control file you are
advised to be sure that the <AUTOPATCH.UTLWRK> area is empty.
If not, DELETE and EXPUNGE all files from that area. Otherwise
you may experience a failure due to the limitation on the size
9. (tape 16) The UTILITIES product set has been redefined. This
tape provides a new product called UTILITIES-V4-1 (UTLV41).
This product supports virtually all of the bundled components
except for GALAXY. LINK, formerly a separate product, has been
included. All components are now supported by full replacement
rather than by correction files. Complete up-to-date source or
REL/EXE files are provided.
In order to select the new utilities product you will need to
load files from the original TOPS-20 V4.1 distribution tape
(BB-D868E-BM/BB-V895A-BM) and from the latest TOPS-20 V4.1
Update tape (BB-R775E-BM). The UPD5.DDC and UTLV41.DDC files
in the second save-set on the Autopatch tape can be used in
this process. Read the INSTAL.DOC file for more information.
10. (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-20-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
11. (tape 10) Revised copies of DBCS24.CMD, DBCS28.CMD and
DBCS2F.CMD for the DBMS-V6 product have been delivered on
previous Autopatch tapes. If you are Autopatching V6.1 be sure
that these copies are NOT in the common patching directory
12. (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 DBMS 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.
13. (tape 10) Be sure to read the T22V41.B10 beware file. This
file contains beware information for edit 3115 which was first
delivered on tape 8 and edit 2995 which was first delivered on
tape 7. A patch to RUNOFF to fix the problem created by edit
2995 is also contained in this beware file.
14. (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 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:.
If these files are currently found in SYS: they must be copied
or moved to PAT:, DIS:, or INS:.
15. (tape 9) The ALGOL, COBOL, LINK and PASCAL Autopatch control
files redefine the local definition of SYS: to ensure the use
of provided Base Building Software items.
16. (tape 8) Users who will be autopatching COBOL or FORTRAN for
the first time MUST use two product-specific directories. Read
section 2.2 of the INSTAL.DOC file.
17. (tape 8) The TOPS-20 monitor and EXEC are now Autopatched by
complete REL library replacement rather then REL module
replacement. This change is transparent to the Autopatch user
except that the time and disk space required are MUCH less then
before. PEPB will 'patch' the REL libraries and MAKLIB is not
18. (tape 8) PEP and PEPB will report high edit levels on some
products (CHECKD and BASIC). These products are setting a bit
which is to be used by the next full release of the EXEC. The
current EXEC has been patched to ignore this bit. PEP and PEPB
will likewise be modified on a future tape.
19. (tape 8) Be sure to read the PAS2V1.B08 and T22V41.B08 beware
20. (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-2020-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-2020-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.
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.
21. (tape 7) Changes have been made to the GALAXY Patch & Build
control file. GALAXY now builds GLXLIB.REL properly. Be sure
that the GALV42.CTL file is restored into PAT: from the
installation (second) save-set on this tape.
22. (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
23. (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.
24. (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
25. (tape 7) The ALL.Ann file used to restore products from the
Autopatch tape must be submitted with at least a 30 minute time
26. (tape 7) Be sure to read the T22V41.B07 and UTKS41.B07 beware
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) Because of directory limitations, the creation and use
of Product-specific Patching Directories are MANDATORY. Read
section 2.2 of the INSTAL.DOC file.
29. (tape 6) The use of any of the Monitor/EXEC DDC files 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 GALV42.DDC and UTLV41.DDC
files are needed ONLY if you do not use one of the T22V41.DDC
30. (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.
31. (tape 6) BATCH time limits for FORTRAN, COBOL and GALAXY 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.
32. (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
SORT be updated before COBOL. In order to apply all patches
correctly you must SUBMIT the Patch and Build Control file for
SORT before the COBOL Control file. The DBMS product requires
that FORTRAN and COBOL be built first. Do not INSTALL any
related products until all have been built.
33. (tape 6) Sites which Autopatch BASIC+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
34. (tape 6) Be sure to read the T22V41.B06 beware file.
35. (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.
36. (tape 5) The Autopatch build process for ALGOL, COBOL, DBMS,
FORTRAN and SORT redefines DSK:. It is MANDATORY that a
structure be specified when providing the directory
specifications during the initial SELECTion process.
37. (tape 5) The ALGOL Autopatch update process redefines the local
definition of SYS: to ensure the use of provided Base Building
38. (tape 4) The SELECTion of TOPS-20 Utilities requires that
CHECKD.EXE, 4-1-SETSPD.EXE, and 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.
39. (tape 4) When PEP is run, the connected directory must be PAT:.
40. (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)
4.0 FILE INDEX
Patch Set 020
README.020 Patch Set 020 Master Documentation File
TAP020.DIR Directory with Checksums of Patch Set 020
PAT220.DPD Patch Directory File for Patch Set 020
APEDIT.020 Autopatch Edit Report for tape 020
APEDIT.RPT Complete Autopatch Edit Report
LAP.DEF Logical Definition File for loading Autopatch tape
PATCLN.CMD Directory Cleanup Command File
UTILTY.UPD Utility checksum and version update file
B20CMA.R20 B20CMA.REL Patch File BASIC-PLUS-2-V2A
P2S1.C20 P2S1.BLI Patch File FORTRAN-20-V11
T2020.X20 T2020 .REL Patch File TOPS-20-2020-V4-1
TFRCOB.C20 TFRCOB.MAC Patch File TRAFFIC-20-V4
CREF.X20 CREF.MAC Patch File UTILITIES-V4-1
Base Building Software
ACTSYM.UNV CMD.REL FORDBM.REL GLXLIB.REL
GLXMAC.UNV HELPER.REL JOBDAT.REL JOBDAT.UNV
LINK.EXE MACREL.REL MACRO.EXE MACSYM.MAC
MACSYM.UNV MACTEN.UNV MAKLIB.EXE MONSYM.MAC
MONSYM.REL MONSYM.UNV ORNMAC.UNV OVRLAY.REL
PA1050.EXE QSRMAC.UNV SCAN.REL SCNMAC.UNV
SERCOD.UNV UUOSYM.UNV WILD.REL
5.0 PRODUCT DOCUMENTATION
Information on which edits are provided in the CURRENT (first) save-set
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 first
two save-sets, and the ALL.Ann file to restore all files for all
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 this tape and in the Autopatch Procedures/Reference Manual. The
Distribution Dumper Control files 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.
Product Dist. tape Dist. DDC
ALGOL-20-V1-2 BB-5471C-BM ALGV12.DDC
APLSF-20-V2 BB-5137E-BM APL2S2.DDC
BASIC-PLUS-2-V2A BB-5543F-BM B20V2A.DDC
COBOL-20-V12C BB-H506E-BM CBL12C.DDC
COBOL-REP-V12C BB-H506E-BM CBR12C.DDC
DBMS-V6-1 BB-4148F-BM DB2V61-CBL.DDC
FORTRAN-20-V11 BB-4157J-SM FTN211.DDC
FORTRAN-20-REP-V11 BB-4147J-SM FTN2X1.DDC
FTS-20-V1 BB-M251A-BM FTS201.DDC
GALAXY-20-V4-2 BB-D868E-BM) T22V41-SML.DDC
PASCAL-20-V1 BB-P557A-BM PAS2V1.DDC
SORT-20-V4D BB-H506E-BM CBL12C.DDC
TOPS-20-2020-V4-1 BB-D868E-BM) T22V41-SML.DDC
TRAFFIC-20-V4 BB-5372E-SM TFR2V4.DDC
UTILITIES-V4-1 BB-D868E-BM) T22V41-SML.DDC
* The SORT product may also be setup for Autopatching with the use of
the SRT24D.DDC file against the BB-4160G-BM 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 GALV42.DDC file and the UTILITIES product with UTLV41.DDC. These
files are only needed if you do not use one of the monitor DDC files.