____________________________________________________
DSNlink Version 2.2E for OpenVMS
Installation Guide
October 7, 1999
This document describes the installation of DSNlink
Version 2.2E, an engineering change order (ECO)
kit. Installing the DSNlink Version 2.2 for OpenVMS
software is the minimum prerequisite.
Revision/Update Information: This is a revised
document.
Operating System and Version: OpenVMS VAX Version
6.2, 7.1, or 7.2
Software Version: DSNlink Version 2.2E
for OpenVMS
________________________________________________________________
© Digital Equipment Corporation 1999. All Rights Reserved.
Digital Equipment Corporation makes no representations
that the use of its products in the manner described in
this publication will not infringe on existing or future
patent rights, nor do the descriptions contained in this
publication imply the granting of licenses to make, use,
or sell equipment or software in accordance with the
description.
Compaq, the Compaq logo, and the DIGITAL logo are
registered in the U.S. Patent and Trademark Office.
The following are trademarks of Compaq Computer
Corporation:
DEC, DECwindows, OpenVMS, VAX, VMS, and VMScluster.
The following are third-party trademarks:
3Com and U.S. Robotics are registered trademarks of 3Com
Corporation or its subsidiaries.
Clarify, ClearSupport, and ClearQuality are registered
trademarks of Clarify Inc.
Hayes is a trademark of Hayes Microcomputer Products, Inc.
MNP is a registered trademark of Microcom, Inc.
Motif is a registered trademark of Open Software
Foundation, Inc.
MultiModem and Multi-Tech are trademarks of Multi-Tech
Systems, Inc.
NCSA Mosaic is a trademark of the University of Illinois.
MultiNet is a registered trademark of Cisco Systems, Inc.
Netscape is a trademark of Netscape Communications
Corporation.
OPTIMA is a trademark of Hayes Microcomputer Products, Inc.
OSF, OSF/1, OSF/Motif, and Motif are registered trademarks
of the Open Software Foundation, Inc.
PostScript is a registered trademark of Adobe Systems Inc.
Practical Peripherals is a registered trademark of
Practical Peripherals, Inc.
UNIX is a registered trademark in the United States and
other countries, licensed exclusively through X/Open
Company, Ltd.
All other trademarks and registered trademarks are the
property of their respective holders.
The MD5 software contained in this product is derived from
the RSA Data Security, Inc. MD5 Message-Digest Algorithm.
This document was prepared using VAX DOCUMENT Version 2.1.
_________________________________________________________________
Contents
Preface................................................... v
1 Preparing to Install DSNlink
1.1 Preinstallation Checklist..................... 1-1
1.2 A Correction to the DSNlink Version 2.2
Installation Guide............................ 1-3
1.3 Installing DSNlink Version 2.2E on an OpenVMS
Cluster....................................... 1-4
1.4 Kit Contents.................................. 1-5
2 A Sample DSNlink Version 2.2E Installation
2.1 Existing Files Changed by the Installation
Procedure..................................... 2-1
2.2 A Sample Installation......................... 2-2
2.3 Postinstallation Tasks........................ 2-5
2.3.1 Modifying the DSNlink Startup to Start
Queues Once............................... 2-6
Index
Examples
2-1 Sample DSNlink Version 2.2E
Installation.............................. 2-2
iii
Tables
1-1 DSNlink Version 2.2E Kit Sizes ........... 1-2
1-2 Required System Parameters................ 1-3
iv
_________________________________________________________________
Preface
The Purpose of the Kit
The primary reason for DSNlink Version 2.2E is to support
X.25 router nodes. The kit also contains several bug fixes.
For more information, see the DSNlink Version 2.2E for
OpenVMS Release Notes.
______________________ Important ______________________
The change to support X.25 router nodes requires that
all customers who use X.25 and the Compaq host run
DSNlink Version 2.2E. If you use X.25, contact your
Customer Support Center to coordinate your DSNlink
Version 2.2E installation with their host DSNlink
Version 2.2E installation.
______________________________________________________
If you do not use the X.25 transport, you can install
DSNlink Version 2.2E without coordinating the installation
with the Compaq host.
Note that some countries do not support the x.25 transport.
Audience
This guide is intended for the system manager who installs
DSNlink software.
v
Where to Get DSNlink Kits
DSNlink Version 2.2 for OpenVMS, Version 2.2C, or Version
2.2D must be installed before you can install DSNlink
Version 2.2E. If you have not installed any of those kits,
you can get them from the following locations:
o The DSNlink Web site:
http://www.support.compaq.com/dsnlink/
Click on Download Kits.
o This anonymous FTP directory:
ftp.support.compaq.com
Set default to the directory that contains the kit you
want to install. For example, these are the directories
with DSNlink kits for the Alpha and VAX systems running
OpenVMS:
ftp> cd /public/DSNlink/ovms-alpha/
Or:
ftp> /public/DSNlink/ovms-vax/
The directory and file names are case-sensitive. Be sure
to type them as shown above.
The Readme files with each kit explain how to proceed.
vi
1
_________________________________________________________________
Preparing to Install DSNlink
This section describes the preinstallation requirements for
DSNlink Version 2.2E.
1.1 Preinstallation Checklist
Use the following checklist <> to ensure that your system
has the prerequisites for installing DSNlink Version 2.2E:
< Verify that you are installing DSNlink Version 2.2E on a
system running OpenVMS Version 6.2, 7.1, or 7.2.
< The minimum DSNlink version that your system must have
is DSNlink Version 2.2 for OpenVMS. DSNlink Version 2.2C
and DSNlink Version 2.2D are also acceptable.
For the location of the documentation and software, see
the Preface.
To see if DSNlink is installed, use this command:
$ DSN SHOW VERSION
DSNlink displays the DSNlink version. Note that DSNlink
Version 1.2 for OpenVMS does not recognize the DSN SHOW
VERSION command.
< Rename any modem scripts you want to continue using.
The DSNlink Version 2.2E installation procedure
overwrites your current modem scripts with new scripts
if the script names are identical. If you use a modem
and want to continue using its dialer script, rename the
script to keep. For example:
$ SET DEFAULT DSN$DATA
$ RENAME CO2264.DDSF_SRC CO2264_KEEP.DDSF_SRC
For more information about modem scripts, see the
DSNlink Version 2.2E for OpenVMS Release Notes.
Preparing to Install DSNlink 1-1
Preparing to Install DSNlink
1.1 Preinstallation Checklist
< Make sure you have enough disk space. The following
is the amount of disk space used by the combined kit,
which you download, and the Alpha and VAX kits after the
installation:
Table_1-1_DSNlink_Version_2.2E_Kit_Sizes___________________
Platform__Size_in_Blocks___________________________________
Alpha 13,500
VAX 13,700
Combined 20,300
kit________________________________________________________
From the combined kit, the installation procedure
supplies only the files for your system. For example,
if you install DSNlink on an Alpha system, DSNlink does
not supply the files for VAX systems.
For more information about installing DSNlink Version
2.2E on a cluster, see Section 1.3.
< Verify that the account from which you will install
DSNlink has SETPRV or at least the following privileges:
CMKRNL
DETACH
NETMBX
SYSPRV
SYSNAM
SYSLCK
TMPMBX
WORLD
< Make sure there are no running DSNlink Version 2.2 for
OpenVMS modem daemons.
The installation procedure checks for running modem
daemons. If any are found, a prompt asks if you want to
have the installation procedure stop them. Answering Y
or Yes interrupts the processes and daemons, which could
annoy users. Answering N or No causes the installation
procedure to exit.
1-2 Preparing to Install DSNlink
Preparing to Install DSNlink
1.1 Preinstallation Checklist
Note that users can continue to use DSNlink on other
non-modem transports, such as TCP/IP, during the
installation.
< Make sure the Queue Manager is running.
< Verify that the queue SYS$BATCH exists.
< Back up your system disk.
1.2 A Correction to the DSNlink Version 2.2 Installation Guide
The DSNlink Version 2.2 for OpenVMS Installation Guide
has incorrect minimum values for the MAXBUF parameter. The
value was listed as 1200 for both Alpha and VAX. It should
be 8192 for both systems.
Table 1-2 lists the minimum required SYSGEN values for
installing and running DSNlink Versions 2.2 and 2.2E.
Table_1-2_Required_System_Parameters_______________________
SYSGEN_Parameter______Minimum_Value________________________
SCSNODE Must be defined
SCSSYSTEMID Must be defined
MAXBUF Alpha: 8192
VAX: 8192
TTY_ALTYPAHD[1] Alpha: 2048
VAX: 2048
GBLPAGES Alpha: 6623
VAX: 6754
GBLSECTIONS Alpha: 21
VAX: 33
[1]TTY_ALTYPAHD_is_checked_only_if_you_choose_the_modem____
transport.
___________________________________________________________
Also, the Installation Guide states that if you enter
more than one access number when installing DSNlink
Version 2.2, only the first access number is tested during
the installation verification procedure (IVP). That is
incorrect. DSNlink tests all access numbers you enter
Preparing to Install DSNlink 1-3
Preparing to Install DSNlink
1.2 A Correction to the DSNlink Version 2.2 Installation Guide
during the installation procedure. If any access number
fails, the Network Exerciser messages notify you.
1.3 Installing DSNlink Version 2.2E on an OpenVMS Cluster
Where to Install DSNlink Version 2.2E in a Cluster
Use these guidelines for installing DSNlink Version 2.2E on
clusters:
o If you have a cluster of both Alpha and VAX systems, you
must install ECOs on one of the Alphas and one of the
VAXes. Do not install DSNlink on a disk shared by Alpha
and VAX systems.
For example, in a mixed cluster of five nodes, A, B,
C, D, and E, if nodes A, B, and C are VAXes that share
a common disk, you must install DSNlink Version 2.2E
on either node A, B, or C. If nodes D and E are Alpha
systems that share a common disk, you must install
DSNlink Version 2.2E on either node D or E.
o If you previously installed DSNlink Version 2.2C,
install DSNlink Version 2.2E on the same systems.
o If your cluster has only VAX or Alpha systems, install
DSNlink Version 2.2E on one node in each group that
shares a common disk.
DSNlink Startup in Clusters
When each DSNlink node in a cluster runs the DSNlink
startup procedure, DSN$STARTUP.COM, the produces the
following error:
%JBC-E-STARTED, queue already started
The individual startup procedures attempt to start a
queue that is already started. For information on how
to modify the startup files to correct this error, see
Section 2.3.1.
1-4 Preparing to Install DSNlink
Preparing to Install DSNlink
1.4 Kit Contents
1.4 Kit Contents
The DSNlink Version 2.2E save set, DSNLINKE022.A, contains:
o Files for both Alpha and VAX systems
o The release notes:
DSNLINK022E_RELEASE_NOTES.TXT - the text version
DSNLINK022E_RELEASE_NOTES.PS - the PostScript version
o The installation guide (this document):
DSNLINK022E_INSTALL_GUIDE.TXT - the text version
DSNLINK022E_INSTALL_GUIDE.PS - the PostScript version
Preparing to Install DSNlink 1-5
2
_________________________________________________________________
A Sample DSNlink Version 2.2E Installation
Before you start a DSNlink Version 2.2E installation,
verify that your system meets the prerequisites listed
in Section 1.1.
2.1 Existing Files Changed by the Installation Procedure
The DSNlink Version 2.2E installation replaces modem
scripts with new scripts if the file names are identical.
The script files are in the directory defined by the
logical name DSN$DATA and have the file extension .DDSF_
SRC. For a list of the modem scripts, see the Files and
Images section of the DSNlink Version 2.2E for OpenVMS
Release Notes.
Because the installation replaces only DSNlink Version
2.2 for OpenVMS files that have the same name as files
in DSNlink Version 2.2E, if you want to keep the files
you have, rename or copy them to another directory before
installing DSNlink Version 2.2E. For example, to prevent
the Codex modem script from being replaced:
$ RENAME DSN$ROOT:[DAT]CODEX.DDSF_SRC -
-$ DSN$ROOT:[DAT]CODEX_KEEP.DDSF_SRC
After the DSNlink Version 2.2E installation, rename the
file to CODEX.DAT.
The installation also provides a new route map template.
The template has changes to the routing entries for
Customer Support Centers around the world. The changes
do not appear in your route map unless you rebuild it. You
do not have to rebuild your route map if you can reach your
Customer Support Center successfully now.
A Sample DSNlink Version 2.2E Installation 2-1
A Sample DSNlink Version 2.2E Installation
2.2 A Sample Installation
2.2 A Sample Installation
Example 2-1 shows a sample DSNlink Version 2.2E
installation on an Alpha system. The DSNlink kit was
previously copied to the SYS$UPDATE directory.
Example 2-1 Sample DSNlink Version 2.2E Installation
$ SET DEFAULT SYS$UPDATE
$ @VMSINSTAL DSNLINKE022 ddcu:[dir]1
OpenVMS AXP Software Product Installation Procedure V6.2
It is 6-OCT-1999 at 10:20.
Enter a question mark (?) at any time for help.
%VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account.
%VMSINSTAL-W-ACTIVE, The following processes are still active:
MARKS
MICHAEL
* Do you want to continue anyway [NO]? Y
* Are you satisfied with the backup of your system disk [YES]? Y
The following products will be processed:
DSNLINKE V2.2
Beginning installation of DSNLINKE V2.2 at 10:20
%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.
********************************************************************************
© Digital Equipment Corporation, 1989-1999. All Rights Reserved.
This software has been installed and enabled to enhance the
maintenance services provided by DIGITAL. Use of this software
by anyone other than DIGITAL maintenance personnel is not permitted
without a license. Customers who have signed a DIGITAL Service
Agreement ("Agreement") have been granted such a license for their
own use on equipment covered by the Agreement. Any other use,
copying or license to any other party whatsoever is not permitted.
DIGITAL reserves the right to remove or disable this software at
its discretion.
(continued on next page)
2-2 A Sample DSNlink Version 2.2E Installation
A Sample DSNlink Version 2.2E Installation
2.2 A Sample Installation
Example 2-1 (Cont.) Sample DSNlink Version 2.2E
Installation
Restricted Rights: Use, duplication, or disclosure by the U.S.
Government is subject to restrictions as set forth in subparagraph
(c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in
FAR 52.227-14 Alt. III, as applicable.
Motif is a registered trademark of the Open Software Foundation, Inc.
The MD5 software contained in this product is derived from the RSA
Data Security, Inc. MD5 Message-Digest Algorithm.
This product includes software developed by the University of
California, Berkeley and its contributors:
Copyright (c) 1983, 1986, 1987, 1988, 1993
The Regents of the University of California.
All rights reserved.
********************************************************************************
Note: You can enter a question mark (?) when prompted for
input and a detailed explanation will be displayed
about what information is needed.
%DSNLINKE-I-PREINSTALL, Checking for required privileges
%DSNLINKE-I-PREINSTALL, Checking for minimum version of OpenVMS
%DSNLINKE-I-PREINSTALL, Checking for minimum version of DSNlink
%DSNLINKE-I-PREINSTALL, Checking for existing DSNlink directory tree
%DSNLINKE-I-PREINSTALL, Checking for sufficient free blocks on system disk
%DSNLINKE-I-PREINSTALL, Checking for executing Queue Manager
%DSNLINKE-I-PREINSTALL, Checking for SYS$BATCH batch queue
%DSNLINKE-I-PREINSTALL, Checking for running DSNlink modem processes
DSNlink modem processes are currently running on this system.
In order to continue with this installation, they must be shut
down, which will terminate all existing modem links. If you
decide to proceed, this installation procedure will shut down
the DSNlink modem processes.
* Do you want to continue with the installation of DSNlink? [NO]? Y 2
(continued on next page)
A Sample DSNlink Version 2.2E Installation 2-3
A Sample DSNlink Version 2.2E Installation
2.2 A Sample Installation
Example 2-1 (Cont.) Sample DSNlink Version 2.2E
Installation
%DSNLINKE-I-PREINSTALL, Starting shutdown of DSNlink...
Job DSN$SHUTDOWN (queue SYS$BATCH, entry 4) started on SYS$BATCH
%DSNLINKE-I-PREINSTALL, Shutdown of DSNlink completed
* Do you want to purge files replaced by this installation [YES]? Y 3
All installation questions have been answered. The rest of the
installation will proceed automatically and may take up to 10
minutes, depending on your system type.
%DSNLINKE-I-PROCOM, Providing files to DSN$COMMAND...
%DSNLINKE-I-PRODAT, Providing files to DSN$DATA...
%DSNLINKE-I-PROEXE, Providing images to DSN$SYSTEM...
%DSNLINKE-I-PROHLP, Providing files to DSN$HELP...
%DSNLINKE-I-PROLIB, Providing images to DSN$LIBRARY...
%DSNLINKE-I-PRORES, Providing English Motif resource files...
%DSNLINKE-I-PROUTL, Providing images to DSN$UTILITIES...
%DSNLINKE-I-UPDDCLHLP, Updating DCL Help
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...
%DSNLINKE-I-POSTINSTALL, Setting the owner and protection on the DSNlink directo
ries
%DSNLINKE-I-POSTINSTALL, Setting the owner and protection on the DSNlink system
files
%DSNLINKE-I-POSTINSTALL, Setting the owner and protection on all DSNlink files
%DSNLINKE-I-POSTINSTALL, Setting the owner and protection on specific DSNlink fi
les
%DSNLINKE-I-POSTINSTALL, Owner and protection successfully set on all DSNlink fi
les
%DSNLINKE-I-POSTINSTALL, Applying corrections to DSN$STARTUP.COM...
%DSNLINKE-I-POSTINSTALL, Recreating the DSNlink Route Map...
%DSNLINKE-I-POSTINSTALL, Submitting DSN$STARTUP.COM to SYS$BATCH...
(continued on next page)
2-4 A Sample DSNlink Version 2.2E Installation
A Sample DSNlink Version 2.2E Installation
2.2 A Sample Installation
Example 2-1 (Cont.) Sample DSNlink Version 2.2E
Installation
Job DSN$STARTUP (queue SYS$BATCH, entry 9) started on SYS$BATCH
Installation of DSNLINKE V2.2 completed at 10:23
Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY
Creating installation data file: VMI$ROOT:[SYSUPD]DSNLINKE022.VMI_DATA
Enter the products to be processed from the next distribution volume set.
* Products:
VMSINSTAL procedure done at 10:12
$
The following refer to items in the previous sample
installation:
1 Replace ddcu:[dir] with the file specification of the
kit on your system.
2 This prompt appears only if there are running DSNlink
modem process on your system. If you enter Yes or Y at
the prompt to continue, the installation procedure stops
the processes, which interrupts the DSNlink applications
and may annoy the users. If you enter No or N, the
installation stops.
3 If you choose to purge the files replaced by the
installation, DSNlink removes only the files for which
there are new files in the kit. For a list, see the
Files and Images section in the DSNlink Version 2.2E for
OpenVMS Release Notes.
2.3 Postinstallation Tasks
The postinstallation tasks are as follows:
o Be sure you have performed all the postinstallation
procedures for DSNlink Version 2.2 for OpenVMS.
For the location of the DSNlink Version 2.2 for OpenVMS
Installation Guide, see the Preface.
A Sample DSNlink Version 2.2E Installation 2-5
A Sample DSNlink Version 2.2E Installation
2.3 Postinstallation Tasks
o If you renamed a modem script to prevent it from being
overwritten by the new modem script, to reinstate the
script for use:
1. Log in to the SYSTEM account.
2. Determine if the modem line is in use with this
command:
$ DSN SHOW LINE
If the value for the Current State field is ONLINE,
the line is in use.
3. When the Current State field has IDLE or LISTENING,
stop the modem line with this command:
$ DSN STOP LINE
4. Rename the modem script to its original name. For
example:
$ SET DEFAULT DSN$DATA
$ RENAME CO2264_KEEP.DDSF_SRC CO2264.DDSF_SRC
5. Start the modem line:
$ DSN START LINE
2.3.1 Modifying the DSNlink Startup to Start Queues Once
On OpenVMS clusters, the DSNlink startup file tries to
start the queue DSN$BATCH_nodename twice, where nodename
is the name of the node in the cluster. This is the error
message:
%JBC-E-STARTED, queue already started
To have DSNlink start the queue once in a cluster, edit the
DSNlink startup file, SYS$STARTUP:DSN$STARTUP.COM, on each
DSNlink node to remove the /START qualifier or the START
/QUEUE command from the INITIALIZE/QUEUE command. This is
the part of the file to change:
2-6 A Sample DSNlink Version 2.2E Installation
A Sample DSNlink Version 2.2E Installation
2.3 Postinstallation Tasks
$! If we're on a VMScluster, then init a
$! generic DSN$BATCH batch queue with
$! DSN$BATCH_nodename execution queues
.
.
.
$create_execution_queues:
$ exec_queue_name = f$element(element_nbr,",",queue_name_list)
$ member_name = f$element(element_nbr,";",batchque_nodename)
$ if exec_queue_name .eqs. "," then goto create_generic_queue
$ on_qual = "/ON=''member_name'::"
$ set noon
$ initialize/queue/batch/start/job_limit=5'on_qual' 'exec_queue_name'
$ start/que'on_qual' 'exec_queue_name'
The items you can remove are shown in boldface text in the
example. Remove either:
o The /start qualifier in the initialize command or
o The start/que'on_qual' 'exec_queue_name' entire last
line in the example above.
The DSNlink Version 2.2E installation is complete.
A Sample DSNlink Version 2.2E Installation 2-7
_________________________________________________________________
Index
C______________________________ M______________________________
Clusters MAXBUF parameter
DSNlink startup, 1-4 correction, 1-3
installations on OpenVMS, Modems
1-4 scripts replaced by the
modify DSNlink startup to installation, 2-1
start queues once, 2-6 Modem transport
stopping and starting modem
D______________________________ lines, 2-5
DSNlink
files in this kit, 1-5 O______________________________
minimum required version, OpenVMS
1-1 supported versions, 1-1
preinstallation checklist,
1-1 P______________________________
required disk space, 1-2 Postinstallation
sample installation, 2-2 tasks, 2-5
startup in clusters, 1-4 Preinstallation
F checklist, 1-1
_______________________________ Privileges
Files installation account, 1-2
kit contents, 1-5
S______________________________
K______________________________ Sample installation, 2-2
Kit size, 1-2 SYSGEN values, 1-3
Index-1