DEC_VTX_______________________________________ Installation Guide Order Number: AA-PKFBD-TE This guide describes how to install DEC VTX on the OpenVMS VAX and OpenVMS AXP operating systems. It also describes how to install the MS-DOS and ULTRIX clients. Revision/Update Information: This is a revised manual. Operating System & Version: OpenVMS VAX Version 5.5-2 or higher, or Open VMS AXP Version 6.1 or higher. Software Version: DEC VTX Version 6.2 Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ May 1995 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation 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. © Digital Equipment Corporation 1995. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: Alpha AXP, AXP, DEC, Digital, DECnet, DECwindows, ULTRIX, ULTRIX-11, ULTRIX-32, ULTRIX Worksystem Software, OpenVMS, VAX, OpenVMS cluster, and the DIGITAL logo DIGITAL The following are third-party trademarks: Motif, OSF, and OSF/Motif are trademarks of Open Software Foundation, Inc. MS-DOS is a registered trademark of Microsoft Corporation. PostScript is a registered trademark of Adobe Systems, Inc. This document was prepared using VAX DOCUMENT, Version 2.1. ________________________________________________________________ Contents Preface.................................................. vii Part I Installing DEC VTX on an OpenVMS VAX or an OpenVMS AXP Operating System 1 Preparing to Install DEC VTX 1.1 Registering the DEC VTX Software License........ 1-1 1.2 Required OpenVMS Operating System Classes....... 1-2 1.3 Prerequisite and Optional Software.............. 1-3 1.4 Installation Procedure Requirements............. 1-3 1.4.1 Privileges ................................... 1-4 1.4.2 Process Account Quotas ....................... 1-4 1.4.3 System Parameters ............................ 1-5 1.4.3.1 Checking System Parameter Values........... 1-7 1.4.3.2 Changing System Parameter Values with AUTOGEN.................................... 1-8 1.4.3.3 Setting Dynamic System Parameter Values.... 1-9 1.4.4 Disk Space ................................... 1-9 1.4.5 Backing Up Your System Disk .................. 1-10 1.5 DEC VTX Requirements............................ 1-11 1.5.1 Saving .INI Files from Earlier Versions ...... 1-11 1.5.2 DEC VTX IVP Requirements ..................... 1-11 1.5.3 The VTX Version 3.1 VISTA Utility ............ 1-11 1.6 VMSINSTAL Requirements.......................... 1-12 iii 2 Installing DEC VTX 2.1 Before You Begin................................ 2-1 2.2 The Installation Procedure...................... 2-3 2.3 Error Recovery.................................. 2-15 3 After Installing DEC VTX 3.1 Establishing a DEC VTX Print Queue.............. 3-1 3.1.1 Editing the System Startup File .............. 3-1 3.1.2 Configuring Print Tables for VTX$QUEUE ....... 3-2 3.1.3 DCLTABLES .................................... 3-5 3.2 Cluster Considerations.......................... 3-5 3.3 Subscriber Account Privileges and Quotas........ 3-5 3.3.1 Privileges ................................... 3-5 3.3.2 Account Quotas ............................... 3-6 3.4 Defining System Logicals........................ 3-7 3.5 DECnet.......................................... 3-7 3.5.1 Establishing a DECnet Node ................... 3-7 3.5.2 Starting DECnet .............................. 3-8 3.6 Creating a VTX Operator Account................. 3-8 3.7 Using Search Lists.............................. 3-10 3.8 Enhancing DEC VTX Performance................... 3-10 3.8.1 Installing DEC VTX as a Shared Image ......... 3-11 3.9 Deleting the [.VTX$VISTA] Subdirectory.......... 3-13 3.10 Print Queue and Workbench Output Files Directory....................................... 3-13 3.11 Workbench Server Command Procedure Changes...... 3-14 3.12 VAS Command Procedure Changes................... 3-14 3.13 Determining and Reporting Problems.............. 3-14 3.14 Online User Guide............................... 3-15 3.14.1 Installing the Getting Started Infobase ...... 3-15 4 Installation Verification Procedure 4.1 Running the DEC VTX IVP......................... 4-1 4.2 Performing the Optional Part of the IVP......... 4-3 4.3 OpenVMS Client Initialization Files............. 4-4 4.3.1 Initialization files for ALL-IN-1 Users ...... 4-8 4.4 Conclusion...................................... 4-8 iv Part II Installing the MS-DOS Client on a Personal Computer 5 Installing the MS-DOS Client 5.1 Before You Begin................................ 5-1 5.2 Installing the Software from an OpenVMS Kit..... 5-2 5.3 Building the Kit on Diskette.................... 5-3 5.3.1 Installing the Software from Diskette ........ 5-4 Part III Installing DEC VTX on an ULTRIX Operating System 6 Preparing for Installation on ULTRIX Clients 6.1 Release Notes................................... 6-2 6.2 Using RIS for Client Installations.............. 6-2 6.3 Installing DEC VTX Into a RIS Server Area ...... 6-2 6.4 Installing DEC VTX Into a DMS Server Area ...... 6-3 6.5 Installation Procedure Requirements............. 6-4 6.5.1 Checking Login Privileges .................... 6-4 6.5.2 Software Requirements ........................ 6-4 6.5.3 Special Requirements for Installing DEC VTX .............................................. 6-5 6.5.4 Determining Which Subsets to Load ............ 6-5 6.5.5 Determining Disk Space Requirements .......... 6-6 6.5.5.1 Checking Disk Space for Installation into a Diskless Environment ...................... 6-7 6.6 Backing Up Your System Disk..................... 6-7 6.7 Stopping the Installation....................... 6-7 6.8 Error Recovery.................................. 6-8 7 Installation Procedure for the ULTRIX Client 7.1 Installing DEC VTX Locally...................... 7-1 7.1.1 Starting the Installation Procedure .......... 7-2 7.1.1.1 Using RA60 or CD-ROM Consolidated Distribution Media......................... 7-4 7.1.1.2 Installing DEC VTX from a RIS Server ...... 7-4 v 7.1.2 Responding to Installation Procedure Prompts....................................... 7-5 7.1.2.1 Selecting Subsets.......................... 7-5 7.1.2.2 Monitoring Displays During the Subset Loading Process............................ 7-6 7.2 Installing DEC VTX into a Server Environment ... 7-6 7.2.1 DMS Server Installations ..................... 7-7 7.2.2 RIS Server Installations ..................... 7-9 7.3 ULTRIX Client Initialization File............... 7-12 A Sample Installation on an OpenVMS VAX System B Sample Installation on an OpenVMS AXP System C Sample Installation on an ULTRIX System Index Tables 1 Conventions .................................. ix 1-1 Process Account Quotas for the Installing Account....................................... 1-4 1-2 Disk Space Requirements ...................... 1-9 3-1 Subscriber Account Quotas for Using DEC VTX .. 3-6 3-2 Required System Parameter Values ............. 3-11 3-3 Workbench Server Command Procedure Changes ... 3-14 4-1 Default Bindings ............................. 4-5 7-1 ULTRIX Language Directories .................. 7-13 vi ________________________________________________________________ Preface Purpose of This Document This document contains instructions for installing DEC VTX[TM] server and client software on a VAX[TM] or Alpha AXP[TM] system running OpenVMS[TM]. It also describes how to install the MS-DOS[R] and ULTRIX[TM] clients. It does not contain instructions for installing the Microsoft[R] Windows[TM] client. For this information, see the TeamLinks Library Services for Windows Getting Started guide. This document applies to DEC VTX V6.2 and all maintenance updates up to, but not including, the next major version. This document does not contain Release Notes information. For information on how to access the online release notes, see Section 2.1. Intended Audience This document is intended for anyone who wants to install DEC VTX software on an OpenVMS VAX or an OpenVMS AXP system, and for anyone who wants to install the MS-DOS and ULTRIX clients. Keep this document with your distribution kit. You will need to refer to it again if you receive any maintenance updates, or if you reinstall the software for any reason. vii Structure of this Document This document is organized as follows: o Part 1 Installing DEC VTX on an OpenVMS VAX or an OpenVMS AXP Operating System Chapter 1 describes the operating system and hardware requirements for DEC VTX installation on an OpenVMS VAX or an OpenVMS AXP system. It also provides an explanation of the procedures you must complete before installing DEC VTX. Chapter 2 provides step-by-step instructions for installing DEC VTX on an OpenVMS VAX or an OpenVMS AXP system. Chapter 3 provides an explanation of the procedures you must complete after installing DEC VTX. Chapter 4 explains the Installation Verification Procedure (IVP). It also provides an explanation of the procedures you must complete after installing DEC VTX. o Part 2 Installing the MS-DOS Client on a Personal Computer Chapter 5 provides step-by-step instructions for installing the MS-DOS client on a Personal Computer (PC). o Part 3 Installing DEC VTX on an ULTRIX Operating System. ________________________Note ________________________ Parts 2 and 3 of this Installation Guide apply only to the OpenVMS VAX operating system. _____________________________________________________ Chapter 6 describes the operating system and hardware requirements for installation of DEC VTX on an ULTRIX operating system. It also provides an explanation of the procedures you must complete before installing DEC VTX. Chapter 7 provides step-by-step instructions for installing DEC VTX on an ULTRIX operating system. viii o Appendix A provides a sample installation logfile for installation of DEC VTX on an OpenVMS VAX system. o Appendix B provides a sample installation logfile for installation of DEC VTX on an OpenVMS AXP system. o Appendix C provides a sample installation logfile for installation of DEC VTX on an ULTRIX system. Associated Documents In addition to this guide, the DEC VTX documentation set includes the following books: o DEC VTX Major Features and Text Retrieval Handbook o DEC VTX Subscriber's Information Guide o DEC VTX Information Provider's Guide o DEC VTX Service Provider's Guide o DEC VTX Application Provider's Guide Conventions Table 1 describes the conventions used in this guide. Table_1_Conventions_______________________________________ UPPERCASE Uppercase letters indicate the name of a command, a file, a parameter, a procedure, or utility. system prompt In interactive examples, this typeface indicates a prompt or displayed text. user input In interactive examples, this bold typeface indicates input entered by the user. $ The dollar sign is used to indicate the DCL prompt. This prompt may be different on your system. (continued on next page) ix Table_1_(Cont.)_Conventions_______________________________ In procedures, a sequence such as indicates that you must hold down the key labeled Ctrl (Control) and the specified key (X) simultaneously. A key name enclosed in a box indicates that you press that key. . Vertical ellipsis in an example means . that information not directly related to . the example has been omitted. file- Horizontal ellipsis indicates that spec, . . . 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.)______________________________ x Part I ________________________________________________________________ Installing DEC VTX on an OpenVMS VAX or an OpenVMS AXP Operating System This section explains how to install DEC VTX on a VAX or Alpha AXP processor running the OpenVMS operating system. 1 ________________________________________________________________ Preparing to Install DEC VTX This chapter describes the preparations and requirements necessary for installing DEC VTX. Your bill of materials (BOM) and indented bills report (BIL) specify the number and contents of your media. Be sure to verify the contents of your kit with this information. If your kit is damaged or if you find that parts of it are missing, contact your Digital representative. DEC VTX provides online release notes. Digital strongly recommends 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 Registering the DEC VTX Software License If you are installing DEC VTX V6.2 on a newly licensed node or cluster, you must first register a License Product Authorization Key (License PAK) using the License Management Facility (LMF). The License PAK may be shipped along with the kit if you ordered the license and media together; otherwise, it is shipped separately to a location based on your license order. If you are installing DEC VTX V6.2 as an update on a node or cluster already licensed for this software, you must register the Service Update PAK (SUP) that is included in your Service Update Kit. If you already registered a License PAK or a SUP for this product on this node or cluster, you do not need to register the SUP. If you are installing an update of DEC VTX but lack a service contract, call your Digital representative for instructions on how to get a License PAK. Preparing to Install DEC VTX 1-1 You must register and load the appropriate license for DEC VTX 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 DEC VTX on more than one node in a OpenVMS cluster, you will need to perform a license load on the other nodes after you complete this installation. See Section 3.2. For complete information on using LMF, see the OpenVMS License Management Utility Manual. 1.2 Required OpenVMS Operating System Classes The OpenVMS operating system comes with a variety of support options, or classes. Classes include such features as networking and RMS journaling. Verify that the following OpenVMS operating system classes are resident on the system disk: o OpenVMS required saveset o Network support o Programming support o Secure user's environment o Utilities DECwindows is required if you will be using DEC VTX through the DECwindows interface. For a complete list of the required classes, see the Software Product Description (SPD). 1-2 Preparing to Install DEC VTX 1.3 Prerequisite and Optional Software This section provides information on the software you must have installed on your system before installing DEC VTX. The Software Product Description (SPD) contains a complete list of prerequisite and optional software, along with their required version numbers. Prerequisite Software o If you are using the VAS component of DEC VTX in an IBM or IBM-compatible environment, you must install DECnet /SNA VMS APPL/LU6.2 V2.0 (or higher) before you install DEC VTX. Optional Software The following optional software can be used with DEC VTX: o DECnet-VMS Version 5.4 o WPS-PLUS V3.1 or 4.0 o ALL-IN-1 o VAX BLISS o VAX PSI Access V4.2 o DECnet/SNA VMS APPL/LU6.2 V2.0 o DECnet/SNA VMS 3270 Data Stream Programming Interface V1.4 o UCX V1.3 1.4 Installation Procedure Requirements This section describes the requirements for installing DEC VTX (process account quotas, system parameters, disk space, and so on). Preparing to Install DEC VTX 1-3 1.4.1 Privileges To install DEC VTX, you must be logged in to an account that has SETPRV or at least the following privileges: o CMKRNL o DETACH o WORLD o SYSPRV o SYSNAM o GROUP o GRPNAM o NETMBX o TMPMBX Note that VMSINSTAL turns off BYPASS privilege at the start of the installation. 1.4.2 Process Account Quotas The account you use to install DEC VTX must have suffi- cient quotas to enable you to perform the installation. Table 1-1 summarizes the process quotas required for the installation account. Table 1-1 Process Account Quotas for the Installing __________Account_________________________________________ Account_Quota____Value____________________________________ ASTLM 250 BIOLM 250 BYTLM 80000 DIOLM 70 ENQLM 250 FILLM 250 (continued on next page) 1-4 Preparing to Install DEC VTX Table 1-1 (Cont.) Process Account Quotas for the __________________Installing_Account______________________ Account_Quota____Value____________________________________ PGFLQUOTA 80000 WSQUO 4096 WSEXTENT 8192 TQELM_______________50____________________________________ User account quotas are stored in the file SYSUAF.DAT. Use the OpenVMS Authorize Utility (AUTHORIZE) to verify and change user account quotas. First set your directory to SYS$SYSTEM and then run AUTHORIZE: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> At the UAF> prompt, enter the SHOW command with an account name to check a particular account. For example: UAF> SHOW SMITH To change a quota, enter the MODIFY command. The following example changes the FILLM quota for the SMITH account and then exits from the utility: UAF> MODIFY SMITH /FILLM=50 UAF> EXIT After you exit from the utility, the system displays messages indicating whether or not changes were made. Once the changes have been made, you must log out and log in again for the new quotas to take effect. For more information on modifying account quotas, see the description of the Authorize Utility in the OpenVMS System Management Subkit. 1.4.3 System Parameters Installing DEC VTX requires certain system parameter settings. The following describes the system parameters you may need to update. Preparing to Install DEC VTX 1-5 VIRTUALPAGECNT This must be set to at least 35,000 on your system. CTLPAGES The process from which you plan to install DEC VTX must have at least 55 free CTLPAGES. You can verify the number of free CTLPAGES by issuing the following command at the DCL prompt: $ SHOW PROCESS/MEMORY The following information is displayed: 20-APR-1995 06:55:09.54 User: BENTLEY Process ID: 21A00115 Node: POCKET Process name: "_FTA11:" Process Dynamic Memory Area Current Size (bytes) 768000 Current Total Size (pages) 1500 Free Space (bytes) 755736 Space in Use (bytes) 12416 Size of Largest Block 755664 Size of Smallest Block 8 Number of Free Blocks 3 Free Blocks LEQU 32 Bytes 20 The value you need to be concerned with is Free Space. In the example shown, the process has 755736 free which is equivalent to: 755736/512 = 1476 full pages If you have 55 or more free pages (21504 bytes), you do not need to change anything. If you have fewer than 55 free pages, you need to increase the value of your CTLPAGES. The value you need on your CTLPAGES is: ((Your free space + 511)/512)+55 CTLPAGES are used, for example, when defining process logical names. It is recommended that if you are close to the minimum required value, you should perform the installation from a new process. GBLPAGES and GBLSECTIONS The DEC VTX installation updates your DCLTABLES and requires at least 160 free GBLPAGES pages in addition to the size of your DCLTABLES.EXE. You can get the size of your DECTABLES.EXE by issuing the following command at the DCL prompt: $ DIRECTORY/SIZE SYS$SHARE:DCLTABLES.EXE 1-6 Preparing to Install DEC VTX The following information is displayed: Directory SYS$COMMON:[SYSLIB] DCLTABLES.EXE;547 945 Total of 1 file, 945 blocks If you are installing DEC VTX on an OpenVMS Version 5.2 (or higher) system, you can use the WRITE command with the F$GETSYI lexical function to find the number of free global pages and global sections. To get the number of free global pages, at your terminal (the default for SYS$OUTPUT), enter: $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") 15848 There must be at least 160 GBLPAGES free in addition to the size of your DCLTABLES.EXE. To get the number of free global sections, at your terminal (the default for SYS$OUTPUT), enter: $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") 24 There must be at least 2 GBLSECTIONS free. You must increase your system parameter setting if you do not meet these requirements. Section 1.4.3.2 describes the procedures for increasing these values using AUTOGEN. 1.4.3.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 following example displays the value for the WSMAX system parameter: SYSGEN> SHOW WSMAX After checking the parameters with the SHOW command, enter the EXIT command at the SYSGEN> prompt to return to DCL level. Preparing to Install DEC VTX 1-7 Section 1.4.3.2 describes the procedures for increasing these values using AUTOGEN. 1.4.3.2 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: WSMAX = 1024 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. 1-8 Preparing to Install DEC VTX For more information about using AUTOGEN, see the OpenVMS System Management Subkit. 1.4.3.3 Setting Dynamic System Parameter Values The System Generation Utility (SYSGEN) is used to set dynamic parameters. Dynamic parameters changed with the SYSGEN WRITE ACTIVE command become active immediately without any need to reboot your system. Rebooting returns dynamic system parameter values to their previous settings. Once you change dynamic parameter values, you should complete the installation before rebooting the system. After you finish with the installation, you can reset the dynamic parameters to their previous values or let them be reset automatically when you next reboot your system. 1.4.4 Disk Space You have the option of installing the full VTX kit, or installing one or more component parts. The space required depends on what you choose to install. Additionally, the requirements for free disk storage space on DEC VTX are different during installation and after installation. Table 1-2 summarizes the storage requirements. Table_1-2_Disk_Space_Requirements_________________________ Then this disk must If you are installing... _______have_at_least...________ Blocks During Blocks After ___________________________Installation___Installation____ Base VTX kit, with 17000 12500 multilanguage clients VTX Server environment 20000 16500 Information Provider 5000 2400 Tools (continued on next page) Preparing to Install DEC VTX 1-9 Table_1-2_(Cont.)_Disk_Space_Requirements_________________ Then this disk must If you are installing... ________have_at_least..._______ Blocks During Blocks After ___________________________Installation___Installation____ ULTRIX and DOS Reference 14600 14600 Kit[1] Back End Applications 900 600 Installation Verification 90 60 Procedure Classic VT Front End 2000 1400 TSM Sources[1] 20000 14000 IP Conversion Tools[1] 250 150 [1]Applies_to_OpenVMS_VAX_only____________________________ __________________________________________________________ A full basic VTX kit on OpenVMS, then, requires approxi- mately 23MB of disk space. Note that installation of the Base Kit includes 1100 blocks for the DECwindows MOTIF client, and that the server part of the kit is required if you install Information Provider Tools. 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.5 Backing Up Your System Disk At the beginning of the installation, the VMSINSTAL installation procedure asks if you have backed up your system disk. Digital recommends 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 OpenVMS System Management Subkit. 1-10 Preparing to Install DEC VTX 1.5 DEC VTX Requirements DEC VTX checks for the following conditions during the installation procedure: o If you are installing DEC VTX for OpenVMS VAX, you must have OpenVMS VAX Version 5.5-2 (or higher) is running on the system. o If you are installing Digital VTX for OpenVMS Alpha, you must have OpenVMS AXP Version 6.1 (or higher) is running on the system. o The appropriate number of free blocks are available on the system disk. o System parameters and account quotas meet the required minimum. 1.5.1 Saving .INI Files from Earlier Versions If you are installing a new version of DEC VTX, you may want to keep your customized VTX.INI or VTXALLIN1.INI file. If you want to keep these files, you should make a copy of them before starting the installation. 1.5.2 DEC VTX IVP Requirements Before you run the Installation Verification Procedure (IVP) as part of the DEC VTX installation or separately, you must stop all VTX, Workbench and Update servers, and all VAS run-time images. DEC VTX IVP starts servers using the default object numbers and could fail if these numbers have already been used. 1.5.3 The VTX Version 3.1 VISTA Utility If you are upgrading directly from Version 3.1 and you want to do additional work on menu structures saved in Version 3.1 files (menu structure files named structure- name_MENUSTR.VTX in your VTX$VISTA subdirectory), follow the steps listed below: 1. Update your infobase with the menu structures before you install this version. Preparing to Install DEC VTX 1-11 2. After you install DEC VTX, convert your VISTA library files to Workbench library files (see the VTX Service Provider's Guide for information on the conversion process). 3. Use the LOCATE option (provided through the Workbench interactive graphical interface, WBGI) to recreate the menu structure. 4. Save the menu structure to a Version 5 menu structure file. If you fail to follow this procedure, you will receive an error message when you try to open Version 3.1 menu structure files. 1.6 VMSINSTAL Requirements Before you invoke VMSINSTAL, you must complete the following steps: 1. Log into a privileged account. 2. Set your default device and directory to SYS$UPDATE. 3. Ensure the system has adequate quotas for installation. 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-12 Preparing to Install DEC VTX 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. Preparing to Install DEC VTX 1-13 2 ________________________________________________________________ Installing DEC VTX 2.1 Before You Begin Before beginning the installation procedure, you may want to go over the following questions and answers: o How long will the installation take? The installation takes approximately 20 minutes to 4 hours, depending on your type of media and your system configuration. Installing DEC VTX and running the Installation Verification Procedure (IVP) on a standalone VAX 8820 system takes 20 minutes. o How can I get help? VMSINSTAL provides additional information about the decisions required to respond to the installation prompts. To get help at any installation prompt, enter ? and press . o Where can I find a sample installation? Appendix A contains a sample of an installation procedure. o How do I access the Online Release Notes? You must specify OPTIONS N when you invoke VMSINSTAL to access the release notes. VMSINSTAL provides a list of options near the beginning of the installation that allows you to decide how you want to view the release notes during the installation. You should review the release notes in case they con- tain any information about changes in the installation procedure. If you are restarting the installation procedure and you have already reviewed the release notes, you do not need to specify OPTIONS N. Installing DEC VTX 2-1 After you install DEC VTX, your system stores the release notes in the following file: SYS$HELP:VTX062.RELEASE_NOTES 2-2 Installing DEC VTX o How can I abort the installation procedure? 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. 2.2 The Installation Procedure The DEC VTX installation procedure uses the VMSINSTAL utility in SYS$UPDATE. The procedures consists of a series of questions and informational messages. VMSINSTAL marks each question in the installation with an asterisk (*) at the beginning of the line. Some questions show the default response in brackets, for example [YES]. To use the default response, press . To install DEC VTX, follow these steps: 1 Log in to a privileged account and set your default device and directory to SYS$UPDATE:. Username: SYSTEM Password: $ SET DEFAULT SYS$UPDATE 2 Invoke VMSINSTAL. $ @VMSINSTAL saveset-name device-name option-list where: saveset-name The installation name for the component. For DEC VTX, use the following installation name: VTX062 device-name The name of the device on which you plan to mount the media. For example, MUA0: is the device name for a tape drive. It is not necessary to use the console drive for this installation. If you do use the console drive, you should replace any media you remove once you complete the installation. Installing DEC VTX 2-3 OPTIONS N An optional parameter that allows you to review the release notes during the installation. If you do not include the OPTIONS N parameter, VMSINSTAL does not provide this option. You should always review the release notes before you begin the installation in case they contain new information about the installation. Note that there are several other options you can select when you invoke VMSINSTAL. See the OpenVMS documentation on software installation for information on these options. The following example displays the command you use to invoke VMSINSTAL to install DEC VTX from tape drive MUA0:, as well as the system response. This example uses the OPTIONS N release note parameter. $ @SYS$UPDATE:VMSINSTAL VTX062 MUA0: VAX/VMS Software Product Installation Procedure 5.4-4 It is 09-April-1995 at 07:15. 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. Because VMSINSTAL does not prompt for options, be sure to include OPTIONS N on the VMSINSTAL command line if you want to access the release notes during the installation. 3 DECnet Status VMSINSTAL displays a list of all active processes on the system and tells you whether your DECnet network is running. It then asks if you want to continue the installation. You should install DEC VTX on a standalone system or cluster with your DECnet network shut down. NO is the default response to the question. $ %VMSINSTAL-W-DECNET, Your DECnet network is up and running. . . . * Do you want to continue anyway [NO]? 4 System Backup 2-4 Installing DEC VTX 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 . Otherwise, enter NO to discontinue the installation. After you back up your system disk, you can restart the installation. * Are you satisfied with the backup of your system disk [YES]? Installing DEC VTX 2-5 5 Release Notes If you specify OPTIONS N when you invoke VMSINSTAL, the procedure now asks you to choose one of the four options for reviewing the release notes. For OpenVMS Version 5.2 or higher, you see the following display: 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 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: * Queue name [SYS$PRINT]: You can press 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. If you select option 4, VMSINSTAL takes no action. Select this option if you have already reviewed the release notes and are restarting the installation. 6 Continuing the Installation The installation procedure now asks if you want to continue the installation. To continue, enter YES. Otherwise, press . 2-6 Installing DEC VTX In either case, VMSINSTAL copies the release notes to a file in the SYS$HELP directory. For example: *Do you want to continue the installation [N]?: YES %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. VMSINSTAL copies the release notes to the following file: SYS$HELP:VTX062.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 the release notes for previous versions of DEC VTX. _____________________________________________________ After the installation, you can enter the following command to review the release notes through the Help facility: $ HELP VTX RELEASE_NOTES 7 Selecting the DEC VTX Components VMSINSTAL gives you the option of installing the subscriber environment, which allows users access to the infobase. When you install the VTX subscriber environment, it includes the following parts: o VTX$CLIENT_CC, the character cell subscriber's interface to VTX o VTX$CLIENT_MOTIF, the DECwindows [TM] Motif subscriber's interface to VTX o VTXCON, the concentrator for VTX subscriber sessions * Would you like to install the VTX Subscriber environment [YES]? Installing DEC VTX 2-7 If you enter YES, you have the option of installing the pre-V5.0 VTXPAD subscriber environment, Classic Subscriber Environment. * Would you like to install the Old VTXPAD Subscriber environment [YES]? If you answer YES, the old character cell interface to VTX, including the ALL-IN-1 keypad are installed. You also have the option to make the COMMON keypad the default keypad. The COMMON keypad is composed of the traditional VTX default keypad and the ALL-IN-1 keypad, except where there are conflicting mappings. If you want to use the COMMON keypad, answer YES to the following question: * Would you like to install the COMMON keypad [NO]? 2-8 Installing DEC VTX Installing the Information Provider Tools You have the option to install the Information Provider tools which are required if you want to update a VTX infobase. This option includes the following tools: o APMS: Automatic Page Management System o WPSSMB: A tool for paginating DDIF documents and text files o PAGER: A tool for paginating DDIF documents and text files o WBGI: Workbench Graphical Interface o WBCLU: Workbench command language o UPD: A command language for updating a VTX infobase o RUSL: A callable interface for remote updates of VTX infobases o IVU: Infobase Verification Utility This option requires that the Subscriber environment is installed. * Would you like to install the VTX Information Provider tools [YES]? Installing the VTX Version 3.x IP Conversion Tools o A few file formats for Information Provider tools changed between VTX Version 3.x and Version 4.0 (there were no changes between V4.0 and V4.1). To upgrade your V3.x files you need the following components: o PFC which is the Page File Conversion tool o VLC which converts a VISTA library to a Workbench library o IAF which converts an APMS Index o If you need to convert your VTX Version 3.x files, answer YES to the question, otherwise NO: * Would you like to install VTX V3.x IP Conversion tools [YES]? Installing the VTX Servers Installing DEC VTX 2-9 You have the option to install the VTX server environment which has the following parts: o SRV, which allows local and remote VTX subscribers to access a VTX infobase on this system. o UPDSRV, which allows remote VTX Information Providers to update VTX infobases on this system. o WBSRV, which allows remote VTX Information Providers to access Workbench libraries on this system. o ACU, the VTX infobase access Authorization and Accounting utility. To install the server environment, answer YES to the following question: * Would you like to install the VTX Servers [YES] ? Installing the VTX Back-End Environment VTX back-end applications are programs started when a subscriber references a page in a VTX infobase. This option includes the following parts: o VAS, a high-level programming interface for writing VTX back-end applications. o ELK, a low-level programming interface to writing VTX back-end applications. Both the components include their programming interfaces and can be installed by answering YES to the following question: * Would you like to install the VTX back end environment [YES] ? Installing the TCP Source Code The VTX Classic Subscriber Environment allows a certain amount of customization by modifying the source code. Refer to your VTX Warranty Exclusion for details on what can be changed without violating your standard VTX support contract. ________________________Note ________________________ You need access to a BLISS32 compiler in order to compile any changes you make. _____________________________________________________ 2-10 Installing DEC VTX If you want this option, answer YES to the following question: * Would you like to install the TCP source code [NO] ? You are then asked where you want to put the TCP source files. You must specify a directory in response to the following question: * Where do you want the TCP sources [SYS$SYSROOT:TCPLIB]: 8 Installing ULTRIX and MS-DOS Clients DEC VTX supports ULTRIX and MS-DOS clients. To install these, you must answer YES to the prompt: * Would you like to install the ULTRIX and MS-DOS Clients Reference kit [NO]? If you answer YES to this prompt, the ULTRIX tar files and DOS saveset are installed in SYS$COMMON:[VTX$LIBRARY.REFKIT] The DOS saveset is expanded into SYS$COMMON:[VTX$LIBRARY.REFKIT.MSDOS] 9 Choosing to Purge Files You have the option to purge files from previous versions of DEC VTX 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. * Do you want to purge files replaced by this installation [YES]? 10 Deleting Obsolete Files The installation procedure asks you if you want to delete all files made obsolete by this installation. The default answer is NO. To delete the obsolete files, answer YES. $ Do you want files made obsolete by this installation deleted [YES]? The following files are made obsolete by installation procedures: SYS$COMMON:[SYSLIB]VTX$TERMSHR.EXE SYS$HELP:VTXCTLVSRV.HLB SYS$LIBRARY:VTXIAF.FDL Installing DEC VTX 2-11 SYS$LIBRARY:VTXIAF_CONVERT.CLD SYS$LIBRARY:VTXKFC.FDL SYS$LIBRARY:VTXPAF.FDL SYS$LIBRARY:VTXPAF_CONVERT.CLD SYS$SYSROOT:[RUSLLIB]RUSLLIB.OLB SYS$SYSROOT:[SYSTEST]VTX$IVP_UPDATE.COM SYS$SYSROOT:[SYSTEST]VTX$IVP_VAS.COM SYS$SYSTEM:VASCTL.EXE SYS$SYSTEM:VTXIAF_CONVERT.EXE SYS$SYSTEM:VTXKFC.EXE SYS$SYSTEM:VTXPAF_CONVERT.EXE SYS$SYSTEM:VTXVISTA.EXE SYS$SYSTEM:VTXVISTASRV.EXE SYS$UPDATE:SAMPLE_STYLE.VTX SYS$UPDATE:VTXBASE.TXT SYS$UPDATE:VTXCON.COM SYS$UPDATE:VTXIAF_CONVERT.COM SYS$UPDATE:VTXMAIN.VTU SYS$UPDATE:VTXPAF_CONVERT.COM SYS$UPDATE:VTXSERVER.COM SYS$UPDATE:VTXUPDSRV.COM SYS$UPDATE:VTXVISASRV.COM SYS$UPDATE:VTX_INTERNALS.VTU VTX$TCPLIB:CON.OLB VTX$TCPLIB:DECTERMLIB.OLB VTX$TCPLIB:DSLLIB.OLB VTX$TCPLIB:NOREGISLIB.OLB VTX$TCPLIB:STRINGS.OBJ VTX$TCPLIB:VTXCON.OPT VTX$TCPLIB:VTXCTLCMD.OBJ VTX$TCPLIB:VTXPAD.OPT 11 Choosing to Run the Installation Verification Procedure (IVP) The Installation Verification Procedure (IVP) for DEC VTX verifies the installation. The installation procedure now asks if you want to run the IVP which checks that the installation is successful. * Do you want to run the IVP after the installation [YES]? It is recommended that you run the IVP. See Chapter 4 for information on how to do this. 2-12 Installing DEC VTX After DEC VTX 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 DEC VTX. 12 Completing the Questions Once you have answered all the questions, the installation asks: Are you satisfied with all your answers for this installation [YES]? If you are satisfied, enter YES and the installation displays a number of informational messages. (Refer to the sample installation in Appendix A.) Installing DEC VTX 2-13 13 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, and updates help files and DCL tables, if necessary. If you chose to have files purged, that work is done now. The following messages are displayed: %VMSINSTAL-I-MOVEFILES, files will now be moved to their target directories... 14 Observe the Installation Verification Procedure (IVP) If you chose to run the IVP, VMSINSTAL runs it now. 15 End the installation procedure When the IVP runs successfully, you see display similar to the following: Installation of DEC VTX completed at 07:44 VMSINSTAL procedure done at 07:44 The previous messages indicate that the entire installation procedure is complete. 16 Log out of the SYSTEM account You can now log out of the privileged account: $ LOGOUT SYSTEM logged out at 19-APR-1995 09:04:17.62 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-14 Installing DEC VTX 2.3 Error Recovery If errors occur during the installation itself or when the IVP is running, VMSINSTAL displays failure messages. If the installation fails, you see the following message: %VMSINSTAL-E-INSFAIL, The installation of DEC VTX has failed. If the IVP fails, you see these messages: The DEC VTX Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for DEC VTX has failed. Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect. o A prerequisite software 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. 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. Installing DEC VTX 2-15 3 ________________________________________________________________ After Installing DEC VTX After installing DEC VTX you need to perform the following tasks: o Establish a VTX print queue. o Editing the system startup and shutdown files. o Start DEC VTX on other nodes in your Alpha AXP or VAXcluster. o Set subscriber account privileges and quotas. o Define the appropriate system logicals. o Set up DECnet. o Create a VTX operator's account. o Install the Online User's Guide. 3.1 Establishing a DEC VTX Print Queue To establish a DEC VTX print queue, you must modify your system startup file. There is no automatic startup procedure for DEC VTX; however, if you want to use an editor to create DEC VTX documents, you must edit the system startup file to provide for automatic startup of the DEC VTX print queue when you reboot your system. 3.1.1 Editing the System Startup File The VTX$STARTUP.COM needs to be added to the system startup procedure SYS$MANAGER:SYSTARTUP_V5.COM. $ @SYS$MANAGER:VTX$STARTUP.COM After Installing DEC VTX 3-1 You need to add the command line that starts the DEC VTX print queue to the system startup file. The following example displays the network startup command line followed by the startup command line for the DEC VTX print queue: $ @SYS$MANAGER:STARTNET.COM . . . $ @SYS$STARTUP:VTXWPS_STARTUP.COM Place the command line to start the DEC VTX print queue in the system startup file at a position that meets the requirements of your site. ________________________Note ________________________ If you create an automatic startup procedure for DEC VTX, you must add the command line that starts that procedure to the system startup file after the @SYS$MANAGER:STARTNET.COM command line entry; you do not, however, need to add the command line after the @SYS$STARTUP:VTXWPS_ STARTUP.COM command line entry. _____________________________________________________ 3.1.2 Configuring Print Tables for VTX$QUEUE To use WPS-PLUS with VTX$QUEUE, you must configure the WPS-PLUS or ALL-IN-1 print tables so that WPS-PLUS recognizes VTX$QUEUE. This section describes how to configure print tables for VTX$QUEUE if your system is running WPS-PLUS Version 3.1 under ALL-IN-1 or as a standalone. If you are running WPS-PLUS Version 3.1 under ALL-IN-1, follow these steps to configure print tables for VTX$QUEUE: 1. Log in to a privileged account, preferably SYSTEM. 2. Locate the device on which the [ALLIN1] directory is located. 3-2 After Installing DEC VTX 3. If you are using WPS Version 3.1, o Copy the files VTX.PRA_OLD and VTX.PRC_OLD from the directory SYS$COMMON:[VTX$LIBRARY] to the directory: DEVICE:[ALLIN1.PRINT]VTX.PRA and VTX.PRC 4. If you are using WPS Version 4.0, o Copy the files VTX.PRA and VTX.PRC from the directory SYS$COMMON:[VTX$LIBRARY] to the directory: DEVICE:[ALLIN1.PRINT]VTX.PRA and VTX.PRC 5. Log in to the ALL-IN-1 manager's account. 6. Establish the VTX print table in ALL-IN-1: o Select the menu option MPR (Manage Printers). ALL-IN-1 displays the two options of the Manage Printers menu, PR and PT. o Select menu option PT (Printer Types). ALL-IN-1 displays the Manage Printer Types menu. o Select menu option C (Create). ALL-IN-1 displays the following form. Fill in the information listed to the right of each field. Be sure to leave the last field (Print Form:) blank. Printer Type: VTX Foreground function: DO WPPSYSTEM Background function: DO WPPBGFORMAT Printer Device: VTX Print Form: o Return to the Manage Printers menu. o Select the Manage Printers menu option PR (Site Printers). ALL-IN-1 displays the Manage Site Printers menu. o Select the SEL menu option. ALL-IN-1 prompts you for a name. Enter VTX$QUEUE and press RETURN. o If ALL-IN-1 cannot find VTX$QUEUE, select menu option C (Create). o If ALL-IN-1 finds VTX$QUEUE, select menu option E (Edit). After Installing DEC VTX 3-3 o Whether you select menu option C or E, ALL-IN-1 displays the following form. If the form is blank, fill in the fields with the information listed to the right of each field in the form in the example. If the fields contain information that differs from the information seen in the example form, edit the form and change the appropriate fields to those listed in the example. Printer Name: VTX$QUEUE Description: Format document and send to VTX Format Printer Type: VTX Destination Printer Type: VTX Print Queue: VTX$QUEUE If you are running WPS-PLUS Version 3.1 in a standalone environment, follow these steps to configure print tables for VTX$QUEUE: 1. Log in to a privileged account, preferably SYSMGR. 2. Locate the device on which the [WPSPLUS] directory is located. 3. Copy the files VTX.PRA_OLD and VTX.PRC_OLD from the directory SYS$COMMON:[VTX$LIBRARY] to the directory: DEVICE:[WPSPLUS.PRINT]VTX.PRA and VTX.PRC. If you are running WPS-PLUS Version 4.0 in a standalone environment, follow these steps to configure print tables for VTX$QUEUE: 1. Log in to a privileged account, preferably SYSMGR. 2. Locate the device on which the [WPSPLUS] directory is located. 3. Copy the files VTX.PRA_OLD and VTX.PRC_OLD from the directory SYS$COMMON:[VTX$LIBRARY] to the directory: DEVICE:[WPSPLUS.PRINT]VTX.PRA and VTX.PRC. 3-4 After Installing DEC VTX 3.1.3 DCLTABLES If you are in a VAXcluster, you must reinstall DCLTABLES on all nodes in the cluster except the node from which you performed the installation. Failure to reinstall DCLTABLES will cause the following error message to be displayed: %CLI-F-SYNTAX, error parsing 'PIC1' -CLI-E-ENTNF, specified entity not found in command tables In addition, VTXPAD will not start. You can reinstall DCLTABLES with the following command: $ RUN SYS$SYSTEM:INSTALL INSTALL> SYS$SHARE:DCLTABLES/REPLACE INSTALL> $ 3.2 Cluster Considerations You must perform the following actions on each node that supports DEC VTX, before DEC VTX starts on other nodes in a VAXcluster. 1. Replace DCL tables using the OpenVMS INSTALL utility. 2. Run VTXWPS_STARTUP.COM (if you will be using the VTX print queue). 3. Load the license. 4. Run the IVP. 3.3 Subscriber Account Privileges and Quotas To work with DEC VTX, subscriber accounts on your system must have certain privileges and quotas, as described in this section. 3.3.1 Privileges To use DEC VTX, each account must have at least the TMPMBX and NETMBX privileges. Use the OpenVMS Authorize Utility to determine if subscribers have the privileges they require. After Installing DEC VTX 3-5 3.3.2 Account Quotas You must ensure that the appropriate subscriber accounts have sufficient quotas to use DEC VTX. Table Table 3-1 summarizes the quotas user accounts require. Table_3-1_Subscriber_Account_Quotas_for_Using_DEC_VTX_____ Account_Quota____Value____________________________________ ASTLM 8 BIOLM 8 BYTLM 10000 DIOLM 6 ENQLM 10 FILLM 3 PGFLQUOTA_________8000____________________________________ DEC VTX stores subscriber account quotas in the file SYSUAF.DAT. Use the OpenVMS Authorize Utility to verify and change subscriber account quotas. First set your directory to SYS$SYSTEM and then run AUTHORIZE: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> At the UAF> prompt, enter the SHOW command with an account name to check a particular account. For example: UAF> SHOW SMITH To change a quota, enter the MODIFY command. The following example changes the FILLM quota for the SMITH account and then exits from the utility: UAF> MODIFY SMITH /FILLM=50 UAF> EXIT After you exit from the utility, the system displays messages indicating whether or not changes were made. Once the changes have been made, you must log out and log in again for the new quotas to take effect. 3-6 After Installing DEC VTX For more information on modifying account quotas, see the description of the Authorize Utility in the OpenVMS System Management Subkit. 3.4 Defining System Logicals If you install the classic subscriber client files for future modification, you should define two system logicals at startup time. The following example shows the DEFINE command lines you should enter in the SYS$MANAGER:SYSTARTUP_V5.COM file for TCP files stored in the default directory. $ DEFINE/SYSTEM/EXECUTIVE VTX$REQUIRE SYS$SYSROOT:[TCPLIB] $ DEFINE/SYSTEM/EXECUTIVE DSL$REQUIRE SYS$SYSROOT:[TCPLIB] DEC VTX does not require that you define these logicals in order for it to run; however, the logicals are useful when you want to modify the TCP. 3.5 DECnet You must have DECnet running on your OpenVMS system to run DEC VTX. The OpenVMS operating system comes with a single node DECnet license, so that even if you have a single node system, you can run DECnet. If DECnet is already running on your OpenVMS system, you can create a VTX operator's account. If your site is not running DECnet, you must execute the two command procedures (described in Section 3.5.1 and Section 3.5.2) in order to establish your OpenVMS system as a DECnet node and to start DECnet. 3.5.1 Establishing a DECnet Node To establish a DECnet node, set your default directory to SYS$MANAGER, and then identify your OpenVMS system as a DECnet node by executing the command procedure NETCONFIG.COM as follows: $ SET DEFAULT SYS$MANAGER $ @NETCONFIG The command procedure is interactive and self-explanatory. The procedure asks you to supply a DECnet node name and DECnet address for your node, and whether you want a default DECnet account. Follow the instructions that After Installing DEC VTX 3-7 appear on your terminal. Your node name can be any 6- character alphanumeric name. If you do not have a multi- node DECnet license, a node address of 1 is recommended. If you are configuring a multi-node network, you should first read the OpenVMS DECnet documentation. This is the only time you should have to run NETCONFIG in order to use DEC VTX. 3.5.2 Starting DECnet After you add your node to the DECnet database, you must start DECnet. This procedure activates the changes you made to the DECnet database and makes your OpenVMS system a recognized DECnet node. To start DECnet, execute the command procedure STARTNET.COM as follows: $ @STARTNET If your site does not have a multi-node DECnet license, your terminal displays a series of error messages while STARTNET.COM is executing. You can ignore these. You must execute STARTNET.COM every time you boot your OpenVMS system, but not every time you start DEC VTX. For convenience, you can insert the @STARTNET command in the SYS$MANAGER:SYSTARTUP_V5.COM file so that DECnet starts automatically every time you boot your OpenVMS system. 3.6 Creating a VTX Operator Account Create a VTX operator account that allows you to run a VTX Server. The operator account requires certain privileges and quotas. To add an operator account to your OpenVMS system, run the OpenVMS Authorize Utility, as described in the documentation on the OpenVMS System Management Subkit. Assign the following authorized and default privileges to the VTX operator's account: GROUP SYSNAM GRPNAM TMPMBX NETMBX 3-8 After Installing DEC VTX In addition, assign the following quotas to the account: __________________________________________________________ Account_Quota____Value____________________________________ ASTLM 250 BIOLM 230 BYTLM[1] 65000 DIOLM 50 ENQLM 300 FILLM 200 TQELM 20 [1]Minimum_value,_see_the_following_note__________________ __________________________________________________________ ________________________Note ________________________ The BYTLM value listed in the previous table is the minimum value required and must be raised sufficiently to accommodate the number of indexes that you use. For example, if you use 72 indexes, the correct value is 260000. _____________________________________________________ After you create an account for the VTX operator, you need to create a directory for that account. Assign the same UIC to the directory as the Authorize Utility assigned to the operator account. If you need to run VTX Workbench from the VTX operator account, set the PGFLQUO value to at least 12,000 (see the DEC VTX Service Provider's Guide). The Operator's account must have GROUP and GRPNAM privileges so that VTX utilities can manage group logical names. Since these privileges also allow the operator account to define group logical names at the DCL level, Digital recommends that you assign group UICs for operator accounts that differ from user accounts on your system. After Installing DEC VTX 3-9 3.7 Using Search Lists When you define the default device and directory names for the VTX operator account with the ADD command in the Authorize Utility, the utility combines these names to become the definition of the logical name SYS$LOGIN when you log in to that account. The format for the command is: ADD new-username /DEVICE=device-name/DIRECTORY=[directory- name] At OpenVMS system startup, if you define the default device name as a system logical name which has an equivalence string that is an OpenVMS search list, you must be sure to create the default directory ([directory- name]) for the VTX account on the first device in this search list. For example, if your system defines SYS$SYSROOT as follows, you can use the DCL command SHOW LOGICAL SYS$SYSROOT to display the definition at your terminal: "SYS$SYSROOT" = "DISK1:[SYS0.]" (LNM$SYSTEM_TABLE) = "SYS$COMMON" "SYS$COMMON" = "DISK1:[SYS0.SYSCOMMON.]" (LNM$SYSTEM_TABLE) Now, suppose you create the VTX account to have the following SYS$LOGIN definition: "SYS$LOGIN" = "SYS$SYSROOT:[VTX]" You must be sure that the VTX directory ([VTX] in the preceding example, or whatever name you have chosen) is a subdirectory of DISK1:[SYS0]. For example: DISK1:[SYS0.VTX] If your default directory is set to the SYS$LOGIN equivalence name rather than to SYS$LOGIN, you will be unable to start the VTX server or create any files. 3.8 Enhancing DEC VTX Performance After you install DEC VTX, you should adjust your system to enhance performance or lower the use of some system resources. See the DEC VTX Operator's Guide for information that may be useful in tuning your system. 3-10 After Installing DEC VTX 3.8.1 Installing DEC VTX as a Shared Image The most frequently used image of DEC VTX is: VTX$CLIENT_ CC.EXE. If you use the classic client, then the image name is VTXPAD.EXE VTX$MSGSHR.EXE While you do not need to install any DEC VTX components as shared images, you can reduce the system overhead and memory requirements by installing it as a shared image, particularly if you expect DEC VTX to be used extensively on your system. To install DEC VTX as a shared image on a system that is currently running, use the OpenVMS Install Utility (INSTALL). You should perform the install operation on a newly rebooted system because the available space in the global page table is less likely to be fragmented. To install DEC VTX as a shared image, first determine the number of available global pages and global sections on your system. Table 3-2 shows correct values for the GBLPAGES and GBLSECTIONS system parameters. Table_3-2_Required_System_Parameter_Values________________ System_Parameter_______Value______________________________ GBLPAGES n + 1300 GBLSECTIONS____________n_+_5______________________________ The n variable refers to the system parameter values currently in use. To install DEC VTX, you must raise those values by the number indicated. The n + 1300 value for GBLPAGES and the n + 5 value for GBLSECTIONS in Table 3-2 indicate that you must have at least 1300 unused pages and 5 unused sections available on your system for the installation to process successfully. To calculate how many unused global pages and global sections your system has, perform the following steps: 1. Run the OpenVMS Install Utility (INSTALL) using the following DCL command: After Installing DEC VTX 3-11 $ INSTALL LIST /GLOBAL /SUMMARY The Install Utility displays a summary of global pages and global sections used by your system, as well as the current number of unused global pages. For example: Summary of Local Memory Global Sections 258 Global Sections Used, 22580/3420 Global Pages Used/Unused 2. Determine if the number of unused global pages (3420 in the example) is equal to or greater than 1300. If the number of unused pages is less than 1300, you need to increase the value for GBLPAGES. 3. Run the System Generation Utility and use the SHOW command to determine how many global sections have been allocated. For example: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> SHOW GBLSECTIONS Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- GBLSECTIONS 512 250 20 4095 Sections 4. Subtract the amount shown in the summary (258 in the example) from the amount allocated. If the difference is less than 5, you need to increase the value of the GBLSECTIONS parameter. After you reset the system parameter values, invoke the OpenVMS Install Utility from a privileged account and then install DEC VTX as a shared image: $ INSTALL INSTALL> ADD SYS$SYSTEM:VTX$CLIENT_CC.EXE /OPEN /SHARED /REPLACE INSTALL> ADD SYS$SYSTEM:VTX$MSGSHR.EXE /OPEN /SHARED /REPLACE INSTALL> EXIT You must add the following lines to the appropriate system startup command file so that each time you start the system, DEC VTX is available as a shared image. If your site modularizes its startup procedures, be sure you add the lines to the correct file. The default startup command file for OpenVMS Version 5.n systems is SYS$MANAGER:SYSTARTUP_V5.COM. 3-12 After Installing DEC VTX ________________________Note ________________________ If you have previously used installed VTX images, make sure you use REPLACE when you install DEC VTX. This command has the following format: $ INSTALL INSTALL> REPLACE SYS$SYSTEM:VTXPAD.EXE /OPEN /SHARED _____________________________________________________ If you install DEC VTX as a shared image, you need to increase the value of the global page and global section parameters. Increase global pages (GBLPAGES) by 1300 pages and global sections (GBLSECTIONS) by 5 sections. 3.9 Deleting the [.VTX$VISTA] Subdirectory After Workbench information providers (IPs) start using the Workbench Utility, DEC VTX no longer requires the [.VTX$VISTA] subdirectory. If you followed the procedure specified in Section 1.5.3, the [.VTX$VISTA] subdirectory should be empty and you can now delete it. 3.10 Print Queue and Workbench Output Files Directory The print queue no longer uses the SYS$SYSROOT:[VISTA_ FILES] directory. When the VTXWPS_STARTUP.COM procedure starts the DEC VTX print queue, the system creates a new directory, SYS$SYSROOT:[VTX$WB_FILES]. After the system creates this directory, you can move all the files from the [VISTA_FILES] directory to the [VTX$WB_FILES] directory using the following command: $ RENAME SYS$SYSROOT:[VISTA_FILES]*.* SYS$SYSROOT:[VTX$WB_FILES]*.* After you move the files, the SYS$SYSROOT:[VISTA_FILES] directory is empty and you can delete it. After Installing DEC VTX 3-13 3.11 Workbench Server Command Procedure Changes If your site previously used VISTA Version 3.n to create VTX infobases, you must modify any command procedures you use to start and stop the VTX Servers. Change the commands and logical definitions as noted in Table 3-3. Table_3-3_Workbench_Server_Command_Procedure_Changes______ Current_______________Change_to:__________________________ START VISTA_SERVER START WORKBENCH_SERVER DEFINE VISTA$SERVER DEFINE VTX$WB_SERVER DEFINE VISTA$STYLE DEFINE VTX$WB_STYLEFILES STOP_VISTA_SERVER_____STOP_WORKBENCH_SERVER_______________ 3.12 VAS Command Procedure Changes Prior to VTX Version 4.0, the VAS runtime system was started using VASCTL. If you have any existing procedures that use VASCTL, they must be modified to use VTXCTL. All VASCTL functionality has been merged into VTXCTL. 3.13 Determining and Reporting Problems If an error occurs while using DEC VTX and you believe that DEC VTX is causing the error, take one of the following actions: o Call your Customer Support Center if you have a BASIC or DECsupport Software Agreement. With these services, you receive telephone support that provides both high- level advisory and remedial assistance. o Submit a Software Performance Report (SPR) if you have a Self-Maintenance Software Agreement. o Submit a Software Performance Report (SPR) if you purchased DEC VTX within the past 90 days and you think the problem is caused by a software error. 3-14 After Installing DEC VTX 3.14 Online User Guide DEC VTX provides an Online User Guide which can be found in VTX$LIBRARY. Called VTX_GETTING_STARTED.VTU, it is to be used instead of the old VTXMAIN.VTU. It is highly recommended you remove VTXMAIN.VTU pages from your infobase, and replace them with the VTX_GETTING_ STARTED.VTU pages. This infobase features: o An introduction to VTX o Detailed information about VTX functions o Supplied keypad mapping o A list of the VTX session status messages ________________________Note ________________________ Digital recommends that you open the provided .VTD file. If you do, you will automatically benefit from any changes that Digital have made to the .VTU file. _____________________________________________________ 3.14.1 Installing the Getting Started Infobase The new infobase page numbers are in the VTX reserved page range, 089*. The prefix for the new infobase is 08967, and the main menu is 08967. You can put these pages in the same page file with the VTX_INTERNALS.VTU infobase (which contains the login forms, usage forms, and so forth). The following section is an example of the steps involved to use the new Getting Started infobase in the same file as VTX_INTERNALS.VTU pages. You must do this for every home server in your VTX network. Note that if you already have a VTX_INTERNALS infobase, you do not need to create a new VTD file. You can simply open the current one and use the UPDATE command to add the VTX_GETTING_STARTED pages. After Installing DEC VTX 3-15 $ VTX/UPD DEC VTX Infobase Update Utility, V6.2 UPD> CREATE/PAGE VTX_INTERNALS/RANGE=(089,089*) %VTX-I-RNGMSG1, Your current range is 0 to 9~~~~~~~~~~~~~ %VTX-I-RNGMSG2, The range for page file VTX_INTERNALS is 089 to 089~~~~~~~~~~~ UPD> CREATE/KEY VTX_INTERNALS/RANGE=(089,089*) %VTX-I-RNGMSG2K, The range for keyword file VTX_INTERNALS is 089 to 089~~~~~~~~~~~ UPD> UPDATE/INPUT=VTX$LIBRARY:VTX_INTERNALS Total of 61 pages added UPD> UPDATE/INPUT=VTX$LIBRARY:VTX_GETTING_STARTED Total of 112 pages added UPD> Exit %VTX-I-KWDFILCLS, Keyword file VTX_INTERNALS closed %VTX-I-PAGFILCLS, Page file VTX_INTERNALS closed $ After completing the above tasks, add a choice to your main menu for the main help menu to the getting started infobase. The main help menu page number is 089672. 3-16 After Installing DEC VTX 4 ________________________________________________________________ Installation Verification Procedure The DEC VTX Installation Verification Procedure (IVP) is used to verify the installation of the product. This procedure takes about 15 minutes. For the most part, the instructions in this chapter assume that you are verifying a new installation of DEC VTX. There are three different IVPs for DEC VTX. The IVP you run depends on the VTX option you choose. The IVP for the full kit consists of two parts, while the IVP for the VALU runtime kit and the remote update kit have only one part each. Even though you can install DEC VTX and run the IVP using either a hardcopy or a video terminal, you must have a video terminal to run the second part of the IVP for the full VTX kit. ________________________Note ________________________ If you install only the TCP and the terminal concentrator, you cannot run the IVP. Also, if you have a previous version of DEC VTX, certain files will already be in place. Therefore, you may need to slightly modify some of these instructions. _____________________________________________________ 4.1 Running the DEC VTX IVP This section describes how to run the DEC VTX IVP. See Section 4.2 for instructions on how to run the optional portion of the IVP for the full VTX kit. Installation Verification Procedure 4-1 You can run the IVP during the DEC VTX installation pro- cedure. To run the IVP independently of the installation procedure, you must have DEC VTX V6.2 installed on your system and you must log in to an account with privileges. Before you run either the IVP or its optional supplement (for the full VTX kit), you must have DECnet running on your system. Run the IVP command procedure using the command procedure: $ @SYS$SYSROOT:[SYSTEST]VTX$IVP.COM After you enter the command, a message appears indicating that the IVP has begun: * * * * * * * * * * * * * * * * * * * * * * * * * * * * Installation Verification Procedure * * * * * * * * * * * * * * * * * * * * * * * * * * * * The VTX$IVP.COM command procedure does the following: o Creates a DEC VTX infobase. o Starts a DEC VTX server. o Starts a Workbench server. o Creates a Workbench library. o Stops the Workbench server. o Starts a VAS server. o Builds and loads VAS transaction definitions. See Appendix A for a sample installation of DEC VTX. These operations verify the installation of the complete DEC VTX kit. The next message introduces the optional part of the IVP: 4-2 Installation Verification Procedure * * * * * * * * * * * * * * * * * * * * * * * * * * * * You can now run the optional part of the IVP. See the "VTX Installation Guide" for instructions. * * * * * * * * * * * * * * * * * * * * * * * * * * * * The automated portion of the IVP is now complete. Assuming it detected no errors, the IVP displays the following message, regardless of the command procedures you chose to run the IVP: * * * * * S U C C E S S * * * * * DEC VTX IVP completed successfully * * * * * S U C C E S S * * * * * 4.2 Performing the Optional Part of the IVP This section describes how to run the optional part of the DEC VTX IVP for the full VTX kit. You must use a video terminal to run this part of the IVP. To perform this part of the DEC VTX IVP, follow these steps: 1 Enter the following command to start your VTX session: $ VTX A VTX menu with only one choice appears on the screen. 2 Enter 1 at the CHOICE: prompt and press : Choice: 1 DEC VTX displays a form with three fields on the screen. 3 Fill in each field with any string of text of no more than five characters, and press the FORM ENTER function key sequence (PF1-ENTER for Digital terminals). A VTX display page appears on the screen. This is the last page in the DEC VTX IVP. 4 Exit from VTX, using the EXIT function key sequence . Installation Verification Procedure 4-3 That completes the optional portion of the DEC VTX IVP. Next you must stop the servers. To so so, follow these steps: 1 Run the VTXCTL Utility using the following command: $ Run SYS$SYSTEM:VTXCTL 2 Type the STOP commands and the EXIT command at the CTL> prompt; for example: CTL> STOP SERVER/NAME=IVP CTL> STOP VAS/NAME=IVP CTL> EXIT $ 3 Next, verify that the information you typed on the DEC VTX form was accepted correctly. Enter the following command to display the VAS log file, VASIVP.ASL: $ TYPE VASIVP.ASL 4 Check that the text you entered in the three fields on the DEC VTX form top appends to the first line in the log file. The log should also include two additional lines. The first of those lines should contain the following text: Installation Verification Procedure 5 The next line should indicate that the IVP has been successfully completed: Installation Verification Procedure Successfully Completed 6 If you see this last line in the VAS.ASL file, you know that the optional part of DEC VTX IVP processed correctly. 4.3 OpenVMS Client Initialization Files DEC VTX provides initialization files (.INI) that can be customized to your specific requirements. If you would like to customize your keypad definitions, copy the .INI file to your SYS$LOGIN and edit it as you like. The clients first look in SYS$LOGIN, then in VTX$LIBRARY for the file. 4-4 Installation Verification Procedure The syntax for the default .INI file is as follows: FUNCTION=VTX Function KEY1=first-key KEY2=second-key (or NULL if none) The default bindings are as follows: Table_4-1_Default_Bindings________________________________ Definition_________________Function____Key1________Key2___ Line Editing Functions CUR-LEFT LEFT NULL CUR-RIGHT RIGHT NULL CUR-END CTRL/E NULL CUR-BEGIN CTRL/H NULL CLEAR- CTRL/U NULL BEGIN Help Functions HELP PF2 NULL HELP HELP NULL HELP PF1 'h' Backup Functions BACKUP PF3 NULL BACKUP F8 NULL BACKUP PF1 'h' BACKUP PF1 'q' BACKUP UP NULL Next Page Function NEXT-PAGE NEXT NULL NEXT-PAGE PF4 NULL Previous Page Function PREV-PAGE PREV NULL PREV-PAGE PF1 PF4 (continued on next page) Installation Verification Procedure 4-5 Table_4-1_(Cont.)_Default_Bindings________________________ Definition_________________Function____Key1________Key2___ Exit Function EXIT CTRL/Z NULL EXIT PF1 KDOT EXIT F10 NULL Main Function MAIN PF1 PF3 MAIN PF1 'm' MAIN PF1 UP MAIN F9 NULL Get Again Function GET-AGAIN PF1 K0 Next Choice Function NEXT- PF1 K2 CHOICE NEXT- PF1 RIGHT CHOICE NEXT- PF1 NEXT CHOICE Previous Choice Function PREV- PF1 K1 CHOICE PREV- PF1 LEFT CHOICE PREV- PF1 PREV CHOICE Set Mark Function SET-MARK PF1 K8 SET-MARK INSERT NULL Goto Mark Function GOTO-MARK PF1 K9 (continued on next page) 4-6 Installation Verification Procedure Table_4-1_(Cont.)_Default_Bindings________________________ Definition_________________Function____Key1________Key2___ Find Function FIND PF1 K7 FIND FIND NULL Reveal Function REVEAL PF1 'v' REVEAL PF1 K4 Set Personal Magazine Function SET-PM PF1 K6 SET-PM PF1 INSERT Get Personal Magazine Function GET-PM PF1 K3 GET-PM PF1 FIND Next Form Feed Function NEXT-FIELD TAB NULL Previous Form Feed Function PREV-FIELD PF1 TAB Form Enter Function FORM-ENTER PF1 ENTER List Menu Item Select Function SELECT- F12 NULL ITEM Menu Bar Activator ACTIVATE- F7 NULL MENU ___________________________GET-AGAIN___CTRL/W______NULL___ Installation Verification Procedure 4-7 4.3.1 Initialization files for ALL-IN-1 Users DEC VTX provides ALL-IN-1 support for the new character cell client. The file, VTXALLIN1.INI, can be copied to the user's account, or used to replace the default VTX.INI file in VTX$LIBRARY for system wide use. The following files are provided: VTXALLIN1.INI VTX.SCP OA$APPL_INTMENU.SCP VTX.COM To use the new character cell client from within ALL-IN-1, follow these steps: 1. Copy VTXALLIN1.INI to SYS$COMMON:[VTX$LIBRARY]VTX.INI 2. Copy VTX.COM, VTX.SCP and OA$APPL_INTMENU.SCP from the VTX$LIBRARY 3. Copy VTX$LIBRARY:VTX.COM to OA$LIB:VTX.COM 4. Copy VTX$LIBRARY:VTX.SCP and OA$APPL_INTMENU.SCP to OA$DO:*.SCP. 4.4 Conclusion After you successfully perform all the IVP tasks, you will have installed your DEC VTX system correctly. If you encounter any difficulties, first verify that the appropriate files for starting VTX are in the expected directories. Next, make sure you have followed the procedures in this manual, including setting up the correct quotas and privileges. Then reinstall VTX. If failures still occur, submit an SPR or contact your local support office for assistance. 4-8 Installation Verification Procedure Part II ________________________________________________________________ Installing the MS-DOS Client on a Personal Computer This section explains how to install the MS-DOS client on a Personal Computer (PC). 5 ________________________________________________________________ Installing the MS-DOS Client This section describes how to install the MS-DOS client on your Personal Computer (PC). Once installed, you can access DEC VTX on your PC running MS-DOS. 5.1 Before You Begin Before you install the MS-DOS client: o Verify which versions of your operating system are compatible with this version of DEC VTX. This is listed in the Software Product Description (SPD), which is included in the DEC VTX kit. o Your PC must be a DECnet node and have DECnet running. o You need access to two OpenVMS systems: the OpenVMS system you install the kit from, which needs to access the directory: SYS$COMMON:[VTX$LIBRARY] and the system that runs your home VTX server. This should be defined as follows: C:> NCP DEFINE NODE area.num NAME nodename You can define the OpenVMS system for your home VTX server after the installation, if you prefer. o You must have write access to the disk on your PC on which you will install the VTX DOS client. o You must have 2MB of free space on the destination disk. o You must have the file ANSI.SYS loaded on the PC on which you will install the VTX DOS client. Installing the MS-DOS Client 5-1 5.2 Installing the Software from an OpenVMS Kit This section describes the tasks you must perform to install the client. You can quit the installation at any time by pressing F3. If you need help on any question, press F1. o Copy the PC installation directory from the VAX to a scratch directory on your PC (see the PCSA NFT COPY /BLOCK utility). This copy must use the /BLOCK qualifier, as it contains image format files. For example: C:>MD TEMPVTX C:>NFT COPY/BLOCK VMSNODE::VTX$COMMON:[VTX$LIBRARY.REFKIT.MSDOS]*.* C:>\TEMPVTX o From the directory on the PC where the files were copied, type INSTALL. For example: C:> CD TEMPVTX C:> INSTALL o The installation will display the following question: Do you wish to continue or quit [C]? o If you are unsure as to whether to continue, refer to the DEC VTX Release Notes supplied with the OpenVMS kit for further information If you press , the installation will display a new screen with the following questions: Where are the installation files to be found? [C:\] o Enter the name of the directory in which the installa- tion files are located and press . The current directory is the default. The installation will then ask: Where are the files to be installed? [C:\VTX]: o Enter the name of the directory in which you want the installation files installed and press . A subdirectory of the current directory (named VTX) is the default. The installation will then ask: Do you wish to install the DECnet MS-DOS client? [y]: 5-2 Installing the MS-DOS Client o Enter YES and press to install the standard MS-DOS VTX client. The installation will then ask: Do you wish to modify any of the above? [y]: o If you need to change any of your responses, enter YES and press . The installation will return to the first screen and display your response as the default. If you are satisfied with your responses, enter NO and press . o Once you have indicated that you are satisfied with all of your responses, the installation displays a screen showing the progress of the installation, as the VTX files are copied into the directory you have specified. o When all the installation files have been copied, the installation displays a message informing you that VTXSTART.BAT has been installed in the directory you have specified. o VTXSTART must be run each time you start your PC, before you run VTX. Once the installation is complete, you can start VTX as follows at the system prompt. For basic DECnet DOS client, type: C:> VTX -sserver -oobject 5.3 Building the Kit on Diskette Included with the DOS kit is a batch file that allows you to build the distribution kit on four diskettes. The diskettes must have a capacity of 720K bytes or greater, and have already been formatted. To build the kit, o Execute the file MAKE_FLP.BAT in the directory containing the distribution kit. The format is: MAKE_FLP [destination disk drive:] If the destination disk drive qualifier is left out, the batch procedure defaults to drive a: Installing the MS-DOS Client 5-3 o You will then be prompted to insert each diskette in turn, until all four diskettes have been built (and labeled DEC VTX #disknumber). 5.3.1 Installing the Software from Diskette To install the kit from diskette, insert disk 1 (labeled DEC VTX #1) into the disk drive, and answer the questions as given in Section 5.2. The installation procedure will prompt you when you need to insert the next diskette. 5-4 Installing the MS-DOS Client Part III ________________________________________________________________ Installing DEC VTX on an ULTRIX Operating System This section explains how to install DEC VTX on an ULTRIX operating system. It also explains how to read the online release notes before or after installing the product. ________________________Note ________________________ Part 3 applies only to the OpenVMS VAX operating system. _____________________________________________________ 6 ________________________________________________________________ Preparing for Installation on ULTRIX Clients This chapter describes the preparations and requirements necessary to install the DEC VTX ULTRIX client. Before starting the installation procedures, you should complete the preparation requirements outlined in this chapter. The sections in this chapter provide the necessary information to make your installation run smoothly. This chapter will help you determine the following: o Whether you need to read the Release Notes o Whether you are installing DEC VTX locally or into a Diskless Management Services (DMS) server area for diskless clients o Whether you need superuser privileges for the system on which you will be installing DEC VTX o If the system on which you will install DEC VTX meets the DEC VTX hardware, software, and disk space requirements o Which optional DEC VTX subsets you should install o How much disk space you will need o Whether you have to back up your system disk During the installation of the OpenVMS VAX kit, the ULTRIX kits are placed in a reference directory on the OpenVMS VAX system. Section 7.1 describes the actions you should take to copy the ULTRIX kits to an ULTRIX node and unpack the ULTRIX kits into a form suitable to install with setld. Preparing for Installation on ULTRIX Clients 6-1 6.1 Release Notes DEC VTX provides online and hardcopy release notes. Digital strongly recommends that you read the release notes before using the product. The release notes may contain information about changes to the application. Your documentation includes the DEC VTX Release Notes, which you should read before installing DEC VTX. 6.2 Using RIS for Client Installations If you expect to use DEC VTX subsets from a Remote Installation Services (RIS) server area of a remote system for installation on your local system, first check with your site system administrator to make sure that: o A DEC VTX kit is installed in the RIS server area and is available for use o Your system is registered as a RIS client If DEC VTX subsets are available to you on a RIS server system, you will need the name of that system to start the installation procedure described in this guide. 6.3 Installing DEC VTX Into a RIS Server Area If you manage a Remote Installation Services (RIS) server area and intend to install DEC VTX into your server area, read the following sections of this guide: o Section 6.5 for hardware and software requirements, for the names and numbers of software subsets, and for disk space requirements o Sections 7.1.2.1 and 7.1.2.2 explain the displays and prompts that are specific to DEC VTX installations To start the installation procedure, do not use the setld command. Use the ris utility (See Section 7.2). 6-2 Preparing for Installation on ULTRIX Clients 6.4 Installing DEC VTX Into a DMS Server Area If you manage a DMS server area and want to install DEC VTX into a DMS server area, read Sections 7.1.2.1 and 7.1.2.2. These sections explain the displays and prompts that are specific to DEC VTX installations. To start the installation procedure, do not use the setld command. Use the dms utility (see Section 7.2). In a local (node-specific) installation, the system on which you are installing DEC VTX will use its own disks when DEC VTX is run. A local (node-specific) installation procedure loads DEC VTX files on the disks that belong to the system where you perform the installation. When DEC VTX is run, its executable files are mapped into memory on the same system. In a diskless client environment, the system on which you are installing DEC VTX is a server for Diskless Management Services (DMS) and provides the disks for client systems running DEC VTX software. This installation environment is referred to as "diskless" because the system uses DEC VTX software accessed through the network by Network File System (NFS) software. When DEC VTX is run by users logged into a client system, DEC VTX executables are mapped into memory on the client system rather than the server system. From the perspective of the client node, DEC VTX installation is handled entirely by the manager of the DMS server area. ________________________Note ________________________ The diskless server area does not provide DEC VTX software to users logged in to the server system itself. Installing DEC VTX into the diskless environment provides DEC VTX software only to client systems. Therefore, if users at your site need to use DEC VTX when logged in to the local server system, you must perform a local (node-specific) installation of DEC VTX in addition to the diskless installation. _____________________________________________________ Preparing for Installation on ULTRIX Clients 6-3 6.5 Installation Procedure Requirements This section discusses various requirements for installing DEC VTX. 6.5.1 Checking Login Privileges You must be able to log in as superuser on the system where you are installing DEC VTX. Only when you are logged in as superuser do you have sufficient privileges to install the DEC VTX software. 6.5.2 Software Requirements DEC VTX requires ULTRIX Version 4.1 or higher to be installed. In addition, DEC VTX requires the following ULTRIX software subsets to be loaded on the system where you install DEC VTX: o UDTBASE410 (for RISC) or ULTBASE410 (for VAX), which is named "ULTRIX Base System" o UDTINET410 (for RISC) or ULTINET410 (for VAX), which is named "TCP/IP Networking Utilities" To install the optional DEC VTX reference pages (manual pages), the following ULTRIX software subsets must be installed on the system where you install DEC VTX: o UDTMAN410 which is named "On Line Manual Pages" o UDTDCMT410 which is named "Document Preparation Software" If you are installing DEC VTX in a local (node-specific) environment, perform the following steps to determine whether the preceding ULTRIX subsets are loaded: 1. Log in to the system where you plan to install DEC VTX. 2. Enter the following commands: % /etc/setld -i | grep BASE410 % /etc/setld -i | grep INET410 % /etc/setld -i | grep MAN410 % /etc/setld -i | grep DCMT410 6-4 Preparing for Installation on ULTRIX Clients 3. Check the displayed rows for the relevant subset names and for any related patch names. The word installed appears in a row after the subset identifier code when a subset is loaded. If the word installed does not appear (the second column in a row is blank), the subset or patch is not loaded. In this case, you must load the missing ULTRIX software before installing DEC VTX. 6.5.3 Special Requirements for Installing DEC VTX Before installing the DEC VTX ULTRIX kit, you must be sure to have ULTRIX and DECnet/Internet installed. 6.5.4 Determining Which Subsets to Load You must choose the DEC VTX subsets you want to load. The DEC VTX subsets have the following titles: o DEC VTX Base Reference Pages The online reference page subset is an optional subset. Its identifier is MAN400 for RISC or VAX systems. You can load the DEC VTX reference page subset only if the ULTRIX reference page subset is already loaded on your system. If users on the system where DEC VTX is being installed use reference pages that are nfs mounted from another system, load the DEC VTX reference pages on the other system rather than the one where you are currently installing DEC VTX. In this case, do not request the reference page subset during this installation of DEC VTX. After the installation is complete, you can log in to the system where the ULTRIX reference pages are installed and load only the DEC VTX reference page subset on that system. See the setld(8) reference page for information about loading specific subsets. o CC Client o Motif Client o Base Files (library file) Preparing for Installation on ULTRIX Clients 6-5 6.5.5 Determining Disk Space Requirements To determine the current amount of free space for a directory path, log in to the system where you plan to install DEC VTX. You can check which file systems are mounted and where they are by displaying the file /etc/fstab. For example: # more /etc/fstab /dev/rd0a:/:rw:1:1:ufs:: /dev/rd0g:/usr:rw:1:2:ufs:: /usr/staff/r1/leslie@bigsys:/usr/staff/r1/leslie:rw:0:0:nfs:bg: /usr/man@bigsys:/usr/man:ro:0:0:nfs:bg: The previous display indicates that /usr (mounted to /dev /rd0g ) is the only mount point that affects where DEC VTX files will reside; the system has only one local disk drive and the /usr/kits and /usr/var/kits file systems reside in the g partition of the disk on that drive. Enter the df command to determine total space and free space for the one or two file systems where DEC VTX files will reside. Based on the previous display of the /etc /fstab file, which shows that only /usr is a mount point, you would only need to inspect free space in the /usr file system: # df /usr Filesystem Total kbytes kbytes % node kbytes used free used Mounted on /dev/rd0g 122598 54447 55892 49% /usr The previous display indicates that there are 55892K bytes free. On systems where /usr/var/kits and /usr/kits are mounted to different devices from /usr, enter the following command: # df /usr/kits /usr/var/kits In this case, you compare space required for DEC VTX files in /usr/kits to the free space displayed in the first line of the df output list, and you compare the space required for DEC VTX files in /usr/var/kits to the free space displayed in the second line of that list. 6-6 Preparing for Installation on ULTRIX Clients 6.5.5.1 Checking Disk Space for Installation into a Diskless Environment For DEC VTX installations into the diskless environment, the disks where DEC VTX subsets reside are on a server system. Therefore, for installations into diskless environments, log in to the server system to check disk space requirements. Inspect the free space in the following file systems; if you have only one diskless installation environment set up on your system, the file systems are rooted at the nodes /dlenv0 and /dlclient0 as follows: o /dlenv0/root0.mips/usr (root area for ULTRIX RISC installations) or /dlenv0/root0.vax/usr (root area for ULTRIX VAX installations) o /dlclient0/client.root (client area) On the client system, the /usr/var file system points to the /var file system. Therefore, you need to check the free space in /dlclient0, /dlclient1, /dlclient2, and so on. If multiple root areas serve the DEC VTX software, each root area requires space for all the installed subsets. 6.6 Backing Up Your System Disk Digital recommends that you back up your system disk before installing any software. Use the backup procedures established at your site. For details on performing a system disk backup, see your ULTRIX documentation. 6.7 Stopping the Installation You can stop the installation procedure any time by using . However, files created up to that point are not deleted. You must delete these files interactively. Preparing for Installation on ULTRIX Clients 6-7 6.8 Error Recovery If errors occur during the installation, the system displays failure messages. If the installation fails due to insufficient disk space, the installation procedure displays the following message: There is not enough file system space for subset ?$S? ?$DESC? (?$S?) will not be loaded. Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect o The prerequisite software version is incorrect o The system parameter values for successful installation are insufficient For descriptions of error messages generated by these conditions, see the ULTRIX documentation on system messages, recovery procedures, and ULTRIX software installation. If you are notified that any of these conditions exist, take the appropriate action described in the message. If an error occurs while using DEC VTX and you believe the error is caused by a problem with DEC VTX, take one of the following actions: o If you have a basic or DECsupport Software Agreement, call your Customer Support Center (CSC). The CSC provides telephone support for high-level advisory and remedial assistance. o If you have a Self-Maintenance Software Agreement, you can submit a Software Performance Report (SPR). o If you purchased DEC VTX within the last 90 days and you think the problem is caused by a software error, you can submit an SPR. 6-8 Preparing for Installation on ULTRIX Clients 7 ________________________________________________________________ Installation Procedure for the ULTRIX Client This chapter describes the installation procedures the for DEC VTX ULTRIX Client. Before you start, read Chapter 1, which describes the general options and requirements that apply to installing DEC VTX. DEC VTX ULTRIX Client can be installed in a number of ways: o Locally from tape, disk, CD-ROM, or Remote Installation Services (RIS) media (for RIS clients). Section 7.1 explains how to do a local installation. o Remotely into a Diskless Management Services (DMS) or RIS server area for future client use. These installation procedures assume that you have already created your server environment and are ready to add DEC VTX to it. Section 7.2 explains how to do a DMS and RIS server installation. 7.1 Installing DEC VTX Locally This installation procedure loads DEC VTX files on a disk that belongs to the system where you perform the installation. When DEC VTX is run, its executable images are mapped into memory on this system. This section explains how to start a local installation procedure and how to respond to installation procedure prompts. Installation Procedure for the ULTRIX Client 7-1 7.1.1 Starting the Installation Procedure The ULTRIX kits are supplied in TAR format as part of the OpenVMS VAX kit in a reference directory. This section describes how to: 1. Copy the ULTRIX kits to an ULTRIX node 2. Unpack the ULTRIX kits into a form suitable to install with setld The ULTRIX client kits consist of two tar files in the directory: SYS$COMMON:[VTX$LIBRARY.REFKIT] The files are: VTX_KIT_ULTRIX_RISC.TAR ULTRIX RISC clients VTX_KIT_ULTRIX_VAX.TAR ULTRIX VAX clients Each tar file contains all files necessary to install the MOTIF and character cell clients for DEC VTX. To install the ULTRIX clients, you need to copy the tar files to the ULTRIX system, unpack the tar files, and then follow the instructions in the installation guide for the installation with setld. Below is a list of steps to follow when installing the kit: o Login to superuser on the ULTRIX system and copy the kit from the OpenVMS VAX system. If you have DECnet, use dcp as follows: # mkdir /vtxkit # cd /vtxkit # dcp -i vmsnode/username/password::'SYS$COMMON:[VTX$LIBRARY.REFKIT] VTX_KIT_ULTRIX_VAX.TAR' VTX_KIT_ULTRIX_VAX.TAR 7-2 Installation Procedure for the ULTRIX Client o If you do not have DECnet, use ftp as follows: $ ftp ftp> open vmsnod Connected to vmsnod.foo.net.com. 220 VMSNOD FTP server (UCX Version 1.3) ready. Name (vmsnod:username): username 331 Password required for USERNAME. Password: 230 User logged in ftp> cd SYS$COMMON:[VTX$LIBRARY.REFKIT] ftp> binary 200 Type set to I. ftp> get VTX_KIT_ULTRIX_RISC.TAR 200 PORT command okay. 150 Opening data connection for VTX_KIT_ULTRIX_RISC.TAR (16.36.128.93,1032) 150 Opening data connection for VTX_KIT_ULTRIX_VAX.TAR (16.36.128.72,1038) 226 Transfer complete. local: VTX_KIT_ULTRIX_VAX.TAR remote: VTX_KIT_ULTRIX_VAX.TAR 1536000 bytes received in 18 seconds (84 Kbytes/s) ftp> bye $ ________________________Note ________________________ It is very important to use the "binary" command above before you copy the tar file. _____________________________________________________ o Untar the file on ULTRIX to the current directory: # tar xvf VTX_KIT_ULTRIX_VAX.TAR o Check for a previous installation of this kit, and de-install if you find one: # setld -i | grep VTX (or grep VTR for RISC) Installation Procedure for the ULTRIX Client 7-3 o If you find a kit on the system, de-install it as follows: # setld -d VTXBASE505 VTXMOTIF505 VTXCC505 VTXMAN505 o Install the kit from the current directory using setld # setld -l `pwd` 7.1.1.1 Using RA60 or CD-ROM Consolidated Distribution Media If you are installing DEC VTX from disk, start the installation procedure as follows: 1. Mount the media on the appropriate disk drive. 2. Log in as superuser (login name root) to the system where you are installing DEC VTX. 3. Make sure that you are at the root (/) directory by entering the following command: # cd / 4. Specify the /mnt directory to be the mount point for the distribution file system on the drive. If your drive is ra1, enter the following command: # mount /dev/ra1c /mnt 5. Enter a setld command that requests the load function and identifies the directory in the mounted file system where DEC VTX subsets are located. See Section 7.1.2 to continue the installation. 7.1.1.2 Installing DEC VTX from a RIS Server To install DEC VTX from a Remote Installation Services (RIS) server to a RIS client you must first install DEC VTX in your RIS server environment. See your RIS manager if DEC VTX is not already installed in the RIS server. To install DEC VTX subsets that reside in an /var/adm /ris distribution area on a remote system, start the installation procedure as follows: 1. Log in as superuser (login name root) to the system where you are installing DEC VTX. 7-4 Installation Procedure for the ULTRIX Client 2. Make sure that you are at the root (/) directory by entering the following command: # cd / 3. Enter a setld command that requests the load function and identifies the system where DEC VTX subsets are located. For example, if you are loading DEC VTX subsets from a RIS distribution area on node bigsys, enter the following command: # setld -l bigsys: If you receive an error, verify that you correctly followed the preparation steps in Section 6.2. See Section 7.1.2 to continue the installation. 7.1.2 Responding to Installation Procedure Prompts This section explains the installation procedure prompts and displays. 7.1.2.1 Selecting Subsets After you enter the setld command for local (node- specific) installations or after you start the dms or ris utility for server installations, the installation procedure displays the names of DEC VTX subsets and asks you to specify the subsets that you want to load: *** Enter Subset Selections *** The subsets listed below are optional: 1) DEC VTX base files for ULTRIX 2) DEC VTX character cell client 3) DEC VTX OSF/Motif client 4) DEC VTX man pages for ULTRIX 4) All of the Above 5) None of the Above 6) Exit without installing subsets Enter your choice(s): When installing from a RIS server, note that the subset numbers may vary depending on what products are available in the RIS area. If you specify more than one number at the prompt, separate each number with a space, not a comma. Installation Procedure for the ULTRIX Client 7-5 Next, the script lets you verify your choice. For example, if you enter 4 in response to the previous prompt, you will see the following display: You are installing the following subsets: 1) DEC VTX base files for ULTRIX 2) DEC VTX character cell client 3) DEC VTX OSF/Motif client 4) DEC VTX man pages for ULTRIX Is this correct? (y/n): If the displayed subsets are not the ones you intended to choose, enter n. In this case, the subset selection menu is again displayed, and you can correct your choice of optional subsets. If the displayed subsets are the ones you want to load, enter y. 7.1.2.2 Monitoring Displays During the Subset Loading Process The procedure displays a message that the installation is starting. If, during the course of the installation, you encounter errors from the setld utility, see the Diagnostics section of the setld(8) reference page for an explanation of the error and the appropriate action to take. If the verification process fails, you can look in the file /usr/var/adm/fverify to find information that can help you diagnose the problem. 7.2 Installing DEC VTX into a Server Environment This section explains how to start the installation procedure and load software subsets when you are installing DEC VTX into an environment controlled by DMS (Diskless Management Services) or RIS (Remote Installation Services). If installing from media, mount the distribution kit as follows: 1. For CD-ROM and RA60 media kits, mount the media onto the appropriate device on the server node. Then use the mount command to identify the special file for the device where you mounted the consolidated media. For 7-6 Installation Procedure for the ULTRIX Client example, if you mount the disk on drive ra1, enter the following command: # mount /dev/ra1c /mnt Section 7.2.1 explains how to install DEC VTX into a DMS server environment. Section 7.2.2 explains how to install DEC VTX into a RIS server environment. 7.2.1 DMS Server Installations The following procedure lets you install DEC VTX with the ULTRIX Version 4.1 dms utility into the diskless server area. The examples in this section show how to install the subsets to /dlenv0/root0.mips. 1. Log in and become the superuser. 2. To invoke the dms utility, enter the following command: # /etc/dms 3. Select the Install Software option from the following menu by typing i: DISKLESS MANAGEMENT SERVICES (DMS) UTILITY MENU a - Add Client Processor m - Modify Client Parameters r - Remove Client Processor l - List Registered Clients s - Show Products in Diskless Environments i - Install Software c - Create Diskless Area on Disk k - Kernel Rebuild or Copy e - Exit Enter your choice: i 4. Choose option 2 in the following menu: The menu below offers you two software installation alternatives: 1) You can install an operating system to a new diskless area. 2) You can install additional software to an existing diskless area that already contains an operating system. Diskless Area Software Installation Menu: Installation Procedure for the ULTRIX Client 7-7 1 Install Operating System to New Area 2 Add Software to Existing Area 3 Return to Previous Menu Enter your choice: 2 5. The following message lists the available installation directories: You have chosen to install additional software into an existing diskless environment. These are the available installation directories: If there is more than one installed rootn.mips directory in the diskless server area, choose the appropriate directory from the menu that lists existing rootn.mips directories. For example: 1. /dlenv0/root0.mips 2. /dlenv0/root1.mips 3. /dlenv0/root0.vax Enter your choice: 1 6. You are next prompted for an input device name: Enter the device special name or mount point of the distribution media, for example, /dev/rmt0h: /dev/rmt0h 7. If you want all registered clients to automatically have access to DEC VTX, enter y to the following question: The product software will automatically be propagated to every registered client. Is this alright? (y/n): y If you answer n, DMS returns you to the main menu. 8. If your distribution media is tape, a message appears asking you to confirm that the tape is ready and on line. If it is, type y. Please make sure your installation tape is mounted and on-line. Are you ready (y/n)? y Positioning Tape 9. The next message lists the software subsets you select for automatic installation. See Section 7.1.2.1 to specify the subsets you want to load. See Section 7.1.2.2 to monitor the displays during the subset load process and to complete the installation procedure. 7-8 Installation Procedure for the ULTRIX Client 10.If diskless clients are registered to share this area, a prompt asks you if you want to update the client_ name.root directories of those clients. Enter yes to keep the diskless clients in a consistent state. Repeat these installation procedures for each rootn.mips area you plan to set up. The dms main menu appears for your next selection. 7.2.2 RIS Server Installations The following sample session describes how to add the DEC VTX product to the ris0.mips area: 1. Log in and become the superuser. 2. Invoke the ris utility by entering the following command: # /etc/ris 3. Select the Install Software option from the Remote Installation Services (RIS) Menu by typing i: REMOTE INSTALLATION SERVICES (RIS) MENU a - Add Client r - Remove Client s - Show Products in Remote Installation Environments m - Modify Client i - Install Software e - Exit Enter your choice: i 4. Choose option 2 from the RIS Software Installation Menu: The menu below offers you two software installation alternatives: 1) You can create a new area to serve either RISC or VAX clients by installing a software product. The ris utility automatically creates the new area. 2) You can install additional software to an existing area that serves either RISC or VAX clients. RIS Software Installation Menu: Installation Procedure for the ULTRIX Client 7-9 1 Install Software to a New Area. 2 Add Software to an Existing Area. 3 Return to Previous Menu Enter your choice: 2 5. A list of available environments appears from which you might select ris0.mips: You have chosen to add a new product into an existing environment. Select the remote installation environment: 1 /var/adm/ris/ris0.mips ULTRIX V4.1/ULTRIX WS V4.1 MANDATORY SUPPORTED (RISC) 2 /var/adm/ris/ris0.vax ULTRIX V4.1/ULTRIX WS V4.1 SUPPORTED (VAX) Enter your choice: 1 6. You are next prompted for an input device name: Enter the device special file name or the path of the directory where the software is located, for example, /dev/rmt0h: /dev/rmt0h 7. If your distribution media is tape, a message appears asking you to confirm that the tape is ready and on line. If it is, type y: Please make sure your installation tape is mounted and on-line. Are you ready (y/n)? y Positioning Tape 8. The next message lists the software subsets you select for automatic installation. See Section 7.1.2.1 to specify the subsets you want to load. See Section 7.1.2.2 to monitor the displays during the subset load process and to complete the installation procedure. 9. After the subsets are installed, the following message appears: Media extraction complete. 7-10 Installation Procedure for the ULTRIX Client 10.Repeat steps a through f for each RIS client allowed to install DEC VTX. a. The ris main menu appears for your next selection. Select the Modify Client option from the Remote Installation Services (RIS) Menu by typing m: REMOTE INSTALLATION SERVICES (RIS) MENU a - Add Client r - Remove Client s - Show Products in Remote Installation Environments m - Modify Client i - Install Software e - Exit Enter your choice: m b. Enter the name of the client to be modified from the list of available clients: The following clients are available to modify: clienta clientb Enter the client processor's hostname: clienta c. Verify the client processor's hardware Ethernet address. Press to choose the address assigned ([default address]) when the client was added to the RIS environment. Enter the client processor's hardware Ethernet address, for example, 08-00-2b-02-67-e1 [08-00-2b-14-ac-d1]: d. Choose the products you want this client to have access to. You are shown the client's currently selected RIS environment and the products the selected client already has access to. At the prompt, enter the products you would like this client to be able to install including DEC VTX. Separate each choice with a space. Installation Procedure for the ULTRIX Client 7-11 The existing environment is /usr/var/adm/ris/ris0.mips. The client currently can install the following products from /usr/var/adm/ris/ris0.mips: 'ULTRIX V4.1/ULTRIX WS V4.1 MANDATORY SUPPORTED (RISC) ' Select one or more products for the client to install from /usr/var/adm/ris/ris0.mips: Product Description 1 'ULTRIX V4.1/ULTRIX WS V4.1 MANDATORY SUPPORTED (RISC) ' 2 'DEC VTX ' Enter one or more choices, for example, 1 2: 1 2 e. If the list of products available to this client is correct, type y. If the list is not correct, type n to return to step d and re-enter the products. You chose the following products: 1 'ULTRIX V4.1/ULTRIX WS V4.1 MANDATORY SUPPORTED (RISC) ' 2 '??product name?? ' Is that correct (y/n)? [y]: y f. After you modify the client's records with the new list of installable products available, the following confirmation message appears: clienta has been modified. 7.3 ULTRIX Client Initialization File Each language has a specific initialization file. In particular, if you want to modify the vtx.ini file you need to edit the specific one in the specific directory. For the ULTRIX client, the language specific files are stored in a specific subdirectory of /usr/lib/vtx. These are shown in Table 7-1. 7-12 Installation Procedure for the ULTRIX Client Table_7-1_ULTRIX_Language_Directories_____________________ Dutch /usr/lib/vtx/nl_NL English /usr/lib/vtx/en_US French /usr/lib/vtx/fr_FR German /usr/lib/vtx/de_DE Italian /usr/lib/vtx/it_IT Spanish /usr/lib/vtx/es_ES Swedish_____/usr/lib/vtx/sv_SE____________________________ Installation Procedure for the ULTRIX Client 7-13 A ________________________________________________________________ Sample Installation on an OpenVMS VAX System This appendix contains a sample installation of DEC VTX. This sample was run on a VAX system that had no previous version of DEC VTX installed. The sample installation assumes that DECnet has been shut down, that no users are logged on to your system, and that OPTIONS N is specified to print the release notes. The Installation Verification Procedure (IVP) runs at the end of the installation. $ @sys$update:vmsinstal vtx062 mua0: OpenVMS VAX Software Product Installation Procedure V6.1 It is 25-APR-1995 at 09:01. Enter a question mark (?) at any time for help. %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account. %VMSINSTAL-W-ACTIVE, The following processes are still active: EGREY MANNION_A DUKE * Do you want to continue anyway [NO]? y * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: VTX V6.2 Beginning installation of VTX V6.2 at 09:01 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Sample Installation on an OpenVMS VAX System A-1 *************************************************************** * * * DEC VTX Text Retrieval System * * Version V6.2 * * * * * * Installation Procedure * * * * Copyright 1995, Digital Equipment Corporation * * * *************************************************************** You will now be asked to select the VTX options that you want to install. If you are not sure about what a question means, please type a ? (question-mark) at the prompt. This will cause a more detailed description to be displayed. At the end of the questions you have the option of confirming your selection or going back to this procedure's main menu. **************************************************************** You have the option of installing the VTX subscriber environment. This option permits VTX Users to access a VTX infobase. * Would you like to install the VTX subscriber environment [YES]? This version of VTX provides a new character-cell client. As this new client can only be used with DEC ANSI terminals, we also provide the old (V4.1) client for compatibility. * Would you like to install the Old VTXPAD subscriber environment [NO]? You have the option of installing the Information Provider tools part of VTX. They are required in order to update a VTX infobase. This option requires the VTX Subscriber Environment. * Would you like to install the VTX Information Provider tools [YES]? A few file formats for information provider tools changed between VTX V3.x and V4.0. However, nothing has changed in these file formats between V4.0 and this kit. If you plan to convert VTX files from a VTX V3.x system then this option is of value to you, otherwise not. A-2 Sample Installation on an OpenVMS VAX System * Would you like to install VTX V3.x IP Conversion tools [NO]? You have the option of installing the files needed to run any of the VTX servers on this system. * Would you like to install the VTX Servers [YES]? You have the option of installing the VTX tools required to create and run VTX Back End Applications. * Would you like to install the VTX Back End environment [YES]? The VTX Subscriber interface can be customized somewhat by changing the source code. Please refer to your VTX Warranty Exclusion for details on what can be changed without violating your standard VTX support contract. You need access to a BLISS32 compiler in order to compile the changes. * Would you like to install the TCP source code [NO]? This VTX installation can provide on-line reference kits for the MS-DOS client. Once on the VMS system, this client can then be copied to the user's local system and installed over there. * Would you like to install the ULTRIX and MS-DOS Client Reference kit [NO]? y * Where do you want the reference kits directory [SYS$COMMON:[VTX$LIBRARY.REFKIT]]: * Do you want to purge files replaced by this installation [YES]? * Do you want files made obsolete by this installation deleted [YES]? This kit contains an Installation Verification Procedure to verify the correct installation of DEC VTX. * Do you want to run the IVP after the installation [YES]? * Are you satisfied with all your answers for this installation [YES]? %VTX-I-ENDCONV, end of questions in conversational part All questions regarding the installation of DEC VTX have now been asked. System Manager: Depending on your configuration, current system activity and options you selected during this installation, it will continue from 20 minutes to 4 hours and 20 minutes. Sample Installation on an OpenVMS VAX System A-3 It takes 4 hours and 20 minutes to install the complete VTX kit, including the optional TCP sources followed by running the IVP, on a VAXstation 2000. It takes approximately 20 minutes to install the complete kit on a VAX 8800. %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-RESTORE, Restoring product save set D ... %VMSINSTAL-I-RESTORE, Restoring product save set F ... %VMSINSTAL-I-RESTORE, Restoring product save set H ... %VTX-I-DELOBS, deleting obsolete files .. %VTX-I-BUILD, building core files %VTX-I-LINK, linking VTX$MSGSHR .. %VTX-I-LINK, linking VTX$DSLSHR .. %VTX-I-LINK, linking VTXCTL .. %VTX-I-LINK, linking RUSLSHR .. %VTX-I-BUILD, building files for IVP %VTX-I-LINK, linking VTXCON (with 3270 Data Stream support) .. %VTX-I-LINK, linking VTX$CLIENT_MOTIF .. %VTX-I-LINK, linking VTX$CLIENT_CC (new client) (with CDA support) .... %VTX-I-BUILD, building IP tools %VTX-I-LINK, linking VTXAPMS .. %VTX-I-LINK, linking VTXWPSSMB .. %VTX-I-LINK, linking VTX$PAGER .. %VTX-I-LINK, linking VTX$WBCLU .. %VTX-I-LINK, linking VTX$WBGI .. %VTX-I-LINK, linking VTXUPD .. %VTX-I-LINK, linking VTXIVU .. %VTX-I-BUILD, building servers %VTX-I-LINK, linking VTXSRV .. %VTX-I-LINK, linking VTXUPDSRV .. %VTX-I-LINK, linking VTX$WBSRV .. %VTX-I-LINK, linking VTXACU .. %VTX-I-BUILD, building backend environment %VTX-I-LINK, linking ELKSHR .. %VTX-I-LINK, linking VASMSGSHR .. %VTX-I-LINK, linking VAS .. %VTX-I-LINK, linking VASSNA .. %VTX-I-BUILD, building CBR environment %VMSINSTAL-I-ACCOUNT, This installation adds an identifier named VTX$CBR_PROFILES. %UAF-E-RDBADDERRU, unable to add VTX$CBR_PROFILES value [000000,000000]to right s database A-4 Sample Installation on an OpenVMS VAX System -SYSTEM-F-DUPLNAM, duplicate name ***** It looks like as if you already have this identifier defined in your rights database from a previous VTX installation. Please, ignore the errors above. The installation now continues .. ***** %VTX-I-LINK, linking VTX$ISCBR .. %VTX-I-LINK, linking VTX$CBR_SLAVE .. %VTX-I-LINK, linking VTX$CBR_VTY_SHR .. %VTX-I-LINK, linking VTX$CBR_SHR .. It appears as if you have previously installed VTX/TR on this machine. The installation will therefore leave your list of active indexes intact. System Manager: The installation will shortly move the VTX files to their target directories. Once done, please consider performing the following steps to complete the installation: a. Verify that the line "@SYS$STARTUP:VTX$STARTUP.COM" is part of your SYS$STARTUP:SYSTARTUP_V5.COM. b. Replace SYS$SHARE:DCLTABLES.EXE using the following commands: $ INSTALL :== $INSTALL/COMMAND $ INSTALL REPLACE SYS$SHARE:DCLTABLES Note: These operations have to be repeated on each node of your VAX cluster. c. If you have ALL-IN-1 users please refer to our release notes for help in completing the VTX/ALL-IN-1 integration. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... VTX will now attempt to rename the multilanguage files. If you see any file access conflict errors we recommend that you re-execute this command procedure (VTX$LIBRARY:VTX$REN_MLV_FILES.COM) Sample Installation on an OpenVMS VAX System A-5 %VTX-I-INIEXS, VTX.INI already exists in SYS$COMMON:[VTX$LIBRARY.EN_US] -VTX-I-NEWPAS, kit version provided as VTX_EN_US.INI -VTX-I-MERGINI, please merge these at your convenience VTX will now attempt to secure files in the SYS$COMMON:[VTX$LIBRARY] directory tree. If you see any file access conflict errors below they come because there are users accessing VTX right now. If that is the case we recommend that you re-execute this command procedure (VTX$LIBRARY:VTX$SECURE_FILES.COM) at a later date (but soon) to be sure that your VTX environment is secure. Securing VTX$COMMON:[VTX$LIBRARY.CBR.BIN.ENGLISH]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY.CBR.BIN.STEMMER]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY.CBR.BIN]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY.CBR.BIN]*.DIR;* .. Securing VTX$COMMON:[VTX$LIBRARY.CBR.PROFILES]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY.CBR]PROFILES.DIR .. Securing VTX$COMMON:[VTX$LIBRARY.CBR]CONCEPTS.DIR .. Securing VTX$COMMON:[VTX$LIBRARY.CBR]BIN.DIR .. Securing VTX$COMMON:[VTX$LIBRARY]LAUNCH.DIR .. Securing VTX$COMMON:[VTX$LIBRARY.LAUNCH]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY.EXAMPLES]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY.REFKIT.MSDOS]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY.REFKIT]MSDOS.DIR .. Securing VTX$COMMON:[VTX$LIBRARY]EN_US.DIR .. Securing VTX$COMMON:[VTX$LIBRARY.EN_US]*.*;* .. %SET-E-READERR, error reading SYS$COMMON:[VTX$LIBRARY.EN_US]VTX$CLIENT_MOTIF.UID ;9 -SYSTEM-W-ACCONFLICT, file access conflict %SET-E-READERR, error reading SYS$COMMON:[VTX$LIBRARY.EN_US]VTX$CLIENT_MOTIF.UID ;8 -SYSTEM-W-ACCONFLICT, file access conflict %SET-E-READERR, error reading SYS$COMMON:[VTX$LIBRARY.EN_US]VTX.INI;1 -SYSTEM-W-ACCONFLICT, file access conflict Securing VTX$COMMON:[VTX$LIBRARY]ES_ES.DIR .. Securing VTX$COMMON:[VTX$LIBRARY.ES_ES]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY]FR_FR.DIR .. Securing VTX$COMMON:[VTX$LIBRARY.FR_FR]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY]IT_IT.DIR .. Securing VTX$COMMON:[VTX$LIBRARY.IT_IT]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY]NL_NL.DIR .. Securing VTX$COMMON:[VTX$LIBRARY.NL_NL]*.*;* .. A-6 Sample Installation on an OpenVMS VAX System Securing VTX$COMMON:[VTX$LIBRARY]SV_SE.DIR .. Securing VTX$COMMON:[VTX$LIBRARY.SV_SE]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY]DE_DE.DIR .. Securing VTX$COMMON:[VTX$LIBRARY.DE_DE]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY]*.*;* .. Securing VTX$COMMON:[000000]VTX$LIBRARY.DIR .. * * * * * * * * * * * * * * * * * * * * * * * * * * * * DEC VTX Installation Verification Procedure Copyright 1995, Digital Equipment Corporation * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This part of the IVP leaves the following files in your SYS$LOGIN: VTX$IVPVTD.VTD VTX$IVPWORKBENCH.VTD You may want to delete these files after the IVP has completed. * * * * * * * * * * * * * * * * * * * * * * * * * * * * %VTXIVP-I-UPD, running VTXUPD to create IVP infobase DEC VTX Infobase Update Utility, V6.2 %VTX-I-RNGMSG1, Your current range is 0 to 9~~~~~~~~~~~~~ %VTX-I-RNGMSG2, The range for page file SYS$LOGIN:VTX$IVPVTD is 0 to 9~~~~~~~~~~ ~~~ Total of 4 pages added %VTX-I-RNGMSG1, Your current range is 0 to 9~~~~~~~~~~~~~ %VTX-I-RNGMSG2, The range for page file SYS$LOGIN:VTX$IVPWORKBENCH is 0 to 9~~~~ ~~~~~~~~~ %VTX-I-PAGFILCLS, Page file SYS$LOGIN:VTX$IVPWORKBENCH closed %VTX-I-PAGFILCLS, Page file SYS$LOGIN:VTX$IVPVTD closed * * * * * * * * * * * * * * * * * * * * * * * * * * * * This part of the IVP leaves the following files in your SYS$LOGIN: VTXBASE.TXT VTXACF.VTA VTXSERVER.COM VTX$WBSRV.COM VTXSRV_IVP.VTE Sample Installation on an OpenVMS VAX System A-7 You may want to delete these files after the IVP has completed. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *" This part of the IVP uses DECnet objects 43 and 59. If these objects are currently being used on this system, this IVP may signal success even though not all components have been tested. If extraneous errors occur while executing this procedure, stop all existing VTX, Workbench, and Update servers, as well as VAS runtime images and execute this procedure again. Refer to the VAX VTX Installation Guide for further details on the Installation Verification Procedure. * * * * * * * * * * * * * * * * * * * * * * * * * * * * %VTXIVP-I-SRV, stopping old VTX IVP server -- ignore errors DEC VTX Control Program, V6.2 ...Working... %VTXIVP-I-SRV, starting a VTX infobase server DEC VTX Control Program, V6.2 ...Working... %VTXIVP-I-WORKBENCH, starting a VTX Workbench server Ignore any ERROPNLIB and INVLIBFIL messages They simply mean that old library files exist for this account, and are normal. DEC VTX Control Program, V6.2 ...Working... DEC VTX Control Program, V6.2 ...Working... * * * * * * * * * * * * * * * * * * * * * * * * * * * * This part of the IVP leaves the following files in your SYS$LOGIN: A-8 Sample Installation on an OpenVMS VAX System VTX$IVPTDS.TDS VAS.COM VTX$IVPTDS.TDI VASIVP.ASL VTX$IVPTDS.LIS VASIVP.ASE You may want to delete these files after the IVP has completed. * * * * * * * * * * * * * * * * * * * * * * * * * * * * %VTXIVP-I-VAS, stopping old VAS server -- ignore errors DEC VTX Control Program, V6.2 ...Working... %VTXIVP-I-VAS, starting a VAS server DEC VTX Control Program, V6.2 ...Working... Known VAS status as of 25-APR-1995 09:26:46.29 VAS started: 25-APR-1995 09:26:43.58 Communication ENABLED DECNET object number: 59 Oper notification DISABLED Logging for log channel VAS$LOG_CHANNEL written to log file CISD$:[VTXEI]VASIVP.ASL;6 Transactions loaded from: CISD$:[VTXEI]VTX$IVPTDI.TDI;4 No CURs loaded VTX form pages displayed to date: 0 Total number of requests made: 0 ---------------------------------------------------- Sessions Current active: 0 Current stopping: 0 Total connects: 0 ---------------------------------------------------- * * * * * S U C C E S S * * * * * DEC VTX IVP completed successfully * * * * * S U C C E S S * * * * * Installation of VTX V6.2 completed at 09:26 VMSINSTAL procedure done at 09:26 Sample Installation on an OpenVMS VAX System A-9 B ________________________________________________________________ Sample Installation on an OpenVMS AXP System This appendix contains a sample installation of DEC VTX. This sample was run on an Alpha AXP system that had no previous version of DEC VTX installed. The sample installation assumes that DECnet has been shut down, that no users are logged on to your system, and that OPTIONS N is specified to print the release notes. The Installation Verification Procedure (IVP) runs at the end of the installation. $ @sys$update:vmsinstal OpenVMS AXP Software Product Installation Procedure V6.1 It is 25-APR-1995 at 22:34. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: BATCH_5 BATCH_6 BATCH_8 BATCH_20 ADOERFER _TNA19: _TNA20: BATCH_18 * Do you want to continue anyway [NO]? y * Are you satisfied with the backup of your system disk [YES]? * Where will the distribution volumes be mounted: user1$:[adoerfer.vtxa062] Enter the products to be processed from the first distribution volume set. * Products: vtxa062 * Enter installation options you wish to use (none): The following products will be processed: VTXA V6.2 Sample Installation on an OpenVMS AXP System B-1 Beginning installation of VTXA T6.2 at 22:34 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. *************************************************************** * * * Digital VTX for OpenVMS Alpha * * Version V6.2 * * * * 21-APR-1995 * * * * Installation Procedure * * * * Copyright 1995, Digital Equipment Corporation * * * *************************************************************** You will now be asked to select the VTX options that you want to install. Type a ? (question mark) at any prompt for more information. At the end of the questions you have the option of confirming your selection or going back to this procedure's main menu. **************************************************************** You have the option of installing the VTX subscriber environment. This option permits VTX Users to access a VTX infobase. * Would you like to install the VTX subscriber environment [YES]? This version of VTX provides a new character-cell client. As this new client can only be used with DEC ANSI terminals, we also provide the old (V4.1) client for compatibility. * Would you like to install the Old VTXPAD subscriber environment [NO]? yes The V4.1 version did add a new keypad. That keypad is a superset of the traditional VTX default keypad and the ALL-IN-1 keypad, except where there were conflicting mappings. You have the option of making the COMMON keypad the default keypad, instead of the one that was default in previous versions of VTX. B-2 Sample Installation on an OpenVMS AXP System * Would you like to install the COMMON keypad [NO]? You have the option of installing the Information Provider tools part of VTX. They are required in order to update a VTX infobase. This option requires and will select the VTX Subscriber Environment. * Would you like to install the VTX Information Provider tools [YES]? You have the option of installing the files needed to run any of the VTX servers on this system. * Would you like to install the VTX Servers [YES]? You have the option of installing the VTX tools required to create and run VTX Back End Applications. * Would you like to install the VTX Back End environment [YES]? * Do you want to purge files replaced by this installation [YES]? * Do you want files made obsolete by this installation deleted [YES]? This kit contains an Installation Verification Procedure to verify the correct installation of Digital VTX for OpenVMS Alpha. * Do you want to run the IVP after the installation [YES]? * Are you satisfied with all your answers for this installation [YES]? %VTXA-I-ENDCONV, end of questions in conversational part All questions regarding the installation of Digital VTX for OpenVMS Alpha have now been asked. System Manager: Depending on your configuration, current system activity and options you selected during this installation, it will continue from 2 to 6 minutes. Sample Installation on an OpenVMS AXP System B-3 %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-RESTORE, Restoring product save set D ... %VMSINSTAL-I-RESTORE, Restoring product save set H ... %VMSINSTAL-I-SYSDIR, This product creates system directory [VTX$LIBRARY.EN_US]. %VMSINSTAL-I-SYSDIR, This product creates system directory [VTX$LIBRARY.LAUNCH]. %VMSINSTAL-I-SYSDIR, This product creates system directory [VTX$LIBRARY.FR_FR]. %VMSINSTAL-I-SYSDIR, This product creates system directory [VTX$LIBRARY.DE_DE]. %VMSINSTAL-I-SYSDIR, This product creates system directory [VTX$LIBRARY.IT_IT]. %VMSINSTAL-I-SYSDIR, This product creates system directory [VTX$LIBRARY.ES_ES]. %VMSINSTAL-I-SYSDIR, This product creates system directory [VTX$LIBRARY.SV_SE]. %VMSINSTAL-I-SYSDIR, This product creates system directory [VTX$LIBRARY.NL_NL]. %VMSINSTAL-I-SYSDIR, This product creates system directory [VTX$LIBRARY.EXAMPLES]. %VMSINSTAL-I-ACCOUNT, This installation adds an identifier named VTX$CBR_PROFILES. %UAF-E-RDBADDERRU, unable to add VTX$CBR_PROFILES value [000000,000000] to rights database -SYSTEM-F-DUPLNAM, duplicate name ***** It looks like as if you already have this identifier defined in your rights database from a previous VTX installation. Please, ignore the errors above. The installation now continues .. ***** %VMSINSTAL-I-SYSDIR, This product creates system directory [VTX$LIBRARY.CBR]. %VMSINSTAL-I-SYSDIR, This product creates system directory [VTX$LIBRARY.CBR.PROFILES]. %VMSINSTAL-I-SYSDIR, This product creates system directory [VTX$LIBRARY.CBR.CONCEPTS]. %VMSINSTAL-I-SYSDIR, This product creates system directory [VTX$LIBRARY.CBR.BIN]. %VMSINSTAL-I-SYSDIR, This product creates system directory [VTX$LIBRARY.CBR.BIN.STEMMER]. %VMSINSTAL-I-SYSDIR, This product creates system directory [VTX$LIBRARY.CBR.BIN.ENGLISH]. System Manager: The installation will shortly move the VTX files to their target directories. Once done, please consider performing the following steps to complete the installation: a. Add the line "@SYS$STARTUP:VTX$STARTUP.COM" to your system startup. b. Replace SYS$SHARE:DCLTABLES.EXE using the following commands: $ INSTALL :== $INSTALL/COMMAND $ INSTALL REPLACE SYS$SHARE:DCLTABLES B-4 Sample Installation on an OpenVMS AXP System Note: These operations have to be repeated on each node of your cluster. c. If you have ALL-IN-1 users please refer to our release notes for help in completing the VTX/ALL-IN-1 integration. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... VTX will now attempt to rename the multilanguage files. If you see any file access conflict errors we recommend that you re-execute this command procedure (VTX$LIBRARY:VTX$REN_MLV_FILES.COM) VTX will now attempt to secure files in the SYS$COMMON:[VTX$LIBRARY] directory tree. If you see any file access conflict errors below they come because there are users accessing VTX right now. If that is the case we recommend that you re-execute this command procedure (VTX$LIBRARY:VTX$SECURE_FILES.COM) at a later date (but soon) to be sure that your VTX environment is secure. Securing VTX$COMMON:[VTX$LIBRARY.CBR.BIN.ENGLISH]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY.CBR.BIN.STEMMER]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY.CBR.BIN]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY.CBR.BIN]*.DIR;* .. Securing VTX$COMMON:[VTX$LIBRARY.CBR.PROFILES]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY.CBR]PROFILES.DIR .. Securing VTX$COMMON:[VTX$LIBRARY.CBR]CONCEPTS.DIR .. Securing VTX$COMMON:[VTX$LIBRARY.CBR]BIN.DIR .. Securing VTX$COMMON:[VTX$LIBRARY]LAUNCH.DIR .. Securing VTX$COMMON:[VTX$LIBRARY.LAUNCH]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY.EXAMPLES]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY]EN_US.DIR .. Securing VTX$COMMON:[VTX$LIBRARY.EN_US]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY]ES_ES.DIR .. Securing VTX$COMMON:[VTX$LIBRARY.ES_ES]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY]FR_FR.DIR .. Securing VTX$COMMON:[VTX$LIBRARY.FR_FR]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY]IT_IT.DIR .. Securing VTX$COMMON:[VTX$LIBRARY.IT_IT]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY]NL_NL.DIR .. Securing VTX$COMMON:[VTX$LIBRARY.NL_NL]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY]SV_SE.DIR .. Securing VTX$COMMON:[VTX$LIBRARY.SV_SE]*.*;* .. Sample Installation on an OpenVMS AXP System B-5 Securing VTX$COMMON:[VTX$LIBRARY]DE_DE.DIR .. Securing VTX$COMMON:[VTX$LIBRARY.DE_DE]*.*;* .. Securing VTX$COMMON:[VTX$LIBRARY]*.*;* .. Securing VTX$COMMON:[000000]VTX$LIBRARY.DIR .. * * * * * * * * * * * * * * * * * * * * * * * * * * * * Digital VTX for OpenVMS Alpha Installation Verification Procedure Copyright 1995, Digital Equipment Corporation * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This part of the IVP leaves the following files in your SYS$LOGIN: VTX$IVPVTD.VTD VTX$IVPWORKBENCH.VTD You may want to delete these files after the IVP has completed. * * * * * * * * * * * * * * * * * * * * * * * * * * * * %VTXIVP-I-UPD, running VTXUPD to create IVP infobase DEC VTX Infobase Update Utility, V6.2 %VTX-I-RNGMSG1, Your current range is 0 to 9~~~~~~~~~~~~~ %VTX-I-RNGMSG2, The range for page file SYS$LOGIN:VTX$IVPVTD is 0 to 9~~~~~~~~~~~~~ Total of 4 pages added %VTX-I-RNGMSG1, Your current range is 0 to 9~~~~~~~~~~~~~ %VTX-I-RNGMSG2, The range for page file SYS$LOGIN:VTX$IVPWORKBENCH is 0 to 9~~~~~~~~~~~~~ %VTX-I-PAGFILCLS, Page file SYS$LOGIN:VTX$IVPWORKBENCH closed %VTX-I-PAGFILCLS, Page file SYS$LOGIN:VTX$IVPVTD closed * * * * * * * * * * * * * * * * * * * * * * * * * * * * This part of the IVP leaves the following files in your SYS$LOGIN: VTXBASE.TXT VTXACF.VTA VTXSERVER.COM VTX$WBSRV.COM VTXSRV_IVP.VTE You may want to delete these files after the IVP has completed. B-6 Sample Installation on an OpenVMS AXP System * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *" This part of the IVP uses DECnet objects 43 and 59. If these objects are currently being used on this system, this IVP may signal success even though not all components have been tested. If extraneous errors occur while executing this procedure, stop all existing VTX, Workbench, and Update servers, as well as VAS runtime images and execute this procedure again. Refer to the VTX Installation Guide for further details on the Installation Verification Procedure. * * * * * * * * * * * * * * * * * * * * * * * * * * * * %VTXIVP-I-SRV, stopping old VTX IVP server -- ignore errors DEC VTX Control Program, V6.2 %VTX-W-SRVNOTRESP, server not responding or not running %VTXIVP-I-SRV, starting a VTX infobase server DEC VTX Control Program, V6.2 ...Working... %VTXIVP-I-WORKBENCH, starting a VTX Workbench server Ignore any ERROPNLIB and INVLIBFIL messages They simply mean that old library files exist for this account, and are normal. ...Working... %VTX-I-LIBCREATED, new Workbench library created DEC VTX Control Program, V6.2 ...Working... * * * * * * * * * * * * * * * * * * * * * * * * * * * * This part of the IVP leaves the following files in your SYS$LOGIN: VTX$IVPTDS.TDS VAS.COM VTX$IVPTDS.TDI VASIVP.ASL VTX$IVPTDS.LIS VASIVP.ASE Sample Installation on an OpenVMS AXP System B-7 You may want to delete these files after the IVP has completed. * * * * * * * * * * * * * * * * * * * * * * * * * * * * %VTXIVP-I-VAS, stopping old VAS server -- ignore errors DEC VTX Control Program, V6.2 %VAS-E-CTL_VAS_FAIL, VAS process not running %VTXIVP-I-VAS, starting a VAS server DEC VTX Control Program, V6.2 ...Working... Known VAS status as of 25-APR-1995 22:40:56.92 VAS started: 25-APR-1995 22:40:53.22 Communication ENABLED DECNET object number: 59 Oper notification DISABLED Logging for log channel VAS$LOG_CHANNEL written to log file SYS$SYSROOT:[SYSMGR]VASIVP.ASL;1 Transactions loaded from: SYS$SYSROOT:[SYSMGR]VTX$IVPTDI.TDI;1 No CURs loaded VTX form pages displayed to date: 0 Total number of requests made: 0 ---------------------------------------------------- Sessions Current active: 0 Current stopping: 0 Total connects: 0 ---------------------------------------------------- * * * * * S U C C E S S * * * * * Digital VTX for OpenVMS Alpha IVP completed successfully * * * * * S U C C E S S * * * * * Installation of VTXA T6.2 completed at 22:40 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]VTXA062.VMI_DATA Enter the products to be processed from the next distribution volume set. * Products: VMSINSTAL procedure done at 22:41 B-8 Sample Installation on an OpenVMS AXP System C ________________________________________________________________ Sample Installation on an ULTRIX System This appendix shows a sample installation of DEC VTX on an ULTRIX system. This sample was run on a system that had no previous version of DEC VTX installed. /kits > su Password: # setld -l `pwd` *** Enter Subset Selections *** The subsets listed below are optional: 1) DEC VTX base files for ULTRIX 2) DEC VTX character cell client 3) DEC VTX OSF/Motif client 4) DEC VTX man pages for ULTRIX 5) All of the Above 6) None of the Above 7) Exit without installing subsets Enter your choice(s): 5 You are installing the following subsets: DEC VTX base files for ULTRI DEC VTX character cell clien DEC VTX OSF/Motif client for DEC VTX man pages for ULTRIX Is this correct? (y/n): y Copying DEC VTX base files for ULTRIX (VTXBASE620) from disk Verifying DEC VTX base files for ULTRIX (VTXBASE620) Copying DEC VTX character cell client for ULTRIX (VTXCC620) from disk Working....Mon Jul 11 13:23:32 GMT 1995 Verifying DEC VTX character cell client for ULTRIX (VTXCC620) Copying DEC VTX OSF/Motif client for ULTRIX (VTXMOTIF620) from disk Working....Mon 11 Jul 13:24:19 GMT 1995 Verifying DEC VTX OSF/Motif client for ULTRIX (VTXMOTIF620) Working....Mon 11 Jul 13:26:10 GMT 1995 Sample Installation on an ULTRIX System C-1 Copying DEC VTX man pages for ULTRIX (VTXMAN620) from disk Verifying DEC VTX man pages for ULTRIX (VTXMAN620) C-2 Sample Installation on an ULTRIX System ________________________________________________________________ Index A Client initialization file ___________________________ (cont'd) AUTOGEN Line Editing function, changing system parameter 4-5 values, 1-8 List Menu Item Select Automatic startup procedure function, 4-7 , 3-2 Main function, 4-6 Menu Bar activator, 4-7 B__________________________ Next Choice function, 4-6 Base reference pages, 6-5 Next Form Feed function, Bill of Materials, 1-1 4-7 BOM Next Page function, 4-5 for OpenVMS Systems, 1-1 Previous Choice function, 4-6 C__________________________ Previous Form Feed Changing system parameter function, 4-7 values Previous Page function, AUTOGEN, 1-8 4-5 SYSGEN, 1-9 Reveal function, 4-7 Checking system parameters, Set Mark function, 4-6 1-7 Set Personal Magazine Client initialization file function, 4-7 Backup functions, 4-5 CTL pages Exit function, 4-6 See Also SHOW PROCESS Find function, 4-7 /MEMORY for ALL-IN-1 users, 4-8 system parameters, 1-6 Form Enter function, 4-7 CTLPAGES, 1-6 Get Again function, 4-6 Get Personal Magazine function, 4-7 Goto Mark function, 4-6 Help functions, 4-5 Index-1 Installation on OpenVMS D__________________________ (cont'd) Device name defining system logicals, for OpenVMS system, 2-3 3-7 Disk space determine free disk space for OpenVMS installation, , 1-10 1-9 disk space requirements, for ULTRIX client, 6-1 1-9 error recovery, 2-15 F__________________________ GBLPAGES, 1-6 Free disk space, 1-10 GBLSECTIONS, 1-6, 1-7 for ULTRIX clients, 6-7 getting help, 2-1 getting online release G notes, 2-1 ___________________________ information provider GBLPAGES, 1-6 tools, 2-9 GBLSECTIONS, 1-6 installation questions, pre-installation, 1-7 2-4 I installing the VTX ___________________________ servers, 2-9 .INI files, 4-8 installing ULTRIX and Installation MS-DOS clients, 2-11 for PC, 5-1 optional software, 1-3 ULTRIX client, 6-1 post installation tasks, Installation on OpenVMS 3-1 aborting the installation privileges, 1-4 , 2-3 process account quotas, automatic startup 1-4 procedure, 3-2 purging files, 2-11 back-end applications, running the IVP, 2-12 2-10 sample installation, 2-1 backups, 2-5 selecting the DEC VTX changing system parameter components, 2-7 values, 1-8 setting dynamic system checking system parameter values, 1-9 parameters, 1-7 software license, 1-2 cluster considerations, software requirements, 3-5 1-3 COMMON keypad, 2-8 subscriber account quotas configuring print tables, , 3-5 3-2 support options, 1-2 CTL pages, 1-6 system classes, 1-2 DCLTABLES, 3-5 system parameters, 1-5 DECnet, 3-7 TCP source code, 2-10 Index-2 Installation on OpenVMS (cont'd) O__________________________ time required for Online release notes, 1-1 installation, 2-1 OpenVMS AXP sample virtual page count, 1-6 installation, B-1 VMSINSTAL, 2-3 OpenVMS requirements, 1-2 VTX operator account, 3-8 OpenVMS VAX sample VTX subscriber installation, A-1 environment, 2-7 Installation on PC P__________________________ access to OpenVMS systems PC client , 5-1 Building the kit on verify operating systems, diskette, 5-3 5-1 Prerequisite software Installation procedure in IBM environment, 1-3 for PC, 5-2 OpenVMS requirements, 1-3 for ULTRIX client, 7-1 Print queue for VMS systems, 2-3 for OpenVMS systems, 3-1 Installation requirements Privileges for ULTRIX clients, 6-1 VMSINSTAL requirements, Installing the PC client, 1-4 5-1 Process account quotas, Installing the ULTRIX 1-4 client using AUTHORIZE, 1-4 disk space, 6-1 L R__________________________ ___________________________ Release notes, 1-1, 2-4 LMF for ULTRIX client, 6-2 for OpenVMS, 1-2 RIS for ULTRIX client M installation, 6-2 ___________________________ MS-DOS VTX client S__________________________ DECnet node, 5-1 Sample installation define OpenVMS node, 5-1 OpenVMS AXP, B-1 disk space requirements, OpenVMS VAX, A-1 5-1 ULTRIX, C-1 installation from OpenVMS Saveset name , 5-2 for OpenVMS system, 2-3 Software license, 1-2 Software requirements for ULTRIX clients, 6-4 Index-3 Starting VTX PC clients ULTRIX client (cont'd) DECnet DOS client, 5-3 privileges, 6-4 Subscriber account release notes, 6-2 privileges software requirements, for OpenVMS systems, 3-5 6-4 Subscriber account quotas stopping the installation for OpenVMS systems, 3-5 , 6-7 SYSGEN tar files, 7-2 setting dynamic system using RIS for parameter values, 1-9 installation, 6-2 System parameters, 1-5 changing system parameter V values, 1-8 ___________________________ checking system VIRTUALPAGECNT, 1-6 parameters, 1-7 VMSINSTAL CTL pages, 1-6 account quotas, 1-5 CTL pages free space, 1-6 changing account quotas, GBLPAGES, 1-6 1-5 GBLSECTIONS, 1-6, 1-7 VTX$STARTUP.COM, 3-1 process account quotas, 1-4 setting dynamic system parameter values, 1-9 virtual page count, 1-6 System startup for OpenVMS systems, 3-1 U__________________________ ULTRIX client backing up your system disk, 6-7 installation, 6-1 installation error recovery, 6-8 installation in RIS server area, 6-2 installation into a DMS server area, 6-3 installation procedure, 7-1 installation requirements , 6-4 installing locally, 7-1 Index-4