Trailing-Edge
-
PDP-10 Archives
-
bb-bt99o-bb
-
readme.021
There are no other files named readme.021 in the archive.
1.0 INTRODUCTION
This is the twenty-first 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, 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: ANF10-V704, CUSTOMER-SUPPORTED-10-V704,
DECNET-10-V704, MCB-10-V704, MONITOR-10-V704, and MPE-10-V704.
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, COBOL-10-V12C, DBMS-10-V5A, DECNET-10-V704,
IBMCOM-10-ET-V4, IBMCOM-10-HASP-V1, 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,
Page 2
a product which was supported by previous tapes.
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*) The D8EINT.MAC file was missing from the 7.04 release.
It is provided on the second save-set of the CURRENT tape.
6. (*new*) 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.
7. (*new*) Be sure to delete files for the previous monitor from
the common patching area before installing the new monitor.
This includes *.FIL and D36PAR.*.
8. (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
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.
9. (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.
10. (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
Page 3
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.
11. (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.
12. (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.
13. (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
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.
14. (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.
15. (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.
Page 4
16. (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.
17. (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.
18. (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:.
19. (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.
20. (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
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:.
Page 5
21. (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.
22. (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.
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:
Page 6
23. (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.
24. (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.
25. (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.
26. (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
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.
27. (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.
28. (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.
29. (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,
Page 7
Customer-supported and Decnet options to the TOPS-10 Monitor
must be Autopatched before the Control file to build the
monitor is submitted.
30. (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.
31. (tape 4) When PEP is run, the default directory must be PAT:.
32. (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 021
File Description
README.021 Patch Set 021 Master Documentation File
TAP021.DIR Directory with Checksums of Patch Set 021
PAT121.DPD Patch Directory File for Patch Set 021
APEDIT.RPT Autopatch Edit Report
APEDIT.021 Autopatch Edit Report for Patch Set 021
PATCLN.CMD Directory Cleanup Command File
UTILTY.UPD Utility checksum and version update file
CDRSER.X21 CDRSER.MAC Patch FIle CUSTOMER-SUPPORTED-10-V704
DSXKON.X21 DSXKON.MAC
PLTSER.X21 PLTSER.MAC
Page 8
GNRCFN.C21 GNRCFN.BLI Patch File FORTRAN-10-V11
REVHST.C21 REVHST.MAC
DORTB.X21 DORTB .EXE
DORTC.X21 DORTC .EXE
DORTD.X21 DORTD .EXE
DORTE.X21 DORTE .EXE
DORTF.X21 DORTF .EXE
DORTG.X21 DORTG .EXE
DORTRA.X21 DORTRA.EXE
FORTB.X21 FORTB .EXE
FORTC.X21 FORTC .EXE
FORTD.X21 FORTD .EXE
FORTE.X21 FORTE .EXE
FORTF.X21 FORTF .EXE
FORTG.X21 FORTG .EXE
FORTRA.X21 FORTRA.EXE
SINGLE.X21 SINGLE.EXE
GLXMAC.X21 GLXMAC.MAC Patch File GALAXY-10-V704
GLXVER.X21 GLXVER.MAC
LPTMAC.X21 LPTMAC.MAC
LPTL03.X21 LPTL03.MAC
BATMAC.X21 BATMAC.MAC
APRSER.X21 APRSER.MAC Patch File MONITOR-10-V704
CD2SER.X21 CD2SER.MAC
COMCON.X21 COMCON.MAC
COMMON.X21 COMMON.MAC
CTXSER.X21 CTXSER.MAC
DCRSER.X21 DCRSER.MAC
DEVPRM.X21 DEVPRM.MAC
DLPSER.X21 DLPSER.MAC
DTESER.X21 DTESER.MAC
FILFND.X21 FILFND.MAC
LP2SER.X21 LPTSER.MAC
LPTSER.X21 LPTSER.MAC
NETPRM.X21 NETPRM.MAC
NETSER.X21 NETSER.MAC
PTYSER.X21 PTYSER.MAC
REFSTR.X21 REFSTR.MAC
SCHED1.X21 SCHED1.MAC
TAPUUO.X21 TAPUUO.MAC
UUOCON.X21 UUOCON.MAC
VMSER.X21 VMSER .MAC
Page 9
DDT.X21 DDT .MAC Patch File UTILITIES-10-V704
FAL.X21 FAL .MAC
LNKHST.X21 LNKHST.MAC
LNKCOR.X21 LNKCOR.MAC
LNKLOD.X21 LNKLOD.MAC
LNKNEW.X21 LNKNEW.MAC
RMS.X21 RMS .EXE
RMS.Y21 RMS .REL
RMSCOB.X21 RMSCOB.EXE
RMSUTL.X21 RMSUTL.EXE
RMSINT.X21 RMSINT.UNV
RMSSYM.X21 RMSSYM.LUS
SWIFIL.X21 SWIFIL.MAC
SWIL.X21 SWIL .MAC
SWISCN.X21 SWISCN.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 10
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 11
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