Digital PDFs

AA-H729A-TK

May 1981

75 pages

Original

3.1MB

Document:	Autopatch Procedures Reference Manual Jan81
Order Number:	AA-H729A-TK
Revision:	0
Pages:	75
Original Filename:	AA-H729A-TK_Autopatch_Procedures_Reference_Manual_Jan81.pdf

OCR Text

TOPS-10/TOPS-20
Autopatch
Proced u res/Reference
Manual
AA-H729A-TK

January 1981

This manual describes the Automatic Patching Facility designed
to patch distributed versions of Digital Equipment Corporation
software products.
.
This is a new manual.
OPERATING SYSTEM:

TOPS-10 Version 7.01
TOPS-20 Version 4

SOFTWARE:

PEP Version 1
PEPS Version 1

Software and manuals should be ordered by title and order number. In the United States, send orders to the nearest
distribution center. Outside the United States, orders should be directed to the nearest DIGITAL Field Sales Office
or representative.
NORTHEAST/MID-ATLANTIC REGION

CENTRAL REGION

WESTERN REGION

Technical Documentation Center
Cotton Road
Nashua, NH 03060
Telephone: (800) 258-1710
New Hampshire residents: (603) 884-6660

Technical Documentation Center
1050 East Remington Road
Schaumburg, Illinois 60195
Telephone: (312) 640-5612

Technical Documentation Center
2525 Augustine Drive
Santa Clara, California 95051
Telephone: (408) 984-0200

digital equipment corporation • marlboro, massachusetts

First Printing, January 1981

The information in this document is subject to change without notice and
should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any
errors that may appear in this document.
The software described in this document is furnished under a license and
may be used or copied only in accordance with the terms of such license.
No responsbility is assumed for the use or reliability of software on equipment that is not supplied by DIGITAL or its affiliated companies.

The postage-prepaid READER'S COMMENTS form on the last page of this
document requests the user's critical evaluation to assist us in preparing
future documentation.

The following are trademarks of Digital Equipment Corporation:
DEC
DECUS
Digi tal Logo
PDP
UNIBUS
VAX

DECnet
DECsystem-10
DECSYSTEM-20
DECwriter
DIBOL
EduSystem

lAS
MASSBUS
PDT
RSTS
RSX
VMS
VT

Contents

Page

Preface
Chapter 1

Introduction
1.1

The Autopatch Concept

1-1

1.1.1
1.1.2
1.1.3
1.1.4

Autopatch Defined . .
System Requirements
Operator Qualifications
Patch Tape Structure .

1-1
1-2
1-3
1-3

1.1.4.1
1.1.4.2
1.1.4.3

Current Patch Save Set
Installation Save Set. .
Cumulative Patch Save Sets

1-3
1-3
1-4

Distribution of Patch Tapes . . . . .

1-4

The Autopatch Environment. . . . . . . . .

1-4

1.1.5
1.2

1.2.1

1.2.2
1.3

Chapter 2

Overview of the Directory Requirements.

1-4

1.2.1.1
1.2.1.2
1.2.1.3
1.2.1.4

Product Distribution Directory.
Product Installation Directory
Autopatching Directory. . . . .
Product Backup Directory . . .

1-4
1-5
1-5
1-5

Special Considerations: Creating the Directories and
Initializing Autopatch . . . . . .

1-6

Overview: the Autopatch Process Described

1-6

Procedures
2.1

TOPS-10 Procedures.

2-1

2.1.1

2-1

Installing Autopatch on a TOPS-10 System

iii

Page
2.1.2
2.1.3
2.2

Chapter 3

Automatic Patching and Rebuilding of a TOPS-I0 Product.
Restoring an Installed TOPS--I0 Product . .

2-5
2-10

TOPS--20 Procedures. . . . . . . . . . . . . . . . . . . . . . . .

2-10

2.2.1
2.2.2
2.2.3

2-10
2-15
2-20

Installing Autopatch on a TOPS-20 System . . . . . . . .
Automatic Patching and Rebuilding of a TOPS-20 Product.
Restoring an Installed TOPS--20 Product. . . . . . . . . .

Reference
3.1

3.2

3.3
3.4

The Patch Executive Program . . . . . . . . .

3-1

3.1.1
3.1.2

3-2
3-11

PEP Commands . . . . . . . . . . . .
PEP Messages and Recovery Procedures

System Programs Used with Autopatch

3-23

3.2.1
3.2.2
3.2.3
3.2.4

3-23
3-24
3-24
3-24

BACKUP and DUMPER.
Batch..
MAKLIB . . . . . . . .
PEPB . . . . . . . . . .

Disk Directories and Logical Names Used with Autopatch
Files Used with Autopatch. . . . . . . . . . . . . . . .
3.4.1
3.4.2
3.4.3
3.4.4

Files Supplied on the Distribution Tapes of Autopatchable
Products . . . . . . . . . . . . . . . . . . . . . . . .
Files Supplied on the Patch Tape Used to Install Autopatch
Files Supplied on the Patch Tape Used for Patching
PEP Data Files . . . . . . . . . . . . . . . . . . . . . .

3-24
3-25
3-25
3-25
3-26
3-27

Tables
1-1

Autopatch Resource Requirements. . . . . . . . . . . . . . . . . . 1-2

1-1
1-2
1-3
1-4

Autopatch Tape Structure. . . . . . . . . . . .
Copying Files from the Product Distribution Tape
Copying the Current Patch Save Set to Disk. . .
Retrieving Patch Data and Setting Up the Command Files for
Applying Patches . . . . . . . . . . .
Batch Processing: Applying the Patches . . . . . . . . .
Batch Processing: Rebuilding the Product . . . . . . . .
Backing Up and Installing an Updated Software Product.
Restoring an Installed Software Product. . . . . . . . .

Figures

1-5
1-6
1-7
1-8

1-4
1-5
1-7
1-8
1--9
1-9
1-10
1-12

Preface

This manual describes Digital Equipment Corporation's automatic software patching facility called Autopatch.

Organization of the Manual
The Autopatch Procedures/Reference Manual consists of three chapters.
The first is an overview chapter that both system administrators and operators should read. The chapter explains the concept of automatic patching,
lists the system requirements for utilizing the Autopatch tools, describes
the contents of the Autopatch tape, and describes the special directories
that you need to set up to prepare your system for automatic patching.
There are eight figures to supplement the overview in Chapter 1.
The second chapter is addressed to the person at your site who is responsible for installing Autopatch and patching your software. It is devoted entirely to procedures: how to set up the directories described in Chapter 1
and install the files required for automatic patching; then, how to do the
patching process itself. Once you become familiar with the step-by-step
procedures in Chapter 2, the two flow charts on the divider between Chapters 1 and 2 should be useful as quick reference for you.
The third chapter also is addressed to both system administrators and operators. In addition to describing the AUTOPATCH command and the other
commands that can be used in the patching process, it includes a section on
error messages and recovery procedures, and a reference section.

Complementary Files
A feature of Autopatch is its use of two files from the patch tape that you
will need to print out because they complement the instructions in the
manual; that is, they add specific information and instruction not given in

the manual. These procedures are not difficult, but they do require close
attention to the step-by-step instructions you receive from the manual and
the files you print. Several other files on the patch tape can also be printed
out to help you run checks on your operation of Autopatch.

Related Documents
TOPS-10 Monitor Installation Guide
TOPS-10 Operating System Commands
TOPS-10 Operator's Guide
TOPS-20 Conl,mands Reference Manual
TOPS-20 Operator's Guide
TOPS-20 Software Installation Guide
TOPS-20 User Utilities Guide

Symbology
Conventions used in this manual
(Red print)

Anything you are expected to type on your terminal. Any
printing the system does (prompting characters, recognition,
messages) is in black.

Indicates when you should press the RETURN key.

®9

Indicates when you should press the ®9 key.

(OJ

In addition to being the TOPS-20 system prompt, this is used
to indicate an indirect file.
The TOPS-IO system prompt.

Chapter 1
Introduction

1.1 The Autopatch Concept
Definitions and descriptions helpful to both system administrators and
operators are included in this introductory chapter.

1.1.1 Autopatch Defined
Autopatch is a combination of software tools and operational procedures for
easily incorporating recommended changes into Digital Equipment Corporation software products. (A product is autopatchable if it is a supported
software product that has been declared autopatchable by Digital.)
Autopatch is designed and engineered to be used at your site.
Autopatch is designed to enable you, the user, to avoid the time-consuming,
complicated, and error-prone manual procedure for applying patches. Once
Autopatch has been installed at your site, it allows you to bring to current
patch level the latest versions of DIGITAL's software with little effort or
operator intervention.
Patching a product with Autopatch consists of making the appropriate corrections to the product's component files, reexecuting the procedures that
generated the executable (.EXE) files, using the patched files as input to
the process, and then, when the product has been rebuilt, replacing the old
versions of the .EXE files on the system area with the patched versions.
A single user interface, a new utility called the Patch Executive Program
(PEP), maintains patch history and status for each autopatchable product
and coordinates the activities required to update your software. You can, in
fact~ initiate the patching and rebuilding operation with a single command
to PEP, and the operation can run, unattended, at your convenience.

1-1

Autopatch is distributed initially as a kit containing these complementary
items:
• the Autopatch Procedures/Reference Manual
• the patch tape itself, a separate tape for products running on TOPS-10
and another for those running on TOPS-20. In addition to containing
machine-readable patches, each patch tape contains two documentation
files that are to be used with the manual. (Both are in save sets on the
patch tape and are to be printed out at different stages to give you specific
instructions for completing those stages.)
See Figure 1-1; see also Section 1.1.4 of this chapter for a description of
the patch tape.
Once the kit is in hand, you need to verify the system requirements for
doing autopatching at your site and review the operator capabilities for
installing and running Autopatch.

1.1.2 System Requirements
Autopatch runs on all supported configurations of DECsystem-10 and
DECSYSTEM-20 hardware that have sufficient on-line mass storage. See
Table 1-1.

Table 1-1: Autopatch Resource Requirements
DECsystem-lO Requirements
Operating
System:

TOPS-10, version 7.01 or later

System
Software:

GALAXY Batch, version 2 or later (Multiprogram Batch (MPH) not
supported)

Hardware:

KSIO, KilO, and KL10 CPU
256K memory (minimum)
1 RP06 or RM03 Disk
1 9-track magnetic tape drive
(800 and/or 1600 BPI)

DECSYSTEM-20 Requirements

1-2

Operating
System:

TOPS-20, version 4 or later

System
Software:

GALAXY Batch, version 4 or later

Hardware:

KS10 or KL10 CPU
256K Memory (minimum)
1 RP06 or RM03 Disk
1 9-track magnetic tape drive
(800 and/or 1600 BPI)

Introduction

1.1.3 Operator Qualifications
It is our expectation that, if you have had varied directory-making experience and are familiar with the BACKUP, CREDIR and REACT programs
on TOPS-I0; the DUMPER program and BUILD command on TOPS-20;
and running GALAXY batch jobs, you will have no difficulty initializing
Autopatch at your site.

The procedures to set up the several disk directories that Autopatch requires for file storage and interchange in the patching process, and thus to
initialize (install) Autopatch, are described in detail in Chapter 2, Procedures, Sections 2.1.1 and 2.2.1.

1.1.4 Patch Tape Structure
You now need to be aware of the structure and contents of the patch tape. It
contains everything you need for your on-site patching, and is organized
into several save sets. (See Figure 1-1, Autopatch Tape Structure.) A save
set is defined as a group of files on tape, stored as the result of one SAVE
command to either BACKUP (TOPS-I0) or DUMPER (TOPS-20).
1.1.4.1 Current Patch Save Set - The current patch save set is the first one
on the tape. It contains a set of files for every autopatchable software product requiring correction. The most important files in this set are:

• README.nnn, where nnn is the number of the current patch tape. This
file contains summary information about the current patch save set, and
is to be printed and used in conjunction with the manual.
• a patch directory file (file type .DPD), which contains a record of all the
patches in this save set, and is to be processed by the Patch Executive
Program.
• the patch files, a set of files for each product requiring patching, which
contain the actual patches you will apply.
• patch retrieval control files (.Pnn and .Ann), one for each autopatchable
product, which you can use to copy the patch files from the patch tape to
disk.
1.1.4.2 Installation Save Set - The installation save set is the second save
set on the patch tape. It contains all of the files (PEP, utility programs,
control files, etc.) required to set up your system for autopatching. The most
important file in this set is:

• INSTAL.DOC, which contains installation information not contained in
this manual. It is to be printed out and its instructions followed in conjunction with the procedures described in the manual. (Chapter 2, Procedures, will tell you the proper time to obtain a listing of INSTAL.DOC.)

Introduction

1-3

1.1.4.3 Cumulative Patch Save Sets - The cumulative patch save sets are a
sequence of patch save sets from previous patch tapes. These accumulated
patch save sets are provided to enable you to install a newly acquired
software product at the current patch level without having to handle more
than one tape.

See Figure 1-1 for the structure of the Autopatch tape.

Figure 1-1: Autopatch Tape Structure

INSTALLATION
SAVE SET

CURRENT PATCH
SAVE SET

MR-S-954-81

1.1.5 Distribution of Patch Tapes
Additional patch tapes will be made available to you periodically, as
patches are found necessary and as the number of autopatchable products
grows. Each tape, as mentioned earlier, will be cumulative; that is, it will
contain all the previous patches, so that you can update any autopatchable
product at any time.

1.2 The Autopatch Environment
Before you can autopatch any software on your system, you must prepare
an autopatching environment consisting of several disk directories. In
these directories, you will need to install the files required for the autopatching operation. Some of these files will be found on the patch tape;
others are supplied on the distribution tape for each product. However, you
will have to set up these directories only once, since they are to be retained
on disk and used whenever you wish to apply distributed patches to update
your software. The next sections deal with the disk directories and the files
that make automatic patching possible.

1.2.1 Overview of the Directory Requirements
Described below are the four storage areas (directories) and their functions;
the steps to set them up are shown in Chapter 2, Procedures, Section 2.1 for
TOPS-10, Section 2.2 for TOPS-20.
Product Distribution Directory Holds the input and control files
(.REL, .MAC, .LNK, etc.) that you use to build the executable files (.EXE)

1.2.1.1

1-4

Introduction

of the product. The files for this directory are distributed with each release
of a software product. (You can generate a single directory to hold all the
input files for all of the autopatchable products at your site, or a separate
directory for each autopatchable product.) See Figure 1-2.

Figure 1-2: Copying Files from the Product Distribution Tape

MR-S-955-81

1.2.1.2 Product Installation Directory - Contains all of the executable program (.EXE) files. Most sites already have a directory set up for this purpose. It is one of the directories belonging to SYS:.

Receives the files copied from the patch
tape. This directory also contains a batch control file (.CTL) for each autopatchable product. This directory serves as a working area where you patch
and rebuild the product.
1.2.1.3 Autopatching Directory -

1.2.1.4 Product Backup Directory - Holds backup copies of the input as well
as the executable files for the product. When you use PEP to install the
patched version of a product, it saves the previous version in this area. (You
can generat~ a single backup directory for all of the autopatchable products
':it your site, or a separate backup directory for each autopatchable product.)

NOTE
These directories can be built on any of your available disk
packs. Although you will need less than 3000 pages (12000
blocks) initially, we recommend that you dedicate an entire
disk for the autopatching, backup, and product distribution
directories. Thus, all of the disk resources required for autopatching can be kept separate from the directories and files
used every day. If you already have directories that can be
utilized for autopatching, you may use those instead of creating new ones.
Earlier in this introductory chapter, we have indicated system requirements for autopatching and the qualifications for the operator, and have
outlined both the patch tape structure and the functions of the special disk
directories. In the next two sections we deal with some special considerations involved in preparing your system for Autopatch, and offer an overview of the activities controlled by the Patch Executive Program (PEP).

Introduction

1-5

1.2.2 Special Considerations: Creating the Directories and
Initializing Autopatch
To avoid problems with creating the directories, the order in which you
should create them, and what you should call them, we make these recommendations:
1.

Dedicate a separate disk pack for the distribution, backup, and autopatching directories, so that you need to mount only a single disk pack
to have everything you need. Our examples refer to this disk structure
as DSKP: for TOPS-I0 storage, or AP20: for TOPS-20 storage.

Of the four needed storage areas, one (which we refer to as the product
installation directory) already exists on your system, probably as SYS:

3. Three other storage areas (directories) must be created as part of the
Autopatch installation procedure. We show you in Chapter 2, Procedures, how to set up these directories (Section 2.1 for TOPS-I0 and
Section 2.2 for TOPS-20):
• Autopatching directory
• Product distribution directory
• Product backup directory

NOTE
We urge that you use the naming conventions used in
Chapter 2, Procedures, when building your directories, so
that your names and those used by both Autopatch and
the sample procedures shown in this manual will be compatible. Conforming to the naming conventions will allow
you to patch your software products by simply executing
the procedures as shown.
4.

Product distribution directories must be initialized before you can run
Autopatch. To hi.itialize these directories, you will store in them the
input files that build each of the products you want to be autopatchable
at your site. (You will find a list of the required files for each autopatchable product in INSTAL.DOC, in the installation save set, the second
set on the patch tape.)

5. The transition step between installing Autopatch and running it to
apply patches is to select the products you want to be autopatchable at
your site. You do this by running PEP and issuing a SELECT command
for each of the desired products.

1.3 Overview: the Autopatch Process Described
This section describes in general terms what happens in the Autopatching
process, that is, how Autopatch works once it has been installed at your
site. You initiate these activities by using BACKUP in a TOPS-I0 system

1-6

Introduction

and DUMPER in a TOPS-20 system to obtain the necessary files from the
patch tape. The activities are then controlled by commands to PEP, the
Patch Executive Program.
As we mentioned earlier, AUTOPATCH, the preferable single command to
PEP, will carry out the patching process; it handles the activities that
RETRIEVE, SETUP and BUILD together handle.
Activity 1.

You copy files from the current save set on the patch tape to
the autopatching directory so that all the distributed patches
for all the autopatchable products are made accessible to
Autopatch. (If you are patching a software product for the
first time, you will have to copy patches from the cumulative
patch save sets also.) See Figure 1-3.

Figure 1-3:

Copying the Current Patch Save Set to Disk

BACKUP

----

(TOPS-10)

~
~

.---DUMPER

(TOPS-20)

MR·S·956·81

Activity 2.

You update the data base in your autopatching directory
with information concerning all the new patches to those
products that you have previously set up for autopatching.
PEP does this activity for you when it processes the
RETRIEVE command.
See Figure 1-4, which illustrates activities 2 and 3.

Activity 3.

You set up the indirect command files needed to apply those
patches that will update y~ur software to the current revision level. PEP does this activity for you when it processes
the SETUP command. See Figure 1-4.
Introduction

1-7

Figure 1-4: Retrieving Patch Data and Setting Up the Command
Files for Applying Patches

RETRIEVING PATCH
DATA AND
SETTING UP
FOR PATCHING
AND REBUILDING

MR-S-957-81

Activity 4.

After you have generated the indirect command files, you
are ready to run the batch control file that will apply the
patches and rebuild the software components of the product.
This job runs unattended, under batch, and can be scheduled
to run at your convenience. However, before you SUBMIT
this job to the Galaxy Batch System, PEP must verify that
all the required files are in place. PEP performs this activity
when it processes the BUILD command.
See Figures 1-5 and 1-6, which ill ustra te the two phases of
activity 4.

1-8

Introduction

Figure 1-5: Batch Processing: Applying the Patches

BATCH
PROCESSING

(APPL VING THE
PATCHES)

MR-S-958-81

Figure 1-6: Batch Processing: Rebuilding the Product

BATCH
PROCESSING

(REBUILDING THE
PRODUCT)

MR-S-959-81

Introduction

1-9

Activity 5.

When the batch job completes, the updated components of
the product will be in the autopatching directory. You then
copy the updated files to the appropriate directories. When
you install the updated version of the software, you are performing two separate operations:
A. Backing up the currently installed versions of both the
input and .EXE files of the patched product to the product
backup directory.
B. Replacing the currently installed version of the input files
in the product distribution directory on disk (superseding
the old version with the new version), and replacing the
currently installed version of the .EXE file in the product
installation directory (SYS:) (superseding the old version
wi th the new one).
See Figure 1-7, which illustrates the two phases of
activity 5.

Figure 1-7:

Backing Up and Installing an Updated Software
Product
A. Backing Up the Original Version

NO
CHANGE

MR-S-960-81

1-10

Introduction

B. Installing the Updated Product

NO
CHANGE

MR-S-961-81

Activity 6.

(Optional) Restoring your software to its original condition
(before the product was patched and rebuilt) is the reverse of
the install process. This option is provided to allow you to
revert to the previous version of a software product if the
rebuilt version does not meet your requirements.
See Figure 1-8.

Introduction

1-11

Figure 1-8: Restoring an Installed Software Product

NO
CHANGE

MR·S·962·81

1-12

Introduction

PATCHING A PRODUCT

( START

1
MOUNT
THE
PATCH TAPE

COpy
DOCUMENTATION
AND
- --CONTROL FILES
(
TO DISK

!
PRINT
DOCUMENTATION
FILE TO
USE WITH
MANUAL

- -- -

1
COPY
PATCH
FILES

f- -- -

!
PATCH AND
REBUILD EACH
PRODUCT

I-

ransfer README.nnn and patch
retrieval control files to the
autopatching directory on disk

onsult

README.nnn for index of
files and instructions for
obtaining them

ransfer

patch files from
patch tape to autopatching
directory

__ _ f i v e the AUTOPATCH command to PEP

I- - - - " ,

~UBMIT the batch control file that applies

~ patches and rebuilds the product

!
TEST
(optional)

____ /:y

the update peaduc" does;t meet

~urneedS?

1
___ / B a c k up your previous version
BACKUP
AND
INSTALL

----~tall the updated product

I
END
MR-S-964-81

Chapter 2.
Procedures

2.1 TOPS-10 Procedures
2.1.1

Installing Autopatch on a TOPS-10 System

In the Introduction, we have given you an overview of the Autopatching
concept and of the capabilities of this facility. To prepare your TOPS-I0
system for autopatching, follow these step-by-step procedures. The ten steps
will take you through the use of the SELECT command to PEP; at that
point, Autopatch is installed, and you are ready to apply patches.
Step 1:
LOGIN ,LOGIN
JOB 43
#

1 ,2

Pas SI,IO rd:
[LGNJSP Othe r Jobs sallIe PPNJ
08:41
3-Dec-80
Wed

Step 2:
Mount the structure to be used for all the operations involved in autopatching. To be consistent with our examples, call this structure DSKP:. It
should be a dedicated disk so that you can continue to update your system
as new patch tapes are distributed.
,MOUNT DSKP:/NOWAIT
Request queued to Iflount units

Step 3:
If you already have a PPN established for the autopatching directory, skip
this step. Otherwise, use REACT to create the accounting file entries for
the autopatching directory. Our examples will reference PPN [7,6] as the

2-1

autopatching directory. This involves creating an entry for PPN [7,6] in
ACCT.SYS. It also involves creating an entry for the autopatching structure DSKP: in AUXACC.SYS. Note that our example creates three structures in the default search list for this account. The first structure in the
list must be the autopatching structure. For more information on REACT,
see the RUNREA specification in the TOPS-IO Notebook Set and the
TOPS-10 Operator's Guide, Part V. It is important that you set large permanent and working quotas for this structure, such as 20,000 blocks .
• R REACT
For help t}'pe "H<CR>"

*R
[793 out of 1100 entries are used]
.q 7,6
L.ist codes?

*.! 7,6
Naflle :AUTOPATCH
Code:PATCH
Privile!le IAlord:$
*C 7,6
Chan!le: SPO ALL
Ch an !Ie: LOG ALL
Chan!le:

*T 7,6
L.ist codes?
7

6
AUTO PATCH
511,,5112,,5
8 SEP 768
0

000000000000
017500001763
511

*w
.R REACT
For help t}'pe "H<CR>"

*A
[422 out of 1100 ent ries are l.1sed]

*T 7,6
*1 7,6
1\11.1111 STRs:

3
STR nafrle: DSKP:
Resrvd: FCFS: 20000
Quota out: 20000
Status bits:
!:iTR nafrle: DSKB:
Resrvd: FCFS: 100
Quota OI.lt: 100
Status bits:
STR name: DSKC:
Resrvd: FCFS: 100
Quota out: 100
Status bits:

*T 7,6
7

*w
*.'" C

2-2

Procedures

DSKP
DSKB
DSKC

0
0
I)

20000
100
100

0
0
0

777777777777

Step 4:
Use CREDIR to create a product backup directory, calling it
DSKP:[7,6,BACKUP]. This directory is important in case you choose to
revert to the previous version after installing the patched software .
• RCREDIR
Create directon': DSKP:(7,6,BACKUP]
Created DSKPO: [7 ,6] .UFD/PROTECTION:775
Created DSKPO:[7,6,BACKUPJ.SFD/PROTECTION:775
Create directon': ···Z

Step 5:
Mount the patch tape we have furnished you .
• MOUNT MTA: TAPE: IREELI D: PATCH
Request queued
Waitin9' ••• 2 ···Cs to EHIT
MTA Mounted, MTA10l Used

Step 6:
Transfer the file called INSTAL. DOC from the patch tape to the autopatching area, the directory named DSKP:[7,6]. This file is in the second save set
(the installation save set) on the tape. Since this installation save set contains tools and control files needed for the autopatching operation, PRINT
out INSTAL.DOC and read it to determine which of these files you need .
• R BACKUP
/TAPE TAPE:
IINTERCHANGE
IREWIND
IFILES
ISKIP 1
I RESTORE DSK P: INSTAL. DOC [7,6]
! I NSTAL
DOC
"Done
IREWIND
ID(IT

.PRINT DSKP:INSTAL.DOC[7,6J
[LPT:INSTAL=/Seq:4602/Lirllit:57, 1 FileJ

Procedures

2-3

Step 8:
Build a product distribution directory for each product on your system that
you want to patch. Call these directories DSKP:[7,6,product name]. For
example, the directory for APLSF-10 would be called DSKP:[7,6,APL] to be
consistent with the example.

NOTE
Remember that the installation of Autopatch is a one-time
procedure. For each product you intend to patch, however,
you need to provide a product distribution directory by
repeating Step 8; then move the needed files into it, as in
Step 9 .
• R CREDIR
Create directorY: DSKP:[7,G,APlJ
C rea te d D5 K PO: [ 7 ,G ,A P l J • 5 F DIP ROT E C T I ON : 775
Create directorl': "'Z

Step 9:
Again using INSTAL.DOC, transfer the files required for autopatching
from the product's distribution tape to the appropriate product distribution
area of DSKP:. The details concerning each autopatchable product and the
list of appropriate files for each product that you have selected are described in INSTAL.DOC.
Step 10:
With all the elements for autopatching now in place on DSKP:, the next
step is to run the PEP program, using the SELECT command to declare

2-4

Procedures

each autopatchable product. Installation is now complete, and the actual
autopatching process can begin. (See Section 2.1.2.)
• R PEP
[PEP version 1(44)J
What is the al.!topatchin!!' director}'? DSKP:[7,BJ
PAT: defined as DSKP:[7,BJ
[Initializin!!' ••• J [DKJ
NOIAI use the SELECT corrllTland to define the autopatchable products.
PEP>SELECT (the product) APLSF-10-!,rz
What is the distribution director}' for APLSF-10-!,rz? DSKP:[7,B,APLJ
DIS: defined as DSKP:[7,B,APLJ
What is the bacf(up director}' for APLSF-10-!.rz? DSKP:[7,B,BACKUPJ
BAK: defined as DSKP:[7,B,BACKUPJ
What is the installation director>' for APLSF-10- I,lZ? SYS:
INS: defined as SYS:[l ,4J
[Checf(in!!' corTIPonents and files for APLSF-10- I•r ZJ [OKJ
[APLSF-10-1,12 SELECTed for al.ltopatchin!!'J
[ChecKpointin!!'J [OKJ
PEP>E)<IT

CAUTION
If PEP generates warning messages %CID (Checksum is different) or %VID (Version is different) during this step, you
have not set up your product distribution directory or installation directory with the distributed (field-image) version of
the product files. Unless you correct this problem, you may
not be able to autopatch your software successfully,

2.1.2 Automatic Patching and Rebuilding of a TOPS-10 Product
This section describes the procedures required to do automatic patching on
a TOPS-I0 configuration. Prior to executing these procedures, you must
have completed the Autopatch installation described in Section 2.1.1.
The following procedure assumes that the autopatching directory is on a
structure called DSKP:. Log in under [7,6]. If you have established another
PPN as your autopatching directory, then log in under that PPN.
Step 1:
Mount the Patch Tape
Mount the patch tape supplied with the Autopatch kit. The procedures
shown in our examples use logical name TAPE:.
MOUNT MTA: TAPE: IREEL I D: APATCH
Re91.lest 9ueued
Waitin!!' ••• Z"'Cs to E)-(IT
MTA Mounted, MTA101 Used

,Step 2:
Copy the Documentation and Control Files from the Patch Tape to Disk
Transfer the documentation and patch retrieval control files from the current patch save set (see Section 1.1.4.1) to the auto patching directory on

Procedures

2-5

disk. These files will include the latest copy of README ~s well as a patch
retrieval control file for each autopatchable product. You can later use
these patch retrieval control files to obtain the patch files from the tape.
There are two types of patch retrieval control files. Those with file type
.Pnn can be used to obtain patch files from the current save set for a specific
product. Those with file type .Ann can be used to obtain the patch files from
all the save sets for a specific product.

Step 3:
Print the Documentation File
At this point, print out the disk file README.nnn, where nnn is the number of the current patch tape.
You need to read this documentation file because it contains the index of
the various files you will use and the instructions for obtaining them from
the patch tape.
@PRINT README.OOl
[LPT:README=/SeQ:4G03/LilTlit:54, 1 File]

Step 4:
Copy the Patch Files for the Products to be Autopatched from the Patch
Tape to Disk
Follow the instructions in the README documentation file so that you are
ready to do autopatching. After obtaining the patch files, DISMOUNT the
patch tape.

2-6

Procedures

Step 5:
Patch and Rebuild the Software Product(s)
To prepare a product for the patch and rebuild operation, run PEP and
issue the AUTOPATCH command.
The A UTOPATCH command to PEP performs the following functions:
• updates the PEP data base with a record of the latest patches.
• generates the command files that the batch control file needs to apply the
patches to the product you are autopatching.
• verifies that all of the required files are present and that they are at the
required revision level.

NOTE
You can use the command AUTOPATCH * to prepare all
your SELECTed products.
Following is a print-out of what you would see on your terminal if, for
example, you were patching APLSF-10-V2:
• R PEP
[PEP l.Jersion 1(44)]
What is the alJtopatchin!l directorY? DSKP:[7,G]
PAT: defined as DSKP:[7,G]
[Initializin!l . . . ] (Readin!l data base . . . ) [OK]
PEP>AUTOPATCH (product narrle) APLSF-10-I,IZ
[Process in !I inforrrlation frorrl patch tape 1]
[Readin!l patch director>' file] [OKJ
[Z3 patches retriel.Jed for APLSF-10- I.JZJ
[ChecKpointin!lJ [OKJ
[Settin!l UP APLSF-iO-I,12 for patch and rebl.lildJ [OKJ
[Z3 patches 'A,ill be applied to APLSF-10- 1.J2J
[Checf(pointin!lJ [OKJ
[ChecfUn!l files for buildin!l APLSF-10-1,l2] [010
[Checf(pointin!lJ [OKJ
[To patch and rebuild APLSF-10_ I,IZ, issue the rrlonitor corrlJrland . . . J
SUBMIT DSKP:APL1S2.CTL[7,GJ/TIME:i:OO:OO/RESTART
PEP>EXIT

After PEP verifies that the product is set up for patching and rebuilding,
SUBMIT its batch control file to the Galaxy Batch System. You may want
to supply additional parameters to schedule the running of this job. Consult
the TOPS-10 Operating System Commands Manual to determine those
parameters .
• SUBMIT DSKP:APL1SZ.CTL[7,GJ/TIME:l:00:00/RESTART
[INP:APL1S2=/SeQ:4G04/TIME:l:00:00J

Procedures

2-7

NOTE
When the batch job completes, you will have a log file. It is a
good idea at this point to compare checksums in your log file
with those in the log file CLnn) furnished with the patch
tape. If they match, fine - but if they differ, put the two
listings side by side to determine exactly where the differences exist.
If you get a message such as ~~version number different" or
~(checksunls different," this will point to possible sources of
error.
Following is the print-out of what you would see on your terminal as you
check to determine whether the rebuilt product (in this case,
APLSF-IO-V2) is ready to be installed; use the INFORMATION command
to PEP .
• R PEP
[PEPI.lersion lUI4)]
What is the autopatchin9' directory?DSKP:[7.G]
PAT: defined as DSKP:[7.G]
[Initializin9' ••• ] (Reading data base ••• ) [OK]
[ C h e c f, i n 9' re suI t s 0 f bat c h job tor e b u i 1 d A P L S F - 1 (I - 1.1 2 ]
[ColT1Pleted successfl.tll)']
[Checf,pointin9'] [OK]
PEP>INFORMATION (about product narrle) APLSF-l0-I,12
APLSF-1(1-ln is ready to be INSTALLed
Patches retriel.led throu9'h patch tape 1
Current installed files:
DSKC:APLSF.D(E[1.4] se c'1l.lential checf,surrI724333. l.lersion 2(435)
DSKC:GENSF.EHE[1.4] se"'1uential checf\surrI22GGG7. l.lersion 2(12)
DSKC:TENTAP.E)-(E[l ,4] se"'1I.1ential checf\sLlrrI430235. version 1(3)
Updated files (read)' to be installed):
DSKP:APLSF.D(E[7.G] se"'1uential checf'surrI7504G7. l.lersion 2(4G4)
DSKP:GENSF.D(E[7.G] se"'1uential checf\sLlfTI22GGG7. version 2(12)
DSKP:TENTAP.D(E[7.G] se"'1uential checf'sl.lfrI430235. version 1(3)
Bacf,up files:
BAK:APLSF.EHE (File not found)
BAK:GENSF.E)-(E (File not found)
BAK:TENTAP.E)-(E (File not fOI.lnd)
Lo9'ical narrles:
PAT: (autopatchin9' directon) defined as DSKP:[7.G]
DIS: (distribution director)') defined as DSKP:[7.G.APL]
BAK: (bacf,up directon') defined as D5KP:[7.G.BACKUP]
IN5: <installation directon') defined as 5'(5:[1.4]
ASL: (autopatch serach list) defined as D5KP:[7.G] .D5KP:[7.G.APL] .5,(S:[1.4]

Step 6:
Testing the Rebuilt Software
Once the batch job completes successfully, the rebuilt software is available
in the autopatching directory and is ready to be installed in the system
area. Before installing it, however, you may want to try running it out of
the autopatching directory to determine whether it performs to your
satisfaction.

2-8

Procedures

If the rebuilt software, after you have run some of your most important
applications with it, does not meet your expectations, do not go on to Step 7,
Installing the Rebuilt Software.
Step 7:
Installing the Rebuilt Software
As you install the rebuilt software, you will be copying files into the PPN
defined to be the installation directory for this product. If you are using
SYS: or another protected PPN as the installatiori directory, you will need
to be logged in under [1,2].

CAUTION
If the installation operation is actually going to change files
in the SYS: area, you must be careful to avoid interfering
with the work others are doing if your system is running
under timesharing.
Following is the print-out of what you would see on your terminal as you
completed the installation of the rebuilt APLSF-10-V2 using the
INSTALL command, and rechecked on the success of the installation by
asking PEP a second time for INFORMATION:
PEP>INSTALL (product narlle) APLSF-l0-1,J2
[ChecfUng files for installing APLSF-l0- 1,J2] [OK]
[Bacf,ing UP files for APLSF-l0- 1,J2]
OSKP:APLG12.REU7,G ,APLJ => OSKP:APLG12.REU7,G ,BACKUP] [OK]
OSKP:APLS12.REU7,G ,APLJ => OSKP:APLS12.REU7,G ,BACKUP] [OK]
OSKP:APLW12.REU7,G ,APLJ => DSKP:APLW12.REU7,G ,BACKUP] [OK]
OSKC:APLSF.E}(E[l ,,~I] => OSKP:APLSF.EHE[7,G,BACKUP] [OK]
OSKC:GENSF.EHE[l,4] => OSKP:GENSF.EHE[7,G,BACKUP] [OK]
OSKC:TENTAP.E)-(E[l,4] => OSKP:TENTAP.EHE[7,G,BACKUP] [OK]
[Checkpointing] [OK]
[Installing l"lelAI files for APLSF-l0- 1,J2]
OSKP:APLG12.REU7,G] => DSKP:APLG12.REU7,G ,APLJ [OK]
OSKP:APLS12.REU7,G] => OSKP:APLS12.REL[7,G,APLJ [OK]
OSKP:APLW12.REU7,G] => OSKP:APLW12.REU7,G ,APLJ [OK]
OSKP:APLSF.E)-(E[7,G] => OSKC:APLSF.E)-(E[l,4] [OK]
OSKP:GENSF.D(E[7,G] => DSKC:GENSF.E)-(E[1,4] [OK]
OSKP:TENTAP.D(E[7,G] => OSKC:TENTAP.EHE[l,4] [OK]
[Checkpointing] [OK]
PEP>INFORMATION (about product naflle) APLSF-10-1,J2
APLSF-l0-I,J2 IAlas successful I}' INSTALLed
Patches retrieved through patch tape 1
Current installed files:
OSKC:APLSF.D(E[1,4] se91.lential checf,sufl17504G7, l.Jersion 2A(4G4)
OSKC:GENSF.D(E[1,4] se9uential checf,sufl122GGG7, l.Jersion 2(12)
DSKC:TENTAP.D(E[l,4] se91.lential checf,surl1430235, version 1(3)
Updated files·( read}' to be installed):
None
Bacf,up files:
OSKP:APLSF.D(E[7,G,BACKUP] se9uential checf'sl.lfl1724333, version 2(435)
OSKP:GENSF.D(E[7,G,BACKUP] se9uential checf'sl.lrl122GGG7, version 2(12)
DSKP:TENTAP.D(E[7,G,BACKUP] se9uential checf'sl.UI1430235, version 1(3)
Logical narlles:
PAT: (autopatching directon') defined as OSKP:[7,G]
DIS: (distribution directon') defined as OSKP:[7,G,APL]
BAK: (bacf,I.lp directon) defined as OSKP:[7,G,BACKUP]
INS: (installation directon') defined as SYS:[l,4]
ASL: (autopatch search list) defined as OSKP:[7,G] ,DSKP:[7,G,APL] ,SYS:[1,4]
PEP>D(IT

Procedures

2-9

A successful installation accomplishes three tasks:
• It establishes a backup copy of the current version of the product you are
patching.
• It moves the rebuilt product into the installation directory.
• It moves the patched input files into the product's distribution directory.

NOTE
If the installation procedure fails, however, because of a system failure, or because of an error such as ~~disk quota exceeded," you will need to correct the error and repeat the
INSTALL command.

2.1.3 Restoring an Installed TOPS-10 Product
If, for some reason, an installed software product does not perform to your
expectations and the previous version is more in keeping with your particular requirements, you can revert to the previous version by using the
RESTORE command to PEP:
• R PEP
[PEPl.Iersion 1<£14)]
What is the autopatchilH directon'?DSKP;[7,S]
PAT: defined as DSKP:[7,8]
[Initializing ••• ] (Reading data base ••• ) [OK]
PEP)RESTDRE (product nclflle) APLSF-10-I,J2
[Checking files for restoring APLSF-10- 1.'Z] [OK]
[Checkpointing] [OK]
[Restoring files for APLSF-10- 1,J2]
DSKP;APLG1Z.REU7 ,8 d3ACKUP] => DSKP:APLG12.REU7 ,8 ,APLJ [OK]
DSKP:APLS12.REU7 ,8 ,BACKUP] => DSKP:APLS1Z.REU7 ,8 ,APLJ [OK]
DSKP:APLW12.REU7 ,8 ,BACKUP] => DSKP:APLW1Z.REU7 ,8 ,APLJ [OK]
DSKP:APLSF.E}(E[7,8,BACKUP] => DSKC:APLSF.EHE[l ,4] [OK]
DSKP:GENSF.E}(E[7,8,BACKUP] => DSKC:GENSF.E)-(E[l ,4] [OK]
DSKP:TENTAP.E>(E[7,8,BACKUP] => DSKC:TENTAP.E)-(E[l ,4] [OK]
[Checkpointing] [OK]
PEP:~EXIT

See Section 3.1.1 for a complete description of the RESTORE command.

2.2 TOPS-20 Procedures
2.2.1

Installing Autopatch on a TOPS-20 System

In the Introduction, we have given you an overview of the Autopatching
concept and of the capabilities of this facility. To prepare your TOPS-20
system for autopatching, follow the procedures below. The ten steps will
take you through the use of the SELECT command to PEP; at that point,
Autopatch is installed, and you are ready to apply patches.

2-10

Procedures

Step 1:
LOGIN - You may log in to any account having WHEEL or OPERATOR
access privileges; ENABLE these privileges.
@LOGIN (USER) WHEEL (PASSWORD)
Job 57 on TTY21 10-Dee-80 10: 18:49
@ENABLE (CAPABILITIES)
$

Step 2:
Prepare a disk structure to be used for all the operations involved in autopatching. To be consistent with our examples, call this structure AP20:. It
should be a dedicated disk so that you can continue to update your
system as new patch tapes are distributed. Edit your
PS:<SYSTEM> MOUNTR.CMD file to declare this a domestic structure. If
you plan to use an existing domestic structure for autopatching, you can
skip this step.
$ CONNECT (TO D I RECTORY) SYSTEM:
$ HI MOUNTR. CMD

INPUT FILE: MOUNTR.CMD.8
482 CHARS

*ZJU

* I DOMEST I C (STRUCTURE) AP20:
$$
*jX$$
OUTPUT FILE: MOUNTR.CMD.7 !Nel,1 9'eneration!

$ TYPE (F I LE) MOUNTR. CMD
! MOUNTR COMMAND FILE
DOMEST I C (STRUCTURE) CBL 79:
DOMEST I C (STRUCTURE) SUPT:
DOMEST I C (STRUCTURE) AP20:
$

Step 3:
Use the BUILD command to create a login directory on PS:. Call this new
directory PS:<AUTOPATCH>. It is important that you set up this directory with LOGIN and WHEEL privileges. In this directory you create a
BATCH.CMD file for running the patch and build batch jobs. BATCH.CMD
should contain commands to MOUNT the autopatching structure and
ACCESS the autopatching directory on that structure.
$ CONNECT (TO D I RECTORY) <. WHEEL>
$BUILD PS:<.AUIOPATCH> PATCH
[Nel,l]
$$WHEEL
$$

$CONNECT (TO D I RECTORY> PS: <AUTOPATCH >
$CREATE BATCH. CMD
Input: BATCH.CMD.1
00100 MOUNT STRUCTURE AP20:
00200 ACCESS AP20: <AUTO PATCH>
00300 $
*EU
[BATCH.CMD.1]
$

Procedures

2-11

At this point you will need to MOUNT the autopatching structure, AP20:,
to BUILD an <AUTOPATCH> directory on it. AP20:<AUTOPATCH>
will be the disk area referred to as your autopatching directory. Set the
parameters for this directory to allow for 20 subdirectories and working and
permanent quotas of 20,000 pages, and supply a user-group number for it
and its subdirectories.
$MOUNT STRUCTURE AP20:
St rlJctl.tre AP20: ITlol.trlted
$INFORMATION (ABOUT) STRUCTURE (NAME) AP20:
Status of strlJcture AP20:
MOI.tnt cOI.(nt: 1, open file count: 0, units in strl.tcture: 1
DorTlestic
Users l,o.Iho have MOUNTed AP20: WHEEL
No users are ACCESSing AP20:
No IJsers CONNECTed to AP20:
$BU I LD AP20: <AUTO PATCH :>
(Nel,o.l ]
$$PERMANENT (D I SK STORAGE PAGE LIM IT) 20000
$$WORK I NG (D I SK STORAGE PAGE LIM IT) 20000
$$MAXIMUM-SUBDIRECTORIES (ALLOWED) 20
nUSER-GROUP (NUMBER) 10
$$SUBDIRECTORY-USER-GROUP (ALLOWED) 10
$$
$

Step 4:
Use BUILD to create your product backup subdirectory, calling it
<AUTOPATCH.BACKUP>. This directory is important in case you wish
to revert to the previous version after installing the patched software. You
will want to set a working quota of 4,000 pages and a permanent quota of
3,000 pages. Assign a directory-group number that is the same as the usergroup number of the autopatching directory.
$BUILD AP20: <AUTOPATCH. BACKUP>
(Nel,o.l ]
$$WORK ING (D I SK STORAGE PAGE LIM IT) 1I000
$$PERMANENT (D I SK STORAGE PAGE LIM IT) 3000
$$DIRECTORY-GROUP (NUMBER) 10
$$
$

Step 5:
CONNECT to the autopatching directory and MOUNT the patch tape we
have furnished you.
$CONNECT (TO D I RECTORY) AP20: <AUTO PATCH :>
$MOUNT TAPE TAPE:
(Mount Request TAPE Queued, Request-ID 88]
(Tape set TAPE, I)OlUrTle TAPE lTlounted]
$

Step 6:
Transfer the file called INSTAL.DOC from the patch tape to the auto patching directory. This file is in the second save set (the installation save set) on
the tape. Since this installation save set contains tools and control files
needed for the autopatching operation, PRINT out INSTAL.DOC and read
it to determine which of these files you need.

2-12

Procedures

$DUMPER
DUMPER >TAPE TAPE:
DUMPER>REWIND
DUMPER>FIlES
DUMPER>SKIP 1
DUMPER tape *I: 1 1,101 i d TAPE, AUTDPATCH SET 002, Monda)', 10-No\,1-80 1003
DUMPER tape *I: 1 1,101 id TAPE, AUTDPATCH INSTALLATION SAI,IE SET, Monda)', 10-Nol.J-80 1005
DUMPER >RESTORE DSK*: < * > INSTAL. DOC DSK:
DUMPER tape *I: 1 1,101 id TAPE, AUTO PATCH INSTALLATION SAI.JE SET, Monday, 10-No\,J-80 1005
Loading file(s) into AP20:<AUTOPATCH>
AP20:<AUTOPATCH>INSTAL.DOC.2;P777700;A (TO) INSTAL.DOC.2
[OK]
End of sal,Jeset
DUMPER>REWIND
DUMPER>EXIT
$PR I NT INSTAL. DOC
[Job INSTAL Queued, Re"luest-ID 38, LifTlit 36]
$

Step 7:
As instructed in Section 2 of INSTAL.DOC (Installing Autopatch), transfer
from the installation save set of the patch tape the files that are specified.
These will include the executable, data, and help files for the Patch
Executive Program (PEP). For each product you intend to autopatch, you
will need to copy a patch and build control file (.CTL) and a DUMPER
distribution control file (.DDC) from this save set to the autopatching directory. The example below shows the files that are necessary for the
2060-MAXIMUM configuration of the TOPS-20 monitor.
$DUMPER
DUMPER >TAPE TAPE:
DUMPER>REWIND
DUMPER>FIlES
DUMPER>SKIP 1
DUMPER tape *I: 1 1,loUd TAPE, AUTOPATCH SET 002, Monday, 10-Nol.J-80 1003
DUMPER tape *I: 1 1,101 id TAPE, AUTO PATCH INSTALLATION SAI,IE SET, Monda)', 10-Nol,J-80 1005
DUMPER>RESTORE DSK*:<*>*.EXE S1'S: 1 DSK*:<*>*.HlP HLP: 1DSK*:<*>*.PDF DSK: 1DSK*: < * >T20BOLI. CTl DSK: 1DSK*: < * >T20BOll-MAX. DOC DSK:
DUMPER tape # 1 1,101 i d TAPE, AUTO PATCH INSTALLATION SAI.JE SET, Monda)', 10-Nol,,-80 1005
Loading file(s) into PS:<SUBSYS>
AP20:<AUTOPATCH>PEP.EXE.2;P777752;A (TO) PS:<SUBSYS>PEP.EXE.2
[OK]
Loading file(s) into PS:<HELP>
AP20:<AUTOPATCH>PEP.HLP.2;P777752;A (TO) PS:<HLP>PEP.HLP.2
[OK]
Loading file(s) into AP20:<AUTOPATCH>
AP20:<AUTOPATCH>PEP201.PDF.l ;P777700;A (TO) PEP201.PDF.l
[OK]
Loading file(s) into PS:<SUBSYS>
AP20:<AUTOPATCH>PEPB.EXE.2;P777752;A (TO) PS:<SUBSYS>PEPB.EXE.2[OKJ
Loading file(s) into AP20:<AUTOPATCH>
AP20: < AUTO PATCH >T2060ll. CTL. 1 ; P777700; A (TO) T2060Ll. CTL. 1
[OK]
AP20:<AUTOPATCH>T2060Ll-MAX.DDC.l ;P777700;A (TO) T2060Ll-MAX.DDC.l[OKJ
End of sal.Jeset
DUMPER>REWIND
DUMPER>EXIT
$

Procedures

2-13

Step 8:
Build a product distribution directory for each product on your system that
you intend to autopatch. Call these directories <AUTOPATCH.product
name>. For example, the directory for the TOPS--20 monitor would be
called <AUTOPATCH.TOPS--20>. For each directory, set up working and
permanent quotas of 3000 pages, and assign a directory-group number that
is the same as the user-group number you assigned to the autopatching
directory.

NOTE
Remember that the installation of Autopatch is a one-time
procedure. For each product you intend to patch, however,
you need to provide a product distribution directory by
repeating Step 8; then move the needed files into it, as In
Step 9.
$BU I LO AP20: < AUTO PATCH • ToPS-20 >
[N e 1,1)
$$WORK I NG (0 I SK STORAGE PAGE LIM IT) 3000
$$PERMANENT (0 I SK STORAGE PAGE LI MIT) 3000
$$01 RECTORY -GROUP (NUMBER) 10
$$
$

Step 9:
Again using INSTAL.DOC, transfer the files required for autopatching
from the product's distribution tape to the appropriate product distribution
area of AP20:. The details concerning each autopatchable product and the
list of appropriate files for each product that you have selected are described in INSTAL.DOC.
Step 10:
With all the elements for autopatching now in place on AP20:, the next step
is to run the PEP program, using the SELECT command to declare each
autopatchable product. Installation is now complete, and the actual autopatching process can begin. (See Section 2.2.2, the section following this
one.)
$PEP
[PEP version lUI4»)
What is the al.ltoF'atching directon'? AP20:<AUToPATCH>
PAT: defined as AP20:<AUToPATCH>
[Initializing ••• ) [OK)
NOI,luse the SELECT cOlTlfrland to define the autoF'atchable F'roducts.
PEP>SELECT ToPS-20-20GO-I)4
What is the distribution director}' for ToPS-20-20GO-I.14? AP20:<AUToPATCH.ToPS-20>
DIS: defined as AP20:<AUToPATCH.ToPS-20>
What is the bacl(uF' director}' for ToPS-20-20GO-I.14? AP20:<AUToPATCH.BACKUP>
BAK: defined as AP20:<AUToPATCH.BACKUP>
What is the installation directon' for ToPS-20-20GO-I.14? PS:<SYSTEM>
INS: defined as PS:<SYSTEM>
[ChecKing COlrlF'Onents and files for ToPS-20-20GO-I.14) [OK)
[ToPS-20-20GO-I.14 SELECTed for autoF'atching)
[ChecKF'ointing) [OK)
PEP>EXIT
$

2-14

Procedures

2.2.2 Automatic Patching and Rebuilding of a TOPS-20 Product
This section describes the procedures required to do automatic patching on
a TOPS-20 configuration. Prior to executing these procedures, you must
have completed the Autopatch installation described in Section 2.2.1.

TOPS-20 Login Procedures - Autopatch requires that the autopatching
directory be the connected directory. If you built the subdirectories as described in Section 2.2.1, you will also have to obtain group ownership rights
for this directory.
The following procedure assumes that the autopatching directory is on a
mountable structure called AP20:. After logging in, you mount the structure, obtain the group ownership rights, and connect to the autopatching
directory.
For example:
@LOGIN (USER) AUTO PATCH (PASSWORD)
Job 7 on TTY42 12-Dec-80 18:28:27
@MOUNT STRUCTURE (NAME) AP20:
St ructure AP20: frlounted
@ACCESS (TO D I RECTORY> AP20: AUTO PATCH:>
@CONNECT (TO D I RECTORY) AP20: AUTO PATCH :>

<
<

Step 1:
Mount the Patch Tape

Mount the patch tape supplied with the Autopatch kit. The procedures
shown in our examples use logical name TAPE:.
@MOUNT TAPE (NAME) TAPE:
[Mount Request TAPE Queued, Request-ID 18]
[Tape set TAPE, l,JOIUfrle TAPE frlounted]
[TAPE: defined as MTO:]
@

Step 2:
Copy the Documentation and Control Files from the Patch Tape to Disk

Transfer the documentation and patch retrieval control files from the current patch save set (see Section 1.1.4.1) to the autopatching directory on
disk. These files will include the latest copy of README as well as a patch
retrieval control file for each autopatchable product. You can later use
these patch retrieval control files to obtain the patch files from the tape.
There are two types of patch retrieval control files. Those with file type
.Pnn can be used to obtain patch files from the current save set for a specific
product. Those with file type .Ann can be used to obtain the patch files from
all the save sets for a specific product.
Procedures

2-15

NOTE
If you have a large amount of disk space available in the
autopatching directory, you may elect to transfer the entire
contents of the current patch save set to disk at this time.
Although this could consume a large amount of disk space, it
will simplify the tape-to-disk transfer operation. You can
then delete the files you do not need. However, your operations then will not correspond to our example.
When DUMPER is ready to accept commands, it types DUMPER>. Enter
the following commands in response to the DUMPER prompts:
@DUMPER
DUMPER>TAPE TAPE:
DUMPER>REWIND
DUMPER>FILES
DUMPER >RESTORE DSK*: (* >README. * DSK: ,DSK*:(*>*.P* DSK: ,DSK*:(*>*.A* DSK:
DUM PER tap e *I 1 1,J 0 1 i d TAP E , AUT 0 PAT CH SET 002 , M0 n d a,' , 1 0 - N0 I) - 80 1003
Loadin!1 file(s) into AP20:<AUTOPATCH>
[OK]
AP20:<AUrOPATCH>APL262.A02.1 ;P777700;A (TO) APL262.A02.1
[OK]
AP20:(AUTOPATCH>APL262.P02.1 ;P777700;A (TO) APL262.P02.1
[OK]
AP20:<AUTOPATCH>APL2S2.A02.1;P777700;A (TO) APL2S2.A02.1
[OK]
AP20:<AUTOPATCH>APL2S2.P02.1;P777700;A (TO) APL2S2.P02.1
[OK]
AP20:<AUTOPATCH>README.002.1;P777700;A (TO) README.002.1
[OK]
AP20:(AUTOPATCH>T20204.A02.1;P777700;A (TO) T20204.A02.1
[OK]
AP20:(AUTOPATCH>T20204.P02.1 ;P777700;A (TO) T20204.P02.1
[OKJ
AP20:(AUTOPATCH>T20404.A02.1 ;P777700;A (TO)'T20404.A02.1
[OK]
AP20:(AUTOPATCH>T20404.P02.1 ;P777700;A (TO) T20404.P02.1
[OKJ
AP20:(AUTOPATCH>T20G04.A02.1 ;P777700;A (TO) T20G04.A02.1
[OKJ
AP20:(AUTOPATCH>T20G04.P02.1 ;P777700;A (TO) T20G04.P02.1
[OKJ
AP20:(AUTOPATCH>T20AL4.A02.1 ;P777700;A (TO) T20AL4.A02.1
[OKJ
AP20:(AUTOPATCH>T20AL4.P02.1 ;P777700;A (TO) T20AL4.P02.1
[OK]
AP20:(AUTOPATCH>T20AS4.A02.1 ;P777700;A (TO) T20AS4.A02.1
[OKJ
AP20:(AUTOPATCH>T20AS4.P02.1 ;P777700;A (TO) T20AS4.P02.1
End of sal,leset
DUMPER >EX IT
@

Step 3:
Print the Documentation File

At this point, print out the disk file README.nnn, where nnn is the number of the current patch tape.
You need to read this documentation file because it contains the index of
the various files you will use and the instructions for obtaining the various
patch files from the patch tape.
@PRINT (FILES) README.002
[Job README Queued, Request-ID 20, Limit 27J
@

Step 4:
Copy the Patch Files for the Products to be Autopatched from the Patch
Tape to Disk

After obtaining the patch files, ,DISMOUNT the patch tape.
@DISMOUNT TAPE TAPE:
[Tape dismounted, lO!1ical name TAPE: deletedJ
@

2-16

Procedures

Step 5:
Patch and Rebuild the Software Product(s)
To prepare a product for the patch and rebuild operation, run PEP and
issue the AUTOPATCH command.
The A UTOPATCH command to PEP performs the following functions:
• updates th~ PEP data base with a record of the latest patches.
• generates the command files that the batch control file needs to apply the
patches to the product you are autopatching.
• verifies that all of the required files are present and that they are at the
required revision level.

NOTE
You can use the command AUTOPATCH * to prepare all
your SELECTed products.
Following is a print-out of what you would see on your terminal if, for
example, you were patching TOPS--20-2060-V4:
@PEP
[PEP I.lersion 1(44)]
What is the autopatching directon-? AP20:<AUTOPATCH>
PAT: defined as AP20:<AUTOPATCH>
[Initializing ••• ] (Reading data base ••• ) [OK]
PEP>AUTOPATCH (product nalTle) TOPS-20-20GO-I.J4
[Processing inforlTlation frOITl patch tape 1]
[Reading patch di rector>' file] [OK]
[32 patches retriel.led for TOPS-20-20GO-I.14]
[Processing inforlTlation frOITl patch tape 2]
[Reading patch director}' file] [OK]
[41 patches retrieved for TOPS-20-20GO-l.J4]
[Checkpointing] [OK]
[Setting UP TOPS-20-20GO-I.J4 for patch and rebuild [OK]
[73 patches I.lill be applied to TOPS-20-20GO-I.J4]
[CheckpointiIH] [OK]
[Checking files for buildilH TOPS-20-20GO-lj4] [OK]
[To patch and rebuild TOPS-20-20GO-I.J4, issue the ITlonitor COITlITland " . ]
SUBMIT AP20:<AUTOPATCH>T20G04.CTL.l/TIME:l:00:00/RESTART
[Checf(pointing] [OK]
PEP >E){ IT
@

After PEP verifies that the product is set up for patching and rebuilding,
SUBMIT its batch control file to the Galaxy Batch System. You may want
to supply additional parameters to schedule the running of this job. Consult
the TOPS-20 Commands Reference Manual to determine those parameters.
@SUBMIT (BATCH JOB) T20G04. CTL. liT I ME: 1 : 00: OO/RESTART
[Job T20G04 Queued, Re"luest-ID 23, LilTlit 1 :00:00]

Procedures

2-17

NOTE
When the batch job completes, you will have a log file. It is a
good idea at this point to compare checksums in your log file
with those in the log file (file type .Lnn) furnished with the
patch tape. If they match, fine - but if they differ, put the
two listings side by side to determine exactly where the differences exist.
If you get a message such as (( version number different" or
((checksums different," this will point to possible sources of
error.
Following is a print-out of what you would see on your terminal as you
check to determine whether the rebuilt product (in this case,
TOPS-20-2060-V 4) is ready to be installed; use the INFORMATION command to PEP.
@ENA8LE (CAPABILITIES)
$PEP
[PEP version 1(44)]
[PAT: (autopatching directorl') defined as AP20:<AUTOPATCH>]
[Initializing ••• ] (Reading data base ••• ) [OK]
[Checf;ing results of batch job to rebuild TOPS-20-2080-1,J4)
[ColllPleted successfull~']
[Checl;pointing] [OK]
PEP>INFORMATION (about product naille) TOPS-20-2080-1,14
TOPS-20-2080- 1,J4 is read~' to be INSTALLed
Patches retrieved through patch tape 2
Current installed files:
P S : < S '( S T EM'> E){ E C • E){ E. 1 seq u e n t i a 1 c h e c I; s 1.\ ITI 785887 , I) e r s ion 4 ( 580 )
PS:<SYSTEM>BUGSTRINGS. T){T.1 sequential checl;sl.1I11 511220
PS:<S,{STEM>MONITR.E)-(E.1 sequential checl;sulll 847550, version 4(32£17)
Updated files (read~' to be installed):
AP20:<AUTOPATCH>EHEC.E){E.1 sequential checl;sl.\111737352, I)ersion 4(587)
AP20:<AUTOPATCH>BUGSTRINGS.THT.1 sequential checKsull1 218048
AP20:<AUTOPATCH>MONITR.E){E.1 seqlJential checl;sulll 80334, I)ersion 4(3370)
Bacl;up files:
BAK:D(EC.EHE (File not found)
BAK:BUGSTRINGS.T){T (File not fOI.lnd)
BAK:MONITR.D(E (File not found)
Logical nalTles:
PAT: (autopatching directon') defined as AP20:(AUTOPATCH>
DIS: (distribution directon-) defined as AP20:<AUTOPATCH.TOPS-20>
BAK: (bacl,up director}') defined as AP20:<AUTOPATCH.BACKUP>
INS: (installation directory) defined as PS:<S,{STEM>
ASL: (alHopatch search list) defined as PAT: ,DIS: ,S,{S:
PEP>

2-18

Procedures

If the rebuilt software, after you have run some of your most important
applications with it, does not meet your expectations, do not go on to Step 7,
Installing the Rebuilt Software.

Step 7:
Installing the Rebuilt Software
As you install the rebuilt software, you will be copying files into the directory defined to be the installation directory for this product. If you are
using SYS: or another protected directory as your installation directory,
you will need to have your WHEEL or OPERATOR privileges enabled.

CAUTION
If the installation operation is actually going to change files
in the SYS: area, you must be careful to avoid interfering
with the work others are doing if your system is running
under timesharing.
Following is a print-out of what you would see on your terminal as you
completed the installation of the rebuilt TOPS-20-2060-V 4 with the command INSTALL, and rechecked on the success of the installation by asking
PEP a second time for INFORMATION:
PEP:>INSTALL (product nallle) TOPS-20-2060- 1•14
[Checking files for installing TOPS-20-2060- 1.'4] [OK]
[Backing UP files for TOPS-20-2060- 1.'4]
AP20: < AUTO PATCH • TOPS-20 >T206M4. REL. 1 = > AP20: : : AUTO PATCH • BACKUP:: T206M4. REL. 1 [OK]
AP20:<AUTOPATCH.TOPS-20>T20EX4.REL.l => AP20:<AUTOPATCH.BACKUP:>T20EX4.REL.l [OK]
PS: < SYSTEM :>EXEC. D(E. 3 =:> AP20: < AUTO PATCH • BACKUP :>D(EC. E)-(E. 1 [OK]
PS: < SYSTEM >BUGSTR I NGS. T>(T. 1 =:> AP20: < AUTO PATCH • BACKUP >BUGSTR I NGS. T>(T. 1 [OK]
PS: < SYSTEM :>MON I TR. EXE. 1 =:> AP20: < AUTO PATCH • BACKUP :>MON I TR. D(E. 1 [OK]
[Checf(pointing] [OK]
[Installing ne'A' files for TOPS-20-2060- 1.'4:l
AP20: < AUTO PATCH :>T206M4. REL. 40 =:> AP20: <: AUTO PATCH • TOPS-20 :>T206M4. REL. 2 [OK]
AP20: <: AUTO PATCH :>T20EX4. REL. 9 =:> AP20: <: AUTO PATCH • TOPS-20 :>T20D(4. REL. 2 [OK]
AP20: <: AUTO PATCH :>EXEC. EXE. 1 =:> PS: <: SYSTEM :>EXEC. E)-(E. 2 [OK]
AP20: < AUTOPATCH:>BUGSTR I NGS. TXT. 1 =:> PS: < S,{STEM:>BUGSTR I NGS. n{T. 2 [OK]
AP20: <: AUTO PATCH :>MON I TR. D(E. 1 =:> PS: <: SYSTEM :>MON I TR. D(E. 2 [OK]
[Checf(pointing] [OK]
PEP:>INFORMATION (about product nallle) TOPS-20-2060- 1.'4
TOPS-20-2060- 1.'4 'A'as successful b INSTALLed
Patches retrieved through patch tape 2
Current installed files:
PS:<SYSTEM:>EXEC.D(E.2 se9uential checf(suII1737352, version 4(567)
PS:<SYSTEM>BUGSTRINGS.nn.2 se9uential checf(suI11216046
PS:<:SYSTEM:>MONITR.EHE.2 se9uential checf(suIll 60334, version 4(3370)
Updated files (read}' to be installed):
None
Backup files:
AP20:<:AUTOPATCH.BACKUP>EXEC.El-(E.l se9uential checf(suII1765667, version 4(560)
A P 2 0 : <: AU TO PATCH • B A CK UP> BUG S T R I N GS • T l{T • 1 s e 9 U e n t i a 1 c h e c f(s U III 5 1 1 2 2 0
AP20:<:AUTOPATCH.BACKUP:>MONITR.EXE.l se9uential checf(suIll 647550, l.lersion 4(3247)
Logical nallles:
PAT: (autopatching directof}') defined as AP20:<:AUTOPATCH>
DIS: (distribution directon) defined as AP20:<:AUTOPATCH.TOPS-20>
BAK: (bacf(up directof}') defined as AP20:<AUTOPATCH.BACKUP>
INS: (installation direston) defined as PS<SYSTEM>
ASL: (autopatch search list) defined as PAT: ,DIS: ,SYS:
PEP>E}(IT
$

Procedures

2-19

A successful installation accomplishes three tasks:
• It establishes a backup copy of the current version of the product you are
au topatching.
• It moves the rebuilt product into the installation directory.
• It moves the patched input files into the product's distribution directory.

NOTE
If the installation procedure fails, however, because of a system failure, or because of an error such as ((disk quota exceeded," you will need to correct the error and repeat the
INSTALL command.

2.2.3 Restoring an Installed TOPS-20 Product
If, for some reason, an installed software product does not perform to your
expectations and the previous version is more in keeping with your particular requirements, you can revert to the previous version by using the
RESTORE command to PEP.
@ENA6LE (CAPABILITIES)
$PEP
[PEP version 1(£14)]
What is the autopatchilH directon? AP20:<AUTOPATCH>
PAT: defined as AP20:<:AUTOPATCH>
[Initializing ••• J (Reading data base ••• ) [OK]
PEP>RESTORE (product nallle)

TOPS-20-20GO-~)4

[Checfdng files for restoring TOPS-20-20GO-I,J4] [OK]
[ChecKpointing] [OK]
[Restoring files for TOPS-20-20GO-I,J4]
AP20: <: AUTO PATCH • BACKUP >T20GM4. REL. 1 = > AP20: <: AUTO PATCH • TOPS-ZO :>TZOGM4. REL. 3 [OK]
APZO: <: AUTO PATCH • BACKUP :>TZOE)-(4. REL. 1 =:> AP20: <: AUTO PATCH • TOPS-ZO >T20EH4. REL. 3 [OK]
APZO: -( AUTO PATCH • BACKUP >E){EC. EHE. 1 = > PS: < SYSTEM )E)o(EC. E){E. 3 [OK]
APZO:<AUTOPATCH.BACKUP>BUGSTRINGS.Dn.3 => PS:-(SYSTEM>BUGSTRINGS.THT.3 [OK]
AP20:<AUTOPATCH.BACKUP>MONITR.E)-(E.l =) PS:<SYSTEM>MONITR.E)-(E.3 [OK]
[ChecKpointing]
[OK]
PEP>EHIT
$

See Section 3.1.1 for a complete description of the RESTORE command.

2-20

Procedures

Contents

Chapter 3

Page

Reference
3.1

The Patch Executive Program . . . . . . . . .

3-1

PEP Commands . . . . . . . . . . . .
PEP Messages and Recovery Procedures

3-2
3-11

3.1.1
3.1.2
3.2

System Programs Used with Autopatch

3-23

BACKUP and DUMPER.
Batch . .
MAKLIB . . . . . . . .
PEPB . . . . . . . . . .

3-23
3-24
3-24
3-24

3.2.1
3.2.2
3.2.3
3.2.4
3.3
3.4

Disk Directories and Logical Names Used with Autopatch
Files Used with Autopatch. . . . . . . . . . . . . . . .
3.4.1
3.4.2
3.4.3
3.4.4

3-24
3-25
3-25
3-25
3-26
3-27

Chapter 3
Reference

3.1

The Patch Executive Program
PEP is a multi-function control program to carry out the Autopatch operation on TOPS-lO and TOPS-20. It provides a single interface to manage
the details of automatic software patching. Among its advantages are
these:
• It reduces the error possibilities inherent in manual patching.
• It requires only a single command to initiate the patching operation.
• It provides a convenient mechanism for installing updated software.
• It provides, as well, a simple means of reverting to the previous software
version.

These are the highlights of PEP's responsibilities in the automatic patching
operation:
• It maintains a data base of patch and software status information.
• It generates the indirect files required by the batch job that applies
patches and rebuilds the software components of a product.
• It performs consistency checks on Autopatch-related files and verifies
that the files required by the batch job are in place before allowing the
batch job to run.

Run PEP as you would any system program. On a TOPS-IO system type

in response to the system prompt.

3-1

On a TOPS-20 system type
@PEPm

in response to the system prompt.
If the logical name PAT: is already defined for your job, PEP assumes that
the definition specifies the autopatching directory. If the logical name PAT:
is not defined, PEP prompts with the question
What is the autopatchin9' directon'?

Respond by typing the structure and directory you are using for the autopatching directory. PEP will then use this definition to define the logical
name PAT:.

NOTE
If your job has the logical name PAT: defined, and the definition does not identify the autopatching directory, you will
have to delete that definition before you can run PEP successfully.
PEP then performs an initialization operation during which it processes the
product description file (file type .PDF) in the autopatching directory. If
this file cannot be accessed, PEP will terminate with a CBM error. (See
Section 3.1.2 for a description of this error and the recovery procedures.) At
this time, PEP also reads the data base file it maintains.
Following a successful initialization, PEP is ready to process commands. If
you have no products SELECTed for autopatching, PEP will prompt you to
declare your autopatchable products. You will not be able to enter the full
set of PEP commands until you have SELECTed at least one product.

3.1.1

PEP Commands

You can type a question mark after the PEP prompt to get the list of valid
PEP commands. Also, you can get the list of valid arguments for a command by typing a question mark after the command name. For example, if
you type a question mark after the PEP prompt, PEP prints the following:
PEP>? one of the follol,Jin9':

AUTO PATCH
INFORMATION
SETUP

BUILD
INSTALL
SUMMARY

DESELECT
RESTORE

E}<IT
RETR I EtTIE

HELP
SELECT

When typing commands to PEP, you do not need to give the full command
name. You can abbreviate the command name, or you can use the recognition feature of PEP. When abbreviating the PEP command, type only
enough characters to make the specific command unique. Usually, the first
three letters are sufficient to distinguish one command from another. To
give a command using the recognition feature of PEP, type a portion of the

3-2

Reference

command, and press the ESCape key. Depending on where in the command
you press the ESCape key, PEP responds with one of the following:
1. The remainder of the command name and any guidewords in
parentheses.
2. The guideword in parentheses.
3. The default value for the next argument.
The guidewords tell you the type of argument PEP is expecting you to type
next.
If you press the ESCape key before you enter enough characters to make
the command unique, PEP rings the terminal bell. At this point, type a
question mark to see the choices you have. Then furnish the characters
needed to make the command complete.
You can also use recognition input when typing arguments to the PEP
commands. If you make a typing error, PEP responds with a question mark.
If you type a [CTRL/ H) at this point, PEP retypes the correct portion of the
command. You must then retype the portion of the command that was
incorrect.
You can mix abbreviated and recognition input in the same command line.
This method requires less typing, so you are less likely to make a mistake.
Use abbreviated input for the parts of the command you know, and use
recognition for the parts of the command you are uncertain of.

AUTOPATCH
Function
The AUTOPATCH command performs three functions:
• updates the PEP data base by processing all of the patch directory files
(RETRIEVE processing)
• generates the indirect command files needed for the batch job to do the
patch and build operation (SETUP processing)
• verifies that all of the required files are in place and that they are at the
required revision level (BUILD processing)
In other words, the A UTOPATCH command performs the same operations
as the sequence of the RETRIEVE, SETUP, and BUILD commands. The
AUTOPATCH command is the recommended command for applying the
patches and rebuilding the product.
Format
AUTOPATCH (product name) product([U)
where product is the name of any product that you have SELECTed to be
autopatchable at your site

Reference

3-3

AUTOPATCH (Cont.)
or
AUTOPATCH * m
where * indicates that you want to patch all of the products you have
SELECTed at your site

BUILD
Function
The BUILD command initiates the patch-and-rebuild operation for a product by verifying that all files required by the batch job are in place and are
at the correct revision level. Before BUILD processing can begin, the product must have been SETUP. When the BUILD command completes success'fully, you can then SUBMIT the batch control file for the product, which
will apply the patches and rebuild the product components.
Format
BUILD (product name) productm
where product is the name of any product that you have SELECTed to be
autopatchable at your site
The following example shows the use of the BUILD command to verify that
everything is in order to patch and rebuild APLSF-IO.
PEP>BUILD (product naMe) APLSF-l0-V2
[ChecKin~ files for buildin~ APLSF-l0-t.12]
[OK]
[To patch and rebuild APLSF-l0-t.12 t issue the ITlonitor COITIlTland • ~.]
SUBMIT DSKP:APL1S2.CTL[7tG]/TIME:l:00:00/RESTART
[ChecKpointin~]
[OK]

PEP>

DESELECT
Function
The DESELECT command removes from your site's autopatchable product
list the name of a product that you had previously SELECTed to patch.
DESELECTing a product will also delete all patch history information for
that product from the PEP data base. Therefore, you should use this command with caution. Once DESELECTed, the product cannot be autopatched
again until you set up the product distribution and installation directories
with the distributed (field-image) version of the product files and use PEP
to SELECT the product.

3-4

Reference

Format
DESELECT (product name) productffiD)
where product is the name of any product that you have SELECTed to be
autopatchable at your site
The following example shows the use of the DESELECT command to remove APLSF-10 from your site's list of autopatchable products. Because
this action also deletes from the PEP data base the patch history for this
product, PEP asks for confirmation before completing the command.
PEP)DESELECT (product naMe) APLSF-l0-V2
I..DDH DESELECTin~ I,•.!ill destro}' the patch histor}' of APLSF-l0-1.12
Do }'OU 1"lant to continue? YES
[APLSF-l0-1.12 relTlol.led frolTl the list of SELECTed products]
[Checkpointin~]
[OK]
PEP>

EXIT
Function
The EXIT command allows you to exit from the PEP program and to return
to monitor level.
Format
EXIT (from program)ffiD)
Example
PEP >E}-{I Tllitl)

HELP

Function
The HELP command prints a paragraph of text about the subject you specify as the keyword.
Format
HELP (with subject name) keywordffiD)
where keyword is usually any valid. PEP command; it can, however, be a
term other than a command.
To get a list of the subjects for which you can get an explanation or description, use a ? as the keyword.

Reference

3-5

INFORMATION
Function
The INFORMATION command displays the current status of an autopatchable product as well as the status of the files and disk directories associated
with that product.
The command lists the following:
• current installed files, with their locations, checksums, edit levels, and
version numbers
• updated files
• backup files
• defined logical names
Format
INFORMATION (about product name) productru
where product is the name of any autopatchable product that you have
SELECTed to be autopatchable at your site

INSTALL
Function
The INSTALL command places the updated (patched) version of a product
into the installation directory (usually defined to be SYS:). It also copies the
patched input files for the product into the distribution directory. This command, before superseding the previous version with the patched version,
creates backup copies of both the input and the executable files for the
product and places these files in the backup directory you have created.
This backing-up action allows you to revert later to the old version if you so
choose. (See the RESTORE command.)
Before you can INSTALL a product, the batch job that applies the patches
and rebuilds the product components must have completed successfully.
Once you type the INSTALL command, the INSTALL processing must be
allowed to complete; otherwise files associated with the product you are
patching would be left in an indeterminate state.
If an error occurs, or there is a system failure, and the INSTALL processing
did not complete, correct the error and reissue the INSTALL command.
Format
INSTALL (product name) productru
where product is the name of any product that you have SELECTed to be
autopatchable at your site

3-6

Reference

RESTORE
Function
The RESTORE command allows you to return to the previous version of the
software product that you have patched and installed. That is, you can undo
the last INSTALL procedure if for any reason the patched software is unsatisfactory to you. This command restores the product input files found in
the distribution directory and the executable files found in the installation
directory to their state prior to execution of the most recent INSTALL
command.

NOTE
It is possible to RESTORE only the previous version of the
software. Multiple backup copies are not maintained.

The RESTORE processing must be allowed to complete; otherwise files associated with the version of the product you are reverting to would be left in
an indeterminate state.
If an error occurs, or there is a system failure, and the RESTORE processing did not complete, correct the error and reissue the RESTORE command.
Format
RESTORE (product name) productOOJ
where product is the name of any product that you have SELECTed to be
autopatchable at your site

RETRIEVE
Function
The RETRIEVE command transfers information about the patches for the
SELECTed product(s) from the patch directory files (file type .DPD) to the
PEP data base in the autopatching directory. When the command completes, it signals that the patches for the products you have SELECTed
have been retrieved and are ready for processing.
Format
RETRIEVE (patch entries for all SELECTed products)OOJ

NOTES
The RETRIEVE command can obtain data only for those
products that have been SELECTed.
Every time you receive a new patch tape, you must do
RETRIEVE processing to enter the data about the new
patches into the PEP data base.

Reference

3-7

RETRIEVE (Cont.)
Example 1
This example shows the use of the RETRIEVE command. In this case,
APLSF-10-V2 was the only SELECTed product and the only patch directory file in the autopatching directory was from patch tape 1.
PEP>RETRIEIJE (patch entries for all SELECTed products)
[ Pro c e s sin gin form a t ion fro ITI pat c h tap e 1]
[Reading patch directon' file] [OK]
[23 patches retrie\)ed for APLSF-l0-1.12]
[ChecKpointing]

[OK]

PEP>

Example 2
This example also shows the use of the RETRIEVE command. However,
this site has declared two products, APL-20-V2 and TOPS-20-2060-V4, to
be autopatchable. Since the autopatching directory contains the patch directory files from patch tape 1 and patch tape 2, the RETRIEVE command
causes PEP to obtain patch information for both these products from both
patch tapes.
PEP>RETRIEIJE (patch entries for all SELECTed products)
[Processing inforlTlation frolTI patch tape 1]
[Reading patch directon' file] [OK]
[20 patches ret rie\,led fo r APL-20-1.12]
[32 patches retrieved for TOPS-20-20GO-lJa]
[Processing inforlTlation frolTI patch tape 2]
[Reading patch directory file] [OK]
(7 patches retrie\}ed fro APL-20-1.12]
[al patches ret rie\}ed fo r TOPS-20-20GO-I.la]
[ChecKpointing] [OK]
PEP>

Example 3
'rhis example shows that once patch data has been RETRIEVEd from a
patch directory file, PEP will not need to process the file again.
PEP>RETRIEI.IE (patch ent ri es fo r all SELECTed products)
[P roc e s sin gin for ITI at ion fro ITI pat c h tap e 1]
[Patches for all SELECTed products already processed frolTI this
"tape]
[ChecKpointing]
PEP>

3-8

Reference

[OK]

SELECT
Function
The SELECT command allows you to declare the products that you want to
be autopatchable at your site. It also allows you to define the disk directories associated with each product.
Before PEP adds to its list of autopatchable products the product you have
SELECTed, it verifies that all of the associated component input files and
control files are available for the products, that they are in the correct
directories, and that each file has the expected version number and
checksum.
Format
SELECT (product name) productm
where product is the name of the product that you are declaring to be
autopatchable at your site

NOTES
1.

Once you SELECT a product, it is permanently
SELECTed, so that you do not need to SELECT it again.

If you change your mind about patching a product, refer
to the DESELECT command for information on removing the product.

A product must be SELECTed before you can reference it
in any other PEP command.

Example I

(TOPS-IO)

The following example shows the use of the SELECT command to declare
that APLSF-IO is autopatchable. This example also demonstrates that, if
necessary, you may set up your disk directories according to your own local
conventions rather than using the directories suggested in Chapter 2.
PEP)SELECT (product naMe) APLSF-10-V2
What is the distribution directon' for APLSF-10-I.J2?
DSKB:[10,Sa,APLJ
DIS: def ined as DSKB: [10 ,sa ,APLJ
What is the bad~up directon' for APLSF-10-I.J2? DLD:
BAK: defined as OLD:[1 ,3J
What is the installation directory for APLSF-10-I.J2? SYS:
INS: defined as DSKB:[10,5277J,SSL:[1,aJ
PEP)

Reference

3-9

SELECT (Cont.)
Example 2

(TOPS-20)

The following example shows the use of the SELECT command to declare
that APLSF-20 is autopatchable. This example also demonstrates that, if
necessary, you may set up your disk directories according to your own local
conventions rather than using the directories suggested in Chapter 2.
PEP>SELECT (product naMe) APLSF-20-V2
What is the distribution directory for APLSF-20-1.12? PS:(APL>
DIS: defined as PS:(APL)
What is the bacKup di recto n' fo r APLSF-20-1.12?
PS:(AUTOPATCH.BACKUP>
BAK: defined as PS:(AUTOPATCH.BACKUP)
What is the installation directory for APLSF-20-1)2? SYS:
INS: defined as SYS:
PEP>

SETUP
Function
The SETUP command creates the indirect command files needed to apply
the patches to a product. PEP will generate commands to apply those
patches necessary to upgrade the product from its current state to the latest
revision level.
SETUP processing must be complete before the batch job that applies the
patches can run.
Format
SETUP (product name) productru
where product is the name of any product that you have SELECTed to be
autopatchable at your site
This example shows the use of the SETUP command to prepare the necessary command files required to apply the patches to APLSF-IO.
PEP>SETUP (product naMe) APLSF-l0-V2
[Setting UP APLSF-l0-1)2 for patch and rebuild]
[23 patches ""dll be applied to APLSF-l0-1.12]
[Checkpointing] [OK]
PEP>

SUMMARY
Function
The SUMMARY command displays on your terminal a list of the patches
available for a given product.

3-10

Reference

Each patch will have a status associated with it. The patch status will be
one of the following:
retrieved

A record of the patch has been transferred from the patch directory file to the PEP data base and the patch is ready for
processing.

selected

The patch is selected to be applied to the product during the
next patch and rebuild operation. During SETUP processing,
command files are generated to apply all ~~selected" patches.

applied

The patch has been applied to all the product input and executa'ble files in the autopatching directory. The batch job that does
the patch and rebuild operation has completed successfully.

installed

The patch has been applied to all the product input files in the
product distribution directory and to all the product executable
files in the product installation directory. ~~Applied" patches
become ~~installed" when you INSTALL the product. All
patches with an ~~installed" status will be removed when you
RESTORE a product.

permanent The patch was applied previous to the last installation of the
product. If a patch has a permanent status, it will not be removed when you RESTORE the product.
Format
SUMMARY (of the patches to product name) productffiTIl
where product is the name of any product that you have SELECTed to be
autopatchable at your site

3.1.2 PEP Messages and Recovery Procedures
In this section you will find an alphabetized listing of three-letter error
message codes, along with the error message strings and the suggestions
for recovering from these errors.
PEP issues two types of error messages. Warning messages are preceded by
the % symbol. When these errors occur, processing will still continue. Fatal
errors are preceded by the? symbol. When a fatal error occurs, the processing of the command is terminated. Some fatal errors will also terminate the
PEP program.

AEM

Address Entry Missing

Under normal conditions, this error should not occur. It indicates that an
internal consistency check has failed.
In most cases you will not be able to correct this problem. It should be
reported to your Software Specialist.

Reference

3-11

BJF

Batch Job Failed

This error indicates that the batch job that applies the patches and rebuilds
the software components of the product did not complete successfully. As a
result, the product cannot be installed.
In order to detennine why the batch job failed, you will have to look at the
.LOG file that was generated. A sample .LO.G file is included on the patch
tape. These .LOG files show the files that were used or created during the
batch jobs. By comparing the corresponding checksums for each file shown
in the two .LOG files, you will be able to determine the differences. After
you have corrected the problem, you must run PEP and give the
AUTOPATCH command before you SUBMIT the batch job again.

CBL

Cannot Build List

·Under normal conditions, this error should not occur. It indicates that an
internal data structure could not be successfully generated.
In most cases you will not be able to correct this problem. It should be
reported to your Software Specialist.

CBM

Cannot Build Master List

This error occurs during PEP initialization. It indicates that the product
description file (file type .PDF) could' not be read, and, as a result, PEP
could not build some of the data structures it requires.
This error will usually be preceded by a COF error message that specifies
why the file cannot be read. Usual causes of this error are failure to install
the product description file in the autopatching directory or failure to provide PEP with the correct directory specification for the autopatching directory. To correct this situation, verify that the .PDF file is in the autopatching directory, that you have read access to the file, and that the logical
name PAT: defines the autopatching directory. Normally, you do not have
to define PAT: yourself. PEP prompts you for the information and then
defines the logical name. However, if you have entered an incorrect directory, you will have to redefine PAT: yourself.

CBP

Cannot Build Product

This error indicates that the BUILD command cannot be completed successfully. Therefore, the operation is terminated.
This error will usually be preceded by other error messages indicating specifically what is wrong. This error usually occurs when some of the files
required to patch and build the product cannot be accessed. In this case, the
preceding COF errors identify the specific files. The problems with each file
will have to be corrected and then the BUILD command can be reentered.

CCD

Cannot Checkpoint Data Base

This error indicates that PEP cannot update the data base file in the autopatching directory. Under normal situations, this error should not occur.

3-12

Heference

This error could indicate that there is no available disk storage in the
autopatching directory. You may be able to free up some space by deleting
unnecessary files. If the structure is full, you may have to delete files from
additional directories. Under TOPS-20, deleted files will have to be
EXPUNGEd. Once disk space is available, run PEP, and enter the last
command again.

CCF

Cannot Close File

This error indicates that the specified file could not be closed.
This error message will give the reason why the close failed. This condition
will have to be corrected, and then the last PEP command can be reentered.
This error might also indicate a system problem.

CCJ

Cannot Complete Batch Job

This error will appear in the .LOG file of the batch job that applies patches
and rebuilds the software components of a product. It will usually be preceded by additional error messages specifying the problems.
After you have corrected the problem, you must run PEP and give the
AUTOPATCH command before you SUBMIT the batch job again.

CCR

Cannot Complete RETRIEVE

This error indicates that the RETRIEVE command cannot be completed
successfully. It is produced when an internal consistency check fails; therefore the operation is terminated.
In most cases you will not be able to correct this problem. It should be
reported to your Software Specialist.

CCS

Cannot Complete SETUP

This error indicates that the SETUP command cannot be completed successfully. Therefore, the operation is terminated.
This error will usually be preceded by other error messages indicating specifically what is wrong. These problems will have to be corrected and then
you can reenter the SETUP command.

CDC

Checkpointed Data Base Corrupt

This error occurs when PEP finds illegal data in the internal data base file
PEPCKP.PDB. Normally, this error should not occur.
If the data base file has been damaged, there may be no easy way to correct
the situation. Simply getting an old copy of the file off your backup recovery tapes is not recommended, since the old copy may not reflect the current state of your system software and patches. However, you can always
recover by deleting the damaged copy of the file and then SELECTing all
the autopatchable products again. You will also have to set up your product
distribution and product installation directories with the distributed (fieldimage) versions of the autopatchable software. If all the patch files are still

Reference

3-13

CDC (Cont.)
in the autopatching directory, you can use the AUTOPATCH command to
update your software to the current patch level. If all the patch files are not
in the autopatching directory, you will have to restore them from the patch
tape before giving the AUTOPATCH command to PEP.

CDF

Cannot Delete File

This error indicates that the specified file could not be deleted.
The error message typed at your terminal will give the reason why the
deleted file failed. For example,
, %CDF Cannot delete file PAT:APL1S2.BCF (Protection violation)
This condition will have to be corrected, and then the last PEP command
can be reentered. This error might also indicate a system problem.

CDL

Cannot Define Logical Name

This error could occur while you are specifying a disk directory for PEP.
The error indicates that the specified directory could not be used to define a
logical name.
The error message will give the reason why the definition is incorrect. This
will usually be due to a syntax error in your response. PEP then repronlpts
you, so that you may enter the definition correctly.

CEC

Cannot Enter Code

CGC

Cannot Get Checksum

This error indicates that PEP was unable to compute the checksum of the
file specified in the error message. The error is only a warning, and all
processing will continue.

CGV

Cannot Get Version

This error indicates that PEP was unable to compute the version of the file
specified in the error message. The error is only a warning, and all processing will continue.

CID

Checksum Is Different

This error is produced while PEP is verifying the sequential checksums of
the files that will be used during the autopatch operation. If a discrepancy
is found, a message such as
%CID Checksum of SYS:MAKLIB.EXE is different than expected
expected 251204 but found 353076

3-14

Reference

is typed on your terminal. This error is only a warning and all processing
continues.
However, since the checksum of the file you are using is different from the
expected checksum, the operation may not complete as expected. You
should try to determine why the checksums are different, before you continue. Most likely, they will be different because you are using an outdated
copy of the file, or the file has been locally modified. If the file has in fact
been modified, you should determine how these changes will affect the
autopatch operation.

CIP

Cannot INSTALL Product

This error indicates that the INSTALL command cannot be completed successfully. Therefore, the operation is terminated.
This error will usually be preceded by other error messages indicating specifically what is wrong. This error usually occurs when some of the files
. being backed up or replaced cannot be accessed. In this case, the preceding
COF errors identify the specific files. The problems with each file will have
to be corrected, and then the INSTALL command can be reentered.

COF

Cannot Open File

This error indicates that a specific file cannot be accessed. The message
that is typed will indicate whether the file needs read or write access and
why the attempt to access it failed. For example,
%COF Cannot open file DIS:APL1S2.REL for input (File not found)
The common causes of this error are ~~file not found" or ~~protection violation." To correct these situations you will have to copy the missing file to
the right directory or change the protection code. Sometimes you will get a
protection violation when you try to create a file in SYS: or another protected directory. In this case, you will need to have OPERATOR or WHEEL
privileges enabled before you can successfully complete the operation.

CPF

Cannot Process Batch Status File

Under normal conditions, this error should not occur. It indicates that the
status file that was created during the batch job cannot be processed by
PEP.
As a result of this error, the PEP data base cannot be updated. Therefore,
you should run PEP and give the AUTOPATCH command for this product.
Then SUBMIT the batch control file to patch and rebuild the product again.

CPI

Cannot Provide Information

This error indicates that the INFORMATION command cannot successfully
be completed and is therefore terminated.
Preceding error messages will give the specific problems.

Reference

3-15

eRC

Cannot Read Checkpointed Data Base

This error occurs during PEP initialization and indicates that the internal
data base file cannot be read. This error will usually be preceded by other
error messages identifying the specific problem.

eRD

Cannot Read Patch Directory

This error indicates that the specified patch directory file (file type .DPD)
cannot be read. Under normal conditions, this error should not occur.
In most cases you will not be able to correct this problem. It should be
reported to your Software Specialist.

CRE

Cannot Read Product Description Entry

This error indicates that the specified product description file (file type
.PDF) cannot be read. Under normal conditions, this error should not occur.
In most cases you will not be able to correct this problem. It should be
reported to your Software Specialist.

CRF

Cannot Read File

This error indicates a data error while trying to read the specified file.
Since this error occurs during the actual transfer of data, you may be able
to reenter the command and have the data transferred without error. This
error could be symptomatic of global system problems.

CRP

Cannot RESTORE Product

This error indicates that the RESTORE command cannot be completed successfully. Therefore, the operation is terminated.
This error will usually be preceded by other error messages indicating specifically what is wrong. For example, if the product was previously
RESTOREd, it cannot be RESTOREd again. This error usually occurs when
some of the files being copied cannot be accessed. In this case, the preceding
COF errors identify the specific files. The problems with each file will have
to be corrected, and then the RESTORE command can be reentered. You
will not be able to RESTORE a product while there is an active batch job to
patch and rebuild the product. This will prevent you from changing any of
the files that the batch job may be using.

CSP

Cannot SELECT Product

This error indicates that the SELECT command cannot be completed successfully. Therefore, the operation is terminated.
This error will usually be preceded by other error messages indicating specifically what is wrong. This error usually occurs when some of the files in
the product distribution directory or product installation directory are
missing or cannot be accessed. In this case, the preceding COF errors identify the specific files. The problems with each file will have to be corrected,
and then the SELECT command can be reentered.

3-16

Reference

CWF

Cannot Write File

This error indicates a data error while trying to write the specified file.
Since the error occurs during the actual transfer of data, you may be able to
reenter the command and have the data transferred without error. This
error could be symptomatic of global system problems.

DAD

Directory is Already Defined

This error occurs while you are defining a disk directory for PEP. This error
indicates that you had previously defined that directory for another use.
PEP then reprompts you, so that you may enter a new definition.

DDH

DESELECTing Will Destroy History

This error warns that DESELECTing the product will delete all status and
patch history information from the PEP data base.
If you complete this command, the product will no longer be autopatchable.
In order to make the product autopatchable again, you will have to set up
the product distribution directory and product installation directory with
the distributed versions of the software components and then run PEP and
SELECT the product again.

DEF

Delete Table Entry Failed

FAM

Files Appear to be lYlissing

This error is produced when PEP cannot access a file that was created
during the patch and build patch job. Normally, this error should not occur.
This error will be preceded by a COF error for each file that cannot be
accessed. The COF error message will specify the file and the associated
problem. The best recovery procedure is to run PEP and enter the command
to AUTOPATCH that product. Then SUBMIT the batch job again.

FCW

Format of Checkpointed Data Base is Wrong

This error indicates that the data in the data base file is not in a format
that PEP can process. This error should not occur under normal conditions.
In most cases you will not be able to correct this problem. It should be
reported to your Software Specialist.

FNB

Files Not Backed Up

This error indicates that during the backup cycle of INSTALL processing,
not all files got backed up. There will be a preceding error message specifying each file that did not get backed up and the problem.
See error INC for possible recovery procedures.
Reference

3-17

FNR

Files Not Replaced

This error indicates that during the replace cycle of INSTALL processing,
not all files got replaced with their updated versions. There will be preceding error message specifying each file that did not get replaced and the
problem.
See error INC for possible recovery procedures.

IDL

Illegal Data in Line

Under normal conditions, this error should not occur. It indicates that a
PEP data file (e.g., patch directory file or product description file) contains
an incorrectly formatted entry.
In most cases you will not be able to correct this problem. It should be
reported to your Software Specialist.

IDT

Illegal Datatype

IFR

Initialization Failed for Reading

This error indicates that PEP was unable to perform the initialization required to read a specified file. In most cases, it means the file cannot be
accessed.
The usual cause of this error is that the specified file is not in the disk
directory that PEP expects it to be in. After verifying that the file is in the
correct directory and that you have read access to it, run PEP and try the
operation again.

INC

Installation Not Completed

This error indicates that INSTALL processing started, but it was terminated before it could complete successfully. This error will usually be preceded by other error messages specifying why the operation was
terminated.
This error usually occurs when disk quotas are exceeded, or disk storage is
exhausted during the file backup or replacement operation. If this is the
problem, you will have to provide additional disk storage before you can
continue. Often you do this by EXPUNGing deleted files from the directory
that is full. Once you obtain the additional disk storage, run PEP and
reenter the INSTALL command for the product. PEP will then complete the
operation.

3-18

Heference

JNF

Job Never Finished

This warning message indicates that, as far as PEP can determine, the
batch job that was SUBMITed to patch and rebuild the product has not
completed. It must complete before the updated software can be
INSTALLed.
If the batch job is still running or in the queue waiting to run, you will have
to let it complete before you can proceed. However, if the batch job is no
longer in the queue, you will have to run PEP and AUTOPATCH the product again. Then reSUBMIT the batch job.

MBI

Must Be INSTALLed

This error indicates that the last INSTALL operation for the product did
not complete successfully. As a result, the correct versions of the product
files may not be in the appropriate directories, and won't be until the
INSTALL operation successfully completes.
Before PEP will process any more commands for that product, you must
correct the problem that previously terminated the INSTALL and then run
PEP and reenter the INSTALL command for the product. PEP will then
complete the INSTALL operation.

MBR

Must Be RESTOREd

This error indicates that the last RESTORE operation for the product did
not complete successfully. As a result, the correct versions of the product
files may not be in the appropriate directories, and won't be until the
RESTORE operation successfully completes.
Before PEP will process any more commands for that product, you must
correct the problem that previously terminated the RESTORE and then
run PEP and reenter the RESTORE command for the product. PEP will
then complete the RESTORE operation.

NDF

No Patch Directory Found

This error indicates that no patch directory files were found in the autopatching directory. Therefore, no patches will be applied to any of the autopatchable products.
This error occurs when the patch directory files from the patch tape are not
transferred from the patch tape to the autopatching directory. Patch directory files have a file type of .DPD.

NFD

Null Files Descriptor

Reference

3-19

NPR

No Patches RETRIEVEd

This warning indicates that PEP has no patch information for the specified
product.
If patches have been distributed for that product, make certain that the
patch directory files (file type .DPD) have been copied from the patch tape
to the autopatching directory. There is one patch directory file for each
patch save set on the tape. Once you have copied these files to the autopatching directory, run PEP and issue the RETRIEVE command. All new
patch information for all autopatchable products will then be read from all
patch directory files and entered in the PEP data base.

NPS

No Product Specified

This error indicates that an incomplete command has been typed. The command requires you to specify the name of a product.
Retype the command specifying a product name. To see a list of valid product names, type the command followed by a question mark. For example,
AUTOPATCH ?

NTS

No HELP Topic Specified

This error indicates that an incomplete HELP command has been typed.
The command requires you to specify the name of a product.
Retype the command specifying a keyword. To see a list of valid keywords,
type the command followed by a question mark. For example,
HEL P '?

P AS

Product Already SELECTed

This error is only a warning and indicates that the product has previously
been SELECTed to be an autopatchable product, and it does not have to be
SELECTed again.
If you want to go through SELECT processing again (to redefine the disk
directories associated with the product), you will first have to DESELECT
the product.

PNB

Product Not Built

This error indicates that you have attempted an operation that first requires the product to be successfully built.
Before you can complete the current operation, you will have to use the
BUILD command to PEP to rebuild the product. The product will be rebuilt
when the batch job successfully completes.

3-20

Reference

PNI

Product Not INSTALLed

This error indicates that you have attempted an operation that first requires that product to be successfully INSTALLed.
Before you can complete the current operation, you will have to run PEP
and INSTALL the product.

PNS

Product Not SETUP

This error indicates that you have attempted an operation that first requires the product to be successfully SETUP. This error may also appear in
the batch .LOG file indicating that the product was not SETUP properly
before the batch control file was SUBMITted.
Before you can complete the current operation, you will have to run PEP
and enter the SETUP command to prepare the product to be patched and
rebuilt. Once you complete SETUP processing, you will need to give the
BUILD command to PEP before the batch job can be SUBMITted.

PPM

Prerequisite Patches Missing

This error occurs during RETRIEVE processing when you attempt to
retrieve patch information for a product from the current patch directory
file without having processed some of the previous patch directory files
containing patch information for that product. Before PEP will enter in its
data base any information about the latest set of patches for a product, a
record of all previously distributed patches must already be in the data
base. PEP obtains this information from the patch directory files (file type
.DPD) during RETRIEVE processing. As long as all the patch directory
files are in the autopatching directory, PEP will be able to obtain the information it needs. However, if some of the previous directories have been
deleted, this error could occur.
To correct this situation, copy the missing patch directory files from the
patch tape to the autopatching directory. Then run the PEP program and
retype the RETRIEVE command. (In general, you can delete a patch directory file from the disk once it has been processed by the RETRIEVE command. However, if you later SELECT a new product to be autopatchable,
you will need all previous patch directory files containing patch information for that product.)

RNC

RESTORE Not Completed

This error indicates that RESTORE processing started, but it was terminated before it could complete successfully. This error will usually be preceded by other error messages specifying why the operation was
terminated.
This error usually occurs when disk quotas are exceeded, or disk storage is
exhausted during the file-copying operaton. If this is the problem, you will
have to provide additional disk storage before you can continue. Often you
can do this by EXPUNGing deleted files from the directory that is full.
Once you obtain the additional disk storage, run PEP and reenter the
RESTORE command for the product. PEP will then complete the operation.
Reference

3-21

SIB

SETUP Will Interface with Batch Job

This warning message indicates that the SETUP operation you are about to
perform could interfere with the patch and rebuild batch job that you have
already SETUP for the product. Once you SETUP a product and initiate
BUILD processing, no additional processing can be done for that product
until its batch job completes. That way, none of the files used during the
batch job will be inadvertently modified.
If you have not already SUBMITted the batch job, you may proceed with
this SETUP without any problems. However, if you have SUBMITted the
batch job, you should cancel it or let it complete before you attempt to
continue with the current SETUP.

SSF

Symbol Table Search Failed

TEF

Table Entry Failed

Under normal conditions, this error should not occur. It indicates that an
internal data structure could not be successfully generated.
In most cases you will not be able to correct this problem. It should be
reported to your Software Specialist.

UDT

Unknown Datatypes

UHT

Unrecognized HELP Topic

This error indicates that an incorrect HELP command has been typed. The
keyword that you specified was not valid.
Retype the command specifying a valid keyword. To see a list of valid
keywords, type the command followed by a question mark. For example,
HELP?

UPL

Unrecognized Product Library

This error is provided as part of a consistency check during the processing
of patch directory files. It should seldom occur.
In most cases you will not be able to correct this problem. It should be
reported to your Software Specialist.

3-22

Reference

UPN

Unrecognized Product Name

This error indicates that an incorrect command has been typed.
Retype the command specifying a valid product name. To see a list of valid
product names, type the command followedl by a question mark. For
example,
AUTO PATCH ?

URC

Unrecognized Command

This error indicates that the command just typed is not valid.
Retype the command. To see a list of valid commands, type a question mark
in response to the PEP prompt. For example,
PEP>?

Remember, many commands (AUTOPATCH, BUILD, INSTALL,
RESTORE, RETRIEVE, and SETUP) will not be recognized until at least
one product has been SELECTed.

VID

Version Is Different

This error is produced while PEP is verifying the version numbers of the
.EXE files that will be used during the autopatch operation. If a discrepancy is found, a message such as
%VID Version number of SYS:MAKLIB.EXE is different than expected
expected 2A(67) but found 2A(21)
is typed on your terminal. This error is only a warning and all processing
continues.
However, since the version of the file you are using is different from the
expected version, the operation may not complete as expected.You should
try to determine why the versions are different, before you continue. Most
likely, they will be different because you are using an outdated copy of the
file, or the file has been locally modified. If the file has in fact been modified, you should determine how these changes will affect the autopatch
operation.

3.2 System Programs Used with Autopatch
3.2.1

BACKUP and DUMPER

The Autopatch tapes are distributed in BACKUP interchange format for
TOPS-IO and in DUMPER format for TOPS-20. You must run these utilities to retrieve all items from the patch tapes and place them in the proper
directories so that they are ac~essible to Autopatch.

Reference

3-23

On the patch tape are included control files that enable you to retrieve
easily only the needed files for the products you are patching. For the
BACKUP utility these are indirect command files. For the DUMPER
. utility, they are batch control files. The README documentation file will
identify these files.

3.2.2 Batch
Each autopatchable product is furnished its own Galaxy batch control file
for patching and rebuilding that software product. The file has been standardized so that you do not need to do any editing or further customizing to
make it run on a supported configuration.
The batch control file performs four sequential functions:
• It defines logical names for the directories associated with the product.
• It applies patches to the product input files.
• It rebuilds the software components of the product from the patched input
files.

• It creates a status file for PEP which signals the success or failure of the
batch job.
The batch job produces a log file which shows exactly what happened while
the batch job was running. It keeps a record of system. errors encountered in
the process, and therefore is a debugging aid. The patch tape contains a
corresponding log file (.Lnn) that you can print out and compare with your
batch log file. (The patch log file is included on the patch tape just for
information; it is not required as part of the Autopatch operation.)

3.2.3 MAKLIB
The MAKLIB utility is run as part of the batch job. It applies the patch files
to the product libraries as instructed by the indirect command files.

3.2.4 PEPB
PEPB is the Patch Executive Program for Batch. It is run as part of the
batch job that patches and rebuilds a software product. It is functionally
different from PEP. PEPB performs the initialization required for the batch
job and verifies the results.

NOTE
Use PEP, not PEPB, to interactively prepare a product for
autopatching.

3.3 Disk Directories and Logical Names Used with Autopatch
Each of the disk directories used by Autopatch has a logical name associated with it.
3-24

Reference

PAT: is the logical name defined for the autopatching directory
DIS: is the logical name defined for the product distribution directory
BAK: is the logical name defined for the backup directory
INS: is the logical name defined for the installation directory
ASL: is the logical name defined for the Autopatch search list, which is
further defined as PAT:,DIS:,SYS:.
The Patch Executive Program (PEP) handles the details of defining these
logical names, so that you do not have to define them explicitly yourself.
The INFORMATION command to PEP will show what logical name definitions have been established for a particular product.

3.4 Files Used with Autopatch
3.4.1

Files Supplied on the Distribution Tapes of Autopatchable
Products

REL Libraries (file type .REL)
These are input files that are used to build the executable files of the
product. Patches are applied to these REL libraries. You copy these
files to the product distribution directory when you prepare your system for autopatching.
Link Command Files (file type .LNK)
These are command files used by Link to build the executable files of
the product from the REL libraries for the product. You copy these
files to the product distribution directory when you prepare your system for autopatching.

3.4.2 Files Supplied on the Patch Tape Used to Install Autopatch
INSTAL.DOC
This file is provided in the Installation Save Set of the patch tape and
gives additional information needed to prepare your system for
autopatching.
DUMPER Distribution Control Files (file type .DDC) (TOPS-20 only)
These files are provided in the Installation Save Set of the patch tape.
You can use these files to help you set up the product distribution
directory for an autopatchable product. Each file runs under batch
and transfers from the product distribution tape to the product distribution directory those files needed for autopatching. INSTAL. DOC
describes the use of these files.
BACKUP Distribution Control Files (file type .CCL) (TOPS-IO only)
These files are provided in the Installation Save Set of the patch tape.
You can use these files to help you set up the product distribution
directory for an autopatchable product. Each file, an indirect command file for BACKUP, transfers from the product distribution tape
to the product distribution directory those files needed for autopatching. INSTAL.DOC describes the use of these files.

Reference

3-25

3.4.3 Files Supplied on the Patch Tape Used for Patching
README.nnn
One of these files is included with each patch save set on the tape. The
file type .nnn specifies the number of the patch set. The number of the
current patch set will be the same as the patch tape number. Each
README file contains important information about the files in that
patch set.
TOPS-lO Patch Retrieval Files (file types .Ann and .Pnn)
These files are included in the current patch save set for each autopatchable product. They are indirect command files for BACKUP. You
can use the .Pnn file to transfer from the current patch save set to the
autopatching directory all those files required to apply the current set
of patches to the product. Or, you can use the .Ann file to transfer
from ALL the patch save sets to the autopatching directory those files
required to apply all patches to the product. The README documentation file will describe the use of these files.
TOPS-20 Patch Retrieval Files (file types .Ann and .Pnn)
These files are included in the current patch save set for each autopatchable product. They are batch control files that run DUMPER.
You can use the .Pnn file to transfer from the current patch save set to
the autopatching directory all those files required to apply the current
set of patches to the product. Or, you can use the .Ann file to transfer
from ALL the patch save sets to the autopatching directory those files
required to apply all patches to the product. The README documentation file will describe the use of these files.
Patch Directory File (file type .DPD)
Each patch save set has a patch directory file that describes all the
patches contained in the save set. You must transfer this file from the
tape to your autopatching directory. PEP will process the entries in
this file when it executes the RETRIEVE command.
Patch and Build Batch Control Files (file type .CTL)
Each autopatchable product has its own patch and build patch control
file. When SUBMITted to the Galaxy Batch System, this control file
will patch and rebuild all the components of the product. Each .CTL
file has been standardized so that you do not need to do any editing or
further customizing to make it run on a supported configuration.
These files are provided in the Installation Save Set of the patch tape.
You copy these files to the autopatching directory when you prepare
your system for autopatching.
Product LOG Files (file type .Lnn)
A LOG file is provided for each autopatchable product. It shows a
successful patch and rebuild operation. These LOG files are provided
only as a reference tool so that you can compare them with your LOG
files.

3-26

Reference

Edit Description Files (file type .Dnn)
The edit description file on each patch tape is a documentation text
file that can be printed out if you wish to see it. (Unlike README and
INSTAL.DOC, which have to be printed out and used in conjunction
with the manual, the use of the edit description file is not mandatory.)
This file provides the user with symptom, diagnosis, and cure information, basically the same kind of information you would find in a
reply to an SPR.

3.4.4 PEP Data Files
These files are used by the Patch Executive Program. Unless otherwise
indicated, these files are created and maintained by PEP. You should not
al ter or delete them.
Product Description File (file type .PDF)
This file describes each autopatchable product. It is distributed in the
Installation Save Set of the patch tape, and you copy it to the autopatching directory when you prepare your system for autopatching.
PEP Data Base (file type .PDB)
PEP creates and maintains this data base file containing the patch
history and status of each product that you have SELECTed for
autopa tching.
Patch Command Files (file type .MKL)
PEP generates one of these command files for each autopatchable
product. Each file contains MAKLIB commands for applying patches
to the product REL libraries.
Batch Communication Files (file type .BCF)
PEPB generates one of these files at the completion of the patch and
rebuild batch job. These files contain data for PEP about the status of
the batch job.

Reference

3-27

Index
NOTE
In this index we refer to some of the complementary files on
tape, chiefly INSTAL.DOC and README.

? (question mark)

with HELP, 3-5
with INFORMATION, 3-6
with PEP, 3-23
Abbreviated command input, 3-2
ACC.SYS
see REACT program
Advantages of Autopatch, 1-3, 3-1
AP20:, 1-6,2-11,2-15
Applying patches
see Patching and rebuilding a product
ASL:, 3-25
Automatic patching
definition, 1-1
TOPS-10 products,2-5 to 2-9
TOPS-20 products, 2-15 to 2-18
Autopatch
advantages, 1-1,3-1
directory-naming conventions, 1-4, 1-6,
2-1, 2-4, 3-24
files used in,1-6, 3-25 to 3-27
kit, 1-2
operator qualifications, 1-3
overview, ch. 1
search list, 3-25
system requirements, 1-2
<AUTOPATCH.BACKUP> = product
backup directory, 2-12
AUTOPATCH command to PEP, 2-7, 2-17,
3-3

Autopatchable products,
declaring, 2-4, 2-14
see also SELECT command
defined, 1-1
for listing, see INSTAL. DOC and
README
Autopatching directory, 1-5, 1-6, 2-1
BACKUP, 1-6, 2-6, 3-23
control files (.CCL), 2-4, 3-25
indirect command files, 3-26
interchange format, 3-23
prompt, 2-6
Backup files, 1-10, 2-18; Figure 1-7 A
BAK:, 3-25
BATCH.CMD file, 2-7, 2-11, 2-17
Batch communication files (.BCF), 3-27
Batch control (status) files (.CTL), 1-8, 2-4,
2-7, 3-26
Batch log file, 3-24
Batch processing, Figures 1-5 and 1-6
TOPS-10, 2-7
TOPS-20, 2-17
BUILD command to PEP, 1-8,2-11,3-4
Building (creating) disk directories, 1-6, 2-1
to 2-5
Checkpointing data base, 3-12
Checksums, 2-5, 2-8, 2-15, 2-18, 3-14
see also INFORMATION command

Index-1

Command recognition, 3-2
Commands to PEP, 3-2 to 3-11
CONNECT command, 2-11
Connected directory, 2-15
Conventions used in this manual
see Symbology
Copying files from product distribution tapes,
Figure 1-2; 2-4, 2-14
Copying patch files to disk, Figure 1-3
TOPS-10, 2-6
TOPS-20, 2-16
see also Patch retrieval control files
Creating disk directories, 1-6, 2-1 to 2-5
CREDIR program, 2-3, 2-4
Cumulative patch tapes, 1-4
Current patch save set, 1-3
Data files for PEP, 2-13, 3-27
Declaring autopatchable products, 1-6, 2-4,
2-14
see also SELECT command
Default search list, 2-2
Defining logical names
see Logical names and disk directories
DESELECT command to PEP, 3-4
DIS:, 3-25
Disk directories
building (creating), 1-6, 2-1 to 2-5
logical names, 3-25
status
see INFORMATION command
Distribution tapes
autopatch, 1-4
product, 2-4
DISMOUNT command, 2-6, 2-16
Documentation files, 2-5, 2-15
see also Edit description files
see also INSTAL.DOC
see also README
DSKP:, 1-6, 2-1, 2-5
DSKP:[7,6,BACKUP], 2-3
DUMPER distribution control files (.DDC),
2-13, 3-25
DUMPER program, 1-7,2-16,3-23
Edit description files (.Dnn), 3-27
Edit levels, 3-24
ENABLE command, 2-11, 2-19
Error messages, 3-11 to 3-23
Executable files, 1-1
EXE files for PEP, 2-4, 2-13
EXIT command to PEP, 3-5

Index-2

Fatal errors, 3-11
File index, 2-6, 2-16
see also README
Galaxy Batch System, 1-8
TOPS-10, 2-7, 3-24
TOPS-20, 2-17, 3-24
Guidewords
in PEP commands, 3-3
HELP command to PEP, 3-5
Help files for PEP, 2-4, 2-13
Indirect command files, 1-7; Figures 1-5 and
1-6; 3-27
Index of patches
see Patch directory file
INFORMATION command to PEP, 2-8, 2-9,
2-18, 3-6
Initializing directories, 1-6
Input files
patched, 1-1, 1-10, 2-20
INS:, 3-25
INSTAL. DOC documentation file, 3-25
TOPS-10, 2-3, 2-4
TOPS-20, 2-12 to 2-14
INSTALL command to PEP, 2-9, 2-19, 3-6
Installation directory (SYS:), 1-6, 1-10, 2-9,
2-19
Installation save set, 1-3
Installed files
current, 1-10, 2-8, 3-6
Installing Autopatch, 2-1 to 2-5, 2-10 to
2-14; INSTAL.DOC print-out
Installing rebuilt software, Figure 1-7B; 2-9,
2-19
Instructions to system administrators, v,
chs. 1 and 3
Instructions to system operators, v, chs. 1,
2,3
Link command files (.LNK), 1-4,3-25
LOG files (.Lnn), 2-8, 2-18, 3-24, 3-26
LOGIN command, 2-1, 2-5, 2-11, 2-15
Logical names
and disk directories, 2-1 to 2-4, 3-24
see also INFORMATION command
MAKLIB (.MKL), 3-24, 3-27
MOUNTR.CMD file, 2-11

Naming conventions with Autopatch, 1-4,
1-6, 2-1, 2-11, 3-24
OPERATOR privileges, 2-11, 2-19
Operator qualifications to do automatic
patching, 1-3
PAT:, 3-25
Patch and build control files (.CTL), 2-4,
2-13, 3-26
Patch command files (.MKL), 3-27
Patch directory files (.DPD), 1-3, 3-26
Patch Executive Program (PEP), 1-1, 3-1
Patch files, 1-3; Figure 1-3
Patch history
see DESELECT command
see Edit description files
Patch index
see Patch directory file
Patch retrieval control files (.Ann and .Pnn),
1-3,2-6,2-15,3-26
Patch status
see SUMMARY command
Patch tape log file, 3-24
Patch tape structure, 1-3; Figure 1-1
Patch tapes, 1-3
cumulative, 1-4
distribution, 1-4
Patching and rebuilding a product
TOPS-10, 2-5 to 2-8
TOPS-20, 2-15 to 2-18
PEP commands, 3-2 to 3-11
PEP data base, 1-7,2-17,3-1
PEP data files, 2-7, 2-13, 3-27
PEP messages and error recovery
see Error messages
PEPB, 3-24
PEP prompt, 2-5
Permanent quotas
see Quotas
PPN[7,6], 2-1, 2-5
Privileges
enabling, 2-11,2-19
Product backup directory, 1-5, 1-6, 2-3, 2-12
Product description file (.PDF), 3-27
Product distribution directory, 1-4, 1-6, 2-4,
2-14
Product installation directory, 1-5, 2-9, 2-19
Product LOG files, 3-26
Product's component files
to build, 3-24
superseding, Figure 1-7B
PS:, 2-11

Quotas, 2-2, 2-11
REACT program, 2-1
README documentation file, 1-3, 2-6, 2-15,
3-24, 3-26
Rebuilding a product
see Patching and rebuilding a product
Recognition command input, 3-3
Reference section, ch. 3
Disk directories and logical names, 3-24
Files used with Autopatch, 3-25
Patch Executive Program, 3-1
PEP commands, 3-2 to 3-11
PEP messages and recovery procedures,
3-11 to 3-23
System programs used with Autopatch,
3-23
REL libraries, 1-4, 3-25
RESTORE command to PEP, 3-7
Restoring a rebuilt installed product,
Figure 1-8
TOPS-10, 2-10
TOPS-20, 2-20
see also RESTORE command
RETRIEVE command to PEP, 1-7,3-7
Retrieving patches, Figure 1-4
see also RETRIEVE command
Reverting to previous version
see Restoring a rebuilt installed product
Revision levels, 2-7
Running batch jobs
see Batch processing
RUNREA specification, 2-2
Save sets, 1-3
SELECT command to PEP, 2-4, 2-14, 3-9
SETUP command to PEP, 1-7,2-7,3-10
Status of disk directories, Figures 1-3 to 1-8
see also INFORMATION command
Storage areas
see Disk directories
SUBMIT command to Batch
TOPS-10, 2-7
TOPS-20, 2-17
SUMMARY command to PEP, 3-10
shows patch status, 3-11
Symbology, vi
SYS:, 1-6, 1-10,2-9,2-19
System requirements for Autopatch, 1-2
TAPE:, 2-5, 2-15
Terminating PEP, 3-5
Index-3

Testing a rebuilt product
TOPS-10, 2-8
TOPS-20, 2-18
Timesharing caution, 2-9, 2-19
TOPS-10 procedures
installing Autopatch, Figures 1-2 to 1-4;
2-1 to 2-5
installing a rebuilt product, 2-9
patching and rebuilding a product, 2-5 to
2-8
restoring a rebuilt product, 2-10
TOPS-20 procedures
installing Autopatch, Figures 1-2 to 1-4;
2-10 to 2-14
installing a rebuilt product, 2-19
patching and rebuilding a product, 2-15
to 2-17

Index-4

TOPS-20 procedures (Cont.),
restoring a rebuilt product, 2-20
Transferring files
see INST AL.DOC
see README

Verifying by PEP, 1-8,2-7,2-17
Version numbers, 2-5, 2-18, 3-6

Warning messages, 3-11
WHEEL privilege, 2-11, 2-19
Working quotas
see Quotas

TOPS-IO/TOPS-20
Autopatch Procedures/Reference Manual
AA-H729A-TK

READER'S COMMENTS
NOTE:

This form is for document comments only. DIGITAL will use comments submitted on this form at the company's discretion. If you require a written reply
and are eligible to receive one under Software Performance Report (SPR) service, submit your comments on an SPR form.

Did you find this manual understandable, usable, and well-organized? Please make
suggestions for improvement.

Did you find errors in this manual? If so, specify the error and the page number.

Please indicate the type of reader that you most nearly represent.

o Assembly language programmer
o Higher-level language programmer
o Occasional programmer (experienced)
o User with little programming experience
o Student programmer
o Other (please specify) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ __
Name _________________________________________ Date ________________________
Organization ______________________________ Telephone ___________
Street ___________________________________________________________________
City ____________________ State _____ Zip Code _ _ __
or Country

I
I

I
I
I

-- -- - - - - - - Do Not Tear - Fold Here and Tape

--------------------- -111--------f~

I
I
I

~~;,~;:;~~

---:

if Mailed in the
United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO. 33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

SOFTWARE PUBLICATIONS
200 FOREST STREET MR1-2/E37
MARLBOROUGH, MASSACHUSETTS 01752

l;j
I

I
I
I

-- - - - - -

Do Not Tear - Fold Here and Tape

____________________________________________ 1

I
I
I
I
I
I
I

I
It
1
1

I
I
I
1

I
I

<Ii

1.5
I.....J

It
I 0

1°
I~
1.9

1=
IU
I
I
I
I~