This guide contains instructions for installing DECdocument on the OpenVMS operating system. It also explains how to read the online release notes before or after installing the product. This document applies to DECdocument Version 3.2 and all maintenance updates throughout that version.
Revision/Update Information: No updates for Version 3.2.
Operating System and Version:
VAX OpenVMS Version 5.4 or higher
Alpha OpenVMS Version 6.1
or higher
Software Version: DECdocument Version 3.2
All Rights Reserved
The information in this document is subject to change without notice and should not be construed as a commitment by Touch Technologies, Inc. Touch Technologies, Inc. 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 responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies.
Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.
The following are trademarks of Touch Technologies, Inc., and may be used only to describe products of Touch Technologies, Inc.:
DYNAMIC TAPE ACCELERATOR INTOUCH 4GL
DYNAMIC LOAD BALANCER PLUS INTOUCH INSA
REMOTE DEVICE FACILITY
|
The following are trademarks of Digital Equipment Corporation:
DEC DIBOL UNIBUS
DEC/CMS EduSystem VAX
DEC/MMS IAS VAXcluster
DECnet MASSBUS VMS
DECsystem--10 PDP OpenVMS
DECSYSTEM--20 PDT VT
DECUS RSTS
DECwriter RSX Digital logo
|
The following are third-party trademarks:
Motif is a registered trademark of Open Software Foundation, Inc.
PostScript is a registered trademark of Adobe Systems Incorporated.
May 1997
| Contents |
This guide describes how to install DECdocument on VAX and Alpha processors that are running the OpenVMS operating system.
Keep this document with your distribution kit. You will need it to install maintenance updates or to reinstall DECdocument for any other reason.
The audience for this guide is the system manager who installs DECdocument software.
This guide is organized as follows:
This manual is part of the DECdocument documentation set that includes the following manuals:
For additional information on installing DECdocument Version 3.2, refer to the OpenVMS system documentation on these topics:
The following conventions are used in this guide:
| UPPERCASE TEXT | Uppercase letters indicate the name of a command, a file, a parameter, a procedure, or utility. |
| $ | The dollar sign is used to indicate the DCL prompt. This prompt may be different on your system. |
| [Ctrl/x] | In procedures, a sequence such as [Ctrl/X] indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button. |
| [Return] | In procedures, a key name is shown enclosed to indicate that you press a key on the keyboard. |
|
.
. . |
Vertical ellipsis in an example means that information not directly related to the example has been omitted. |
| file-spec,... | Horizontal ellipsis indicates that additional parameters, values, or information can be entered. |
| [logical-name] | Square brackets indicate that the enclosed item is optional. (Square brackets are not, however, optional in the syntax of a directory name in a file specification or in the syntax of a substring specification in an assignment statement.) |
This chapter discusses the preparations and requirements necessary for installing DECdocument.
This manual applies to Version 3.2 of DECdocument and all subsequent maintenance releases up to the next major product release.
Be sure to verify the contents of your kit. If your kit is damaged or if you find that parts of it are missing, contact your sales representative.
DECdocument provides online release notes. It is strongly recommended that you read the release notes before proceeding with the installation. For information on accessing the online release notes, see Section 2.1.
1.1 Required Operating System Components
The OpenVMS operating system comes with a variety of support options,
or classes. Classes include such features as networking and RMS
journaling.
For a complete list of the required classes, see the Software Product Description (SPD).
1.2 Prerequisite and Optional Software
Please refer to the Software Product Description (SPD) for a complete
list of prerequisite and optional software and their required version
numbers.
1.3 License Registration
You must register and load your license for DECdocument before you
start the installation in order to run the Installation Verification
Procedure (IVP) and use the software.
To register a license under OpenVMS, first log in to the system manager's account, SYSTEM. You then have a choice of two ways to perform the registration:
If you plan to use DECdocument on more than one node in a VAXcluster, you will need to perform a license load on the other nodes after you complete this installation. See Section 3.3.
For complete information on using LMF, see the VMS License Management Utility Manual.
1.4 Installation Procedure Requirements
This section and those that follow discuss various requirements for
installing DECdocument.
Installing DECdocument and running the Installation Verification Procedure (IVP) takes approximately 15 to 60 minutes.
1.4.1 Privileges and Disk Space
To install DECdocument, you must be logged in to an account that has
SETPRV or at least the following privileges:
Note that VMSINSTAL turns off BYPASS privilege at the start of the installation.
Installing DECdocument requires a certain amount of disk storage space during the installation. Once DECdocument is installed, less storage space is required. Table 1-1 specifies the space requirements.
| TASK | VAX | Alpha |
|---|---|---|
| Installation: | 88,600 blocks | 90,100 blocks |
| (44.3MB) | (45.1MB) | |
| Permanent: | 78,000 blocks | 78,000 blocks |
| (39.0MB) | (39.0MB) |
Most of the files are stored in a directory tree called [DOC$TOOLS...] on the device and directory that you specify. A system-wide logical name, DOC$ROOT, is created to refer to this directory tree.
To determine the number of free disk blocks on the current system disk, enter the following command at the DCL prompt:
$ SHOW DEVICE SYS$SYSDEVICE
|
Installing DECdocument requires certain system parameter settings. Table 1-2 lists the minimum required system parameter values for the installation. Depending on the kinds of programs and applications running at your site, you might need higher values for some settings.
| System Parameter | Minimum Value |
|---|---|
| GBLPAGES | 102 |
| GBLSECTIONS¹ | 1 |
| VIRTUALPAGECNT | 15000 |
The following sections show you how to:
To check the values of your system parameters, enter the following command at the DCL prompt to invoke the System Generation Utility (SYSGEN):
$ RUN SYS$SYSTEM:SYSGEN
SYSGEN>
|
At the SYSGEN> prompt, enter the SHOW command to display the value of a system parameter. The values displayed should equal or exceed the value of each system parameter listed in Table 1-2. The following example displays the value for the WSMAX system parameter:
SYSGEN> SHOW VIRTUALPAGECNT
|
After checking the parameters with the SHOW command, enter the EXIT command at the SYSGEN> prompt to return to DCL level.
1.4.2.2 Calculating the Values for GBLPAGES and GBLSECTIONS
To install and run DECdocument, you must have sufficient free global
pages and global sections. You must first find out how many free global
pages and sections you have on your system. Then use AUTOGEN if you
need to increase the GLBPAGES and GBLSECTIONS system parameters.
If you are installing DECdocument on a OpenVMS Version 5.2 system, you can use the WRITE command with the F$GETSYI lexical function to find the number of free global pages and global sections. The following example shows how to get this information at your terminal (the default for SYS$OUTPUT):
$ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES")
15848
$ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS")
24
|
If the values displayed by the system are greater than the values in Table 1-2, you do not need to increase the values for these parameters. If the value of free global pages or global sections is less than the value in Table 1-2, you must increase the system parameter setting.
Section 1.4.2.3 describes the procedures for increasing these values using AUTOGEN.
1.4.2.3 Changing System Parameter Values with AUTOGEN
Use the AUTOGEN command procedure to change system parameters. AUTOGEN
automatically adjusts values for parameters that are associated with
the values you reset manually. To change system parameters with
AUTOGEN, edit the following file:
SYS$SYSTEM:MODPARAMS.DAT
|
Use an editor to access the file. To change a parameter value listed in this file, delete the current value associated with that parameter and enter the new value.
To add a new parameter, add a line to the file that includes both the name of the parameter and its value. For example:
GLBPAGES = 102
|
To modify incremental parameters such as GBLPAGES and GBLSECTS, use ADD_. The following example increases the global page setting by 2000:
ADD_GBLPAGES = 2000
|
Note that when you set the page file quota, do not use a value that exceeds the amount of page file space available on the system.
After you make all your changes, exit from the editor and execute the AUTOGEN procedure to recalculate your system parameters. Enter the following command at the DCL prompt:
$ @SYS$UPDATE:AUTOGEN GETDATA REBOOT
|
When you specify REBOOT, AUTOGEN performs an automatic system shutdown and then reboots the system. Any users logged on to the system are immediately disconnected during the shutdown. The automatic reboot puts the new parameter values into effect.
The AUTOGEN Utility automatically adjusts some of the SYSGEN parameters based on the consumption of resources since the last reboot. If you do not want to take advantage of this automatic adjustment, include the NOFEEDBACK qualifier on the AUTOGEN command line.
For more information about using AUTOGEN, see the VMS System Management Subkit.
1.4.3 Process Account Quotas
The account you use to install DECdocument must have sufficient quotas
to enable you to perform the installation. Table 1-3 summarizes the
process quotas required for the installation account.
| Account Quota | Value |
|---|---|
| ASTLM | 24 |
| BIOLM | 18 |
| BYTLM | 18,000 |
| DIOLM | 18 |
| ENQLM | 30 |
| FILLM | 30 |
| PGFLQUOTA | 25,000 |
An open file limit (FILLM) value of 20 is adequate only for the installation of DECdocument. The FILLM value must be 30 or greater in order to run DECdocument after installation. It is recommended that you increase your FILLM value to 30 so the IVP can be executed as part of the installation procedure. A page file quota (PGFLQUOTA) of 10,000 is adequate for only the installation of DECdocument. The PGFLQUOTA value must be 25,000 or greater to run DECdocument after installation and to execute the IVP (which runs DECdocument). It is recommended that you increase your PGFLQUOTA value to 25,000 so the IVP can be executed as part of the installation procedure. |
User account quotas are stored in the file SYSUAF.DAT. Use the VMS Authorize Utility (AUTHORIZE) to verify and change user account quotas. First set your directory to SYS$SYSTEM and then run AUTHORIZE:
$ SET DEFAULT SYS$SYSTEM
$ RUN AUTHORIZE
UAF>
|
At the UAF> prompt, enter the SHOW command with an account name to check a particular account. For example:
UAF> SHOW SMITH
|
To change a quota, enter the MODIFY command. The following example changes the FILLM quota for the SMITH account and then exits from the utility:
UAF> MODIFY SMITH /FILLM=50
UAF> EXIT
|
After you exit from the utility, the system displays messages indicating whether or not changes were made. Once the changes have been made, you must log out and log in again for the new quotas to take effect.
For more information on modifying account quotas, see the description of the Authorize Utility in the VMS System Management Subkit.
1.4.4 VMSINSTAL Requirements
When you invoke VMSINSTAL, it checks the following:
Note that the VMSINSTAL requires that the installation account have a minimum of the following quotas:
If VMSINSTAL detects any problems during the installation, it notifies
you and asks if you want to continue the installation. In some
instances, you can enter YES to continue. To stop the installation
process and correct the situation, enter NO or press Return. Then
correct the problem and restart the installation.
1.4.5 Backing Up Your System Disk
At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. It is recommended that you do a system disk backup before installing any software.
Use the backup procedures that are established at your site. For details on performing a system disk backup, see the section on the Backup Utility in the VMS System Management Subkit.
| Next | Contents |