Trailing-Edge
-
PDP-10 Archives
-
bb-l014r-bm_tops20_v6_1_atpch_18
-
autopatch/instal.doc
There are 31 other files named instal.doc in the archive. Click here to see a list.
INSTAL.DOC for DECSYSTEM-20
Installation Information for Autopatch-10/20 V1.2
-------------------------------------------------
1.0 INTRODUCTION
This document describes the procedures necessary to set up your
DECSYSTEM-20 for patching software with Autopatch-10/20 V1.2. It
augments the information provided in chapter 2 of the Autopatch
Procedures/Reference Manual. This initialization operation is
required only once. After it has been completed, you will be able
to apply the patches distributed periodically in the Autopatch
Kits.
In order to set up your system for autopatching, you must create a
disk directory referred to as the autopatching directory. This
directory is used to patch and rebuild the software. In the
autopatching directory you must install some of the files supplied
on this patch tape as described in section 2 of this document.
In addition, you must also prepare a distribution directory for
each product you intend to autopatch. This operation is described
for each of the autopatchable products in section 3 of this
document.
For the DECSYSTEM-20 the following products are currently
autopatchable:
Version 1.2 of ALGOL-20
Version 2 of the APL products:
APL-20
APLSF-20
Version 2.1 of BASIC-PLUS-2
Version 13 of COBOL-20
Version 6.1 of DBMS-20
Version 4 of DECNET-20
Version 11 of FORTRAN-20
Version 1 of FTS-20
Version 5 of GALAXY-20
Version 2.1 of IBMCOM-20-ET
Page 2
Version 1.1 of IBMCOM-20-HASP
Version 11 of MS-SOURCES-20
Version 1 of PASCAL-20
Version 1.1 of PSI-20
Version 5 of SORT-20
Version 6.1 of TOPS-20 and utilities
Version 4 of TRAFFIC-20
Autopatch V1.2 is supported for applying only those patches
provided by Digital Equipment Corporation as part of an Autopatch
Kit. Furthermore, those patches are supported for distributed
(field-image) software or distributed software that has been
modified only by autopatching.
Page 3
2.0 INSTALLING AUTOPATCH
If you are not using an autopatching structure named AP20:, we
recommend that you make an entry in the LOGIN.CMD file and the
BATCH.CMD file that DEFINEs AP20: to be the structure you will be
using. If you do this, you will not need to edit the Dumper
Control Files used to set up the product distribution directories
or to retrieve patches. The LOGIN.CMD and BATCH.CMD files must be
on the PS: structure for the account you will be logging into to
SUBMIT these batch control files. We recommend that you use
<AUTOPATCH> as this directory name.
The second save-set of the patch tape contains tools and control
files that are used in the autopatching operation. A list of all
the files in this save-set is given in section 4 of this document.
Use the DUMPER program to restore from this save set to the
appropriate disk directories those files you need.
The following files should be installed in PS:<SUBSYS> or one of
the directories belonging to SYS:
PEP.EXE
PEPB.EXE
The following file should be installed in PS:<HELP> or one of the
directories belonging to HLP:
PEP.HLP
The following file should be installed in the disk directory you
have set up as the autopatching directory:
PEP201.PDF
In addition, a product-specific patch and build control file and a
product description file must be installed in the autopatching
directory for each product you intend to autopatch. These files
are in the installation save-set of the patch tape. See the last
section for a list of these files.
The installation save-set also contains batch control files to
assist you in setting up the product distribution directories.
These "Distribution DUMPER Control" files are intended to run under
batch. They issue a MOUNT request for the product distribution
tape and then run DUMPER to restore the required files. See the
last section for a list of these files.
For each product you intend to autopatch, you should install the
associated control files in the autopatching directory. For
example, if you intend to autopatch the APLSF-20-V2 product you
would install
APL2S2.CTL for APLSF-20 rebuild
APL2S2.PDF for Autopatch installation
APL2S2.DDC for preparing distribution directory
Page 4
in the autopatching directory.
Page 5
3.0 AUTOPATCH INSTALLATION OF SPECIFIC PRODUCTS
3.1 PREPARING FOR AUTOPATCHING ALGOL-20
Before preparing this product for Autopatching, you should install
the product on your system as described in the installation
documentation supplied on the product distribution tape. Unless
the product is correctly installed, you will not be able to SELECT
it for Autopatching.
The disk directory in which you have installed the executable files
for ALGOL-20 is referred to as the product installation directory.
In most cases this will be PS:<SUBSYS> or one of the directories
belonging to SYS:. This directory must contain the files:
ALGOL.EXE
ALGOTS.EXE
ALGLIB.REL
ALGDDT.HLP
ALGOL.HLP
*NOTE* The ALGOL distribution does not have a ALGOTS.EXE file but
does have a ALG310.EXE file. For Autopatching this file must be
named ALGOTS.EXE in the ALGOL Autopatch Installation directory
(INS:). Unless you COPY or RENAME to create the ALGOTS.EXE file
the PEP SELECT process for ALGOL-20-V1-2 will fail. An edit
supplied for the ALGOL compiler changes generated code to use the
new generic reference to the OTS.
The following file is required to build the ALGOL product. It must
be available either in the patching area (PAT:), the distribution
area (DIS:), or in INS:.
From the first save-set of the Autopatch tape
HELPER.REL
This file will be moved from the Autopatch tape when you use one of
the DUMPER control files described in the README file.
You will need to copy the following files from the ALGOL-20
distribution tape BB-5471C-BM into the disk directory you have set
up as the ALGOL-20 distribution directory.
From save-set "SOURCE files for ALGOL"
ALGCOD.MAC ALGCON.MAC ALGDDT.MAC ALGDEC.MAC
ALGEXP.MAC ALGFOR.MAC ALGFUN.MAC ALGLIB.MAC
ALGMAC.MAC ALGOTS.MAC ALGPRM.MAC ALGSER.MAC
ALGSTB.MAC ALGSTM.MAC ALGSYS.MAC ALGUTL.MAC
A batch control file to perform this operation has been included in
the installation save-set on this patch tape. This file will issue
Page 6
a mount request for the ALGOL-20 distribution tape and then restore
the appropriate files to the logical name DIS:. In this batch
file, DIS: is defined to be AP20:<AUTOPATCH.ALGOL>. If you wish
to use this control file, but are not using an AP20: structure,
you will want to include a 'DEF AP20: str:' command in the
BATCH.CMD file on the PS: structure for the LOGIN account from
which you will SUBMIT this control file. However, you will have to
edit this control file if you choose not to use <AUTOPATCH.ALGOL>
as the distribution directory.
To execute this control file, issue the following command:
@SUBMIT AP20:<AUTOPATCH>ALGV12.DDC
The Patch and Build control file for the re-build of this product
as well as the Autopatch product description file are supplied in
the Installation save-set on the Autopatch tape. See the last
section of this document for a list of these files. There is a
DUMPER control file provided in the first save-set which will
restore these files to the proper directory. See the README
documentation file in the first save-set for more information. The
Autopatch build process for ALGOL redefines DSK:. It is MANDATORY
that a structure be specified when providing the directory
specifications during the initial SELECTion process.
Page 7
3.2 PREPARING FOR AUTOPATCHING APL
Both APL-20 and APLSF-20 are autopatchable with Autopatch-10/20.
Before preparing these products for autopatching, they should be
installed on your system as described in the installation
documentation supplied on the APL distribution tapes.
To make the product autopatchable, some of the files from the
product distribution tape will have to be installed in the disk
directory that you have set up as the APL distribution directory.
Page 8
3.2.1 APL-20 -
The disk directory in which you have installed the executable files
for APL-20 is referred to as the product installation directory.
In most cases this will be PS:<SUBSYS> or one of the directories
belonging to SYS:. This directory must contain the files:
APL.EXE
GENBAS.EXE
You will need to copy the following files from the APL-20
distribution tape BB-5135E-BM into the disk directory you have set
up as the APL-20 distribution directory.
From save-set "REL LIBRARY FOR TOPS-20 APL-BASIC VERSION 2"
APLB22.REL
APLH22.REL
APLB22.LNK
APLH22.LNK
A batch control file to perform this operation has been included in
the installation save-set on this patch tape. This file will issue
a mount request for the APL-20 distribution tape and then restore
the appropriate files to the logical name DIS:. In this batch
file, DIS: is defined to be AP20:<AUTOPATCH.APL>. If you wish to
use this control file, but are not using an AP20: structure, you
will want to include a 'DEF AP20: str:' command in the BATCH.CMD
file on the PS: structure for the LOGIN account from which you
will SUBMIT this control file. However, you will have to edit this
control file if you choose not to use <AUTOPATCH.APL> as the
distribution directory.
To execute this control file, issue the following command:
@SUBMIT AP20:<AUTOPATCH>APL2B2.DDC
The Patch and Build control file for the re-build of this product
as well as the Autopatch product description file are supplied in
the Installation save-set on the Autopatch tape. See the last
section of this document for a list of these files. There is a
DUMPER control file provided in the first save-set which will
restore these files to the proper directory. See the README
documentation file in the first save-set for more information.
Page 9
3.2.2 APLSF-20 -
The disk directory in which you have installed the executable files
for APLSF-20 is referred to as the product installation directory.
In most cases this will be PS:<SUBSYS> or one of the directories
belonging to SYS:. This directory must contain the files:
APLSF.EXE
GENSF.EXE
APLTAP.EXE
You will need to copy the following files from the APLSF-20
distribution tape BB-5137E-BM into the disk directory you have set
up as the APLSF-20 distribution directory.
From save-set "REL LIBRARY FOR TOPS-20 APLSF VERSION 2"
APLS22.REL
APLG22.REL
APLW22.REL
APLS22.LNK
APLG22.LNK
APLW22.LNK
A batch control file to perform this operation has been included in
the installation save-set on this patch tape. This file will issue
a mount request for the APLSF-20 distribution tape and then restore
the appropriate files to the logical name DIS:. In this batch
file, DIS: is defined to be AP20:<AUTOPATCH.APL>. If you wish to
use this control file, but are not using an AP20: structure, you
will want to include a 'DEF AP20: str:' command in the BATCH.CMD
file on the PS: structure for the LOGIN account from which you
will SUBMIT this control file. However, you will have to edit this
control file if you choose not to use <AUTOPATCH.APL> as the
distribution directory.
To execute this control file, issue the following command:
@SUBMIT AP20:<AUTOPATCH>APL2S2.DDC
The Patch and Build control file for the re-build of this product
as well as the Autopatch product description file are supplied in
the Installation save-set on the Autopatch tape. See the last
section of this document for a list of these files. There is a
DUMPER control file provided in the first save-set which will
restore these files to the proper directory. See the README
documentation file in the first save-set for more information.
Page 10
3.3 PREPARING FOR AUTOPATCHING BASIC-PLUS-2
Before preparing this product for Autopatching, you should install
the product on your system as described in the installation
documentation supplied on the product distribution tape. Unless
the product is correctly installed, you will not be able to SELECT
it for Autopatching.
The disk directory in which you have installed the executable files
for BASIC-PLUS-2 is referred to as the product installation
directory. In most cases this will be PS:<SUBSYS> or one of the
directories belonging to SYS:. This directory must contain the
files:
BASIC.EXE
BASOTS.EXE
You will need to copy the following files from the BASIC-PLUS-2
distribution tape BB-5543F-BM into the disk directory you have set
up as the BASIC-PLUS-2 distribution directory.
From save-set "Autopatch files for BASIC PLUS 2 version 2.1(320)"
B20CMA.LNK
B20CMA.REL
B20OTA.LNK
B20OTA.REL
A batch control file to perform this operation has been included in
the installation save-set on this patch tape. This file will issue
a mount request for the BASIC-PLUS-2 distribution tape and then
restore the appropriate files to the logical name DIS:. In this
batch file, DIS: is defined to be AP20:<AUTOPATCH.BASIC>. If you
wish to use this control file, but are not using an AP20:
structure, you will want to include a 'DEF AP20: str:' command in
the BATCH.CMD file on the PS: structure for the LOGIN account from
which you will SUBMIT this control file. However, you will have to
edit this control file if you choose not to use <AUTOPATCH.BASIC>
as the distribution directory.
To execute this control file, issue the following command:
@SUBMIT AP20:<AUTOPATCH>B20V2A.DDC
The Patch and Build control file for the re-build of this product
as well as the Autopatch product description file are supplied in
the Installation save-set on the Autopatch tape. See the last
section of this document for a list of these files. There is a
DUMPER control file provided in the first save-set which will
restore these files to the proper directory. See the README
documentation file in the first save-set for more information.
Page 11
3.4 PREPARING FOR AUTOPATCHING COBOL-20
Before preparing this product for Autopatching, you should install
the product on your system as described in the installation
documentation supplied on the product distribution tape. Unless
the product is correctly installed, you will not be able to SELECT
it for Autopatching.
The disk directory in which you have installed the executable files
for COBOL-20 is referred to as the product installation directory.
In most cases this will be PS:<SUBSYS> or one of the directories
belonging to SYS:. This directory must contain the files:
COBDDT.REL
COBLIB.REL
COBOL.EXE
COBOTS-V13.EXE
CPYLIB.EXE
ISAM.EXE
RERUN.EXE
The COBOL V13 product may be patched via source file updates with
re-build and/or via encrypted EXE/REL file replacement. If you
desire to use encryption then KEY files must be retrieved from the
COBOL distribution tape. You will need to copy the following files
from the COBOL-20 V13 distribution tape BB-Z795A-SM into the disk
directory you have set up as the COBOL-20 distribution directory.
From save-set "SOURCE files for COBOL V13"
COBDDT.KEY
COBLIB.KEY
COBOL.KEY
COBOTS-V13.KEY
CPYLIB.KEY
ISAM.KEY
RERUN.KEY
If using COBOL-20 V13 with DBMS V6 or V6.1:
From save-set "BUILDING files for COBOL V13"
C8XSHR.REL
If you desire to Autopatch COBOL via updated sources the following
files are required to build the COBOL product. They must be
available either in the patching area (PAT:), the distribution area
(DIS:), or in INS:.
From the first save-set of the Autopatch tape
HELPER.REL MACREL.REL MACSYM.UNV MONSYM.UNV
UUOSYM.UNV
From the second save-set of the Autopatch tape
Page 12
CBBDEL.CMD CBLASM.CMD CBLB.CMD CBLD.CMD
CBLDB.CMD CBLDEL.CMD OTSASM.CMD OTSDEL.CMD
UNVDEL.CMD
These files will be moved from the Autopatch tape when you use one
of the DUMPER control files described in the README file.
You will need to copy the following files from the COBOL-20
distribution tape into the disk directory you have set up as the
COBOL-20 distribution directory.
From save-set "SOURCE files for COBOL V13"
ACCEPT.MAC ALBSTB.MAC ARGS.MAC ARITH.MAC
ASCEBC.MAC ASCSIX.MAC BISGEN.MAC BTREE.MAC
C8XSHR.MAC CANCEL.MAC CBLIO.MAC CDD.MAC
CHREQV.MAC CLEANC.MAC CLEAND.MAC CLEANT.MAC
CLRNAM.MAC CMLSYM.MAC *CMND20.MAC CMNGEN.MAC
CMP.MAC COBASM.MAC COBCOM.MAC COBDDT.MAC
COBFUN.MAC COBOLA.MAC COBOLB.MAC COBOLC.MAC
COBOLD.MAC COBOLE.MAC COBOLF.MAC COBOLG.MAC
COBOLK.MAC COBOLO.MAC COBSCN.MAC COBSRT.MAC
COBST.MAC COBTST.MAC COBVER.MAC COMUNI.MAC
*COPYRT.MAC COVRLY.MAC CPYLIB.MAC CTREE.MAC
DBDML.MAC DBDUM.MAC DBGETF.MAC DBSDCL.MAC
DBSTUB.MAC DEBSTB.MAC DIAGS.MAC DMLERR.MAC
DMLIO.MAC DMLVOK.MAC DSPFP.MAC DTREE.MAC
EASTBL.MAC EBCASC.MAC *EDIT.MAC EDITB.MAC
EXPGEN.MAC EXPON.MAC FIX.MAC FLGDF.MAC
FLOAT.MAC FTDEFS.MAC GC.MAC GD.MAC
GENDCL.MAC GETITM.MAC HANDAN.MAC IFGEN.MAC
IMPURE.MAC INSPEC.MAC INTERM.MAC IOGEN.MAC
IOTMP.MAC IOTMPU.MAC IPCGEN.MAC ISAM.MAC
KEY.MAC LBLERR.MAC LBLPRM.MAC LCM20.MAC
LCMIPC.MAC LIBREL.MAC LILOWS.MAC LINE.MAC
LSU.MAC MATGEN.MAC MESGEN.MAC MMANGR.MAC
MMANGU.MAC MOVE.MAC MOVGEN.MAC MSCGEN.MAC
NTBSTB.MAC NUBSTB.MAC NUM.MAC NUMEQV.MAC
OPCTAB.MAC P.MAC PC.MAC PD.MAC
PERF.MAC PMATCH.MAC PNZ.MAC PSCAN.MAC
PURE.MAC PUTCPY.MAC PUTLST.MAC PUTRES.MAC
REMOVL.MAC RERUN.MAC RESOLV.MAC RMSIO.MAC
RPWGEN.MAC SETEOF.MAC SETRET.MAC SIZ23.MAC
SIZE1.MAC SPAC.MAC SQUIRL.MAC SRTCRF.MAC
SRTGEN.MAC SRTTAB.MAC STRDCL.MAC STRGEN.MAC
STRING.MAC STRUNV.MAC SUBSCR.MAC TABLES.MAC
TODAY.MAC TRACED.MAC TRACER.MAC TRYNAM.MAC
USRDSP.MAC XFRGEN.MAC ZERC.MAC
SCHIO2.REL STRHI.REL
DBCSYM.UNV RMSINT.UNV
* because of a file name conflict with UTILITIES-20
Autopatch renames EDIT.MAC to be EDITC.MAC
Page 13
because of a file name conflict with FORTRAN-20
Autopatch renames CMND20.MAC to be CMND2C.MAC
because of a file name conflict with SORT-20
Autopatch renames COPYRT.MAC to be COPYRT.CBL
A batch control file to perform this operation has been included in
the installation save-set on this patch tape. This file will issue
a mount request for the COBOL-20 distribution tape and then restore
the appropriate files to the logical name DIS:. In this batch
file, DIS: is defined to be AP20:<AUTOPATCH.CBL13>. If you wish
to use this control file, but are not using an AP20: structure,
you will want to include a 'DEF AP20: str:' command in the
BATCH.CMD file on the PS: structure for the LOGIN account from
which you will SUBMIT this control file. However, you will have to
edit this control file if you choose not to use <AUTOPATCH.CBL13>
as the distribution directory.
To execute this control file, issue the following command:
@SUBMIT AP20:<AUTOPATCH>CBL13.DDC
for source file updating
@SUBMIT AP20:<AUTOPATCH>CBL13R.DDC
for EXE/REL replacement updating
The Patch and Build control file and utility command files for the
re-build of this product as well as the Autopatch product
description file are supplied in the Installation save-set on the
Autopatch tape. See the last section of this document for a list
of these files. There is a DUMPER control file provided in the
first save-set which will restore these files to the proper
directory. See the README documentation file in the first save-set
for more information. The Autopatch build process for COBOL
redefines DSK:. It is MANDATORY that a structure be specified when
providing the directory specifications during the initial SELECTion
process.
If you will be using DBMS-20 with COBOL-20 you will need to copy
the following files from the DBMS-20 distribution tape into the
disk directory you have set up as the COBOL-20 distribution
directory.
From save-set "DBMS SOURCE FILES"
DBMS V6.1 BB-4148F-BM
CMLSYM.MAC
DBDML.MAC
DBGETF.MAC
DBSDCL.MAC
DMLERR.MAC
DMLIO.MAC
DMLVOK.MAC
Page 14
GENDCL.MAC
STRDCL.MAC
STRUNV.MAC
COPYRT.MAC
A batch control file to perform this operation has been included in
the last save-set on this patch tape. This file will issue a mount
request for the DBMS-20 distribution tape and then restore the
appropriate files to the logical name DIS:. In this batch file,
DIS: is defined to be AP20:<AUTOPATCH.DBMS> and CDIS: is defined
to be AP20:<AUTOPATCH.CBL13>. If you wish to use this control
file, but are not using an AP20: structure, you will want to
include a 'DEF AP20: str:' command in the BATCH.CMD file on the
PS: structure for the LOGIN account from which you will SUBMIT
this control file. However, you will have to edit this control
file if you choose not to use <AUTOPATCH.DBMS> or <AUTOPATCH.CBL13>
as the distribution directory.
To execute this control file, issue the following command:
@SUBMIT AP20:<AUTOPATCH>DB2V61-CBL.DDC
If you are NOT autopatching the DBMS-20 product the selection
process for COBOL V13 will report checksum mismatches for the DBMS
components of the COBOL compiler. These messages can be ignored.
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.
Page 15
3.5 PREPARING FOR AUTOPATCHING DBMS-20 V6.1
Before preparing this product for Autopatching, you should install
the product on your system as described in the installation
documentation supplied on the product distribution tape. Unless
the product is correctly installed, you will not be able to SELECT
it for Autopatching.
The disk directory in which you have installed the executable files
for DBMS-20 is referred to as the product installation directory.
In most cases this will be PS:<SUBSYS> or one of the directories
belonging to SYS:. This directory must contain the files:
SCHEMA.EXE
DBMEND.EXE
DBINFO.EXE
DBMS.REL
FORDML.EXE
XDML.EXE
The following files are required to build the DBMS product. They
must be available either in the patching area (PAT:), the
distribution area (DIS:), or in INS:.
From the first save-set of the Autopatch tape
HELPER.REL SCAN.REL WILD.REL
These files will be moved from the Autopatch tape when you use one
of the DUMPER control files described in the README file.
You will need to copy the following files from the DBMS-20 V6.1
distribution tape BB-4148F-BM into the disk directory you have set
up as the DBMS-20 distribution directory.
From save-set "DBMS SOURCE FILES"
DBMEN2.REL GENME1.REL
DBS20.REL GENME2.REL
DBSANY.REL GENMS2.REL
DBSI20.REL INFANY.REL
DBSTUB.REL MNDANY.REL
DDL20.REL SCHIO2.REL
DDLANY.REL STRHI.REL
FMLANY.REL XDANY.REL
GENIO2.REL XDTB79.REL
DBCS13.CMD DBMEND.CMD
DBCS24.CMD FORDML.CMD
DBCS28.CMD SCHEMA.CMD
DBCS2F.CMD XDML.CMD
DBINFO.CMD
Page 16
XDBIND.FIX
A batch control file to perform this operation has been included in
the installation save-set on this patch tape. This file will issue
a mount request for the DBMS-20 V6.1 distribution tape and then
restore the appropriate files to the logical name DIS:. In this
batch file, DIS: is defined to be AP20:<AUTOPATCH.DBMS>.
If you wish to use this control file, but are not using an AP20:
structure, you will want to include a 'DEF AP20: str:' command in
the BATCH.CMD file on the PS: structure for the LOGIN account from
which you will SUBMIT this control file. However, you will have to
edit this control file if you choose not to use <AUTOPATCH.DBMS> as
the distribution directory.
To execute this control file, issue the following command:
@SUBMIT AP20:<AUTOPATCH>DB2V61.DDC
Revised copies of DBCS24.CMD, DBCS28.CMD and DBCS2F.CMD for the
DBMS-V6 product have been delivered on Autopatch tapes. Be sure
that these files are NOT in the common patching directory (PAT:).
If you will be using DBMS-20 with COBOL-20 you will need to copy
the following files from the DBMS-20 distribution tape into the
disk directory you have set up as the COBOL-20 distribution
directory.
From save-set "DBMS SOURCE FILES"
DBMS V6.1 BB-4148F-BM
CMLSYM.MAC
DBDML.MAC
DBGETF.MAC
DBSDCL.MAC
DMLERR.MAC
DMLIO.MAC
DMLVOK.MAC
GENDCL.MAC
STRDCL.MAC
STRUNV.MAC
COPYRT.MAC
A batch control file to perform this operation has been included in
the last save-set on this patch tape. This file will issue a mount
request for the DBMS-20 distribution tape and then restore the
appropriate files to the logical name DIS:. In this batch file,
DIS: is defined to be AP20:<AUTOPATCH.DBMS>. In the DDC file
which also prepares the COBOL-20 directory CDIS: is defined to be
AP20:<AUTOPATCH.CBL13>. If you wish to use this control file, but
are not using an AP20: structure, you will want to include a 'DEF
AP20: str:' command in the BATCH.CMD file on the PS: structure
for the LOGIN account from which you will SUBMIT this control file.
Page 17
However, you will have to edit this control file if you choose not
to use <AUTOPATCH.DBMS> or <AUTOPATCH.CBL13> as the distribution
directory.
To execute this control file, issue the following command:
@SUBMIT AP20:<AUTOPATCH>DB2V61-CBL.DDC
If you are NOT autopatching the DBMS-20 product the selection
process for COBOL V13 will report checksum mismatches for the DBMS
components of the COBOL compiler. These messages can be ignored.
The Patch and Build control file for the re-build of this product
as well as the Autopatch product description file are supplied in
the Installation save-set on the Autopatch tape. See the last
section of this document for a list of these files. There is a
DUMPER control file provided in the first save-set which will
restore these files to the proper directory. See the README
documentation file in the first save-set for more information. The
Autopatch build process for DBMS redefines DSK:. It is MANDATORY
that a structure be specified when providing the directory
specifications during the initial SELECTion process.
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.
Page 18
3.6 PREPARING FOR AUTOPATCHING DECNET-20
Before preparing this product for Autopatching, you MUST install
the product on your system as described in the DECNET-20
Installation Guide in Notebook 7 of the TOPS-20 Notebook set.
Unless the product is correctly installed, you will not be able to
SELECT it for Autopatching.
The disk directory in which you have installed the executable files
for DECNET-20 is referred to as the product installation directory.
In most cases this will be PS:<SUBSYS> or one of the directories
belonging to SYS:. This directory must contain the files:
CTERM-SERVER.EXE NETGEN.EXE
DNMAC.EXE NFT.EXE
DTEDMP.SYS NIPGEN.EXE
DTEMPS.SYS NMLT20.EXE
DTEMPT.SYS SETHOST.EXE
FAL.EXE TKB36.EXE
NCPTAB.REL VNP36.EXE
*.SYS
*.SYS is the front end system file with your node name
You will need to copy all of the files in the PS:<DN20> directory
from the DECNET-20 distribution tape BB-H240E-BM into the disk
directory you have set up as the DECNET-20 distribution directory.
These files should already exist in the PS:<DN20> directory as part
of the original DECNET-20 installation.
From the second save-set
NMLT20.KEY
From the third save-set
CEX.STB CEX.TSK CEXCOM.STB CEXCOM.TSK
DCP.STB DCP.TSK DMC.STB DMC.TSK
DMR.STB DMR.TSK DTE.STB DTE.TSK
DTR.STB DTR.TSK INI.STB INI.TSK
KDP.STB KDP.TSK MDT.STB MDT.STK
NDT.STB NDT.TSK NML.STB NML.TSK
NMS.STB NMS.TSK NMX.STB NMX.TSK
NS1.STB NS1.TSK NS2.STB NS2.TSK
NSP.STB NSP.TSK RSX11S.STB RSX11S.TSK
SC.STB SC.TSK SC1.STB SC1.TSK
SCX.STB SCX.TSK TLI.STB TLI.TSK
TOP.STB TOP.TSK XPE.STB XPE.TSK
XPT.STB XPT.TSK RSXMS.STB
CEXLIB.M11 CEXLLC.M11 DATML.M11 DCPDLC.M11
DMCDLC.M11 DMRDLC.M11 DTEDLC.M11 DTRLLC.M11
INILLC.M11 KDPDDM.M11 MCBLIB.M11 NMTAB.M11
NMXLLC.M11 NSTAB.M11 NSPLLC.M11 RSXLIB.M11
SCLLC.M11 SCXLLC.M11 TOPLLC.M11 XPTLLC.M11
Page 19
MCBLIB.OLB SYSLIB.OLB
From the fourth save-set
CEX.STB CEX.TSK CEXCOM.STB CEXCOM.TSK
SERVER.MAC NCPTAB.MAC FAL.MAC DAPSYM.MAC
DAPLIB.MAC DNCONN.MAC NFT.MAC SETHOS.MAC
A batch control file to retrieve these files has been included in
the installation save-set on this patch tape. This file will issue
a mount request for the DECNET-20 distribution tape and then
restore the third save-set to the logical name DIS:. In this batch
file, DIS: is defined to be AP20:<AUTOPATCH.DECNET>. If you wish
to use this control file, but are not using an AP20: structure,
you will want to include a 'DEF AP20: str:' command in the
BATCH.CMD file on the PS: structure for the LOGIN account from
which you will SUBMIT this control file. However, you will have to
edit this control file if you choose not to use <AUTOPATCH.DECNET>
as the distribution directory.
To execute this control file, issue the following command:
@SUBMIT AP20:<AUTOPATCH>DEC2V4.DDC
The DECNET-20 front end build also requires the following files
from the original installation:
CETAB.MAC
NETPAR.MAC
NMLACC.MAC
The above files are NOT on the release tape. They are created
during the required installation process. NMLACC.MAC is deleted
after a successful front end build to protect the Network
Management Access Control information it contains. Connect to the
directory in which your front end was built and do the following:
@NETGEN
NETGEN>RESTORE xxxxxx.CNF
;where xxxxxx is your front end node
;name. The configuration file (.CNF)
;was automatically saved when you did
;the original installation.
;If your site doesn't use Network Management Access Control
;skip the following 3 DEFINE commands
NETGEN>DEFINE EXECUTOR MANAGEMENT USER foo1
NETGEN>DEFINE EXECUTOR MANAGEMENT PASSWORD foo2
NETGEN>DEFINE EXECUTOR MANAGEMENT ACCOUNT foo2
NETGEN>FINISH
Copy CETAB.MAC and NETPAR.MAC into the DECNET-20 Autopatch
Page 20
distribution directory. If you wish the protection of having the
NMLACC.MAC file deleted after a successful build, rename it into
the directory you have set up as the DECNET-20 patching directory,
and the above procedure will be required before each Autopatch
update of DECNET-20. Otherwise, copy NMLACC.MAC into the DECNET-20
Autopatch distribution directory.
When SELECTing this product for Autopatching the PEP program will
ask for the nodename. Use the same name as was used during the
initial installation. If your product installation directory
(INS:) does not include the front end system image, usually
"nodename".SYS, then copy it into that directory.
Connect back to your original directory.
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:.
When SELECTing DECNET answer the node name with FOO.SYS.
The Patch and Build control file for the re-build of this product
as well as the Autopatch product description file are supplied in
the Installation save-set on the Autopatch tape. See the last
section of this document for a list of these files. There is a
DUMPER control file provided in the first save-set which will
restore these files to the proper directory. See the README
documentation in the first save-set for more information.
Page 21
3.7 PREPARING FOR AUTOPATCHING FORTRAN-20
Before preparing this product for Autopatching, you should install
the product on your system as described in the installation
documentation supplied on the product distribution tape. Unless
the product is correctly installed, you will not be able to SELECT
it for Autopatching.
The disk directory in which you have installed the executable files
for FORTRAN-20 is referred to as the product installation
directory. In most cases this will be PS:<SUBSYS> or one of the
directories belonging to SYS:. This directory must contain the
files:
FORTRA.EXE
FORO11.EXE
FORLIB.REL
FORDDT.REL
The FORTRAN V11 product may be patched via source file updates with
re-build and/or via encrypted EXE/REL file replacement. If you
desire to use encryption the KEY files must be retrieved from the
FORTRAN distribution tape. You will need to copy the following
files from the FORTRAN-20 V11 distribution tape BB-4157I-SM into
the disk directory you have set up as the FORTRAN-20 distribution
directory.
From the seventh save set
FORTRA.KEY
FORLIB.KEY
FORO11.KEY
FORDDT.KEY
If you are also using DBMS with FORTRAN you will need the
FORDBM.REL file from the first save set of the Autopatch tape.
If you desire to Autopatch FORTRAN via updated sources the
following files are required. They must be available either in the
patching area (PAT:), the distribution area (DIS:), or in INS:.
From the first save set of the Autopatch tape
GLXMAC.UNV HELPER.REL MACSYM.UNV MACTEN.UNV
MONSYM.UNV QSRMAC.UNV SCAN.REL SCNMAC.UNV
UUOSYM.UNV
These files will be moved from the Autopatch tape when you use on
of the DUMPER control files described in the README file.
You will need to copy the following files from the FORTRAN-20
distribution tape BB-4157I-SM into the disk directory you have set
up as the FORTRAN-20 distribution directory.
Page 22
From save set "Subsys files for FORTRAN V11"
DYNBOO.REL RMSINJ.UNV RMSZER.REL RTLZNM.REL
ZERBOO.REL
From save set "Ots and Debugger files for FORTRAN V11"
FDBML6.MAC FDDT .MAC FORBOT.MAC FORCHR.MAC
FORCNV.MAC FORCOM.MAC FORDBM.MAC FORDDT.MAC
FORDST.MAC FORDUM.MAC FORERR.MAC FORFMT.MAC
FORHST.MAC FORINI.MAC FORIO .MAC FORMEM.MAC
FORMSC.MAC FORMSG.MAC FORNML.MAC FOROP .MAC
FOROPN.MAC FOROTS.MAC FORPL2.MAC FORPRM.MAC
FORPSE.MAC FORRMS.MAC FORSRT.MAC FORXIT.MAC
F20REL.MAC MTHARG.MAC MTHCDX.MAC MTHCGX.MAC
MTHCNV.MAC MTHCPX.MAC MTHDBL.MAC MTHDUM.MAC
MTHGDB.MAC MTHMSG.MAC MTHPRM.MAC MTHSNG.MAC
MTHTRP.MAC M20REL.MAC
FORPRM.UNV MTHPRM.UNV
F20LIB.CCL F20OTS.CCL
DBCS2F.CMD
FORPL1.FOR
From save set "Compiler files for FORTRAN V11"
ACT0 .BLI ACT1 .BLI ALCBLO.BLI ARRXPN.BLI
ASHELP.BLI BLIO .BLI BUILD .BLI CANNON.BLI
CGDO .BLI CGEXPR.BLI CGSTMN.BLI CMPBLO.BLI
CMPLEX.BLI CODETA.BLI COMSUB.BLI DATAST.BLI
DEBUG .BLI DEFLT .BLI DEFPT .BLI DOALC .BLI
DOXPN .BLI DRIVER.BLI ERROR0.BLI ERROUT.BLI
EXPRES.BLI FAZ1 .BLI FIRST .BLI FMTLEX.BLI
FORMAT.BLI GCMNSB.BLI GLOBAL.BLI GNRCFN.BLI
GOPT2 .BLI GOPTIM.BLI GRAPH .BLI INOUT .BLI
INPT .BLI IOFLG .BLI IOPT .BLI LEFT72.BLI
LEFTFM.BLI LEXAID.BLI LEXCLA.BLI LEXICA.BLI
LEXNAM.BLI LEXSUP.BLI LISTNG.BLI LISTOU.BLI
MAIN .BLI MEMCMP.BLI MOVA .BLI NUMIO1.BLI
OPTAB .BLI OPTMAC.BLI OUTMOD.BLI OUTZ .BLI
P2S1 .BLI P2S2 .BLI P3R .BLI PEEPOP.BLI
PH2S .BLI PH3G .BLI PHA2 .BLI PHA3 .BLI
PNROPT.BLI REGAL2.BLI REGUTL.BLI RELBUF.BLI
REQREL.BLI SCAN0 .BLI SCNR .BLI SKSTMN.BLI
SRCA .BLI STA0 .BLI STA1 .BLI STA2 .BLI
STA3 .BLI STREGA.BLI TABLES.BLI TBL .BLI
TRACE1.BLI TSTR .BLI UNEND .BLI UTIL .BLI
VER5 .BLI VLTPPR.BLI
CMND20.MAC CNSTCM.MAC ERR3 .MAC ERRTB3.MAC
EXOSUP.MAC FLTGEN.MAC GFOPDF.MAC JOBD .MAC
OPGNTA.MAC QTAB1 .MAC REVHST.MAC
F72BNF.SYN FRMBNF.SYN
ALL20 .CMD BLD .CMD LEFT72.CMD LEFTFM.CMD
From save set "Fortran tools"
Page 23
BLIS10.ERR BLIS10.EXE BLIS10.HLP
A batch control file to perform this operation has been included in
the installation save set on this patch tape. This file will issue
a mount request for the FORTRAN-20 distribution tape and then
restore the appropriate files to the logical name DIS:. In this
batch file, DIS: is defined to be AP20:<AUTOPATCH.FORTRAN>. If
you wish to use this control file, but are not using an AP20:
structure, you will want to include a 'DEF AP20: str:' command in
the BATCH.CMD file on the PS: structure for the LOGIN account from
which you will SUBMIT this control file. However, you will have to
edit this control file if you choose not to use <AUTOPATCH.FORTRAN>
as the distribution directory.
To execute this control file, issue the following command:
@SUBMIT AP20:<AUTOPATCH.FTNPAT>FTN211.DDC
for source file updating
@SUBMIT AP20:<AUTOPATCH.FTNPAT>FTN2X1.DDC
for EXE/REL replacement updating
The Patch and Build control file and utility command files for the
re-build of this product as well as the Autopatch product
description file are supplied in the Installation Save-set on the
Autopatch tape. See the last section of this document for a list
of these files. There is a DUMPER control file provided in the
first Save-set which will restore these files to the proper
directory. See the README documentation file in the first Save-set
for more information. The Autopatch build process for FORTRAN
redefines DSK:. It is MANDATORY that a structure be specified when
providing the directory specifications during the initial SELECTion
process.
Page 24
3.8 PREPARING FOR AUTOPATCHING FTS-20
Before preparing this product for Autopatching, you should install
the product on your system as described in the installation
documentation supplied on the product distribution tape. Unless
the product is correctly installed, you will not be able to SELECT
it for Autopatching.
The disk directory in which you have installed the executable files
for FTS-20 is referred to as the product installation directory.
In most cases this will be PS:<SUBSYS> or one of the directories
belonging to SYS:. This directory must contain the files:
FTS.EXE
FTSLIB.REL
You will need to copy the following files from the FTS distribution
tape BB-M251A-BM into the disk directory you have set up as the
FTS-20 distribution directory.
From the second save-set
FTSLIB.REL
From the third save-set
FTS20.REL
A batch control file to perform this operation has been included in
the installation save-set on this patch tape. This file will issue
a mount request for the FTS-20 distribution tape and then restore
the appropriate files to the logical name DIS:. In this batch
file, DIS: is defined to be AP20:<AUTOPATCH.FTS>. If you wish to
use this control file, but are not using an AP20: structure, you
will want to include a 'DEF AP20: str:' command in the BATCH.CMD
file on the PS: structure for the LOGIN account from which you
will SUBMIT this control file. However, you will have to edit this
control file if you choose not to use <AUTOPATCH.FTS> as the
distribution directory.
To execute this control file, issue the following command:
@SUBMIT AP20:<AUTOPATCH>FTS201.DDC
Since there is some file/module set-up processing and some of the
files must be renamed, we recommend that you use the control file
to set up the directory.
The FTS product build also requires some files from the Autopatch
tape. The following files are put into the FTS patching directory
by the DUMPER Control Files which process the Autopatch Tape.
DAP2V1.REL
XPN2V1.REL
Page 25
The Patch and Build control file for the re-build of this product
as well as the Autopatch product description file are supplied in
the Installation save-set on the Autopatch tape. See the last
section of this document for a list of these files. There is a
DUMPER control file provided in the first save-set which will
restore these files to the proper directory. See the README
documentation file in the first save-set for more information.
Page 26
3.9 PREPARING FOR AUTOPATCHING GALAXY-20
The disk directory in which you have installed the executable files
for GALAXY-20 is referred to as the product installation directory.
In most cases this will be PS:<SUBSYS> or one of the directories
belonging to SYS:. This directory must contain the files:
BATCON.EXE ORION.EXE
CDRIVE.EXE PLEASE.EXE
GLXLIB.EXE QMANGR.EXE
GLXLIB.REL QUASAR.EXE
LPTSPL.EXE SPRINT.EXE
MOUNTR.EXE SPROUT.EXE
OPR.EXE
The following files are required to build the GALAXY product. They
must be available either in the patching area (PAT:), the
distribution area (DIS:), or in INS:.
From the first save-set of the Autopatch tape
ACTSYM.UNV MACREL.REL MACSYM.UNV MONSYM.UNV
These files will be moved from the Autopatch tape when you use one
of the DUMPER control files described in the README file.
You will need to copy the following files from a TOPS-20
distribution set into the disk directory you have set up as the
GALAXY-20 distribution directory.
TOPS-20 V6.1 Installation tape BB-H137E-BM
From save-set "SUBSYS FILES FOR TOPS-20 V6.1"
ARMAIL.REL
SERCOD.UNV
From save-set "GALAXY SUBSYS FILES FOR TOPS-20 V6.1"
NCPTAB.REL
TOPS-20 V6.1 Distribution tape BB-H138E-BM
From save-set "SOURCE FILES FOR TOPS-20 V6.1"
ARMAIL.MAC
From save-set "GALAXY SOURCES FOR TOPS-20 V6.1"
BATCON.MAC BATLOG.MAC BATMAC.MAC CDRIVE.MAC
D60JSY.MAC D60UNV.MAC GALCNF.MAC GLXCOM.MAC
GLXFIL.MAC GLXINI.MAC GLXINT.MAC GLXIPC.MAC
GLXKBD.MAC GLXLNK.MAC GLXMAC.MAC GLXMEM.MAC
GLXOTS.MAC GLXSCN.MAC GLXTXT.MAC GLXVER.MAC
Page 27
LPTSPL.MAC MOUNTR.MAC NURD.MAC OPR.MAC
OPRCMD.MAC OPRERR.MAC OPRLOG.MAC OPRNET.MAC
OPRPAR.MAC OPRQSR.MAC ORION.MAC ORNMAC.MAC
PLEASE.MAC QMANGR.MAC QSRADM.MAC QSRDSP.MAC
QSRFSS.MAC QSRIPC.MAC QSRMAC.MAC QSRMDA.MAC
QSRMEM.MAC QSRNET.MAC QSRQUE.MAC QSRSCH.MAC
QSRT20.MAC QUASAR.MAC SPRINT.MAC SPROUT.MAC
A batch control file to perform this operation has been included in
the installation save-set on this patch tape. This file will issue
mount requests for the TOPS-20 distribution tapes and then restore
the appropriate files to the logical name DIS:. In this batch
file, DIS: is defined to be AP20:<AUTOPATCH.GALAXY>. If you wish
to use this control file, but are not using an AP20: structure,
you will want to include a 'DEF AP20: str:' command in the
BATCH.CMD file on the PS: structure for the LOGIN account from
which you will SUBMIT this control file. However, you will have to
edit this control file if you choose not to use <AUTOPATCH.GALAXY>
as the distribution directory.
To execute this control file, issue the following command:
@SUBMIT AP20:<AUTOPATCH>GALV50.DDC
If you use any of the TOPS-20 Monitor/EXEC DDC files, the required
files for this product will be loaded into a common distribution
directory which must be specified when selecting this product for
autopatching.
The Patch and Build control file for the re-build of this product
as well as the Autopatch product description file are supplied in
the Installation save-set on the Autopatch tape. See the last
section of this document for a list of these files. There is a
DUMPER control file provided in the first save-set which will
restore these files to the proper directory. See the README
documentation file in the first save-set for more information.
Page 28
3.10 PREPARING FOR AUTOPATCHING IBMCOM-20
Before preparing this product for Autopatching, you should install
the product on your system as described in the installation
documentation supplied on the product distribution tape. Unless
the product is correctly installed, you will not be able to SELECT
it for Autopatching.
The disk directory in which you have installed the executable files
for IBMCOM-20 is referred to as the product installation directory.
In most cases this will be PS:<SUBSYS> or one of the directories
belonging to SYS:. This directory must contain the files:
HASP only
D6TK3.BIN D6TKH.BIN
D6TK3.EXE D6TKH.EXE
D6TK3D.BIN D6TKHD.BIN
D6TK3D.EXE D6TKHD.EXE
IBMSPL.EXE
D60SPD.EXE
The following files are required to build the IBMCOM product. They
must be available either in the patching area (PAT:), the
distribution area (DIS:), or in INS:.
From the first save-set of the Autopatch tape
ACTSYM.UNV GLXINI.REL GLXMAC.UNV HELPER.REL
JOBDAT.UNV MACSYM.UNV MACTEN.UNV MONSYM.UNV
ORNMAC.UNV QSRMAC.UNV UUOSYM.UNV
These files will be moved from the Autopatch tape when you use one
of the DUMPER control files described in the README file. The
DUMPER control files will also load the PROD.P11 file from the
Autopatch tape into the same names as assumed below for the DIS:
product distribution area.
From a previous GALAXY Autopatch build or GALAXY Installation
GALCNF.UNV D60JSY.MAC D60UNV.MAC
You will need to copy the following files from the TOPS-20 IBMCOM
distribution tape BB-D351C-SM (ET) or BB-J724B-SM (HASP) into the
disk directory you have set up as the IBMCOM-20 distribution
directory.
HASP only
20TK3.P11 20TKH.P11
C11SIM.MAC
CHK60.P11
D60SPD.MAC
DEBUG.P11
Page 29
HBSC.P11
IBMMAC.MAC
IBMPAT.MAC
IBMSPL.MAC
IBMUSR.MAC
INIT.P11
INIT1.P11
INIT2.P11
LINDRV.P11
MACROS.P11
MDCODE.P11
MININT.P11
MSGHDL.P11
QUEING.P11
S60.P11
STGMAN.P11
TRNTAB.P11
XDEFIN.P11
XDTE10.P11
XDISPA.P11
XL3780.P11
XTENCM.P11
An indirect command file to perform this operation has been
included in the installation save-set on this patch tape. This
file will issue mount requests for the IBMCOM-20 distribution tapes
and then restore the appropriate files to the logical name DIS:.
In this batch file, DIS: is defined to be AP20:<AUTOPATCH.IBMET>
or AP20:<AUTOPATCH.IBMHSP>. If you wish to use this control file,
but are not using an AP20: structure, you will want to include a
'DEF AP20: str:' command in the BATCH.CMD file on the PS:
structure for the LOGIN account from which you will SUBMIT this
control file. However, you will have to edit this control file if
you choose not to use the supplied defaults as the distribution
directory.
To use this command file, issue the following commands:
@SUBMIT AP20:<AUTOPATCH>IETV21.DDC for IBMCOM-20-ET-V2-1
or
@SUBMIT AP20:<AUTOPATCH>IHSV11.DDC for IBMCOM-20-HASP-V1-1
The PROD.P11 file is included on the Autopatch tape. The IETV21
and IHSV11 DUMPER command files to process the Autopatch tape will
copy the PROD.P11 file to the default distribution directory. This
must be done before the IBMCOM products will be able to be
SELECTed.
The Patch and Build control file for the re-build of this product
as well as the Autopatch product description file are supplied in
the Installation save-set on the Autopatch tape. See the last
section of this document for a list of these files. There is a
DUMPER command file provided in the first save-set which will
Page 30
restore these files to the proper directory. See the README
documentation file in the first save-set for more information.
Page 31
3.11 PREPARING FOR AUTOPATCHING MS-SOURCES-20
You will need to copy the following files from the TOPS-20 UPDATE
TAPE BB-JF18A-BM into the disk directory you have set up as the
MS-SOURCES-20 distribution directory.
From save-set "SOURCE files for Tops-20 V6.1 Update tape"
ARMAIL.MAC MS.MAC MSCNFG.MAC MSDLVR.MAC
MSDSPL.MAC MSFIL.MAC MSGUSR.MAC MSHOST.MAC
MSLCL.MAC MSMCMD.MAC MSNET.MAC MSSEQ.MAC
MSTXT.MAC MSUNV.MAC MSUTL.MAC MSUUO.MAC
MSVER.MAC CPYRYT.MAC SENVAX.MAC LISVAX.MAC
SMTSEN.MAC SMTLIS.MAC MXNT20.MAC NETTAB.MAC
MXVER.MAC MXNLIB.REQ M20TYP.REQ MXPORT.REQ
MXNSTR.REQ MXNTLB.REQ MXDBUG.REQ MXNRSP.REQ
MXNCOM.REQ MXNCMI.REQ MXNRCH.REQ MXINI.REQ
MXLIB.REQ MXCNDT.REQ MXQMAN.REQ MXUFIL.REQ
MXERR.REQ MXLCL.REQ TBL.REQ MXNT20.R36
BLT.R36 MONSYM.L36 MXJLNK.L36 MXLIB.L36
MXNLIB.L36 TBL.L36 M20INT.BLI M20INT.REL
MXNMEM.BLI MXNMEM.REL MXNQUE.BLI MXNQUE.REL
MXNTBL.BLI MXNTBL.REL MXNTXT.BLI MXNTXT.REL
MXDATA.BLI MXDATA.REL MXHOST.BLI MXHOST.REL
MXLCL.BLI MXLCL.REL MXQMAN.BLI MXQMAN.REL
MXUFIL.BLI MXUFIL.REL TBL.BLI TBL.REL
MXERR.BLI MXERR.REL MXDCNT.BLI MXDCNT.REL
MXNSKD.BLI MXNSKD.REL MXNPAG.B36 MXNPAG.REL
NEWT20.B36 M20IPC.B36 M20IPC.REL MXNNET.B36
MXNNET.REL NETT20.B36
A batch control file to perform this operation has been included in
the installation save-set on this patch tape. This file will issue
a mount request for the TOPS-20 UPDATE TAPE and then restore the
appropriate files to the logical name DIS:. In this batch file,
DIS: is defined to be AP20:<AUTOPATCH.MS>. If you wish to use
this control file, but are not using an AP20: structure, you will
want to include a 'DEF AP20: str:' command in the BATCH.CMD file
on the PS: structure for the LOGIN account from which you will
SUBMIT this control file. However, you will have to edit this
control file if you choose not to use <AUTOPATCH.MS> as the
distribution directory.
To execute this control file, issue the following command:
@SUBMIT AP20:<AUTOPATCH>MS211S.DDC
The Patch and Build control file for the re-build of this product
as well as the Autopatch product description file are supplied in
the Installation save-set on the Autopatch tape. See the last
section of this document for a list of these files. There is a
DUMPER control file provided in the first save-set which will
restore these files to the proper directory. See the README
Page 32
documentation file in the first save-set for more information.
3.12 PREPARING FOR AUTOPATCHING PASCAL-20
Before preparing this product for Autopatching, you should install
the product on your system as described in the installation
documentation supplied on the product distribution tape. Unless
the product is correctly installed, you will not be able to SELECT
it for Autopatching.
The disk directory in which you have installed the executable files
for PASCAL-20 is referred to as the product installation directory.
In most cases this will be PS:<SUBSYS> or one of the directories
belonging to SYS:. This directory must contain the files:
PASCAL.EXE
PASDDT.REL
PASLIB.REL
PASOTS.EXE
The following files are required to build the PASCAL product. They
must be available either in the patching area (PAT:), the
distribution area (DIS:), or in INS:.
From the first save-set of the Autopatch tape
CMD.REL MACREL.REL
These files will be moved from the Autopatch tape when you use one
of the DUMPER control files described in the README file.
You will need to copy the following files from the PASCAL
distribution tape BB-P557A-BM into the disk directory you have set
up as the PASCAL-20 distribution directory.
From the fourth save-set
PAS2D1.REL
PAS2L1.REL
PAS2O1.REL
From the fifth save-set
HSPACE.REL
PAS2C1.REL
A batch control file to perform this operation has been included in
the installation save-set on this patch tape. This file will issue
a mount request for the PASCAL-20 distribution tape and then
restore the appropriate files to the logical name DIS:. In this
batch file, DIS: is defined to be AP20:<AUTOPATCH.PASCAL>. If you
wish to use this control file, but are not using an AP20:
structure, you will want to include a 'DEF AP20: str:' command in
Page 33
the BATCH.CMD file on the PS: structure for the LOGIN account from
which you will SUBMIT this control file. However, you will have to
edit this control file if you choose not to use <AUTOPATCH.PASCAL>
as the distribution directory.
To execute this control file, issue the following command:
@SUBMIT AP20:<AUTOPATCH>PAS2V1.DDC
The Patch and Build control file for the re-build of this product
as well as the Autopatch product description file are supplied in
the Installation save-set on the Autopatch tape. See the last
section of this document for a list of these files. There is a
DUMPER control file provided in the first save-set which will
restore these files to the proper directory. See the README
documentation file in the first save-set for more information.
Page 34
3.13 PREPARING FOR AUTOPATCHING PSI-20 V1.1
Before preparing this product for Autopatching, you should install
the product on your system as described in the installation
documentation supplied on the product distribution tape. Unless
the product is correctly installed, you will not be able to SELECT
it for Autopatching.
This product is very closely related to the DECNET-20-V4 product.
In fact, there are many common modules. We have designed the
Autopatch process for PSI to use part of the Autopatch process for
DECNET. You should read and follow the instructions for 'PREPARING
FOR AUTOPATCHING DECNET-20 V4'. DO NOT, however, SELECT DECNET-20
for Autopatching. The PSI products include the DECNET products and
you will be Autopatching the complete product set when you
Autopatch PSI.
The disk directory in which you have installed the executable files
for PSI-20 is referred to as the product installation directory.
In most cases this will be PS:<SUBSYS> or one of the directories
belonging to SYS:. In addition to the files listed in the DECNET
section of this document, this directory must contain the files:
PSITST.EXE X25GAF.REL X25GAM.REL X25GEN.EXE
X29SRV.EXE
*.SYS
where * is the desired node name for your system and must match
your response to the node name question which is asked when
SELECTing PSI for Autopatching.
In addition to the files listed in the DECNET section of this
document, you will need to copy the following files from the PSI-20
V1.1 distribution tape BB-W661B-BM into the disk directory you have
set up as the DECNET-20 distribution directory.
From the third save-set
FLN.STB FLN.TSK FLP.STB FLP.TSK
GAN.STB GAN.TSK GAT.STB GAT.TSK
NML.STB NML.TSK PLE.STB PLE.TSK
PLN.STB PLN.TSK PLP.STB PLP.TSK
FLPDLC.M11 GATLLC.M11 PLPLLC.M11
Note that the NML.STB and NML.TSK files on the PSI distribution are
different from the ones on the DECNET-20 distribution.
A batch control file to perform this operation has been included in
the installation save-set on this patch tape. This file will issue
a mount request for the PSI-20 distribution tape and then restore
the appropriate files to the logical name DIS:. In this batch
file, DIS: is defined to be AP20:<AUTOPATCH.DECNET>. If you wish
to use this control file, but are not using an AP20: structure,
you will want to include a 'DEF AP20: str:' command in the
BATCH.CMD file on the PS: structure for the LOGIN account from
Page 35
which you will SUBMIT this control file. However, you will have to
edit this control file if you choose not to use <AUTOPATCH.DECNET>
as the distribution directory.
To execute this control file, issue the following command:
@SUBMIT AP20:<AUTOPATCH>PSI.DDC
Remember to FIRST use the DEC2V4.DDC file as described in the
DECNET-20 section of this document.
The Patch and Build control file for the re-build of this product
as well as the Autopatch product description file are supplied in
the Installation save-set on the Autopatch tape. See the last
section of this document for a list of these files. There is a
DUMPER control file provided in the first save-set which will
restore these files to the proper directory. See the README
documentation file in the first save-set for more information.
Page 36
3.14 PREPARING FOR AUTOPATCHING SORT-20
Before preparing this product for Autopatching, you should install
the product on your system as described in the installation
documentation supplied on the product distribution tape. Unless
the product is correctly installed, you will not be able to SELECT
it for Autopatching.
The disk directory in which you have installed the executable files
for SORT-20 is referred to as the product installation directory.
In most cases this will be PS:<SUBSYS> or one of the directories
belonging to SYS:. This directory must contain the files:
SORT.EXE
The SORT V5 product may be patched via source file updates with
re-build and/or via encrypted EXE/REL file replacement. If you
desire to use encryption then KEY files must be retrieved from the
SORT or COBOL distribution tape. You will need to copy the
following files from the SORT-20 V5 distribution tape BB-Z761A-SM
or the COBOL-20 V13 distribution tape BB-Z795A-SM into the disk
directory you have set up as the SORT-20 distribution directory.
From save-set "SOURCE files for SORT V5"
SORT.KEY
If you desire to Autopatch SORT via updated sources the following
files are required to build the SORT product. They must be
available either in the patching area (PAT:), the distribution area
(DIS:), or in INS:.
From the first save-set of the Autopatch tape
MACTEN.UNV MACSYM.UNV MONSYM.UNV
These files will be moved from the Autopatch tape when you use one
of the DUMPER control files described in the README file.
You will need to copy the following files from the SORT-20
distribution tape or from the COBOL-20 distribution tape into the
disk directory you have set up as the SORT-20 distribution
directory.
From save-set "SOURCE files for SORT V5"
COPYRT.MAC
COPYRT.TXT
SORT.MAC
SRTCBL.MAC
SRTCER.MAC
SRTCMD.MAC
SRTCMP.MAC
SRTDTR.MAC
Page 37
SRTFLT.MAC
SRTJSS.MAC
SRTPRM.MAC
SRTSTA.MAC
From save-set "BUILDING files for SORT V5"
FTDEFS.UNV
A batch control file to perform this operation has been included in
the installation save-set on this patch tape. This file will issue
a mount request for the SORT-20 distribution tape and then restore
the appropriate files to the logical name DIS:. In this batch
file, DIS: is defined to be AP20:<AUTOPATCH.SRTV5>. If you wish
to use this control file, but are not using an AP20: structure,
you will want to include a 'DEF AP20: str:' command in the
BATCH.CMD file on the PS: structure for the LOGIN account from
which you will SUBMIT this control file. However, you will have to
edit this control file if you choose not to use <AUTOPATCH.SRTV5>
as the distribution directory.
To execute this control file, issue the following command:
@SUBMIT AP20:<AUTOPATCH>SRTV5.DDC
for source file patching from the SORT tape
@SUBMIT AP20:<AUTOPATCH>SRTV5R.DDC
for replacement patching from the SORT tape
@SUBMIT AP20:<AUTOPATCH>CBL13.DDC
for source file patching from the COBOL tape
@SUBMIT AP20:<AUTOPATCH>CBL13R.DDC
for replacement patching from the COBOL tape
The use of one of the first two DDC files is only required if you
do not have the COBOL distribution tape. Use of either of the last
two DDC files will load files into both the SORT and COBOL
distribution areas.
The Patch and Build control file for the re-build of this product
as well as the Autopatch product description file are supplied in
the Installation save-set on the Autopatch tape. See the last
section of this document for a list of these files. There is a
DUMPER control file provided in the first save-set which will
restore these files to the proper directory. See the README
documentation file in the first save-set for more information. The
Autopatch build process for SORT redefines DSK:. It is MANDATORY
that a structure be specified when providing the directory
specifications during the initial SELECTion process.
Page 38
3.15 PREPARING FOR AUTOPATCHING TOPS-20
The monitor and EXEC for all supported hardware configurations are
autopatchable with Autopatch-10/20. Before preparing TOPS-20 for
autopatching, the monitor and EXEC should be installed on your
system as described in the installation documentation for TOPS-20.
The directory PS:<SYSTEM> in which you have installed the
executable files for the monitor and EXEC is referred to as the
installation directory. This directory must contain the files:
MONITR.EXE
EXEC.EXE
BUGSTRINGS.TXT
The following files are required to build the TOPS-20 product.
They must be available either in the patching area (PAT:), the
distribution area (DIS:), or in INS:.
From the first save-set of the Autopatch tape
D36PAR.UNV GLOBS.UNV MACREL.REL MACSYM.UNV
MONSYM.REL MONSYM.UNV PHYPAR.UNV SCAPAR.UNV
These files will be moved from the Autopatch tape when you use one
of the DUMPER control files described in the README file.
To make the product autopatchable, some of the files from the
product distribution tape will have to be installed in the disk
directory that you have set up as the TOPS-20 product distribution
directory.
Page 39
3.15.1 TOPS-20-2060 -
You will need to copy the following files from the TOPS-20 2060
installation tape BB-H137E-BM and the distribution tape BB-H138E-BM
into the disk directory you have set up as the TOPS-20-2060-V6-1
distribution directory.
From save-set "Subsys files for TOPS-20 V6.1"
of the Installation tape
LDINIT.REL PROLOG.UNV SERCOD.UNV
From save-set "Sources for TOPS-20 V6.1"
of the Distribution tape
EXECC0.REL PARAMS.MAC STG.MAC SYSFLG.MAC
LN2061.REL T20EX6.REL VERSIO.MAC
NAMAM0.MAC PARAM0.MAC
BIG monitor N60BIG.MAC P60BIG.MAC
MAXIMUM monitor N60MAX.MAC P60MAX.MAC
A batch control file to perform this operation has been included in
the installation save-set on this patch tape. This file will issue
mount requests for the TOPS-20 tapes and then restore the
appropriate files to the logical name DIS:. In this control file,
DIS: is defined to be AP20:<AUTOPATCH.TOPS-20>. If you wish to
use this control file, but are not using an AP20: structure, you
will want to include a 'DEF AP20: str:' command in the BATCH.CMD
file on the PS: structure for the LOGIN account from which you
will SUBMIT this control file. However, you will have to edit this
control file if you choose not to use <AUTOPATCH.TOPS-20> as the
distribution directory. After creating the product distribution
directory, submit the required control file as a batch job.
@SUBMIT AP20:<AUTOPATCH>T26V61-BIG.DDC for BIG monitor
@SUBMIT AP20:<AUTOPATCH>T26V61-MAX.DDC for MAX monitor
Since there are a number of files involved and some of the files
must be renamed, we recommend that you use the control file to set
up the directory.
The Patch and Build control file for the re-build of this product
as well as the Autopatch product description file are supplied in
the Installation save-set on the Autopatch tape. See the last
section of this document for a list of these files. There is a
DUMPER control file provided in the first save-set which will
restore these files to the proper directory. See the README
documentation file in the first save-set for more information.
Page 40
3.15.2 TOPS-20-TCPIP -
You will need to copy the following files from the TOPS-20 TCPIP
distribution tape BB-EV83A-BM into the disk directory you have set
up as the TOPS-20-TCPIP-V6-1 distribution directory.
From save-set "SOURCE FILES FOR TCP/IP-20 V4.0 UTILITIES AND TOOLS"
FTP1.MAC FTP2S.MAC FTP4.MAC FTPSRT.MAC
HSTNAM.MAC MAISER.MAC MMAILR.MAC MMLBX.MAC
RELAY.MAC SMTPSV.MAC SNDDEF.MAC SNDMSG.MAC
TCPSIM.MAC
LNKANI.CCL
T20AN.REL T20AN.KEY
NAMAM0.MAC PARAM0.MAC ANLNK.CCL
BIG monitor ANNBIG.MAC ANPBIG.MAC LNKANS.CCL
DCN monitor ANNDCN.MAC ANPDCN.MAC LNKAND.CCL
MAXIMUM monitor ANNMAX.MAC ANPMAX.MAC LNKANM.CCL
A batch control file to perform this operation has been included in
the installation save-set on this patch tape. This file will issue
mount requests for the TOPS-20 and TCP/IP tapes and then restore
the appropriate files to the logical name DIS:. In this control
file, DIS: is defined to be AP20:<AUTOPATCH.TOPS-20>. If you wish
to use this control file, but are not using an AP20: structure,
you will want to include a 'DEF AP20: str:' command in the
BATCH.CMD file on the PS: structure for the LOGIN account from
which you will SUBMIT this control file. However, you will have to
edit this control file if you choose not to use <AUTOPATCH.TOPS-20>
as the distribution directory. After creating the product
distribution directory, submit the required control file as a batch
job.
@SUBMIT AP20:<AUTOPATCH>T26A61-BIG.DDC for BIG monitor
@SUBMIT AP20:<AUTOPATCH>T26A61-DCN.DDC for DCN monitor
@SUBMIT AP20:<AUTOPATCH>T26A61-MAX.DDC for MAX monitor
Since there are a number of files involved and some of the files
must be renamed, we recommend that you use the control file to set
up the directory.
The Patch and Build control file for the re-build of this product
as well as the Autopatch product description file are supplied in
the Installation save-set on the Autopatch tape. See the last
section of this document for a list of these files. There is a
DUMPER control file provided in the first save-set which will
restore these files to the proper directory. See the README
documentation file in the first save-set for more information.
Page 41
3.16 PREPARING FOR AUTOPATCHING TRAFFIC-20-V4
Before preparing this product for Autopatching, you should install
the product on your system as described in the installation
documentation supplied on the product distribution tape. Unless
the product is correctly installed, you will not be able to SELECT
it for Autopatching.
The disk directory in which you have installed the executable files
for TRAFFIC-20 is referred to as the product installation
directory. In most cases this will be PS:<SUBSYS> or one of the
directories belonging to SYS:. This directory must contain the
files:
TFR.EXE TFRCAL.UNV
TFRCOB.REL TFRUNV.UNV
IP20.REL DUMVET.REL
The following files are required to build the TRAFFIC product.
They must be available either in the patching area (PAT:), the
distribution area (DIS:), or in INS:.
From the current save-set of the Autopatch tape
MACSYM.UNV MACTEN.UNV MONSYM.UNV
These files will be moved from the Autopatch tape when you use one
of the DUMPER control files described in the README file.
You will need to copy the following files from the TRAFFIC-20 V4
distribution tape BB-5372E-SM into the disk directory you have set
up as the TRAFFIC-20 distribution directory.
From the third save-set
CLEAR.MAC TFRCAL.MAC
DUMVET.MAC TFRCOB.MAC
IP20.MAC TFRUNV.MAC
TFR.MAC
A batch control file to perform this operation has been included in
the installation save-set on this patch tape. This file will issue
a mount request for the TRAFFIC-20 distribution tape and then
restore the appropriate files to the logical name DIS:. In this
batch file, DIS: is defined to be AP20:<AUTOPATCH.TRAFFIC>. If
you wish to use this control file, but are not using an AP20:
structure, you will want to include a 'DEF AP20: str:' command in
the BATCH.CMD file on the PS: structure for the LOGIN account from
which you will SUBMIT this control file. However, you will have to
edit this control file if you choose not to use <AUTOPATCH.TRAFFIC>
as the distribution directory.
To execute this control file, issue the following command:
@SUBMIT AP20:<AUTOPATCH.TFRPAT>TFR2V4.DDC
Page 42
The Patch and Build control file for the re-build of this product
as well as the Autopatch product description file are supplied in
the Installation save-set on the Autopatch tape. See the last
section of this document for a list of these files. There is a
DUMPER control file provided in the first save-set which will
restore these files to the proper directory. See the README
documentation file in the first save-set for more information.
Page 43
3.17 PREPARING FOR AUTOPATCHING UTILITIES-20
The disk directory in which you have installed the executable files
for UTILITIES-20 is referred to as the product installation
directory. In most cases this will be PS:<SUBSYS> or one of the
directories belonging to SYS:. This directory must contain the
files:
6-1-SETSPD.EXE (in <SYSTEM>)
6-1-SYSJOB.EXE (in <SYSTEM>)
ACTGEN.EXE
ACTSYM.UNV
ARMAIL.REL
B362LB.REL
BOOT.EXB
CHECKD.EXE (also in <SYSTEM>)
CHKPNT.EXE
CMD.REL
CMD.UNV
CREF.EXE
D36PAR.UNV
DDT11.EXE
DIL.LIB
DIL.REL
DILV7.FOR
DITV7.FOR
DIXV7.FOR
DLUSER.EXE
DUMPER.EXE
DX20LD.EXE
DXMCA.ADX
DXMCA.RMC
DXMCE.ADX
DXMCE.RMC
EDDT.REL
EDIT.EXE
EDT.EXE
EDTCAL.REL
EDTHELP.HLB
ERRMES.BIN
FE.EXE
FILCOM.EXE
FILDDT.EXE
GLOBS.UNV
HELPER.REL
INFO.EXE
IPALOD.EXE
JOBDAT.REL
JOBDAT.UNV
KDDT.REL
KNILDR.EXE
LINK.EXE
LOGGER.EXE
LP64.RAM
LP96.RAM
Page 44
MACREL.REL
MACRO.EXE
MACSYM.UNV
MACTEN.UNV
MAIL.EXE
MAILER.EXE
MAKDMP.EXE
MAKLIB.EXE
MAKRAM.EXE
MAKVFU.EXE
MAPPER.EXE
MDDT.REL
MONSYM.REL
MONSYM.UNV
MSCPAR.UNV
MSGARG.SPT
MTBOOT.EXB
NORMAL.VFU
NOTIFY.EXE
OVRLAY.REL
PA1050.EXE
PHYPAR.UNV
PROLOG.UNV
PTYCON.EXE
RDDT.REL
RDMAIL.EXE
REAPER.EXE
RFB.EYE
RP2DBT.EXB
RP2MBT.EXB
RSXFMT.EXE
RUNOFF.EXE
SCAN.REL
SCAPAR.UNV
SCNMAC.UNV
SCOMM.EXE
SDDT.EXE
SERCOD.UNV
SPEAR.EXE
SPRCOM.EXE
SPRINS.EXE
SPRKLE.EXE
SPRRET.EXE
SPRSUM.EXE
TCX.EXE
TGHA.EXE
TOC.EXE
TV.EXE
UDDT.EXE
ULIST.EXE
UUOSYM.UNV
VERIFY.EXE
WATCH.EXE
WILD.REL
XDDT.EXE
Page 45
XPORT.REL
The following files are required to build the UTILITIES product.
They must be available either in the patching area (PAT:), the
distribution area (DIS:), or in INS:.
From the first save-set of the Autopatch tape
ACTSYM.UNV CMD.REL GLXMAC.UNV HELPER.REL
JOBDAT.REL JOBDAT.UNV MACREL.REL MACSYM.UNV
MACTEN.UNV MONSYM.UNV ORNMAC.UNV QSRMAC.UNV
SCAN.REL SCNMAC.UNV SERCOD.UNV UUOSYM.UNV
These files will be moved from the Autopatch tape when you use one
of the DUMPER control files described in the README file.
The following files were not delivered on the distribution tape and
must be available in DIS:. They are to be restored from the second
save-set of the Autopatch tape:
EDTHLP.RNO
MAKHLP.EXE
PMT.MAC
RP2.MAC
The UT2V61 DUMPER control files for the Autopatch tape will load
these files to PAT:. They should then be copied to your DIS: area
for UTILITIES.
You will need to copy the following files from a TOPS-20
distribution tape into the disk directory you have set up as the
UTILITIES-20 distribution directory.
TOPS-20 V6.1 Installation tape BB-H137E-BM
From save-set "SUBSYS FILES FOR TOPS-20 V6.1"
PROLOG.UNV
TOPS-20 V6.1 Distribution tape BB-H138E-BM
From save-set "SOURCE FILES FOR TOPS-20 V6.1"
ACTGEN.MAC ACTSYM.MAC ARMAIL.MAC BOOT.MAC
CHECKD.MAC CHKPNT.MAC CMD.MAC CREF.MAC
DDT11.MAC DDTFIL.MAC DDTGP.MAC DDTSIM.MAC
DDTSYM.MAC DLUSER.MAC DUMPER.MAC DX20LD.MAC
EDIT.MAC FE.MAC FILCOM.MAC HELPER.MAC
INFO.MAC JOBDAT.MAC KNILDR.MAC MACRO.MAC
MACSYM.MAC MACTEN.MAC MAIL.MAC MAILER.MAC
MAKDMP.MAC MAKLIB.MAC MAKRAM.MAC MAKVFU.MAC
MAPPER.MAC MONSYM.MAC PAT.MAC PTYCON.MAC
RAM.ULD RDMAIL.MAC REAPER.MAC REL1.MAC
RSXFMT.MAC SCAN.MAC SETSPD.MAC SYMSUB.MAC
SYSFLG.MAC SYSJOB.MAC TV.MAC ULIST.MAC
UUOSYM.MAC VERIFY.MAC WATCH.MAC WATDAT.MAC
Page 46
WATMAI.MAC WILD.MAC
From save-set "LANGUAGE SOURCES FOR TOPS-20 V6.1"
DDT.MAC F2EDDT.MAC F2FDDT.MAC F2KDDT.MAC
F2MDDT.MAC F2RDDT.MAC F2XDDT.MAC LNKCOR.MAC
LNKCST.MAC LNKERR.MAC LNKFIO.MAC LNKHSH.MAC
LNKHST.MAC LNKINI.MAC LNKLOD.MAC LNKLOG.MAC
LNKLOW.MAC LNKMAP.MAC LNKNEW.MAC LNKOLD.MAC
LNKOV1.MAC LNKOV2.MAC LNKOVS.MAC LNKPAR.MAC
LNKPLT.MAC LNKSCN.MAC LNKSUB.MAC LNKT20.MAC
LNKWLD.MAC LNKXIT.MAC OVRLAY.MAC OVRPAR.MAC
PLTDCL.MAC PLTGLB.MAC PLTIO.MAC PLTMTH.MAC
PLTPRM.MAC PLTUTL.MAC UDDT.MAC
C2PLNK.CMD C2POVL.CMD L2PLNK.CCL
A batch control file to perform this operation has been included in
the installation save-set on this patch tape. This file will issue
mount requests for the TOPS-20 distribution tapes and then restore
the appropriate files to the logical name DIS:. In this batch
file, DIS: is defined to be AP20:<AUTOPATCH.TOPS-20>. If you wish
to use this control file, but are not using an AP20: structure,
you will want to include a 'DEF AP20: str:' command in the
BATCH.CMD file on the PS: structure for the LOGIN account from
which you will SUBMIT this control file. However, you will have to
edit this control file if you choose not to use <AUTOPATCH.TOPS-20>
as the distribution directory.
To execute this control file, issue the following command:
@SUBMIT AP20:<AUTOPATCH>UT2V61.DDC
If you use any of the TOPS-20 Monitor/EXEC DDC files, the required
files for this product will be loaded into a common distribution
directory which must be specified when selecting this product for
autopatching.
The Patch and Build control file for the re-build of this product
as well as the Autopatch product description file are supplied in
the Installation save-set on the Autopatch tape. See the last
section of this document for a list of these files. There is a
DUMPER control file provided in the first save-set which will
restore these files to the proper directory. See the README
documentation file in the first save-set for more information.
Page 47
3.18 PREPARING FOR AUTOPATCHING UTILITIES-B-V6-1
Before preparing this product for Autopatching, you should install
the product on your system as described in the installation
documentation supplied on the product distribution tape. Unless
the product is correctly installed, you will not be able to SELECT
it for Autopatching.
The disk directory in which you have installed the executable files
for UTILITIES-B-V6-1 is referred to as the product installation
directory. In most cases this will be PS:<SUBSYS> or one of the
directories belonging to SYS:. This directory must contain the
files:
DIL.LIB
DIL.HLP
DIL.REL
DILV7.FOR
DITV7.FOR
DIXV7.FOR
DIU.EXE
DIU.HLP
DYNBOO.REL
DYNLIB.L36
DYNSYM.UNV
RTL.EXE
RTLDYN.UNV
RTLJCK.REL
RTLLDB.REL
RTLZER.REL
ZERBOO.REL
MS.EXE
MS.HLP
MX.EXE
FFF.EXE
NETJOB.EXE
RMS.EXE
RMSDEB.EXE
RMSDEB.REL
RMSFAL.EXE
RMSFAL.HLP
INI.REL
RMSINT.L36
RMSINT.INV
RMSJCK.REL
RMSLDB.REL
RMSLOD.EXE
RMSUSR.R36
RMSUTL.EXE
RMSZER.REL
XRMS.EXE
The Patch and Build control file for the re-build of this product
as well as the Autopatch product description file are supplied in
the Installation save-set on the Autopatch tape. See the last
Page 48
section of this document for a list of these files. There is a
DUMPER control file provided in the first save-set which will
restore these files to the proper directory. See the README
documentation file in the first save-set for more information.
Page 49
4.0 CONTENTS OF INSTALLATION SAVE-SET
File Description
---- -----------
PEP.EXE Patch Exec Program
PEPB.EXE Patch Exec for BATCH
PEP.HLP PEP Help file
PEP201.PDF TOPS-20 Product Description Master file
SOUPR.DOC Documentation for the Source Update tool
COMPAR.EXE Compare module of SOUPR
COMPAR.HLP COMPAR Help file
MERGE.EXE Merge module of SOUPR
MERGE.HLP MERGE Help file
UPDATE.EXE Update module of SOUPR
UPDATE.HLP UPDATE Help file
INSTAL.DOC Installation Documentation for Autopatch 10/20
AUTINS.DIR Checksummed directory of the Autopatch
Installation Area
*ALGOL-20*
ALGV12.CTL patch and build control file
ALGV12.PDF product description file
ALGV12.DDC control file for preparing distribution area
*APL-20*
APL2B2.CTL patch and build control file
APL2B2.PDF product description file
APL2B2.DDC control file for preparing distribution area
*APLSF-20*
APL2S2.CTL patch and build control file
APL2S2.PDF product description file
APL2S2.DDC control file for preparing distribution area
*BASIC-PLUS-2*
B20V2A.CTL patch and build control file
B20V2A.PDF product description file
B20V2A.DDC control file for preparing distribution area
*COBOL-20*
CBL13.CTL patch and build control file
CBL13.PDF product description file
CBLASM.CMD command files for MACRO
CBLB.CMD
CBLD.CMD
CBLDB.CMD
OTSASM.CMD
CBBDEL.CMD command files for EXEC
CBLDEL.CMD
OTSDEL.CMD
UNVDEL.CMD
CBL13.DDC control file for preparing distribution area
Page 50
-Replacement patching-
CBL13R.CTL patch and build control file
CBL13R.PDF product description file
CBL13R.DDC control file for preparing distribution area
*DBMS-V6-1*
DB2V61.CTL patch and build control file
DB2V61.PDF product description file
DB2V61.DDC control file for preparing DBMS-20 distribution area
DB2V61-CBL.DDC control file for preparing DBMS-20 and COBOL
distribution areas
*DECNET-20*
DEC2V4.CTL patch and build control file
DEC2V4.PDF product description file
DEC2V4.DDC control file for preparing distribution area
*FORTRAN-20*
FTN211.CTL patch and build control file
FTN211.PDF product description file
FTN211.DDC control file for preparing distribution area
*FORTRAN-20-REP*
FTN2X1.CTL patch and build control file
FTN2X1.PDF product description file
FTN2X1.DDC control file for preparing distribution area
*FTS-20*
FTS201.CTL patch and build control file
FTS201.PDF product description file
FTS201.DDC control file for preparing distribution area
DAP2V1.REL supporting code from DIL V1
XPN2V1.REL
*GALAXY-20*
GALV50.CTL patch and build control file
GALV50.PDF product description file
GALV50.DDC control file for preparing distribution area
*IBMCOM-20-ET*
IETV21.CTL patch and build control file
IETV21.PDF product description file
IETV21.DDC control file for preparing distribution area
PROD.P11 source file for building product
*IBMCOM-20-HASP*
IHSV11.CTL patch and build control file
IHSV11.PDF product description file
IHSV11.DDC control file for preparing distribution area
PROD.P11 source file for building product
*MS-SOURCES-20*
MS211S.CTL patch and build control file
MS211S.PDF product description file
Page 51
MS211S.DDC control file for preparing distribution area
*PASCAL-20*
PAS2V1.CTL patch and build control file
PAS2V1.PDF product description file
PAS2V1.DDC control file for preparing distribution area
*PSI-20*
PSIV11.CTL patch and build control file
PSIV11.PDF product description file
PSIV11.DDC control file for preparing distribution area
*SORT-20*
SRTV5.CTL patch and build control file
SRTV5.PDF product description file
SRTV5.DDC control file for preparing distribution area
from SORT distribution
-Replacement patching-
SRTV5R.CTL patch and build control file
SRTV5R.PDF product description file
SRTV5R.DDC control file for preparing distribution area
from SORT distribution
*TOPS-20*
T26V61.CTL patch and build control file
T26V61.PDF product description file
T26V61-BIG.DDC control file for preparing distribution area
for BIG monitor
T26V61-MAX.DDC control file for preparing distribution area
for MAX monitor
*TOPS-20-TCPIP*
T26A61.CTL patch and build control file
T26A61.PDF product description file
T26A61-BIG.DDC control file for preparing distribution area
for BIG monitor
T26A61-DCN.DDC control file for preparing distribution area
for DCN monitor
T26A61-MAX.DDC control file for preparing distribution area
for MAX monitor
*TRAFFIC-20*
TFR2V4.CTL patch and build control file
TFR2V4.PDF product description file
TFR2V4.DDC control file for preparing distribution area
*UTILITIES-20*
UT2V61.CTL patch and build control file
UT2V61.PDF product description file
UT2V61.DDC control file for preparing distribution area
*UTILITIES-B*
UTBV61.CTL patch and build control file
UTBV61.PDF product description file
Page 52