DECdocument Installation Guide 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 NOTICE __________ Copyright ©1995, 1997 Touch Technologies, Inc. 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 ____________________________________________________________ PREFACE vii __________________________________________________________________ CHAPTER 1 PREPARING FOR DECDOCUMENT INSTALLATION 1-1 ____________________________________________________________ 1.1 REQUIRED OPERATING SYSTEM COMPONENTS 1-1 ____________________________________________________________ 1.2 PREREQUISITE AND OPTIONAL SOFTWARE 1-1 ____________________________________________________________ 1.3 LICENSE REGISTRATION 1-2 ____________________________________________________________ 1.4 INSTALLATION PROCEDURE REQUIREMENTS 1-2 1.4.1 Privileges and Disk Space ______________ 1-2 1.4.2 System Parameters ______________________ 1-3 1.4.2.1 Checking System Parameter Values o 1-4 1.4.2.2 Calculating the Values for GBLPAGES and GBLSECTIONS o 1-4 1.4.2.3 Changing System Parameter Values with AUTOGEN o 1-5 1.4.3 Process Account Quotas _________________ 1-6 1.4.4 VMSINSTAL Requirements _________________ 1-7 1.4.5 Backing Up Your System Disk ____________ 1-8 __________________________________________________________________ CHAPTER 2 INSTALLING DECDOCUMENT 2-1 ____________________________________________________________ 2.1 THE VMSINSTAL INSTALLATION PROCEDURE 2-1 ____________________________________________________________ 2.2 DETERMINING THE FILES AND LOGICAL NAMES ADDED TO THE SYSTEM 2-13 ____________________________________________________________ 2.3 ERROR RECOVERY 2-13 iii Contents __________________________________________________________________ CHAPTER 3 AFTER INSTALLING DECDOCUMENT 3-1 ____________________________________________________________ 3.1 RUNNING THE INSTALLATION VERIFICATION PROCEDURE SEPARATELY 3-1 ____________________________________________________________ 3.2 EDITING THE SYSTEM FILES 3-2 ____________________________________________________________ 3.3 VAXCLUSTER CONSIDERATIONS 3-2 ____________________________________________________________ 3.4 USER ACCOUNT REQUIREMENTS 3-3 3.4.1 Privileges _____________________________ 3-3 3.4.2 User Account Quotas ____________________ 3-3 ____________________________________________________________ 3.5 SYSTEM-WIDE TASKS 3-3 ____________________________________________________________ 3.6 CHECK YOUR LN03 PRINTER 3-4 3.6.1 Terminal Queue Characteristics _________ 3-4 3.6.2 LN03 Bit Settings ______________________ 3-5 ____________________________________________________________ 3.7 ERROR CONDITIONS 3-5 3.7.1 IVP Error Conditions ___________________ 3-6 ____________________________________________________________ 3.8 MAINTENANCE UPDATES 3-6 ____________________________________________________________ 3.9 DETERMINING AND REPORTING PROBLEMS 3-7 __________________________________________________________________ APPENDIX A SAMPLE INSTALLATION A-1 ____________________________________________________________ A.1 MOTIF-BASED DECDOCUMENT INSTALLATION A-1 __________________________________________________________________ APPENDIX B FILES AND LOGICAL NAMES INSTALLED ON YOUR SYSTEM B-1 ____________________________________________________________ B.1 FILE NAMES B-1 iv Contents ____________________________________________________________ B.2 DIRECTORY NAMES B-12 ____________________________________________________________ B.3 LOGICAL NAMES B-13 __________________________________________________________________ APPENDIX C USER NOTES C-1 __________________________________________________________________ TABLES 1-1 Space Requirements on System Disk ____________ 1-3 1-2 Minimum Required System Parameter Values _____ 1-3 1-3 Process Account Quotas for the Installing Account ______________________________________ 1-6 3-1 User Account Quotas for Using DECdocument ____ 3-3 v __________________________________________________________________ Preface __________________________________________________________________ Purpose of this Guide 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. __________________________________________________________________ Intended Audience The audience for this guide is the system manager who installs DECdocument software. __________________________________________________________________ Structure of this Document This guide is organized as follows: o Chapter 1 describes the operating system and hardware requirements for DECdocument installation and related procedures that you complete before installing DECdocument. o Chapter 2 describes the step-by-step instructions for the installation. o Chapter 3 describes actions and considerations after the installation. o Appendix A contains a sample listing for DECdocument installation. o Appendix B contains the names of files, directories, and logical names installed on your system. __________________________________________________________________ Manuals in the DECdocument Documentation Set This manual is part of the DECdocument documentation set that includes the following manuals: o Installation Guide o Tutorial and Application Guide o Producing Online and Printed Documentation o Using Global Tags o Using Doctypes and Related Tags - 2 Volumes o Tags Quick Reference vii Preface o Command Summary and Processing Messages o Graphics Editor User's Guide for Motif __________________________________________________________________ Related Manuals For additional information on installing DECdocument Version 3.2, refer to the OpenVMS system documentation on these topics: o VMSINSTAL procedure o INSTALL utility o System management and operations __________________________________________________________________ Conventions 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. In procedures, a sequence such as indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button. 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.) viii __________________________________________________________________ 1 Preparing for DECdocument Installation 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-1 Preparing for DECdocument Installation __________________________________________________________________ 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: o Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your License PAK. o At the DCL prompt, enter the LICENSE REGISTER command with the appropriate qualifiers that correspond to License PAK information. 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: o CMKRNL o WORLD o SYSPRV 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. 1-2 Preparing for DECdocument Installation Table_1-1_Space_Requirements_on_System_Disk____________________ TASK_______VAX_________Alpha___________________________________ Installatio88,600 90,100 blocks blocks (44.3MB) (45.1MB) Permanent: 78,000 78,000 blocks 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 ___________________________ 1.4.2 System Parameters 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. Table_1-2_Minimum_Required_System_Parameter_Values_____________ System_Parameter_______Minimum_Value___________________________ GBLPAGES 102 GBLSECTIONS[1] 1 VIRTUALPAGECNT 15000 _______________________________________________________________ [1]The values listed for these system parameters represent the number of free global pages and global sections required for the installation, not the total number you need to run your system and other software. _______________________________________________________________ The following sections show you how to: o Check system parameter values o Calculate values for the GBLPAGES and GBLSECTIONS system parameters o Change parameter values with the VMS AUTOGEN command procedure 1-3 Preparing for DECdocument Installation _____________________ 1.4.2.1 Checking System Parameter Values 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 Preparing for DECdocument Installation _____________________ 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-5 Preparing for DECdocument Installation ___________________________ 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. Table_1-3_Process_Account_Quotas_for_the_Installing_Account____ Account Quota__________Value___________________________________________ ASTLM 24 BIOLM 18 BYTLM 18,000 DIOLM 18 ENQLM 30 FILLM 30 PGFLQUOTA______25,000__________________________________________ ____________________ Note ____________________ 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: 1-6 Preparing for DECdocument Installation $ 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: o Whether you have set your default device and directory to SYS$UPDATE o Whether you are logged in to a privileged account o Whether you have adequate quotas for installation o Whether DECnet is running o Whether any users are logged in to the system Note that the VMSINSTAL requires that the installation account have a minimum of the following quotas: ASTLM = 24 BIOLM = 18 BYTLM = 18,000 DIOLM = 18 ENQLM = 30 FILLM = 20 1-7 Preparing for DECdocument Installation 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. 1-8 __________________________________________________________________ 2 Installing DECdocument This chapter explains how to install DECdocument. Section 2.1 contains a step-by-step description of the installation procedure. ____________________ Note ____________________ DECdocument for OpenVMS VAX and DECdocument for OpenVMS Alpha are both included on the media. DECdocument will determine the system type and take appropriate action. The installation steps are identical for both products. __________________________________________________________________ 2.1 The VMSINSTAL Installation Procedure The DECdocument installation procedure consists of a series of questions and informational messages. See Appendix A for the sample installation. To abort the installation procedure at any time, press Ctrl/Y. When you press Ctrl/Y, the installation procedure deletes all files it has created up to that point and exits. You can then start the installation again. Log in to a privileged account. Log in to a privileged account and set your default device and directory to SYS$UPDATE. Username: SYSTEM Password: $ SET DEFAULT SYS$UPDATE Invoke VMSINSTAL. @SYS$UPDATE:VMSINSTAL DOC032 ddcu: OPTIONS N 2-1 Installing DECdocument To start the installation, invoke the VMSINSTAL command procedure from a privileged account, such as the SYSTEM account. VMSINSTAL is in the SYS$UPDATE directory. The following list defines the elements of the VMSINSTAL command procedure: DOC032 The installation name for the component (DECdocument 3.2). ddcu: The name of the device on which you plan to mount the media. For example, MTA0: is the device name for a tape drive. It is not necessary to use the console drive for this installation. However, if you do use the console drive, you should replace any media you removed once the installation is complete. If you are installing from a CD-ROM, this is the name of the CD drive and you would use this command: $ @SYS$UPDATE:VMSINSTAL DOC032 cd-drive-name:[DECDOC032.KIT] OPTIONS N OPTIONS N An optional parameter that indicates you want to see the question on release notes. If you do not include the OPTIONS N parameter, VMSINSTAL does not ask you about the release notes. You should review the release notes before proceeding with the installation in case they contain additional information about the installation. If you are restarting the installation and have already reviewed the release notes, you do not need to specify OPTIONS N. Note that there are several other options you can select when you invoke VMSINSTAL: o Auto_answer option (A): Initially creates a file that contains your answers to VMSINSTAL questions and prompts. You can then use the option (and the answer file) to save time during a reinstallation (typically after upgrading your system). o Get save set option (G): Lets you store product save sets temporarily on a magnetic tape or in a disk directory. o File log option (L): Logs all activity to the terminal during installation. o Alternate root option (R): Lets you install the product to a system root other than that of the running system. 2-2 Installing DECdocument See the VMS documentation on software installation in the VMS System Management Subkit for detailed information on these options. If you specify more than one option, separate the options with commas (OPTIONS A,N). The following example invokes VMSINSTAL to install DECdocument from device MUA0: on an Alpha system and shows the system response. This example uses the OPTIONS N release note parameter. $ @SYS$UPDATE:VMSINSTAL DOC032 MUA0: OPTIONS N 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. If you do not supply either the product name or the device name, VMSINSTAL prompts you for this information later in the installation procedure. VMSINSTAL does not prompt you for any options, so be sure to include OPTIONS N on the VMSINSTAL command line to access the release notes during the installation. Confirm system backup. * Are you satisfied with the backup of your system disk [YES]? VMSINSTAL asks if you are satisfied with your system backup. You should always back up your system disk before performing an installation. If you are satisfied with the backup of your system disk, press to accept the YES default. Otherwise, enter NO to discontinue the installation. After you back up your system disk, you can restart the installation. Beginning the install. The following products will be processed: DOC V3.2 Beginning installation of DOC V3.2 at 09.32 %VMSINSTAL-I-RESTORE, Restoring product saveset A... 2-3 Installing DECdocument You should now mount the distribution media on the device you specified when you invoked VMSINSTAL if you have not already done so. The device name appears in the line preceding the "mount" question if the media has not been mounted and, VMSINSTAL will ask you if you are ready to continue with the installation. If you respond YES to indicate that you are ready, VMSINSTAL displays a message that the media containing DECdocument has been mounted on the specified device and that the installation has begun. If you entered the wrong device name when you invoked VMSINSTAL and need to restart the installation, enter NO in response to the "Are you ready?" question. To abort the installation for other reasons, press Ctrl/Y. Mount additional media volumes. If your installation kit contains more than one volume, VMSINSTAL prompts you to mount the additional volumes and then asks you to indicate that you are ready for the installation to proceed. Select a release notes option. Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: If you specified OPTIONS N when you invoked VMSINSTAL, you are now asked to choose one of the four options for reviewing the release notes. If you select option 1, VMSINSTAL displays the release notes immediately on the console terminal. You can terminate the display at any time by pressing Ctrl/C. If you select option 2, VMSINSTAL prompts you for the name of the print queue that you want to use: 2-4 Installing DECdocument * Queue name [SYS$PRINT]: You can press Return to send the file to the default output print device or you can enter another queue name. If you select option 3, VMSINSTAL displays the release notes immediately on the console terminal and then prompts you for a queue name for the printed version. Select option 4 if you have already reviewed the release notes and are restarting the installation. Next, VMSINSTAL displays the following question: * Do you want to continue the installation [N]?: YES %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. To continue the installation, enter YES. Otherwise, press . In either case, the release notes are copied to a file in the SYS$HELP directory: SYS$HELP:DOC032.RELEASE_NOTES After the installation, you can enter the following command to review the release notes through the Help facility: $ HELP DOCUMENT RELEASE_NOTES ____________________ Note ____________________ The name of the release notes file installed by VMSINSTAL consists of the current product name and version number. Do not delete release notes for previous versions of DECdocument. Respond to license registration queries. Installation of DECdocument V3.2 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.2 Release Date: dd-mmm-yyyy * Does this product have an authorization key registered and loaded? 2-5 Installing DECdocument The installation procedure displays license information about your product and then asks if you have registered and loaded your Product Authorization Key (PAK). If you have not registered and loaded your PAK, you must answer NO to this question. You have to register and load your PAK to successfully complete the installation. If you have not done so, you should stop the installation, register and load your PAK, and then restart the installation. Choose the Installation Verification Procedure (IVP) option. * Do you want to run the IVP after the installation [YES]? The installation procedure now asks if you want to run the IVP. The IVP for DECdocument checks to be sure that the installation is successful. It is recommended that you run the IVP; however if you run the IVP and your open file quota for the current process is not 30 or greater, you see the following message and prompt: The open file quota for your process is less than 30. The installation of DECdocument can proceed, but the Installation Verification Procedure cannot be run unless the open file quota is increased to 30. You may want to stop installation, run the AUTHORIZE utility to increase your open file quota, log out and log in, then restart the installation. If you elect to proceed with the installation without increasing the open file quota, the IVP will be bypassed. * Do you want to proceed with the installation [NO]? Enter NO to terminate the installation so that you can increase the open file quota for your process (refer to Section 1.4.3 for additional information). If you type YES, the installation continues but the IVP is not run. After DECdocument is installed, you can run the IVP independently to verify that the software is available on your system. You might need to run the IVP after a system failure to make sure that users can access DECdocument. 2-6 Installing DECdocument Purge files. * Do you want to purge files replaced by this installation [YES]? You have the option to purge files from previous versions of DECdocument that are superseded by this installation. Purging is recommended; however, if you need to keep files from the previous version, enter NO in response to the question. Select a device and directory. You must specify a storage area for DECdocument files. The following message is displayed: 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. If this is a reinstallation of DECdocument, the logical name DOC$ROOT is already defined. If DOC$ROOT is already defined, you are asked whether you want to restore the [DOC$TOOLS . . . ] tree to that device and directory: The logical name DOC$ROOT is already defined. It refers to the directory ddcu:[dir]. * Do you want to install the new files at that same location [YES]? You should install DECdocument onto the same device and directory. If you do not, the existing [DOC$TOOLS . . . ] tree will not be accessible through the logical name DOC$ROOT. If the logical name DOC$ROOT is not currently defined, you receive the following prompt: * Enter the device and directory where [DOC$TOOLS...] should be created [SYS$SYSDEVICE:[000000]]: Enter the name of the device and directory on which you want the [DOC$TOOLS...] tree installed, or press Return to install on the system disk. ____________________ Note ____________________ The directories SYS$HELP, SYS$LIBRARY, SYS$MANAGER, and SYS$MESSAGE, and all files in the [DOC$TOOLS . . . ] directory tree may contain previous versions of DECdocument 2-7 Installing DECdocument files. This may happen if you stop an installation and then restart it. Any such files are replaced during the restarted installation with new files, but the old files are not automatically purged. Purging is recommended. In response to a purging prompt, press Return to purge the files or type NO to keep them. Select LSE support. If the Language-Sensitive Editor (LSE) is not installed on your system, you do not receive a prompt for the installation of SDML with LSE. Instead, you receive an informational message stating that LSE is not installed: 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. If your system has LSE installed, the procedure instead supplies a prompt for the support of SDML with LSE option. You can choose to install this option or continue the installation with the prompt for the next option. DECdocument provides support for the preparation of documents that use the Standard Digital Markup Language (SDML) with the Language- Sensitive Editor (LSE). * Do you want support for SDML use with LSE [YES]? Select an IVP destination. If you indicated that you want the IVP executed after installation, you are asked to specify the command-line destination parameter that corresponds to the device to which you want to send the output of the DOCUMENT command execution (for example, PS, LN03 or LINE). You are also asked if you want the output to be queued automatically to that device. 2-8 Installing DECdocument 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. If you do not have LN03 fonts installed on your system, you will receive the following notice: +-------------------------------------------------------------------+ ! **** 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]? * Enter the printer queue name: queue_name If you have not set up the printing device, reply NO to this prompt. The DECdocument files will now be installed. Your OpenVMS system will be updated to include the new or modified files: SYS$HELP:DOC032.RELEASE_NOTES Select the Graphics Editor Option. At this point, you have the option of installing the Graphics Editor. The Graphics Editor is available for Motif. DECdocument will determine if DECWindows is installed on the system. If so, DECdocument will then determine which version of DECWindows is installed. o If DECWindows Motif is installed, you will see the following display: VMS DECwindows/Motif is installed on this system. DECdocument Graphics Editor Installation Options: 1. Install DECdocument Graphics Editor V3.2-Motif 2. Do not install Graphics Editor * Select option [1]: If you select option 1, the Graphics Editor V3.2-Motif is installed. You will be asked the following questions: 2-9 Installing DECdocument 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]? * Where should the library of drawings be installed [SYS$COMMON:[SYSHLP.EXAMPLES.DOC_GRAPHICS]]: If you choose to have the library of drawings installed, the following is displayed: The DECdocument Graphics Editor drawings files will be installed in SYS$COMMON:[SYSHLP.EXAMPLES.DOC_GRAPHICS] The installation continues, and the following is displayed: 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]? * Do you want the Quick Reference card (270 blocks) [NO]? Delete obsolete files. If you want to delete the obsolete files from previous DECdocument installations, select Yes by pressing Return at the next question: * Do you want to delete obsolete files from previous installations [YES]? o If DECWindows is not installed on the system, the DECdocument Graphics Editor will not be installed; no questions are asked. Read informational messages. At this point, the installation procedure displays a number of informational messages that report on the progress of the installation. There are no further questions. If the installation procedure has been successful up to this point, VMSINSTAL moves the new or modified files to their target directories, updates help files, and updates DCL tables, if necessary. If you chose to have files purged, that work is done now. 2-10 Installing DECdocument After responding to the last prompt, you see the following message: 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 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. Note: For VAX V5.*, the system startup file is SYS$STARTUP:SYSTARTUP_V5.COM. For VAX V6.* the system startup file is SYS$STARTUP:SYSTARTUP_VMS.COM. Refer to Section 3.3 for more information. The installation procedure displays the following message: End of prompts. Now beginning restoration of savesets. No further questions will be asked. Installation should be complete in 25-35 minutes. Additional messages are displayed as VMSINSTAL restores backup savesets and creates directories; for example: %VMSINSTAL-I-RESTORE, Restoring product saveset B ... . . %VMSINSTAL-I-RESTORE, Restoring product saveset C ... . . %VMSINSTAL-I-RESTORE, Restoring product saveset D ... . . . %VMSINSTAL-I-RESTORE, Restoring product save set H ... %VMSINSTAL-I-RESTORE, Restoring product save set I ... 2-11 Installing DECdocument Installation of DECdocument V3.2 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.2 Observe the IVP. If you chose to run the IVP, VMSINSTAL runs it now. When the IVP runs successfully, you see the following display: %DOC-I-IVPSTART, DECdocument V3.2 Installation Verification Procedure %DOC-I-IVPRUN, Running DECdocument ... %DOC-I-IDENT, DECdocument V3.2 (c) 1995-1997 Touch Technologies, Inc. . . . %DVC-I-PAGESOUT, 13 pages written to file: DOC$ROOT:[TEMPLATES]DOC$SAMPLE.PS %DOC-I-IVPSUCCESS, DECdocument V3.2 IVP was successful. With the successful completion of the IVP, your installation of DECdocument is finished and completion messages are displayed. If the execution of DECdocument fails, you will see the following messages: %DOC-I-IVP_FAILURE, DECdocument V3.2 IVP failed. %VMSINSTAL-E-IVPFAIL, The IVP for DOC V3.2 has failed. See Section 3.7 if you receive this message. End the installation procedure. The following installation completion messages are displayed: Installation of DECdocument V3.2 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 You can now log out of the privileged account: 2-12 Installing DECdocument $ LOGOUT SYSTEM logged out at 11-APR-97 09:48:06.13 ____________________ Note ____________________ Note that VMSINSTAL deletes or changes entries in the process symbol tables during the installation. Therefore, if you are going to continue using the system manager's account and you want to restore these symbols, you should log out and log in again. __________________________________________________________________ 2.2 Determining the Files and Logical Names Added to the System 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: o The operating system version is incorrect. o Quotas necessary for successful installation are insufficient. o System parameter values for successful installation are insufficient. o The OpenVMS help library is currently in use. o The product license has not been registered and loaded. 2-13 Installing DECdocument 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. 2-14 __________________________________________________________________ 3 After Installing DECdocument The following tasks take place after installing DECdocument: o Running the Installation Verification Procedure (IVP) separately o Editing the system startup and shutdown files o Modifying system parameter settings o Making the product usable on a VAXcluster o Setting user account quotas o Tailoring your system o Enhancing performance o Reporting problems __________________________________________________________________ 3.1 Running the Installation Verification Procedure Separately 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]? 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. 3-1 After Installing DECdocument __________________________________________________________________ 3.2 Editing the System Files 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, SYS$STARTUP:SYSTARTUP_V5.COM - if VAX V5.4 - V5.5 SYS$STARTUP:SYSTARTUP_VMS.COM - if V6.0 or greater 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 __________________________________________________________________ 3.3 VAXcluster Considerations 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-2 After Installing DECdocument __________________________________________________________________ 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. Table_3-1_User_Account_Quotas_for_Using_DECdocument____________ 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: 1 Edit the appropriate system startup file to provide for automatic startup of DECdocument when your system is rebooted. Add the following command line to the system startup file: 3-3 After Installing DECdocument $ @SYS$STARTUP:DOC$STARTUP.COM 2 Verify that all users of DECdocument have the requisite FILLM and PGFLQUOTA quotas. 3 If you are on a cluster, perform the commands outlined in Section 3.3. 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-4 After Installing DECdocument ___________________________ 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: o Insufficient disk space o Insufficient system virtual page count parameter o Insufficient AST quota o Insufficient buffered I/O byte count o Insufficient subprocess quota o Insufficient open file quota o Insufficient process paging file quota o Incorrect version of OpenVMS 3-5 After Installing DECdocument 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: o The output queue name is not correctly specified o The output device is not correctly set up for printing DECdocument output __________________________________________________________________ 3.8 Maintenance Updates 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-6 After Installing DECdocument __________________________________________________________________ 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: o Call Digital if your software contract or warranty agreement entitles you to telephone support. o Submit a Software Performance Report (SPR). 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. 3-7 __________________________________________________________________ A Sample Installation 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 A-1 Sample Installation * 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. A-2 Sample Installation * 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. A-3 Sample Installation %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]. A-4 Sample Installation %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 A-5 Sample Installation [ 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 A-6 __________________________________________________________________ B Files and Logical Names Installed on Your System The DECdocument installation procedure installs a number of files and directories on your system and defines some logical names. The following sections list the files and directories installed and the logical names that are added to the system logical name table. ____________________ Note ____________________ Some file names and extensions contain "_AXP" or "_VAX" depending on whether the DECdocument installation is on an Alpha system or a VAX system. __________________________________________________________________ B.1 File Names The following list contains the names of all new files installed on your system when DECdocument is installed. The few that are modified are denoted by an asterisk (*). Directory DOC$ROOT: DEVBUILD.DIR EXAMPLES.DIR GHOSTSCRIPT.DIR LOCAL.DIR TEMPLATES.DIR TEX.DIR TOOLS.DIR Directory DOC$ROOT:[DEVBUILD] MESSAGES.DIR (no files) Directory DOC$ROOT:[EXAMPLES] B-1 Files and Logical Names Installed on Your System ARTICLE_SAMPLE.SDML BORIS.BRF BORIS.PS COLOR_IN_DOC.PS COLOR_IN_DOC.SDML CUSTOM_DRAFT_BOX.PS DRAFT_BOX.PS EXERCISE_CHAP1.SDML EXERCISE_CHAP2.SDML EXERCISE_FRONT.SDML EXERCISE_PROFILE.DECW$BOOK EXERCISE_PROFILE.DECW$BOOKSHELF EXERCISE_PROFILE.PS EXERCISE_PROFILE.SDML EXERCISE_PROFILE.XREF LENDL.BRF LENDL.PS LETTER_SAMPLE.SDML MANUAL_SAMPLE.SDML MEMO_SAMPLE.SDML MILSPEC_DRAFT_SAMPLE.SDML MILSPEC_SECURE_SAMPLE.SDML OVERHEADS_SAMPLE.SDML REPORT_SAMPLE.SDML REPORT_TWOCOL_SAMPLE.SDML SHRIVER.BRF SHRIVER.PS UNDERLAY.PS UNDERLAY_CUSTOM.PS Directory DOC$ROOT:[GHOSTSCRIPT] ALLOC.H ALPHABET.PS ANSI2KNR.C ANSI2KNR.MAN ANSIHEAD.MAK ARCH.H ASTATE.H BCHB.AFM BCHB.GSF BCHBI.AFM BCHBI.GSF BCHR.AFM BCHR.GSF BCHRI.AFM BCHRI.GSF BCWIN.MAK BDFTOPS. BDFTOPS.BAT BDFTOPS.PS BFONT.H BNUM.H BSEQ.H BTOKEN.H CC-HEAD.MAK CCFONT.H CCGS. CHEQ.PS CHESS.PS COLORCIR.PS COPYING. CP.BAT CYR.GSF CYRI.GSF DECRYPT.PS DEVS.MAK DICT.H DODEBUG.H DOS_.H DPARAM.H DRIVERS.DOC DS.TMP DSTACK.H ECHOGS.C EGA.C EGA.TR EMPTY.PS ERRORS.H ESCHER.PS ESTACK.H FILES.H FONT.H FONT2C. FONT2C.BAT FONT2C.PS FONTMAP. FONTS.DOC FONTS.MAK GCC-HEAD.MAK GCONFIG.C GCONFIG.H GCONFIGF.H GDEBUG.H GDEV3B1.C GDEV4081.C GDEVBGI.C GDEVBIT.C GDEVBJ10.C GDEVCDJ.C GDEVDFAX.C GDEVDFG3.H GDEVDJET.C GDEVDJTC.C GDEVEGAA.ASM GDEVEPSC.C GDEVEPSN.C GDEVGIF.C GDEVLBP8.C GDEVLN03.C GDEVMEM.H GDEVMEM1.C GDEVMEM2.C GDEVMEM3.C GDEVMSWN.C GDEVN533.C GDEVNP6.C GDEVPBM.C GDEVPCCM.C GDEVPCCM.H GDEVPCFB.C GDEVPCFB.H GDEVPCL.C GDEVPCL.H GDEVPCX.C GDEVPE.C GDEVPJET.C GDEVPRN.C GDEVPRN.H GDEVS3GA.C GDEVSNFB.C GDEVSUN.C GDEVSVGA.C GDEVSVGA.H GDEVTKNK.C GDEVTRFX.C GDEVX.C GDEVX.H GDEVXINI.C GENARCH.C GHOST.H GOLFER.PS GP.H GPCHECK.H B-2 Files and Logical Names Installed on Your System GP_DOSFB.C GP_ITBC.C GP_IWATC.C GP_MSDOS.C GP_MSWIN.C GP_MSWIN.H GP_SYSV.C GP_UNIX.C GP_VMS.C GS.C GS.C_951009 GS.DEF GS.H GS.MAK GS.RC GS.TR GSADDMOD. GSADDMOD.BAT GSBJ. GSBJ.BAT GSCHAR.C GSCHAR.H GSCHAR0.C GSCIE.C GSCIE.H GSCOLOR.C GSCOLOR.H GSCOLOR2.C GSCOLOR2.H GSCONFIG. GSCONFIG.BAT GSCOORD.C GSCOORD.H GSCRYPT1.H GSCSPACE.H GSDEVICE.C GSDJ. GSDJ.BAT GSDJ500.BAT GSDPS1.C GSERRORS.H GSFILE.C GSFONT.C GSFONT.H GSGRAPH.ICX GSIMAGE.C GSIMAGE2.C GSIMPATH.C GSLINE.C GSLJ. GSLJ.BAT GSLP. GSLP.BAT GSLP.PS GSMAIN.C GSMATRIX.C GSMATRIX.H GSMISC.C GSND. GSND.BAT GSNDT.BAT GSPAINT.C GSPAINT.H GSPATH.C GSPATH.H GSPATH2.C GSPROPS.H GSSETDEV. GSSETDEV.BAT GSSETMOD. GSSETMOD.BAT GSSTATE.C GSSTATE.H GST.BAT GSTDEV.C GSTEXT.ICX GSTYPE1.C GSTYPE1.H GSUID.H GSUTIL.C GSUTIL.H GSW.TR GS_2ASC.PS GS_AXP.EXE GS_AXP.OLB GS_DPS1.PS GS_FONTS.PS GS_INIT.PS GS_INIT.PS_951009 GS_INIT.PS_OLD GS_LEV2.PS GS_STATD.PS GS_VAX.EXE GS_VAX.OLB GX.H GXARITH.H GXBITMAP.H GXCACHE.C GXCACHE.H GXCHAR.H GXCLIST.C GXCLIST.H GXCOLOR.C GXCPATH.C GXCPATH.H GXDEVICE.H GXDEVMEM.H GXDITHER.C GXDRAW.C GXFDIR.H GXFILL.C GXFIXED.H GXFONT.H GXHINT1.C GXHT.C GXIMAGE.H GXLUM.H GXMATRIX.H GXOP1.H GXPATH.C GXPATH.H GXPATH2.C GXPCOPY.C GXSTROKE.C GXTYPE1.H GZCOLOR.H GZDEVICE.H GZHT.H GZLINE.H GZPATH.H GZSTATE.H HERSHEY.DOC HISTORY.DOC HRGE_R.GSF HRGE_RB.GSF HRGE_RO.GSF HRGK_C.GSF HRGK_S.GSF HRGR_R.GSF HRGR_RB.GSF HRGR_RO.GSF HRIT_R.GSF HRIT_RB.GSF HRIT_RO.GSF HRPL_R.GSF HRPL_RB.GSF HRPL_RO.GSF HRPL_S.GSF HRPL_SB.GSF HRPL_SBO.GSF HRPL_SO.GSF HRPL_T.GSF HRPL_TB.GSF HRPL_TBI.GSF HRPL_TI.GSF HRSC_C.GSF HRSC_CB.GSF HRSC_CO.GSF HRSC_S.GSF HRSC_SB.GSF HRSC_SO.GSF HRSY_R.GSF HUMOR.DOC IALLOC.C IBNUM.C IBSCAN.C ICCFONT.C IDEBUG.C IDICT.C IDPARAM.C IINIT.C IMPATH.PS INAME.C INTERP.C IREF.H ISAVE.C ISCAN.C IUTIL.C IUTIL.H IUTILASM.ASM B-3 Files and Logical Names Installed on Your System LANDSCAP.PS LANGUAGE.DOC LIB.DOC LINES.PS MAIN.H MAINT.MAK MAKE.DOC MALLOC_.H MAN.DOC MATH_.H MEMORY_.H MV.BAT NALLOC.H NAME.H NCRB.GSF NCRBI.GSF NCRR.GSF NCRRI.GSF NEWALLOC.MAK NEWS. NMMAN.H NPACKED.H NSAVE.H NSTD.H OPDEF.H OPER.H OSTACK.H OVERLAY.H PACKED.H PAGD.GSF PAGDO.GSF PAGK.GSF PAGKO.GSF PBKD.GSF PBKDI.GSF PBKL.GSF PBKLI.GSF PCHARSTR.PS PHVB.GSF PHVBO.GSF PHVR.GSF PHVRO.GSF PHVRRN.GSF PNCB.GSF PNCBI.GSF PNCR.GSF PNCRI.GSF PPATH.PS PPLB.GSF PPLBI.GSF PPLR.GSF PPLRI.GSF PRFONT.PS PS2IMAGE.PS PSFILES.DOC PSTOPPM.PS PSYR.GSF PTMB.GSF PTMBI.GSF PTMR.GSF PTMRI.GSF PUTB.GSF PUTBI.GSF PUTR.GSF PUTRI.GSF PV.SH PZDR.GSF QUIT.PS README. README.DOC RM.BAT SAVE.H SCANCHAR.H SCF.H SCFD.C SCFDGEN.C SCFDTAB.C SCFE.C SCFTAB.C SCREEN.PS SFILTER.C SFILTER2.C SHOWPAGE.PS SLZWD.C SLZWE.C SNOWFLAK.PS STATE.H STAT_.H STD.H STDIO_.H STORE.H STREAM.C STREAM.H STRING_.H SYM__ENC.PS TAR_CAT. TBCPLUS.MAK TCCOMMON.MAK TIGER.PS TIME_.H TIMING.PS TRACEOP.PS TURBOC.CFG TURBOC.MAK TYPE1OPS.PS UGLYR.GSF UNIQ.C UNIX-ANSI.MAK UNIX-CC.MAK UNIX-GCC.MAK UNIXHEAD.MAK UNIXTAIL.MAK UNPROT.PS USE.DOC VMS-CC.MAK VMS-GCC.MAK VMSMATH.H WATC.MAK WRFONT.PS X_.H ZARITH.C ZARRAY.C ZBSEQ.C ZCB.GSF ZCHAR.C ZCIE.C ZCOLOR.C ZCOLOR2.C ZCONTEXT.C ZCONTROL.C ZCR.GSF ZCRO.GSF ZDEVICE.C ZDICT.C ZDOSIO.C ZDPS1.C ZFILE.C ZFILEIO.C ZFILTER.C ZFILTER2.C ZFONT.C ZFONT0.C ZFONT1.C ZFONT2.C ZGENERIC.C ZGSTATE.C ZHT.C ZHT2.C ZIMAGE2.C ZK-9557.PS ZMATH.C ZMATRIX.C ZMISC.C ZPACKED.C ZPAINT.C ZPATH.C ZPATH2.C ZPROPS.C ZRELBIT.C ZSTACK.C ZSTRING.C ZTYPE.C ZUPATH.C ZVMEM.C B-4 Files and Logical Names Installed on Your System Directory DOC$ROOT:[LOCAL] FORMATS.DIR (no files) TEMPLATES.DIR (no files) TOOLS.DIR (no files) Directory DOC$ROOT:[TEMPLATES] ALASKA_ARTICLE.SDML ALASKA_MANUAL.SDML ALASKA_REPORT.SDML ALASKA_SOFTWARE.SDML COMMAND.SDML DOC$SAMPLE.SDML FURNITURE_OVERHEADS.SDML MILSPEC_80008A.SDML MILSPEC_80012A.SDML MILSPEC_80013A.SDML MILSPEC_80014A.SDML MILSPEC_80015A.SDML MILSPEC_80017A.SDML MILSPEC_80018A.SDML MILSPEC_80019A.SDML MILSPEC_80021A.SDML MILSPEC_80022A.SDML MILSPEC_80024A.SDML MILSPEC_80025A.SDML MILSPEC_80026A.SDML MILSPEC_80027A.SDML MILSPEC_80029A.SDML MILSPEC_80030A.SDML MILSPEC_80534A.SDML MILSPEC_DID_80008.SDML MILSPEC_DID_80009.SDML MILSPEC_DID_80010.SDML MILSPEC_DID_80011.SDML MILSPEC_DID_80012.SDML MILSPEC_DID_80013.SDML MILSPEC_DID_80014.SDML MILSPEC_DID_80015.SDML MILSPEC_DID_80016.SDML MILSPEC_DID_80017.SDML MILSPEC_DID_80018.SDML MILSPEC_DID_80019.SDML MILSPEC_DID_80020.SDML MILSPEC_DID_80021.SDML MILSPEC_DID_80022.SDML MILSPEC_DID_80023.SDML MILSPEC_DID_80024.SDML MILSPEC_DID_80025.SDML MILSPEC_DID_80026.SDML MILSPEC_DID_80027.SDML MILSPEC_DID_80028.SDML MILSPEC_DID_80029.SDML MILSPEC_DID_80030.SDML MILSPEC_DID_80031.SDML MILSPEC_SAMPLE.SDML MILSPEC_SYMBOLS.SDML ROUTINE.SDML SMITH_LETTER.SDML STATEMENT.SDML TAG.SDML Directory DOC$ROOT:[TEX] BOOKR.DIR FORMATS.DIR LN03.DIR LPR.DIR PostScript.DIR B-5 Files and Logical Names Installed on Your System Directory DOC$ROOT:[TEX.BOOKR] FONTS.DIR TOOLS.DIR Directory DOC$ROOT:[TEX.BOOKR.FONTS] AMEX140.TFM AMMI140.TFM AMR140.TFM AMSY140.TFM DECWAVANT100.TFM DECWAVANT120.TFM DECWAVANT140.TFM DECWAVANT180.TFM DECWAVANT240.TFM DECWAVANT80.TFM DECWAVANTD100.TFM DECWAVANTD120.TFM DECWAVANTD140.TFM DECWAVANTD180.TFM DECWAVANTD240.TFM DECWAVANTD80.TFM DECWAVANTDO100.TFM DECWAVANTDO120.TFM DECWAVANTDO140.TFM DECWAVANTDO180.TFM DECWAVANTDO240.TFM DECWAVANTDO80.TFM DECWAVANTO100.TFM DECWAVANTO120.TFM DECWAVANTO140.TFM DECWAVANTO180.TFM DECWAVANTO240.TFM DECWAVANTO80.TFM DECWCENT100.TFM DECWCENT120.TFM DECWCENT140.TFM DECWCENT180.TFM DECWCENT240.TFM DECWCENT80.TFM DECWCENTB100.TFM DECWCENTB120.TFM DECWCENTB140.TFM DECWCENTB180.TFM DECWCENTB240.TFM DECWCENTB80.TFM DECWCENTBI100.TFM DECWCENTBI120.TFM DECWCENTBI140.TFM DECWCENTBI180.TFM DECWCENTBI240.TFM DECWCENTBI80.TFM DECWCENTI100.TFM DECWCENTI120.TFM DECWCENTI140.TFM DECWCENTI180.TFM DECWCENTI240.TFM DECWCENTI80.TFM DECWCOUR100.TFM DECWCOUR120.TFM DECWCOUR140.TFM DECWCOUR180.TFM DECWCOUR240.TFM DECWCOUR80.TFM DECWCOURB100.TFM DECWCOURB120.TFM DECWCOURB140.TFM DECWCOURB180.TFM DECWCOURB240.TFM DECWCOURB80.TFM DECWCOURBO100.TFM DECWCOURBO120.TFM DECWCOURBO140.TFM DECWCOURBO180.TFM DECWCOURBO240.TFM DECWCOURBO80.TFM DECWCOURO100.TFM DECWCOURO120.TFM DECWCOURO140.TFM DECWCOURO180.TFM DECWCOURO240.TFM DECWCOURO80.TFM DECWHELV100.TFM DECWHELV120.TFM DECWHELV140.TFM DECWHELV180.TFM DECWHELV240.TFM DECWHELV80.TFM DECWHELVB100.TFM DECWHELVB120.TFM DECWHELVB140.TFM DECWHELVB180.TFM DECWHELVB240.TFM DECWHELVB80.TFM DECWHELVBO100.TFM DECWHELVBO120.TFM DECWHELVBO140.TFM DECWHELVBO180.TFM DECWHELVBO240.TFM DECWHELVBO80.TFM DECWHELVO100.TFM DECWHELVO120.TFM DECWHELVO140.TFM DECWHELVO180.TFM DECWHELVO240.TFM DECWHELVO80.TFM DECWLUBA100.TFM DECWLUBA120.TFM DECWLUBA140.TFM DECWLUBA180.TFM DECWLUBA240.TFM DECWLUBA80.TFM DECWLUBAD100.TFM DECWLUBAD120.TFM DECWLUBAD140.TFM DECWLUBAD180.TFM DECWLUBAD240.TFM DECWLUBAD80.TFM DECWLUBADO100.TFM DECWLUBADO120.TFM DECWLUBADO140.TFM DECWLUBADO180.TFM DECWLUBADO240.TFM DECWLUBADO80.TFM DECWLUBAO100.TFM DECWLUBAO120.TFM DECWLUBAO140.TFM DECWLUBAO180.TFM DECWLUBAO240.TFM DECWLUBAO80.TFM DECWSOUV100.TFM DECWSOUV120.TFM DECWSOUV140.TFM DECWSOUV180.TFM DECWSOUV240.TFM B-6 Files and Logical Names Installed on Your System DECWSOUV80.TFM DECWSOUVB100.TFM DECWSOUVB120.TFM DECWSOUVB140.TFM DECWSOUVB180.TFM DECWSOUVB240.TFM DECWSOUVB80.TFM DECWSOUVBI100.TFM DECWSOUVBI120.TFM DECWSOUVBI140.TFM DECWSOUVBI180.TFM DECWSOUVBI240.TFM DECWSOUVBI80.TFM DECWSOUVI100.TFM DECWSOUVI120.TFM DECWSOUVI140.TFM DECWSOUVI180.TFM DECWSOUVI240.TFM DECWSOUVI80.TFM DECWTIMEB100.TFM DECWTIMEB120.TFM DECWTIMEB140.TFM DECWTIMEB180.TFM DECWTIMEB240.TFM DECWTIMEB80.TFM DECWTIMEBI100.TFM DECWTIMEBI120.TFM DECWTIMEBI140.TFM DECWTIMEBI180.TFM DECWTIMEBI240.TFM DECWTIMEBI80.TFM DECWTIMEI100.TFM DECWTIMEI120.TFM DECWTIMEI140.TFM DECWTIMEI180.TFM DECWTIMEI240.TFM DECWTIMEI80.TFM DECWTIMER100.TFM DECWTIMER120.TFM DECWTIMER140.TFM DECWTIMER180.TFM DECWTIMER240.TFM DECWTIMER80.TFM DVC$BOOKR_FONTCONFIG.DAT SYMBOL140.TFM TEX$BOOKRCHARS.TEX Directory DOC$ROOT:[TEX.BOOKR.TOOLS] DVC$BOOKRSHR_AXP.EXE Directory DOC$ROOT:[TEX.FORMATS] DANISH.FMT_HYPH DOC$DESIGNS.DAT DOC$DESTINATIONS.DAT DOC$LANGUAGE.NLB DUTCH.FMT_HYPH ENGLISH.FMT_HYPH FINNISH.FMT_HYPH FRENCH.FMT_HYPH GERMAN.FMT_HYPH ITALIAN.FMT_HYPH NORWEGIAN.FMT_HYPH PORTUGUESE.FMT_HYPH SDMLBOOKR.FMT_MACRO SDMLLN03.FMT_MACRO SDMLLPR.FMT_MACRO SDMLPS.FMT_MACRO SPANISH.FMT_HYPH SWEDISH.FMT_HYPH TAG$ARTICLE.STT TAG$BACK_MATTER.STT TAG$FRONT_MATTER.STT TAG$GENERATE.STT TAG$HELP.STT TAG$LETTER.STT TAG$LOCAL_SYMBOL_TAGS.STT TAG$MANUAL.STT TAG$MILSPEC.STT TAG$MIL_ONLINE.STT B-7 Files and Logical Names Installed on Your System TAG$MIL_SECURITY.STT TAG$MULTCOL_TAGS.STT TAG$M_PRIMER.STT TAG$ONLINE_DESTINATION_STRINGS.STT TAG$ONLINE_SOP.STT TAG$ONLINE_TAGS.STT TAG$OVERHEADS.STT TAG$O_SHELF.STT TAG$PART_PAGE_TAGS.STT TAG$REPORT.STT TAG$R_OUTLINE_TAGS.STT TAG$R_TWOCOL.STT TAG$SDML_TAGS.STT TAG$SOFTWARE.STT TAG$S_BROCHURE.STT TAG$S_DEFLIST_TAGS.STT TAG$S_GUIDE.STT TAG$S_HANDBOOK.STT TAG$S_KEYPAD_TAGS.STT TAG$S_MESSAGE_TAGS.STT TAG$S_ONLINE.STT TAG$S_POCKET_REFERENCE.STT TAG$S_REFERENCE.STT TAG$S_SPECIFICATION.STT TAG$S_TEMPLATES.STT TEX$ARTICLE.DESIGN TEX$AVANT_MODULE.POST_FONTS TEX$CANADIAN_MODULE.TEX TEX$CENTURY_MODULE.POST_FONTS TEX$DANISH_MODULE.TEX TEX$DUTCH_MODULE.TEX TEX$ENGLISH_MODULE.TEX TEX$EXCEPTIONS.TEX TEX$FINNISH_MODULE.TEX TEX$FRENCH_MODULE.TEX TEX$GERMAN_MODULE.TEX TEX$HELP.DESIGN TEX$ITALIAN_MODULE.TEX TEX$LANGUAGE_MODULES.TEX TEX$LETTER.DESIGN TEX$LUBALIN_MODULE.POST_FONTS TEX$MIL_DRAFT.DESIGN TEX$MIL_ONLINE.DESIGN TEX$MIL_SECURITY.DESIGN TEX$MIL_SECURITY.LINE_FONTS TEX$MIL_SECURITY.LN03_FONTS TEX$MIL_SECURITY.POST_FONTS TEX$M_GUIDE.DESIGN TEX$M_PRIMER.DESIGN TEX$M_REFERENCE.DESIGN TEX$NORWEGIAN_MODULE.TEX TEX$OVERHEADS.DESIGN TEX$O_35MM.DESIGN TEX$O_SHELF.DESIGN TEX$PORTUGUESE_MODULE.TEX TEX$REPORT.DESIGN TEX$R_TWOCOL.DESIGN TEX$SOUVENIR_MODULE.POST_FONTS TEX$SPANISH_MODULE.TEX TEX$STANDARD_FONTS.BOOKR_FONTS TEX$STANDARD_FONTS.LINE_FONTS TEX$STANDARD_FONTS.LN03_FONTS TEX$STANDARD_FONTS.POST_FONTS TEX$STARTUP.TEX TEX$SWEDISH_MODULE.TEX TEX$S_BROCHURE.DESIGN TEX$S_GUIDE.DESIGN TEX$S_HANDBOOK.DESIGN TEX$S_ONLINE.DESIGN TEX$S_POCKET_REFERENCE.DESIGN TEX$S_REFERENCE.DESIGN TEX$S_SPECIFICATION.DESIGN TEX$TIMES_MODULE.POST_FONTS TTI_GENERAL.DESIGN Directory DOC$ROOT:[TEX.LN03] FONTS.DIR (no files) TOOLS.DIR B-8 Files and Logical Names Installed on Your System Directory DOC$ROOT:[TEX.LN03.TOOLS] DVC$LN03SHR_AXP.EXE Directory DOC$ROOT:[TEX.LPR] FONTS.DIR TOOLS.DIR Directory DOC$ROOT:[TEX.LPR.FONTS] LPAMEX10.TFM LPAMR10.TFM LPAMR6.TFM LPAMR8.TFM LPAMR9.TFM LPBD.TFM LPBI.TFM LPEX.TFM LPIT.TFM LPMI.TFM LPRM.TFM LPSY.TFM LPTT.TFM TEX$LPCHARS.TEX TEX$LPCHARS_ISO.TEX TEX$LPCHARS_MCS.TEX Directory DOC$ROOT:[TEX.LPR.TOOLS] DVC$LPRSHR_AXP.EXE Directory DOC$ROOT:[TEX.PostScript] FONTS.DIR TOOLS.DIR Directory DOC$ROOT:[TEX.PostScript.FONTS] AMEX10.1500PXL AMEX10.TFM AMMI10.1500PXL AMMI10.TFM AMMI6.1500PXL AMMI6.TFM AMMI8.1500PXL AMMI8.TFM AMMI9.1500PXL AMMI9.TFM AMR10.1500PXL AMR10.TFM AMR6.1500PXL AMR6.TFM AMR8.1500PXL AMR8.TFM AMR9.1500PXL AMR9.TFM AMSY10.1500PXL AMSY10.TFM AMSY6.1500PXL AMSY6.TFM AMSY8.1500PXL AMSY8.TFM AMSY9.1500PXL AMSY9.TFM AVANT.TFM AVANTD.TFM AVANTDO.TFM AVANTO.TFM CENT.TFM CENTB.TFM CENTBI.TFM CENTI.TFM COUR.TFM COURB.TFM COURBO.TFM COURO.TFM DECCALLOUT.TFM DEC_CALLOUT.PS DOC$COLOR_INIT.DAT DVC$PROLOG.PS DVC$PS_FONTCONFIG.DAT HELV.TFM HELVB.TFM HELVBO.TFM HELVO.TFM JINETE.PS JINETE.TFM LUBA.TFM LUBAD.TFM LUBADO.TFM LUBAO.TFM SOUV.TFM SOUVB.TFM SOUVBI.TFM SOUVI.TFM SYMBOL.TFM TEX$PSCHARS.TEX TIMEB.TFM TIMEBI.TFM TIMEI.TFM TIMER.TFM B-9 Files and Logical Names Installed on Your System Directory DOC$ROOT:[TEX.PostScript.TOOLS] DVC$PSSHR_AXP.EXE Directory DOC$ROOT:[TOOLS] BEGIN.GIF CAUTION.GIF DOC$MOPS_VAX.EXE DOC$MSG_VAX.EXE DOC$PARSE_VAX.EXE DOC$RAGS_VAX.EXE DOC$SYMBOL_GENERATOR_VAX.EXE DOC$VOYER_VAX.EXE DOCUMENT_VAX.EXE DVC$HTML.COM DVC$HTML.INT_IMG DVC$HTML.INT_IMG_AXP DVC$MANPAGE.COM DVC$MANPAGE.INT_IMG DVC$MANPAGE.INT_IMG_AXP INDEX.GIF INTOUCH_RUN.EXE INTOUCH_RUN.EXE_AXP INT_PASS.COM NEXT.GIF PREV.GIF TAG$TRANSLATESHR_VAX.EXE TOC.GIF The following system files are installed, or, where marked by an asterisk, modified: SYS$HELP:HELPLIB.HLB * SYS$HELP:DOC032.RELEASE_NOTES SYS$LIBRARY:DOC$LSEUPDATE_ENV.TPU SYS$LIBRARY:SDML_ENV SYS$LIBRARY:LSE$SYSTEM_ENVIRONMENT.ENV * SYS$MESSAGE:DOC$MSG.EXE SYS$SHARE:DCLTABLES.EXE * SYS$TEST:DOC$IVP.COM The following files are created by the installation for LN03 support: DOC$ROOT:[TEX.FORMATS]TEX$MIL_SECURITY.LN03_FONTS DOC$ROOT:[TEX.FORMATS]TEX$STANDARD_FONTS.LN03_FONTS DOC$ROOT:[TEX.LN03.TOOLS]DVC$LN03SHR.EXE The following files are created by the installation for PostScript support: B-10 Files and Logical Names Installed on Your System DOC$ROOT:[TEX.FORMATS]TEX$AVANT_MODULE.POST_FONTS DOC$ROOT:[TEX.FORMATS]TEX$CENTURY_MODULE.POST_FONTS DOC$ROOT:[TEX.FORMATS]TEX$LUBALIN_MODULE.POST_FONTS DOC$ROOT:[TEX.FORMATS]TEX$MIL_SECURITY.POST_FONTS DOC$ROOT:[TEX.FORMATS]TEX$SOUVENIR_MODULE.POST_FONTS DOC$ROOT:[TEX.FORMATS]TEX$STANDARD_FONTS.POST_FONTS DOC$ROOT:[TEX.FORMATS]TEX$TIMES_MODULE.POST_FONTS DOC$ROOT:[TEX.PostScript.FONTS]AMEX10.1500PXL DOC$ROOT:[TEX.PostScript.FONTS]AMEX10.TFM DOC$ROOT:[TEX.PostScript.FONTS]AMMI10.1500PXL DOC$ROOT:[TEX.PostScript.FONTS]AMMI10.TFM DOC$ROOT:[TEX.PostScript.FONTS]AMMI6.1500PXL DOC$ROOT:[TEX.PostScript.FONTS]AMMI6.TFM DOC$ROOT:[TEX.PostScript.FONTS]AMMI8.1500PXL DOC$ROOT:[TEX.PostScript.FONTS]AMMI8.TFM DOC$ROOT:[TEX.PostScript.FONTS]AMMI9.1500PXL DOC$ROOT:[TEX.PostScript.FONTS]AMMI9.TFM DOC$ROOT:[TEX.PostScript.FONTS]AMR10.1500PXL DOC$ROOT:[TEX.PostScript.FONTS]AMR10.TFM DOC$ROOT:[TEX.PostScript.FONTS]AMR6.1500PXL DOC$ROOT:[TEX.PostScript.FONTS]AMR6.TFM DOC$ROOT:[TEX.PostScript.FONTS]AMR8.1500PXL DOC$ROOT:[TEX.PostScript.FONTS]AMR8.TFM DOC$ROOT:[TEX.PostScript.FONTS]AMR9.1500PXL DOC$ROOT:[TEX.PostScript.FONTS]AMR9.TFM DOC$ROOT:[TEX.PostScript.FONTS]AMSY10.1500PXL DOC$ROOT:[TEX.PostScript.FONTS]AMSY10.TFM DOC$ROOT:[TEX.PostScript.FONTS]AMSY6.1500PXL DOC$ROOT:[TEX.PostScript.FONTS]AMSY6.TFM DOC$ROOT:[TEX.PostScript.FONTS]AMSY8.1500PXL DOC$ROOT:[TEX.PostScript.FONTS]AMSY8.TFM DOC$ROOT:[TEX.PostScript.FONTS]AMSY9.1500PXL DOC$ROOT:[TEX.PostScript.FONTS]AMSY9.TFM DOC$ROOT:[TEX.PostScript.FONTS]AVANT.TFM DOC$ROOT:[TEX.PostScript.FONTS]AVANTD.TFM DOC$ROOT:[TEX.PostScript.FONTS]AVANTDO.TFM DOC$ROOT:[TEX.PostScript.FONTS]AVANTO.TFM DOC$ROOT:[TEX.PostScript.FONTS]CENT.TFM DOC$ROOT:[TEX.PostScript.FONTS]CENTB.TFM DOC$ROOT:[TEX.PostScript.FONTS]CENTBI.TFM DOC$ROOT:[TEX.PostScript.FONTS]CENTI.TFM DOC$ROOT:[TEX.PostScript.FONTS]COUR.TFM DOC$ROOT:[TEX.PostScript.FONTS]COURB.TFM DOC$ROOT:[TEX.PostScript.FONTS]COURBO.TFM DOC$ROOT:[TEX.PostScript.FONTS]COURO.TFM B-11 Files and Logical Names Installed on Your System DOC$ROOT:[TEX.PostScript.FONTS]DECCALLOUT.TFM DOC$ROOT:[TEX.PostScript.FONTS]DEC_CALLOUT.PS DOC$ROOT:[TEX.PostScript.FONTS]COLOR_INIT.DAT DOC$ROOT:[TEX.PostScript.FONTS]DVC$FONT_CONFIG.DAT DOC$ROOT:[TEX.PostScript.FONTS]DVC$PROLOG.PS DOC$ROOT:[TEX.PostScript.FONTS]HELV.TFM DOC$ROOT:[TEX.PostScript.FONTS]HELVB.TFM DOC$ROOT:[TEX.PostScript.FONTS]HELVBO.TFM DOC$ROOT:[TEX.PostScript.FONTS]HELVO.TFM DOC$ROOT:[TEX.PostScript.FONTS]JINETE.PS DOC$ROOT:[TEX.PostScript.FONTS]JINETE.TFM DOC$ROOT:[TEX.PostScript.FONTS]LUBA.TFM DOC$ROOT:[TEX.PostScript.FONTS]LUBAD.TFM DOC$ROOT:[TEX.PostScript.FONTS]LUBADO.TFM DOC$ROOT:[TEX.PostScript.FONTS]LUBAO.TFM DOC$ROOT:[TEX.PostScript.FONTS]SOUV.TFM DOC$ROOT:[TEX.PostScript.FONTS]SOUVB.TFM DOC$ROOT:[TEX.PostScript.FONTS]SOUVBI.TFM DOC$ROOT:[TEX.PostScript.FONTS]SOUVI.TFM DOC$ROOT:[TEX.PostScript.FONTS]SYMBOL.TFM DOC$ROOT:[TEX.PostScript.FONTS]TEX$PSCHARS.TEX DOC$ROOT:[TEX.PostScript.FONTS]TIMEB.TFM DOC$ROOT:[TEX.PostScript.FONTS]TIMEBI.TFM DOC$ROOT:[TEX.PostScript.FONTS]TIMEI.TFM DOC$ROOT:[TEX.PostScript.FONTS]TIMER.TFM DOC$ROOT:[TEX.PostScript.TOOLS]DVC$PSSHR.EXE __________________________________________________________________ B.2 Directory Names The following directories are created by the installation: DOC$ROOT:[DEVBUILD] DOC$ROOT:[DEVBUILD.MESSAGES] DOC$ROOT:[EXAMPLES] DOC$ROOT:[GHOSTSCRIPT] DOC$ROOT:[LOCAL] DOC$ROOT:[LOCAL.FORMATS] DOC$ROOT:[LOCAL.TEMPLATES] DOC$ROOT:[LOCAL.TOOLS] DOC$ROOT:[TEMPLATES] B-12 Files and Logical Names Installed on Your System DOC$ROOT:[TEX] DOC$ROOT:[TEX.BOOKR] DOC$ROOT:[TEX.BOOKR.FONTS] DOC$ROOT:[TEX.BOOKR.TOOLS] DOC$ROOT:[TEX.FORMATS] DOC$ROOT:[TEX.LN03] DOC$ROOT:[TEX.LN03.FONTS] DOC$ROOT:[TEX.LN03.TOOLS] DOC$ROOT:[TEX.LPR] DOC$ROOT:[TEX.LPR.FONTS] DOC$ROOT:[TEX.LPR.TOOLS] DOC$ROOT:[TEX.PostScript] DOC$ROOT:[TEX.PostScript.FONTS] DOC$ROOT:[TEX.PostScript.TOOLS] DOC$ROOT:[TOOLS] The following directories are created for LN03 support: DOC$ROOT:[TEX.LN03.FONTS] DOC$ROOT:[TEX.LN03.TOOLS] The following directories are created for PostScript support: DOC$ROOT:[TEX.PostScript.FONTS] DOC$ROOT:[TEX.PostScript.TOOLS] __________________________________________________________________ B.3 Logical Names The following logical names are entered into the system logical name table when DECdocument is installed. These names are stored in the product's startup file. DOC$BOOKR_FONTS DOC$BOOKR_TOOLS DOC$DOCUMENT DOC$HTML_FONTS DOC$LN03_FONTS DOC$LOCAL_ELEMENTS DOC$LPR_FONTS DOC$MESSAGE DOC$MOPS DOC$PARSE DOC$PS_FONTS DOC$RAGS DOC$ROOT DOC$STANDARD_FORMATS DOC$SYMBOL_GENERATOR DOC$TEMPLATES DOC$VOYER B-13 Files and Logical Names Installed on Your System DVC$BOOKRSHR DVC$LN03SHR DVC$LPRSHR DVC$PSSHR TAG$$LOCAL_STRINGS TAG$TRANSLATESHR The following logicals are used by the DECdocument HTML converter. These logicals and several others are described in the "HTML Publishing with DECdocument" chapter in the DECdocument Tutorial and Application Guide. DOC$HTML_FILENAMES DOC$HTML_FILESIZE B-14 __________________________________________________________________ C User Notes C-1