There is 1 other file named readme.019 in the archive. Click here to see a list.
This is the nineteenth Autopatch set. It contains patches for
ALGOL-10-V10B, ANF10-V703, APLSF-10-V2, COBOL-10-V12C,
CUSTOMER-SUPPORTED-10-V703, DECNET-10-V703, FORTRAN-10-V11,
GALAXY-10-V703, IBMCOM-10-ET-V4, IBMCOM-10-HASP-V1, MONITOR-10-V703,
MPE-10-V703, MS-EXE-10-V11, MS-SOURCES-10-V11, SORT-10-V4D,
TOPS-10-MCB-V703, and UTILITIES-10-V703. 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: ANF10-V23,
APL-10-V2, COBOL-10-V12B, DECNET-10-UTILITIES-V702,
FORTRAN-10-V6, FORTRAN-10-V7, FORTRAN-10-V10 GALAXY-10-V4-1,
GALAXY-10-V702, LINK-10-V5-1, MCB-10-V702, MPE-10-V702,
MS-10-V10, 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-MPE-V701A, TOPS-10-TSK-V701, UTILITIES-10-V701A, and
*NOTE* It is strongly suggested that you DESELECT any of these
products before proceeding with processing any currently
2. The following Autopatched product(s) do not have any new edits
delivered with this patch set: ALGOL-10-V10B, ANF-10-V703,
APLSF-10-V2, DBMS-10-V5A, IBMCOM-10-ET-V4, IBMCOM-10-HASP-V1,
MPE-10-V703, MS-EXE-10-V11, MS-SOURCES-10-V11, SORT-10-V4D, and
3. 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.
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)
4. (*new*) 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.
5. (*new*) We have eliminated the product-specific BACKUP ccl
files. There are now two files. The ALL.P19 file will restore
files for all desired products from the CURRENT patch tape.
The ALL.A19 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.
6. (*new*) The QSRMAC file has the FTDQS switch on. In order to
build QUASAR with this switch on you must have the CHRFRM.REL
file which is in the first saveset as part of the NEBULA
7. (*new*) You may see checksum warnings on the DIL components.
An update to DIL was delivered on the CUSP Update Tape of July
'86. These warnings may be ignored. The new checksums are in
the UTL703.PDF file for customers who will be selecting the
product after putting up the Update tape.
8. (tape 18) An updated GALGEN.EXE is included on the first
save-set of the CURRENT tape. This file must be in the
patching directory (PAT:) before the GAL703.CTL file is
submitted. The GALGEN dialogue has changed. Because of this
and changes to PATH commands, be sure to use the revised .CTL
files for GALAXY in the second save-set. Make your edits to
GALAXY.CTL if you do not want to use the provided GALGEN
9. (tape 18) An update of NEBULA is provided in the first save-set
of the CURRENT tape.
NEBULA is a GALAXY component which transfers jobs from
specially-defined TOPS-10 output queues to output queues on
NEBULA Version 1(20) is included on this Autopatch tape to
provide support for the VAX/VMS Distributed Queuing Service
(DQS) Version 1.0 product. Earlier versions of NEBULA will not
work with this product.
However, NEBULA Version 1(20) will work with the VAX/VMS DQS
Version 1.0 product and the earlier, unsupported implementation
of the DQS protocol.
NEBULA is provided as an unsupported tool.
10. (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.
11. (tape 18) Be sure to read the GAL703.B18 Beware file.
12. (tape 17) Be sure to read the MON703.B17 beware file which
contains a late fix for IME stopcodes during tape reel
13. (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.
14. (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.
15. (tape 17) The MONGEN.X17 file is a copy of the MONGEN.X15 file
which was delivered on tape 15. The patch directory file on
that tape (PAT115.DPD) did not make any reference to the MONGEN
file. There are no new edits. Autopatching the MON703 product
for the first time will now properly update the MONGEN file.
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) The SMFILE.EXE file is included on tape 17. This
product is NOT currently defined as part of any Autopatchable
product. The file will be restored to DSKP:[7,6]. In order to
use the revised SMFILE product you should copy it to the system
18. (tape 17) There are updates available to several microcode
products. This tape provides new images of KLPCOD.ULD,
KNICOD.ULD and DXMCA.ADX. These files are used by the BOOT
build procedure in the UTILITIES Autopatch product.
19. (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
20. (tape 16) The DEC703.CTL file has been updated. The new
version is in the second save-set. The previous version did
not delete intermediate sources. This file will be restored
with the use of DEC703.Pnn.
21. (tape 16) There is a new module for the GALAXY-10-V703 product.
CNFHDW.MAC is in the second save-set of the current tape. Also
the second save-set contains an updated OPERAT.CTL file. These
files will be restored with the use of GAL703.Pnn.
22. (tape 16) The TOPS10.FIL file has been updated. The new
version is in the second save-set. The previous version
refered to SYS:EDDT.REL. Since we provide this file as part of
the Base Building Software set, and try to control the building
environment, the SYS: has been deleted. This file will be
restored with the use of MON703.Pnn.
23. (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
24. (tape 15) There was an error in the Utilities PDF file
(UTL703.PDF) which causes PEP to ignore the RMS.EXE file. This
tape delivers a new RMS.EXE file. The only way to succeed in
Autopatching Utilities is to obtain the corrected UTL703.PDF
file from the second save-set, DESELECT UTILITIES, SELECT
UTILITIES using the same logical definitions as before and then
to proceed with normal Autopatching of UTILITIES.
25. (tape 15) If you are using Autopatch to build more than one
monitor, particular attention is needed when defining PAT: to
PEP at SELECT time and in the BUILDS.PTH file. The common area
should be first in the PAT: list. A sample copy of a
BUILDS.PTH file for both a KS and KL monitor is provided in the
26. (tape 14) The version of BOOT supplied in the 7.03 distribution
kit will NOT load the Autopatch 7.03 monitor. BOOT version
3A(50) MUST be installed on the front-end file system BEFORE
you load the Autopatch monitor. This version of BOOT WILL load
the distributed 7.03 monitor; it will NOT load any monitor
prior to 7.02 without a patch to ONCE. In ONCE, at ONCE4C+3,
change the HRRZ T1,JOBFF to a MOVEI T1,MONORG.
27. (tape 14) The MONITOR-10-V703 build process is designed to be
as close as possible to the standard monitor build procedure.
One set of sources is maintained from which any flavor or
multiple monitors can be built. However, Autopatch will track
and move only one monitor.
You must include a path definition for PAT: in the BUILDS.PTH
file for proper operation of Autopatch. You must also have the
files created by START.CTL and GEN.CTL in the PAT: area before
selecting the MONITOR-10 product.
If your monitor is to include DECNET support, then you should
define DIS: when selecting the MONITOR-10 product to be a path
which includes the DIS: area for the DECNET-10 product. For
instance, DSKP:[7,6,MON],DSKP:[7,6,DECNET]. The following
files must be in PAT: when the monitor is Autopatched:
BUILDS.DCL BUILDS.PTH TOPS10.CCL TOPS10.CMD
It is expected that you will place a customized copy of
BUILDS.PTH in PAT:. Please observe the following rules.
First, you MUST specify directories other then PAT: for the
REL (FGEN) and EXE (BUILD) areas. The START.CTL procedure
creates a START.MIC file which deletes all entries in these
areas. Second, you should use explicit structures and PPNs
when defining areas for FGEN, BUILD and BASE:. Third, the
distributed START.CTL will delete all *.LOG files in BASE:. A
revised START.CTL with that command commented out can be found
in the second save-set of the Autopatch tape. Fourth, you must
include your definition for PAT: and DIS: in the definition
of CTLS: and MON:. Lastly, invoking START.CTL is required
before you can select MONITOR-10 since several files are
created. A minimum BUILDS.PTH for building a monitor can be
found in the second save-set of the Autopatch tape. The MPE,
DECNET and Customer Supported options to the TOPS-10 Monitor,
if used, must be autopatched before the Control file to build
the monitor is submitted.
28. (tape 14) When selecting the UTILITIES-10 product for
Autopatching you should include the DIS: for MONITOR-10 as
part of your path definition for DIS: for the UTILITIES-10
product. For example, DSKP:[7,6,CSP],DSKP:[7,6,MON].
29. (tape 14) The ANF10 product is NOT rebuilt by Autopatch. The
Autopatch process will update the supported sources in the DIS:
area. After the INSTALL command has been processed, you may
use the sources in DIS: to rebuild the product with procedures
which are appropriate for your site.
Also, there are 11 .P11 files that were omitted from the ANF
distribution. These files have been included on the second
save-set of this Autopatch tape. You must restore these files
to the DIS: area for ANF10 before ANF10 can be selected for
Autopatching. Use of ANF703.P15 will attempt to restore thes
files to DSKP:[7,6,ANF].
30. (tape 14) The UTILITIES-10 product now includes virtually all
products found on the CUSP tape. This includes 11-based
products. All output files must be 'seen' in INS: before
UTILITIES-10 can be selected. This includes components which
don't normally reside in SYS: such as BOOT.EXB and BOOTML.EXB.
Be sure to read the UTILITIES-10 section of the INSTAL.DOC file
in the second save-set for a complete list of files that must
be intially found in INS:.
31. (tape 14) The version of SOUP for Autopatch (SOUPR) has a
filename which conflicts with the original and still supported
SOUP product. The name of the SOUPR file in the second
save-set has been changed from COMPAR.MAC to COMPR.MAC.
If the COMPAR.MAC file has been previously restored to PAT:
then it must be deleted or the selection of UTLITIES-10-V703
will report a checksum mismatch and the wrong COMPAR.REL file
will be created.
32. (tape 14) There is support for LINK-V6 provided as part of the
UTILITIES-10-V703 product. Be sure that any obsolete versions
of the C1PLNK.CMD and C1POVL.CMD files are deleted. The new
ones should be in the DIS: for the UTILITIES product.
33. (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
34. (tape 11) A revised copy of TGHA.EXE is contained in the first
save-set on this tape. This copy is required for use of the
new MG20 memory.
35. (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:.
36. (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.
37. (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
IBMCOM HASP and ET
DDT11.EXE GALCNF.UNV MACDLX.EXE
If these files are currently found in SYS: they must be copied
or moved to PAT:, DIS:, or INS:.
38. (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.
39. (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.
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:
LINK-10-V5-1 is ready to be SETUP for patch and rebuild
Patches retrieved through patch tape 7
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:
40. (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.
41. (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.
42. (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.
43. (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.
44. (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.
45. (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
46. (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.
47. (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.
48. (tape 4) When PEP is run, the default directory must be PAT:.
49. (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 019
README.019 Patch Set 019 Master Documentation File
TAP019.DIR Directory with Checksums of Patch Set 019
PAT119.DPD Patch Directory File for Patch Set 019
APEDIT.RPT Autopatch Edit Report
APEDIT.019 Autopatch Edit Report for Patch Set 019
PATCLN.CMD Directory Cleanup Command File
UTILTY.UPD Utility checksum and version update file
COBVER.C19 COBVER.MAC Patch File COBOL-10-V12C
CBLIO.C19 CBLIO .MAC
CBL74.X19 CBL74 .EXE
68274.X19 68274 .EXE
D36COM.C19 D36COM.MAC Patch File DECNET-10-V703
LEXICA.C19 LEXICA.BLI Patch File FORTRAN-10-V11
P2S1 .C19 P2S1 .BLI
DORTB.X19 DORTB .EXE
DORTC.X19 DORTC .EXE
DORTD.X19 DORTD .EXE
DORTE.X19 DORTE .EXE
DORTF.X19 DORTF .EXE
DORTG.X19 DORTG .EXE
FORTB.X19 FORTB .EXE
FORTC.X19 FORTC .EXE
FORTD.X19 FORTD .EXE
FORTE.X19 FORTE .EXE
FORTF.X19 FORTF .EXE
FORTG.X19 FORTG .EXE
CNFORN.X19 CNFORN.MAC Patch File GALAXY-10-V703
ORION.X19 ORION .MAC
QUEUE.X19 QUEUE .MAC
COMDEV.X19 COMDEV.MAC Patch File MONITOR-10-V703
FILIO.X19 FILIO .MAC
KLSER.X19 KLSER .MAC
RTTRP.X19 RTTRP .MAC
VMSER.X19 VMSER .MAC
TX1KON.X19 TX1KON.MAC Patch File CUSTOMER-SUPPORTED-10-V703
BACKRS.X19 BACKRS.MAC Patch File UTILITIES-10-V703
DDT.X19 DDT .MAC
GLOB.X19 GLOB .MAC
MACRO.X19 MACRO .MAC
PLTIO.X19 PLTIO .MAC
WILD.X19 WILD .MAC
Base Building Software
ACTLIB.REL ACTSYM.UNV B361LB.REL BTSPRM.UNV C74SHR.REL
CATPRM.UNV CATTAB.REL COMPIL.EXE CREF.EXE D60JSY.MAC
D60JSY.REL D60UNV.MAC D60UNV.UNV DIRECT.EXE EDDT.REL
FORDBM.REL FGEN.HLP FILEX.EXE GALCNF.UNV GLOB.EXE
GLXINI.REL GLXLIB.REL GLXMAC.UNV HELPER.REL JOBDAT.MAC
JOBDAT.REL JOBDAT.UNV KLPCOD.ULD KNICOD.ULD LCPORN.REL
LCPTAB.REL LINK.EXE LNK999.EXE LNKERR.EXE LNKLOD.EXE
LNKMAP.EXE LNKOV1.EXE LNKOV2.EXE LNKSCN.EXE LNKXIT.EXE
MACRO.EXE MACSYM.MAC MACSYM.UNV MACTEN.UNV MAKLIB.EXE
MONGEN.EXE NCPTAB.REL OPRPAR.REL ORNMAC.UNV OVRLAY.REL
PATH.EXE PIP.EXE QSRMAC.UNV RMSINT.UNV SCAN.REL
SCNMAC.UNV SWIL.REL SWIL.UNV TECO.EXE TGHA.EXE
UFDPRM.UNV UFDSET.REL UUOSYM.MAC UUOSYM.REL UUOSYM.UNV
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
Below is a list which identifies these files and the Distribution tape
for each product.
Product Dist. tape Dist. CCL
ALGOL-10-V10B BB-D608D-SB ALG10B.CCL
ANF10-V703 BB-X140B-SB MON703.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
DBMS-10-V5A BB-D478D-BB DBMV5A.CCL
DECNET-10-V703 BB-X116B-SB DEC703.CCL
FORTRAN-10-V11 BB-D480G-SB FTN111.CCL
GALAXY-10-V703 BB-JF24A-BB GAL703.CCL
IBMCOM-10-ET-V4 BB-J992D-SB IETV04.CCL
MONITOR-10-V703 BB-X140B-SB MON703.CCL
MS-EXE-10-V11 BB-JF24A-BB --
SORT-10-V4D BB-H580E-SB CBL12C.CCL*
* 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