Trailing-Edge
-
PDP-10 Archives
-
BB-AI48A-BM
-
dtr20-doc/dtr20.mem
There are no other files named dtr20.mem in the archive.
APPENDIX A
DATATRIEVE-20 INSTALLATION PROCEDURES
A.1 INTRODUCTION
This document describes the procedures for installing Version 1.0 of
DATATRIEVE-20 on TOPS-20. The product software includes runnable EXE
files, documentation, demonstration data, dictionary definitions,
plotting definitions for a variety of terminals, sources for local
modifications, a relocatable library for callable DATATRIEVE, and UETP
tests.
DATATRIEVE-20 requires the TOPS-20 V5.1 or later monitor, microcode
version 326 or later, SORT V5 or later, and RMS-20 V2.0 or later. If
the distributed DATATRIEVE facility is used, DECnet-20 V2.1 or later
is required. If distributed DATATRIEVE to PDP-11s is required,
DATATRIEVE-11 V3.1 or later is required. If distributed DATATRIEVE to
VAXes is required, VAX-11 DATATRIEVE V3.0 is required.
The release is in the form of a 1600 bpi 9-track DATATRIEVE-20
distribution tape written in TOPS-20 DUMPER format containing 12
savesets.
A.2 CONTENTS OF THE DISTRIBUTION TAPE
The distribution tape consists of the following savesets:
1. DTR20 DOCUMENTS
This saveset includes all DATATRIEVE documentation files
2. DTR20 SYSTEM FILES
This saveset includes the .EXE, .REL, .L36, .UNV, and help
files that should be installed on SYS:.
3. DTR20 DEMOS
This saveset includes all DATATRIEVE demonstration files.
DATATRIEVE-20 INSTALLATION PROCEDURES Page A-2
4. DTR20 DEMO DICTIONARY
This saveset includes all DATATRIEVE dictionary files for
demonstration purposes.
5. DTR20 VT125 PLOTS
This saveset includes all DATATRIEVE plot definitions for the
VT125 terminal.
6. DTR20 VT240 PLOTS
This saveset includes all DATATRIEVE plot definitions for the
VT240 terminal.
7. DTR20 PC350 PLOTS
This saveset includes all DATATRIEVE plot definitions for the
PC350 personal computer.
8. DTR20 GIGI PLOTS
This saveset includes all DATATRIEVE plot definitions for the
GIGI terminal.
9. DTR20 VT100 PLOTS
This saveset includes all DATATRIEVE plot definitions for the
VT100 terminal.
10. DTR20 SOURCES
This saveset includes only the DATATRIEVE sources necessary
for making local modifications to the product; relocatable
libraries; control files for rebuilding.
11. RTL SOURCES
This saveset includes the Run Time Library relocatable
library.
12. DTR20 UETP TEST
This saveset includes the files for UETP tests.
A.3 INSTALLING DATATRIEVE-20
Perform the following steps to install the DATATRIEVE system:
DATATRIEVE-20 INSTALLATION PROCEDURES Page A-3
1. Read the cover letter.
Follow the "Special Instructions" (if any) at the end of the
cover letter. Also, read the DATATRIEVE beware file for any
last minute instructions. (This file is enclosed in hardcopy
form in your distribution package.)
2. LOGIN as the operator or as a user with WHEEL privileges.
3. Type the ENABLE command.
4. Mount the DATATRIEVE distribution tape giving it the logical
name DTR20. See the TOPS-20 Operator's Guide (part of the
TOPS-20 Notebook Set) for instructions on mounting a tape.
5. Use the BUILD command to create directories for the contents
of the DATATRIEVE distribution tape. Each directory
corresponds to a saveset on the tape. Refer to the section
on "Contents of the Distibution Tape" for a description of
the contents of the saveset. Type the following commands:
(The following are directories used for installation and
archival. These directories may be placed on any convenient
structure. They may also be retained or killed after the
installation depending on site policies.)
$BUILD <DTR20-DOC><RET>
$$WORK 100<RET>
$$PERM 100<RET>
$$<RET>
$BUILD <DTR20-RUN><RET>
$$WORK 500<RET>
$$PERM 500<RET>
$$<RET>
$BUILD <DTR20-SOURCES><RET>
$$WORK 600<RET>
$$PERM 600<RET>
$$<RET>
$BUILD <DTR20-RTL><RET>
$$WORK 50<RET>
$$PERM 50<RET>
$$<RET>
$BUILD <DTR20-TESTS><RET>
$$WORK 50<RET>
$$PERM 50<RET>
$$<RET>
DATATRIEVE-20 INSTALLATION PROCEDURES Page A-4
The following directories and subdirectories are part of the
DATATRIEVE-20 product.
The directory PS:<DATATRIEVE> can be assigned any name that
is site specific, and so long as the logical name CDD$DTR:
is directed to the assigned name. However, the logical name
CDD$DTR and the subdirectories shown in the following
examples cannot be changed as to appear differently than as
shown in the documentation.
$BUILD PS:<DATATRIEVE><RET>
$$WORK 1000<RET>
$$PERM 1000<RET>
$$FILES-ONLY<RET>
$$MAXIMUM-SUBDIRECTORIES 5<RET>
$$PROTECTION 777740<RET>
$$DEFAULT-FILE-PROTECTION 777752<RET>
$$<RET>
$BUILD PS:<DATATRIEVE.DEMO><RET>
$$WORK 100<RET>
$$PERM 100<RET>
$$FILES-ONLY<RET>
$$PROTECTION 777740<RET>
$$DEFAULT-FILE-PROTECTION 777752<RET>
$$<RET>
$BUILD PS:<DATATRIEVE.VT125><RET>
$$WORK 200<RET>
$$PERM 200<RET>
$$FILES-ONLY<RET>
$$PROTECTION 777740<RET>
$$DEFAULT-FILE-PROTECTION 777752<RET>
$$<RET>
$BUILD PS:<DATATRIEVE.VT240><RET>
$$WORK 200<RET>
$$PERM 200<RET>
$$FILES-ONLY<RET>
$$PROTECTION 777740<RET>
$$DEFAULT-FILE-PROTECTION 777752<RET>
$$<RET>
$BUILD PS:<DATATRIEVE.PC350><RET>
$$WORK 200<RET>
$$PERM 200<RET>
$$FILES-ONLY<RET>
$$PROTECTION 777740<RET>
$$DEFAULT-FILE-PROTECTION 777752<RET>
$$<RET>
$BUILD PS:<DATATRIEVE.GIGI><RET>
$$WORK 200<RET>
DATATRIEVE-20 INSTALLATION PROCEDURES Page A-5
$$PERM 200<RET>
$$FILES-ONLY<RET>
$$PROTECTION 777740<RET>
$$DEFAULT-FILE-PROTECTION 777752<RET>
$$<RET>
$BUILD PS:<DATATRIEVE.VT100><RET>
$$WORK 200<RET>
$$PERM 200<RET>
$$FILES-ONLY<RET>
$$PROTECTION 777740<RET>
$$DEFAULT-FILE-PROTECTION 777752<RET>
$$<RET>
6. Use the DUMPER program to restore the files from the
distribution tape to disk. If you do not want to restore a
particular saveset, just replace the particular RESTORE
command with a SKIP 1 command. Type the following:
$DUMPER<RET>
DUMPER>TAPE DTR20:<RET>
DUMPER>REWIND<RET>
DUMPER>FILE<RET>
DUMPER>DENSITY 1600<RET>
DUMPER>RESTORE PS:<*>*.*.* (TO) <DTR20-DOC>*.*.*<RET>
DUMPER>RESTORE PS:<*>*.*.* (TO) <DTR20-RUN>*.*.*<RET>
DUMPER>RESTORE PS:<*>*.*.* (TO) PS:<DATATRIEVE>*.*.*<RET>
DUMPER>RESTORE PS:<*>*.*.* (TO) PS:<DATATRIEVE.DEMO>*.*.*<RET>
DUMPER>RESTORE PS:<*>*.*.* (TO) PS:<DATATRIEVE.VT125>*.*.*<RET>
DUMPER>RESTORE PS:<*>*.*.* (TO) PS:<DATATRIEVE.VT240>*.*.*<RET>
DUMPER>RESTORE PS:<*>*.*.* (TO) PS:<DATATRIEVE.PC350>*.*.*<RET>
DUMPER>RESTORE PS:<*>*.*.* (TO) PS:<DATATRIEVE.GIGI>*.*.*<RET>
DUMPER>RESTORE PS:<*>*.*.* (TO) PS:<DATATRIEVE.VT100>*.*.*<RET>
DUMPER>RESTORE PS:<*>*.*.* (TO) <DTR20-SOURCES>*.*.*<RET>
DUMPER>RESTORE PS:<*>*.*.* (TO) <DTR20-RTL>*.*.*<RET>
DUMPER>RESTORE PS:<*>*.*.* (TO) <DTR20-TESTS>*.*.*<RET>
DUMPER>EXIT<RET>
@DISMOUNT TAPE DTR20:<RET>
7. Install the DATATRIEVE software to SYS: by giving the
commands:
$COPY <DTR20-RUN>*.EXE SYS:*.*<RET>
$COPY <DTR20-RUN>*.REL SYS:*.*<RET>
$COPY <DTR20-RUN>*.UNV SYS:*.*<RET>
$COPY <DTR20-RUN>*.L36 SYS:*.*<RET>
$COPY <DTR20-RUN>*.HLP HLP:*.*<RET>
$COPY <DTR20-RUN>*.COMBINED-HLP HLP:*.*<RET>
$COPY <DTR20-RUN>*.TXT SYSTEM:*.*<RET>
DATATRIEVE-20 INSTALLATION PROCEDURES Page A-6
$COPY <DTR20-RUN>*.ERROR-HLP HLP:*.*<RET>
8. Edit the configuration file for your system (e.g.,
5-1-CONFIG.CMD). The following should be added to this file:
DEFINE CDD$DTR: PS:<DATATRIEVE>
To have DATATRIEVE immediately usable use the ^EDEFINE
command to have CDD$DTR: defined before the next system
restart.
9. If you are installing a distributed DATATRIEVE perform this
step. If not, stop, you are finished. (Refer to the
DATATRIEVE-20 User's Guide for a discussion of distributed
DATATRIEVE.)
The following steps set up the distributed DATATRIEVE Server
Controller program--NETJOB.EXE.
o Issue the following commands to PTYCON from the CTY.
(For more information on starting PTYCON subjobs see the
TOPS-20 Operator's Guide in the TOPS-20 Notebook Set.)
DEFINE ^$ DTR
CONNECT DTR
LOG OPERATOR
ENABLE
RUN SYS:NETJOB
^X
o Insert the above commands into your system's PTYCON.ATO
file or other automatic system startup file.
o If logging is desired, you must define DTRLOG:NETJOB.LOG
as a log file in your connected directory. If
DTRLOG:NETJOB.LOG doesn't exist, type:
$DEFINE DTRLOG: DSK:<RET>
Then create a NETJOB.LOG file; the file can be empty.
NOTE
The NETJOB.EXE uses the parameter file
NETJOB.TXT, which is installed on SYSTEM:. This
text file contains the following defaults: The
DATATRIEVE-20 INSTALLATION PROCEDURES Page A-7
"2" indicates the number of available DATATRIEVE
server jobs desired; the "5" indicates maximum
number of simultaneous server jobs.
A.3.1 System Verification (UETP)
Perform the following procedures to test the DATATRIEVE-20 system:
1. Install the DATATRIEVE UETP test module by giving the
commands:
$COPY <DTR20-TESTS>*.* PS:<UETP.LIB>*.*<RET>
NOTE
To run UETP, you must have OPERATOR privileges, IPCF
privileges, and be in USER group 100.
2. If you are testing distributed DATATRIEVE perform this step,
otherwise skip this step. The UETP test makes a remote
access and therefore requires that there be a remote user
with a domain to access. For security purposes the user-id
and password of any account accessed on a remote TOPS-20
system must be supplied when the access is made. As a
result, the following two steps are necessary.
o Edit the REMDTR.CMD in <UETP.LIB> so that a valid
user-id, password, and account for the remote user
(actually on the local node) are entered into the file.
Also change the node name (REMOTE) to that of the local
node.
o Connect to the PS:<user-id> entered into the REMDTR.CMD
file. Issue the command: TAKE CDD$DTR:NEWUSER.CMD in
order to create the sample domains and data files.
3. Once the DATATRIEVE components have been placed on SYS:, (see
Section 3.0, STEP 7 above) you can run the UETP test module
provided by giving the following commands:
$BUILD PS:<UETP.DTR20><RET>
DATATRIEVE-20 INSTALLATION PROCEDURES Page A-8
$$DIRECTORY 100<RET>
$$USER 100<RET>
$$PERM 200<RET>
$$WORK 200<RET>
$$<RET>
If you have not installed the DATATRIEVE components on SYS:,
you must edit DTR20.VER in PS:<UETP.LIB> to set up your SYS:
definition before continuing.
$CONNECT PS:<UETP.RUN><RET>
$DEFINE DSK: DSK:,PS:<UETP.LIB><RET>
$RUN UETP<RET>
UETP>ENABLE DTR20<RET>
UETP>BEGIN<RET>
UETP>STATUS<RET> !To get status of job
UETP>EXIT<RET>
$DEFINE DSK:<RET>
If any errors occur, UETP reports them at your terminal and
in the file EXCEPT.LOG. For more information on UETP, see
the UETP Procedures/Reference Manual in the TOPS-20 Notebook
Set.
4. Run your own tests if desired.
A.3.2 System Clean-Up
After you have completed testing, you can destroy any directories you
do not want. (These can be any of the installation or archival
directories created earlier.) For each directory you want to destroy,
give the following commands:
$BUILD <name-of-directory-to-destroy><RET>
$$KILL<RET>
[Confirm] <RET> !to confirm
$$<RET> !to exit build
Note that a directory cannot be deleted unless all of its
subdirectories have been deleted.