| Previous | Contents |
During the installation, DECdocument creates some files and logical names on your system. See Appendix B for a complete list.
2.3 Error Recovery
If errors occur during the installation itself or when the Installation
Verification Procedure (IVP) is running, VMSINSTAL displays failure
messages. If the installation fails, you see the following message:
%VMSINSTAL-E-INSFAIL, The installation of DOC V3.2 has failed.
|
If the IVP fails, you see these messages:
The DECdocument V3.2 Installation Verification Procedure failed.
%VMSINSTAL-E-IVPFAIL, The IVP for DOC V3.2 has failed.
|
Errors can occur during the installation if any of the following conditions exist:
For descriptions of the error messages generated by these conditions, see the OpenVMS documentation on system messages, recovery procedures, and OpenVMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action as described in the message. For information on installation requirements, see Chapter 1.
The following tasks take place after installing DECdocument:
You usually run the Installation Verification Procedure (IVP) during installation. If you want to run the IVP separately to ensure the integrity of installed files should system problems occur, execute the following command procedure:
$ @SYS$TEST:DOC$IVP
* Enter the destination parameter: PS
* Do you want the IVP queued automatically [YES]? [Return]
|
If the IVP fails for any reason, the following messages are displayed:
%DOC-I-IVP_FAILURE, DECdocument V3.2 IVP failed.
%VMSINSTAL-E-IVPFAIL, The IVP for DOC V3.2 has failed.
|
You must edit the system startup file to provide for automatic startup of DECdocument when your system is rebooted.
Add the command line that starts DECdocument to the system startup file,
The following example shows how the system startup file can be edited to include the DECdocument startup command line:
$ @SYS$MANAGER:STARTNET.COM
.
.
.
$ @SYS$STARTUP:DOC$STARTUP.COM
|
If you want to run DECdocument on multiple nodes of a VAXcluster, first check to see that you have the appropriate software license. Then, execute the following commands after installing DECdocument:
$ RUN SYS$SYSTEM:SYSMAN
SYSMAN> SET ENVIRONMENT/CLUSTER
SYSMAN> DO @SYS$STARTUP:DOC$STARTUP.COM
SYSMAN> DO INSTALL REPLACE SYS$SHARE:DCLTABLES.EXE
SYSMAN> EXIT
|
For more information about the SYSMAN utility, see the VMS SYSMAN Utility Manual.
3.4 User Account Requirements
To work with DECdocument, user accounts on your system must have
certain privileges and quotas. The next two sections contain
information on these requirements.
3.4.1 Privileges
To use DECdocument, each account must have at least the TMPMBX and
NETMBX privileges. Use the VMS Authorize Utility to determine whether
users have the privileges they require.
3.4.2 User Account Quotas
You must make sure that the appropriate user accounts have sufficient
quotas to be able to use DECdocument Version 3.2.
Table 3-1 summarizes the required user account quotas.
| Account Quota | Value |
|---|---|
| BYTLM | 8192 |
| ENQLM | 100 |
| FILLM | 30 |
| PGFLQUOTA | 25,000 |
| TQELM | 10 |
See Section 1.4.3 for a description of how to verify and change account quotas.
3.5 System-Wide Tasks
Perform the following system-wide tasks after the installation:
$ @SYS$STARTUP:DOC$STARTUP.COM
|
The following sections describe additional steps and conditions that must exist before the system is made available to users.
3.6 Check Your LN03 Printer
DECdocument system support for LN03 output requires that the LN03 be
equipped with a minimum of two LN03X-CR RAM cartridges to download the
necessary fonts. Without RAM cartridges, the LN03 has only 27K RAM;
each cartridge adds an additional 128K.
If the output produced by the LN03 has erratic characteristics (for example, if white space occurs where text should be) or if the LN03 displays the numbers 2 and 4 on its LED display while printing the file, you need to order the cartridges and install them to get LN03 output.
For correct printing of LN03 output files, the terminal queue characteristics and the device's switch settings must be verified. Discussion of terminal queue characteristics and LN03 bit settings are discussed in the following sections.
3.6.1 Terminal Queue Characteristics
The following list summarizes the terminal queue characteristics
required for correct output of DECdocument output files produced for
the LN03. In the following example, TTcn: is the terminal
number of the LN03 printer.
Place the following commands in the system startup file to enable the terminal queue:
$ SET TERMINAL TTcn: -
_$ /SPEED=19200-
_$ /DEVICE=(LN03)-
_$ /PERMANENT/NOBROAD/NOECHO/FORM-
_$ /PAGE=66/NOTYPEAHEAD/WIDTH=80/NOWRAP
$ SET DEVICE TTcn:/SPOOLED=(queue-name,SYS$DEVICE:TTcn)
$ INITIALIZE/QUEUE/START/NOENABLE queue-name/ON=TTcn:
|
The queue-name is the same queue name specified in the installation procedure.
3.6.2 LN03 Bit Settings
You can determine the bit settings on your LN03 by pressing the Test
Button on the back of the device. The summary sheet settings should be
as follows:
S U M M A R Y S H E E T Revision Level DEC004.4
SWITCH # SETTING MEANING
1-1 OFF SERIAL INPUT
2 ON
3 ON 19200 BAUD
4 ON
5 OFF 8 DATA BITS
6 OFF PARITY DISABLED
2-1 ON
2 OFF LN03 DEVICE ID
3 OFF
4 OFF AUTO WRAP OFF
5 OFF XON/XOFF ENABLED
6 OFF
|
Note that the revision level must be 004.4 or greater.
3.7 Error Conditions
If the installation procedure fails for any reason, the following
message is displayed:
DOC V3.2 Installation failed.
Please consult the DECdocument Installation Guide for further information.
|
An error during the installation can be caused by one or more of the following conditions:
For descriptions of the error messages generated by these conditions, see the VMS System Messages and Recovery Procedures Reference Volume and your processor-specific installation/operations guide.
If you are notified that any of these conditions exist, you should take the appropriate action, as described in the message. You may need to change a system parameter or increase an authorized quota value. For information on requirements, see Chapter 2.
If the installation fails, you must restart the installation procedure from step 2. If the installation fails due to an IVP failure, contact a Digital field service representative.
3.7.1 IVP Error Conditions
If the Installation Verification Procedure fails for any reason, you
receive OpenVMS system messages indicating the cause of the error. The
most likely problem areas are as follows:
The DECdocument development group may periodically issue maintenance updates of DECdocument. Each update consists of an installation kit. You should install this kit as described in this guide or in any documentation that may accompany the maintenance update.
Each time a maintenance update is released, the version number changes. For example, if the current version is 1.0, the version number of the first maintenance update will be 1.1. In addition, the maintenance update will usually include changes to the release notes. The release notes describe the changes that have been made to DECdocument since the previous release.
The update release notes are provided online. You can read the release notes before you install DECdocument and at any time after the product is installed. For information on reading the release notes before DECdocument is installed, follow the installation procedure through step 7. To read the release notes after installing the product, display or print the file SYS$HELP:DOC032.RELEASE_NOTES.
3.9 Determining and Reporting Problems
If you encounter a problem while using DECdocument, report it to
Digital. Depending on the nature of the problem and the type of support
you have, you can take one of the following actions:
Review the Software Product Description (SPD) for an explanation of warranty. If you encounter a problem during the warranty period, report the problem as indicated above or follow alternate instructions provided by Digital for reporting SPD nonconformance problems.
This appendix contains a log file from an installation of DECdocument on an Alpha system. The sample shows a Motif-based installation procedure.
Be sure to read this installation guide and the release notes which note any significant changes in the installations that vary from this example before you install this product.
The example installation assumes that DECnet has been shut down, that no users are logged on to your system, and that OPTIONS N is not specified. The Installation Verification Procedure (IVP) runs at the end of the installation.
A.1 Motif-Based DECdocument Installation
$ @sys$update:vmsinstal doc032 mua0:
OpenVMS AXP Software Product Installation Procedure V6.2
It is 11-APR-1997 at 09:32.
Enter a question mark (?) at any time for help.
* Are you satisfied with the backup of your system disk [YES]? yes
The following products will be processed:
DOC V3.2
Beginning installation of DOC V3.2 at 09:32
%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.
Installation of DECdocument V3.2a
Copyright 1995-1997 Touch Technologies, Inc.
beginning at 11-APR-1997 09:32:57.87.
In order to run DECdocument, you must have its product authorization key
registered and loaded.
Product: DOCUMENT
Producer: DEC or TTI
Version: 3.2A
Release Date: dd-mmm-yyyy
* Does this product have an authorization key registered and loaded? yes
* Do you want to run the IVP after the installation [YES]? yes
* Do you want to purge files replaced by this installation [YES]? yes
You will now be asked for the device and directory where you want
the DECdocument files to be stored. The files will be stored in a
directory tree called [DOC$TOOLS...] on the device and directory
you specify. A system-wide logical name called DOC$ROOT will be
created to refer to this directory tree.
* Enter the device and directory where [DOC$TOOLS] should
be created [SYS$SYSDEVICE:[000000]]: sys$sysdevice:[000000]
Support for the use of SDML with LSE cannot be installed because
version 3.2 or higher of the Language-Sensitive Editor is not installed
on this system. If you want the Language-Sensitive Editor support, you
must do the following:
1. Install the Language-Sensitive Editor version 3.2 or greater
2. Set default to the SYS$LIBRARY directory
3. Link the SDML.ENV file using the following command:
$ lsedit/nodisp/nosyst/envi=(SDML)/nosect/command=(doc$lseupdate_env.tpu)
These steps can be taken any time after this installation is completed.
There is no need to stop the current installation.
The IVP will execute a DOCUMENT command. You must supply
the destination parameter for this DOCUMENT command and then
indicate whether you want the output queued automatically.
+-----------------------------------------------------------------+
| **** NOTICE **** |
| |
| The IVP for this installation of DECdocument should not be |
| run against an LN03 destination until the LN03 fonts are |
| installed. Do not select an LN03 destination for this IVP. |
+-----------------------------------------------------------------+
* Enter the IVP destination parameter
(BOOKREADER,PS,LINE,MAIL,TERMINAL): ps
* Do you want the IVP output queued automatically [YES]? no
VMS DECwindows/Motif is installed on this system.
DECdocument Graphics Editor Installation Options:
1. Install DECdocument Graphics Editor V3.2a-Motif
2. Do not install Graphics Editor
* Select option [1]: 1
Installation of the Graphics Editor will require between 3600 and
15600 free blocks on the target medium, depending on selected options.
A library of drawings is available to you.
* Do you want to install the library of drawings (12000 blocks) [NO]? yes
* Where should the library of drawings be installed
[SYS$COMMON:[SYSHLP.EXAMPLES.DOC_GRAPHICS]]:
The DECdocument Graphics Editor drawings files will be installed in
SYS$COMMON:[SYSHLP.EXAMPLES.DOC_GRAPHICS]
There are two additional pieces of documentation available to you. One
is a Bookreader version of the Graphics Editor User's Guide
(MOTIF_GRA.DECW$BOOK). The other is a Quick Reference card in Postscript
format (GRA_QUICKREF.PS). These files will be put in the SYS$HELP
directory if selected.
* Do you want the User's Guide in Bookreader form (2000 blocks) [NO]? yes
* Do you want the Quick Reference card (270 blocks) [NO]? yes
* Do you want to delete obsolete files from previous installations [YES]? yes
The DECdocument files will now be installed. Your VMS system
will be updated to include the new or modified files:
SYS$HELP:DOC032.RELEASE_NOTES
SYS$HELP:HELPLIB.HLB
SYS$SHARE:DCLTABLES.EXE
SYS$STARTUP:DOC$STARTUP.COM
SYS$MESSAGE:DOC$MSG.EXE
Upon completion of this installation, please be sure to do the following:
. Edit the system startup file (SYS$STARTUP:SYSTARTUP_VMS.COM) so that
it will execute the command @SYS$STARTUP:DOC$STARTUP.COM. This
insures that DOCUMENT will be available after the next system boot.
. If you are on a cluster, you should execute the following commands:
$ RUN SYS$SYSTEM:SYSMAN
SYSMAN> SET ENVIRONMENT/CLUSTER
SYSMAN> DO @SYS$STARTUP:DOC$STARTUP.COM
SYSMAN> DO INSTALL REPLACE SYS$SHARE:DCLTABLES.EXE
SYSMAN> EXIT
This will make DECdocument available to all properly licensed
nodes of the cluster prior to the next system boot.
End of prompts. Now beginning restoration of savesets.
No further questions will be asked. Installation should
be complete in 25-35 minutes.
%VMSINSTAL-I-RESTORE, Restoring product save set B ...
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.DEVBUILD].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.DEVBUILD.MESSAGES].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.EXAMPLES].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.GHOSTSCRIPT].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.LOCAL].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.LOCAL.FORMATS].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.LOCAL.TEMPLATES].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.LOCAL.TOOLS].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.TEMPLATES].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.TEX].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.TEX.BOOKR].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.TEX.FORMATS].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.TEX.LN03].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.TEX.LPR].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.TEX.LPR.FONTS].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.TEX.LPR.TOOLS].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.TEX.POSTSCRIPT].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.TOOLS].
%VMSINSTAL-I-RESTORE, Restoring product save set C ...
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.TEX.LN03.FONTS].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.TEX.LN03.TOOLS].
%VMSINSTAL-I-RESTORE, Restoring product save set D ...
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.TEX.POSTSCRIPT.FONTS].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.TEX.POSTSCRIPT.TOOLS].
%VMSINSTAL-I-RESTORE, Restoring product save set E ...
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.TEX.BOOKR.FONTS].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
TEST$DKA400:[DOC$TOOLS.TEX.BOOKR.TOOLS].
%VMSINSTAL-I-RESTORE, Restoring product save set G ...
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
VMI$ROOT:[SYSHLP.EXAMPLES.DOC_GRAPHICS].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
SYS$COMMON:[SYSHLP.EXAMPLES.DOC_GRAPHICS].
%CREATE-I-EXISTS, SYS$COMMON:[SYSHLP.EXAMPLES.DOC_GRAPHICS] already exists
%VMSINSTAL-I-RESTORE, Restoring product save set H ...
%VMSINSTAL-I-RESTORE, Restoring product save set I ...
Installation of DECdocument V3.2a completed
successfully at 11-APR-1997 09:41:40.21.
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...
Starting DECdocument V3.2a
%DOC-I-IVPSTART, DECdocument V3.2A Installation Verification Procedure
%DOC-I-IVPRUN, Running DECdocument ...
%DOC-I-IDENT, DECdocument V3.2A (c) 1995-1997 Touch Technologies, Inc.
[ T a g T r a n s l a t i o n ]...
%TAG-I-DEFSLOADD, End of Loading of Tag Definitions
%TAG-I-SETCONDTN, Setting condition SOFTWARE
on line 1 of file DOC$ROOT:[TEMPLATES]DOC$SAMPLE.SDML;1
%TAG-I-ENDPASS_1, End of first pass over the input
[ T e x t F o r m a t t i n g ]...
%TEX-I-PAGESOUT, 12 pages written.
-TEX-I-OUTFILENAME, 'DOC$ROOT:[TEMPLATES]DOC$SAMPLE.DVI_PS'
[ C o n t e n t s G e n e r a t i o n ]...
[ T e x t F o r m a t t i n g C o n t e n t s ]...
%TEX-I-PAGESOUT, 1 page written.
-TEX-I-OUTFILENAME, 'DOC$ROOT:[TEMPLATES]DOC$SAMPLE_CONTENTS.DVI_PS'
[ I n d e x G e n e r a t i o n ]...
%INX-I-READING, reading file 'DOC$ROOT:[TEMPLATES]DOC$SAMPLE.INX'
%INX-I-WRITING, writing file 'DOC$ROOT:[TEMPLATES]DOC$SAMPLE_INDEX.TEX;'
%INX-S-CREATED, 'DOC$ROOT:[TEMPLATES]DOC$SAMPLE_INDEX.TEX;' created
[ T e x t F o r m a t t i n g I n d e x ]...
%TEX-I-PAGESOUT, 2 pages written.
-TEX-I-OUTFILENAME, 'DOC$ROOT:[TEMPLATES]DOC$SAMPLE_INDEX.DVI_PS'
[ D e v i c e C o n v e r s i o n ]...
%DVC-I-INCLUDING, including input file:
DOC$ROOT:[TEMPLATES]DOC$SAMPLE_CONTENTS.DVI_PS
%DVC-I-INCLUDING, including input file:
DOC$ROOT:[TEMPLATES]DOC$SAMPLE_INDEX.DVI_PS
%DVC-I-PAGESOUT, 13 pages written to file:
DOC$ROOT:[TEMPLATES]DOC$SAMPLE.PS
%DOC-I-IVPSUCCESS, DECdocument V3.2A IVP was successful.
Installation of DECdocument V3.2a terminating at 11-APR-1997 09:47:20.40.
Installation of DOC V3.2 completed at 09:47
Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY
Creating installation data file: VMI$ROOT:[SYSUPD]DOC032.VMI_DATA
VMSINSTAL procedure done at 09:47
|
| Previous | Next | Contents |