Installation manual

ManualsBrandsVax ManualsHousehold AppliancesV-040

Installing and Upgrading

ENVOXr

r Configuration

Software on DEC VAX and

DEC AXP Systems

This manual applies to ENVOX software version P4.0 only. Retain

and use previous versions of this manual for earlier versions of

ENVOX software.

Installation Manual

PN6.1:SW3151:VMS

Revision B — May 1998

This manual supercedes the issue dated July 1996.

D3P01461202

Summary of content (220 pages)

PAGE 1
Installing and Upgrading ENVOXr r Configuration Software on DEC VAX and DEC AXP Systems This manual applies to ENVOX software version P4.0 only. Retain and use previous versions of this manual for earlier versions of ENVOX software. Installation Manual D3P01461202 PN6.1:SW3151:VMS Revision B — May 1998 This manual supercedes the issue dated July 1996.
PAGE 2
DOCVUE, ENVOX, Fisher-Rosemount, Fisher-Rosemount Systems, Managing The Process Better, PROFLEX, PROVOX, and PROVUE are marks of one of the Fisher-Rosemount group of companies. All other marks are the property of their respective owners. ã 1995, 1996, 1998 Fisher-Rosemount Systems, Inc. All rights reserved.
PAGE 3
Installing and Upgrading ENVOXr Configuration Software on DEC VAX and DEC AXP Systems (Revision B — May 1998) Your Evaluation Please ... Name: Title and Department: Company: Years of Experience: ___ Instrumentation ___ Distributed Control Telephone: ( ) -- iii Education: ____High School ____Years College ____Degree Job Responsibility: Please indicate your evaluation of this manual. Attach extra sheets if needed. 1. How and when do you use this manual? 2.
PAGE 4
Your Evaluation Please ... iv Installing and Upgrading ENVOXr Configuration Software on DEC VAX and DEC AXP Systems (Revision B — May 1998) 5. Describe the amount of usable information in this manual including tables. Please explain. V Too much information — not all required to perform task V Proper amount provided — not too much nor too little V Too little information — needed additional information to perform task V No Opinion Sections 6.
PAGE 5
Installing and Upgrading ENVOXr Configuration Software on DEC VAX and DEC AXP Systems (Revision B — May 1998) Contents v Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENVOXR Software Version This Manual Supports . . . . . . . . . . . New This Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 6
vi Contents 4 4.1 4.2 4.2.1 4.2.2 4.3 4.4 5 5.1 5.1.1 5.1.2 5.1.3 5.1.4 5.1.5 5.2 5.2.1 5.2.2 5.2.3 5.3 5.3.1 5.3.2 5.3.3 5.4 5.5 6 6.1 6.2 7 7.1 7.2 7.3 8 8.1 8.1.1 8.1.2 8.1.3 8.2 8.3 8.4 Installing and Upgrading ENVOXr Configuration Software on DEC VAX and DEC AXP Systems (Revision B — May 1998) Installing ENVOX Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 New System Installation Method . . . . . . . . . . . . . . . . . . . . . . . . . . . Before Installing ENVOX Software .
PAGE 7
Installing and Upgrading ENVOXr Configuration Software on DEC VAX and DEC AXP Systems (Revision B — May 1998) 8.5 9 Contents De-installing ENVOX and SYBASE Software . . . . . . . . . . . . . . . . vii 96 Retrieving Files from the Installation Tape . . . . . . . . . . . . 99 9.1 9.2 Procedure for Retrieving Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Examples of Retrieving Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 101 10 System Tuning . . . . . . .
PAGE 8
viii Installing and Upgrading ENVOXr Configuration Software on DEC VAX and DEC AXP Systems (Revision B — May 1998) Contents 12.11.7 12.11.8 12.11.9 12.11.10 12.11.11 12.11.12 12.11.13 12.11.14 12.11.15 12.11.16 12.11.17 12.11.18 12.11.19 12.11.20 Stopping the Diagnostic Daemon . . . . . . . . . . . . . . . . . . . . . . . . Starting the Devrev Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping the Devrev Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 9
Installing and Upgrading ENVOXr Configuration Software on DEC VAX and DEC AXP Systems (Revision B — May 1998) Contents ix Figures Figure 3-1. Figure 4-1. Figure 5-1. System Installation Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Installation Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENVOX P2.x, P3.0, P3.2, P3.3 and SYBASE Software Upgrade Process for a Client-Server System . . . . . . . . . . Figure 5-2. ENVOX P3.
PAGE 10
x Contents Installing and Upgrading ENVOXr Configuration Software on DEC VAX and DEC AXP Systems (Revision B — May 1998) Tables Table 1-1. Table 2-1. Table 2-2. Table 2-3. Table 2-4. Table 2-5. Table 2-6. Table 2-7. Table 2-8. Table 9-1. Table 10-1. Table 10-2. Table 10-3. Type Style Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Systems and Number of Users . . . . . . . . . . . . . . Software Version Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 11
Introduction F Section 1 1 Figure 1-Table 1 1 1 1 Introduction This installation manual describes the procedures necessary to install or upgrade and to verify proper operation of ENVOXâ configuration software, version P4.0, and SYBASE software on DEC OpenVMS operating systems. The ENVOX software types are: J Type SW3151 ENVOX Configuration Software (ENVOX DEC VAX) J Type SW3155 ENVOX Configuration Software (ENVOX DEC AXP) Note ... ENVOX, Version P4.0, runs on SYBASE SQL Server, Version 10.0.2.6.
PAGE 12
Section 1 F Introduction 2 1.3 1 New This Release ENVOX P4.0 includes several product and document enhancements. The enhancements are listed below and further explained in appropriate ENVOX documents. J J J J J J J J J J J J J J ENVOX P4.0 operates on a SYBASE 10.0.2.6 SQL Server. With this server, installation and upgrade procedures for Client-Server systems use the Portable Database Transfer (PDX) utility to improve the installation and upgrade process.
PAGE 13
Introduction F Section 1 J J Field help has been enhanced for the Console Device Definition Operation Display List Display No. field. CHIP generate performance has been enhanced. J Interactive abort has been added for the Item Delete operation. J J J 1.4 In installation and upgrade logs, the Installation log file now distinguishes more clearly between subsequent attempts.
PAGE 14
Section 1 F Introduction 4 Section 7 — Creating ENVOX User Accounts: provides instructions on how to add extra ENVOX users. Section 8 — Backing Up, Restoring and De-Installing the Software: provides instructions for backing up and restoring the system and de-installing the SYBASE and ENVOX software. 1 Section 9 — Retrieving Files from the Installation Tape: provides instructions on getting the ENVOX and SYBASE directories and files from the installation tape without running the installation again.
PAGE 15
Introduction F Section 1 5 Prompt Style — This manual may present displays and prompt lines differently than they appear on your screen. Enter the commands shown in this manual at the equivalent prompt as shown on your screen. Commands — Commands do not include a notation to enter the command with the Return key. When the manual describes an operating system command, assume that a Return is required to enter the command. Note ...
PAGE 16
Section 1 F Introduction 6 1.6 Cautions and Notes Special attention and Notes forms and symbols are used to attract attention to essential or critical information in a document. The types of information included in each are explained in the following: 1 Caution ... All cautions have this form and symbol. Do not disregard cautions.
PAGE 17
Introduction F Section 1 J J J J J J J 7 User manual, Using ENVOX Configuration Software, UM6.1:SW3151 (Revision J — May 1998): describes how to use ENVOX Configuration Software to configure your PROVOXR system databases. Includes generating, downloading, uploading, trace and tune functions, diagnostic procedures, and documenting. Technical reference, The Technical Reference for ENVOX Configuration Software, TR1.
PAGE 18
Section 1 F Introduction 8 1.8 1 Control Desktop Documentation Type SW331 Control Desktop is the Windows NT interface to ENVOX configuration software. Control Desktop, version P2.0, is compatible with ENVOX, version P4.0. The user documentation available for Control Desktop P2.0 is: J J J 1.9 Installation and User Manual, Getting Started with Control Desktop, UM6.
PAGE 19
Introduction F Section 1 J J 1.10 9 Configuration engineering manual, Configuring DH6200-Series Computer/Highway Interface Package (CHIP) Software (CE8.0:DH6200) User manual, Using DH6200-Series Computer/Highway Interface Package (CHIP) Software (UM3:0:DH6200) Electronic Documentation This manual is also available in DOCVUEt Electronic Documentation, a CD-ROM Documentation set containing current and past Fisher-Rosemount Systems sales literature, manuals, and technical service bulletins.
PAGE 20
10 Section 1 F Introduction 1 Blank page.
PAGE 21
System Requirements F Section 2 11 Figure 2-Table 2 2 2 System Requirements This section describes the system requirements for running Type SW3151 ENVOXr Configuration Software (ENVOX DEC VAX) and Type SW3155 ENVOX Configuration Software (ENVOX DEC AXP) on OpenVMS systems, the time required to install ENVOX configuration software, the software module sizes, and the required disk memory sizes. Procedure overviews with flow diagrams for installing and upgrading a system are included. 2.
PAGE 22
Section 2 F System Requirements 12 2.2 Product Compatibility ENVOX P4.0, Control Desktop P2.0, and CDOS P2.0 are compatible. Earlier versions of these products are not compatible with later versions. For instance, when you upgrade ENVOX software to version P4.0, and you wish to use Control Desktop, you must also upgrade Control Desktop and CDOS to P2.0. 2 2.3 Hardware Requirements ENVOX software will run on a MicroVAX, VAX, VAXstation, DEC AXP workstation or a DEC AXP server, as listed in Table 2-1.
PAGE 23
System Requirements F Section 2 2.4 13 Software Requirements ENVOX software, version P4.0, requires an OpenVMS operating system, DECnet, CHIP software, SYBASE SQL (Data) Server, APT, and Open Client software, and DECwindows Motif software. Table 2-2 lists the required software versions. Table 2-2. Software Version Levels Software Revision OpenVMS 7.1(3) DECwindows Motif(VAX) 1.2--3 DECwindows Motif(AXP) 1.2--4 CHIP DEC OpenVMS VAX (1) P5.0 or later CHIP DEC OpenVMS AXP (1) P5.
PAGE 24
Section 2 F System Requirements 14 2.6 2 Software and Disk Space Requirements for VAX Systems Note ... While it is possible to install all of ENVOX, SYBASE, and the other required software on a single disk, it is recommended for best system performance that the software be installed on two disks, as described below. To install ENVOX software on a DEC VAX system, a minimum of 32 Mbytes of memory is required.
PAGE 25
System Requirements F Section 2 Table 2-4. 15 Fixed System Requirements for CHIP on VAX Systems CHIP Memory CHIP Programs Disk Space 165 Kbytes 2.1 Mbytes 4150 blocks 500 points 235 Kbytes 1.56 Mbytes/ 3100 blocks 2500 points 870 Kbytes 2.5 Mbytes/ 5000 blocks 10,000 points 3341 Kbytes 5 Mbytes/ 10,000 blocks CHIP Database Options: (select one) Note ...
PAGE 26
Section 2 F System Requirements 16 2.8 2 Software and Disk Space Requirements for AXP Systems Note ... While it is possible to install all of ENVOX, SYBASE, and the other required software on a single disk, it is recommended for best system performance that the software be installed on two disks, as described below. To install the ENVOX software on a DEC AXP system, a minimum of 64 Mbytes of memory is required.
PAGE 27
System Requirements F Section 2 17 size (number of blocks) of CHIP to the size of the software required by the ENVOX system to see if your system has enough space. Table 2-7. Fixed System Requirements for CHIP on AXP Systems CHIP Memory CHIP Programs Disk Space 400 Kbytes 11,000 blocks 500 points 985 Kbytes 10,000 blocks 2500 points 2850 Kbytes 18,000 blocks 10,000 points 8100 Kbytes 23,000 blocks CHIP Database Options: (select one) Note ...
PAGE 28
18 Section 2 F System Requirements 2 Blank page.
PAGE 29
Installing SYBASE Software F Section 3 19 Figure 3-Table 3 3 3 Installing SYBASE Software This section explains how to install SYBASE software on a MicroVAX 3100 computer, a VAXstation 3100, a VAXstation 4000 and the AlphaStation 200 series. This section also includes information about recovering from errors. See Appendix A for the meaning of error messages. See Appendix C for log files of a typical installation.
PAGE 30
Section 3 F Installing SYBASE Software 20 Note ... System backup before and after installation is extremely important. Always back up the system in case the system configuration needs to be restored. Store backup tapes in an environmentally and physically protected area. 3 3.2 Before Installing SYBASE Software Several procedures and considerations need to be done before you perform the installation. They are explained in the following subsections. 3.2.
PAGE 31
Installing SYBASE Software F Section 3 3.2.2.1 21 Installing Motif ECO Kit (AXP Platform Only) An ECO kit ALPMOTF03_U4012 for AXP systems must be applied, after installing Motif software and before attempting the SYBASE installation. The following steps let you determine whether or not the ECO kit has been installed and, if it has not, include instructions on how to install it.
PAGE 32
22 Section 3 F Installing SYBASE Software 3.2.2.2 Installing Year 2000 ECO Kits (VAX and AXP Platforms) An ECO kit VAXY2K01_071 for VAX systems and an ECO kit ALPY2K01_071 for AXP systems must be applied, after installing Motif software and before attempting the SYBASE installation. The following steps let you determine whether or not the ECO kit has been installed and, if it has not, include instructions on how to install it.
PAGE 33
Installing SYBASE Software F Section 3 3.2.2.3 23 Installing SCSI ECO Kit (AXP Platform Only) An ECO kit ALPSCSI02_071 for AXP systems must be applied, after installing Motif software and before attempting the SYBASE installation. The following steps let you determine whether or not the ECO kit has been installed and, if it has not, include instructions on how to install it.
PAGE 34
24 Section 3 F Installing SYBASE Software 3.2.2.4 Recovering SCSI ECO Kit From the Control Desktop CDROM Recovering the SCSI ECO kit from the Control Desktop CDROM requires copying the kit to a directory on your PC hard drive, and then transferring the kit to your AXP workstation over your network using file transfer protocol (FTP). 3 You may recover the kit before or after Control Desktop installation, but do not recover the kit during Control Desktop installation.
PAGE 35
Installing SYBASE Software F Section 3 Step 5: 25 Login in as SYSTEM and enter your password. When the system prompt appears, enter: > binary sets file mode to binary > mkdir [directory_name]creates a directory on your AXP workstation. (you may call it, axpatch) > cd directory_name changes directory to your new directory on your AXP workstation. > put alpcsci02_71.a copies the ECO Kit to your new directory on your AXP workstation. Upon entering the “put” command, the transfer process starts.
PAGE 36
26 Section 3 F Installing SYBASE Software 3.2.3 Initializing the Second Disk Drive The following steps let you initialize the second (external) disk drive and should only be carried out on disks which have not been initialized. The second disk drive must be initialized as shown so that there is enough contiguous disk space on the disk to load the SYBASE database software.
PAGE 37
Installing SYBASE Software F Section 3 3.2.4 27 Guidelines for Running the Installation Script The following information provides guidelines for running the installation script: sybase_envox_install. J J J When sybase_envox_install is run, a menu driven interface is displayed on the screen. It is a character based menu. Navigation through the menu items is accomplished by using the up and down arrow keys or by pressing Return on any of the menu item fields.
PAGE 38
Section 3 F Installing SYBASE Software 28 3.3 Installing SYBASE Software on Client-Server Systems The following section describes how to install SYBASE software in a client-server system. Step 1: 3 If you are not logged into the system manager’s account, log in by entering the user name SYSTEM and the password at the prompts: Username: SYSTEM Password: your_password The DCL prompt appears.
PAGE 39
Installing SYBASE Software F Section 3 29 Choose which type of installation. Move cursor to item and press . CLIENT-SERVER CLIENT-ONLY QUIT Step 5: Move the cursor to CLIENT-SERVER and press Return.
PAGE 40
30 3 Section 3 F Installing SYBASE Software Step 8: For menu item 3), answer Y to place the list of recommended sysgen parameters detailed in sys$manager:sybase_vms_resources.dat into sys$system:fisher_sybase_modparams.dat. When the sysgen parameters are located in this file, the system is set to the parameters whenever Autogen is executed by the system manager. Step 9: For menu item 4), enter the UIC code for the SYBASE account.
PAGE 41
Installing SYBASE Software F Section 3 31 You can configure the SYBASE server to allow TCP/IP entry after installing CDOS.(see section 12). Step 14: For menu item 9), enter the SYBASE SQL server name. The server name can contain only alphanumeric characters, dollar signs ($) and underscore ( _ ) characters. It must be 10 characters or less. A default name of SYBASE is recommended. Step 15: For menu item 10), enter the memory allocated to the SYBASE dataserver.
PAGE 42
32 Section 3 F Installing SYBASE Software The following display appears: Checking menu options Please wait... If there are no errors, the following display appears: 3 Options validated OK Move cursor to item and press PROCEED WITH INSTALLATION MODIFY OPTIONS QUIT Any system parameters which require changing will be displayed. Please refer to subsection 14.4 in the ENVOX System Manager’s Guide for changing system parameters.
PAGE 43
Installing SYBASE Software F Section 3 3.4 33 tempdb Considerations for Client-Server Systems During the installation of client-server SYBASE, a database called tempdb is created. This database holds temporary tables created when ENVOX software is running. For large ENVOX databases or for an ENVOX database which will be used by many users at the same time, the database tempdb should be increased in size and directed to a logical device which you define.
PAGE 44
Section 3 F Installing SYBASE Software 34 3.5 Installing SYBASE Software on Client-Only Systems The following section describes how to install SYBASE software for a client-only system. Step 1: 3 If you are not logged into the system manager’s account, log in by entering the user name SYSTEM and the password at the prompts: Username: SYSTEM Password: your_password The DCL prompt appears.
PAGE 45
Installing SYBASE Software F Section 3 35 Choose which type of installation. Move cursor to item and press . CLIENT-SERVER CLIENT-ONLY QUIT Step 5: Move the cursor to CLIENT-ONLY and press Return.
PAGE 46
36 3 Section 3 F Installing SYBASE Software Step 8: For menu item 3), answer Y to place the list of recommended sysgen parameters detailed in sys$manager:sybase_vms_resources.dat into sys$system:fisher_sybase_modparams.dat. When the sysgen parameters are located in this file, the system is set to these parameters whenever Autogen is executed by the system manager. Step 9: For menu item 4), enter the UIC code for the SYBASE account.
PAGE 47
Installing SYBASE Software F Section 3 37 not yet installed TCP/IP software, then leave this field blank. You can configure the SYBASE server to allow TCP/IP entry after installing CDOS.(see section 12). Step 14: For menu item 9), enter the name of the node where the SQL server resides. A valid entry for the node name and address must exist in the client’s NCP database and be reachable.
PAGE 48
38 Section 3 F Installing SYBASE Software Step 17: Move the cursor to PROCEED WITH INSTALLATION and press Return to continue the installation. If there are no errors, the installation continues to completion. During installation, the following display appears: 3 start of inst_upg_sybase.com Deleting existing sybase files... Installing SYBASE files... Sybase install completed successfully on 15-Dec-1997 11:46.40 This completes the SYBASE client-only installation. See Subsection 4.
PAGE 49
Installing ENVOX Software F Section 4 39 Figure 4-Table 4 4 4 Installing ENVOX Software This section explains how to install ENVOXR configuration software on a MicroVAX 3100 computer, a VAXstation 3100, a VAXstation 4000 and the AlphaStation 200 series. The section also includes information about recovering from errors and setting up user accounts. See Appendix A for the meaning of error messages. See Appendix C for log files of a typical installation.
PAGE 50
Section 4 F Installing ENVOX Software 40 Note ... System backup before and after installation is extremely important. Always back up the system in case the system configuration needs to be restored. Store backup tapes in an environmentally and physically protected area. 4 4.2 Before Installing ENVOX Software Several procedures and considerations need to be done before you perform an installation. They are explained in the following subsections. 4.2.
PAGE 51
Installing ENVOX Software F Section 4 J Navigation through the menu item data fields is accomplished by using the left and right arrow keys. J The menu item data fields are in insert mode. J If any menu item is incorrect, its data field is shown in reverse video. J J J J Most of the menu data is defaulted for you when the menu is displayed. The defaulted data can be modified. Moving the cursor to ENTER and pressing Return causes the data from the menu to be checked.
PAGE 52
Section 4 F Installing ENVOX Software 42 4.3 Installing ENVOX Software on Client-Server Systems The following section describes how to install ENVOX software for a client-server system. Step 1: If you are not logged into the system manager’s account, log in by entering the user name SYSTEM and the password at the prompts: Username: SYSTEM Password: password 4 The DCL prompt appears.
PAGE 53
Installing ENVOX Software F Section 4 Step 4: 43 Move the cursor to INSTALL ENVOX and press Return. The following display appears: ENVOX Client-Server Installation 1)ENVOX System Disk = SYS$SYSDEVICE 2)ENVOX Log Disk = SYS$SYSDEVICE 3)ENVOX Database Disk = USER$1 4)ENVOX Account UIC code = 17,1011 5)ENVOXSUPPORT Account UIC code = 17,1012 6)Create ENVOXDB = Y 7)Tape device = ENTER QUIT Step 5: For menu item 1), enter the name of the disk which will contain the main ENVOX directory structure.
PAGE 54
44 Section 4 F Installing ENVOX Software Step 11: For menu item 7): to install from tape, enter the tape device name where the ENVOX software media is located. To install from disk, enter the full directory pathname where the savesets are stored. Step 12: Move the cursor to ENTER and press Return to continue the installation. The following display appears: Checking menu options 4 Please wait...
PAGE 55
Installing ENVOX Software F Section 4 45 Note ... For new installations, the ENVOX forms password is set to password. We recommend that you change the password to one of your own and keep the new password safe. This completes the ENVOX client-server installation. 4.4 Installing ENVOX Software on Client-Only Systems The following section describes how to install ENVOX software for a client-only system.
PAGE 56
46 Section 4 F Installing ENVOX Software The following display appears: Choose whether to install or de-install SYBASE and ENVOX Move cursor to item and press . INSTALL SYBASE INSTALL ENVOX DE-INSTALL SYBASE and ENVOX 4 QUIT Step 4: Move the cursor to INSTALL ENVOX and press Return.
PAGE 57
Installing ENVOX Software F Section 4 Step 9: 47 Move the cursor to ENTER and press Return to continue the installation. The following display appears: Checking menu options Please wait... If there are no errors, the following display appears: Options validated OK Move cursor to item and press PROCEED WITH INSTALLATION MODIFY OPTIONS QUIT Step 10: Move the cursor to PROCEED WITH INSTALLATION and press Return to continue the installation.
PAGE 58
48 Section 4 F Installing ENVOX Software 4 Blank page.
PAGE 59
Upgrading Software on Client-Server Systems F Section 5 49 Figure 5-Table 5 5 5 Upgrading Software on Client-Server Systems This section explains how to upgrade SYBASE and ENVOXR software for client-server systems. Since client-server upgrade methods differ depending on the ENVOX version on which are you are operating, this section divides software upgrade into two methods: J J 5 A method for upgrading SYBASE and ENVOX software from ENVOX P2.x, P3.0, P3.2, and P3.3 to ENVOX P4.
PAGE 60
Section 5 F Upgrading Software on Client-Server Systems 50 5.1 Before Upgrading SYBASE and ENVOX Software Several procedures and considerations need to be done before you perform an installation. They are explained in the following subsections. 5.1.1 Precautions Before you upgrade, you should understand the precautions listed below. They can save you time and can reduce the possibility of errors.
PAGE 61
Upgrading Software on Client-Server Systems F Section 5 5.1.2 51 Setting the Password Before Upgrading Before you can upgrade SYBASE software, the SYBASE system administrator’s password must be set to database. To change the password, perform the following steps: Step 1: Log into the SYBASE account as follows: Username: SYBASE Password: your_password The DCL prompt appears. Step 2: Enter the following command at the DCL prompt: $ isql/u=“sa”/password=“sa_password” The command runs the ISQL utility.
PAGE 62
52 Section 5 F Upgrading Software on Client-Server Systems 5.1.4 Considerations for Using the PDX Utility The following items are important points to consider before proceeding with the client-server upgrade: J J J 5 J J J J SYBASE software already existing on your system and all of the database information will be completely deleted. The PDX dump method is the only way of saving your database information. The existing login.com will be saved away as old_login.
PAGE 63
Upgrading Software on Client-Server Systems F Section 5 J 53 The menu system considers a PDX dump to be both a PDX dump and a PDX verification of that dump. The verification phase is transparent to the user, unless several tapes are used for one database. Caution ... Do not PDX dump databases to any of the SYBASE or ENVOX directories because they are subsequently deleted during the installation and you will lose the data in the databases. 5.1.
PAGE 64
Section 5 F Upgrading Software on Client-Server Systems 54 J J J J 5 5.2 Pressing Ctrl-e deletes the current data field. If there are no error messages, the menu disappears from the screen and is replaced with informational messages from the various stages of the upgrade. Once upgrade has started, do not try to interrupt it. SYBASE software installation and upgrade typically lasts about 60 minutes on a VAX system and 20 minutes on an AXP system.
PAGE 65
Upgrading Software on Client-Server Systems F Section 5 55 Start System Backup See Section 8 Backup Databases See ENVOX System Managers Guide List Database Statistics and Save See Subsection 5.2.1 PDX Dump Data from Databases See Subsection 5.2.2 De-install SYBASE and ENVOX See Section 8.5 Upgrade VMS and DECWindows Motif See OpenVMS Manuals Install SYBASE Software See Subsection 3.3 Install ENVOXr Software See Subsection 4.3 Create Logical Devices See Subsection 5.
PAGE 66
Section 5 F Upgrading Software on Client-Server Systems 56 5.2.1 Determining Database Structure and Statistics Before upgrading ENVOX versions P2.x, P3.0, P3.2 and P3.3, you must determine the database structure and statistics of your system. This information is used to determine the size to make the new databases after the software upgrade. Determine the database structure and statistics as described in the steps below.
PAGE 67
Upgrading Software on Client-Server Systems F Section 5 J $ $ For upgrades from P2.x (VAX platform only), enter: mount/for tapedrive: backup tapedrive:ENVOX040.Z envox$application:pdx.exe /SELECT=P20_pdx.exe/log/ignore=label/owner=ENVOX/replace J $ $ 57 For upgrades from P3.0 (VAX platform only), enter: mount/for tapedrive: backup tapedrive:ENVOX040.Z envox$application:pdx.exe /SELECT=P30_pdx.
PAGE 68
58 Section 5 F Upgrading Software on Client-Server Systems 5.2.2 Dumping Data from ENVOX and Open Databases — ENVOX P2.x, P3.0, P3.2 and P3.3 Dump the data from ENVOX and Open databases which are on ENVOX versions P2.x, P3.0, P3.2 and P3.3 as described in the steps below: Step 1: Log into the ENVOX account as follows: Username: ENVOX Password: your_password The DCL prompt appears.
PAGE 69
Upgrading Software on Client-Server Systems F Section 5 5.2.3 59 Completing the Upgrade Process Complete the upgrade process as described in the following steps: Note ... Before completing the upgrade process, it is recommended that you review the information in subsections 5.1.5, 3.1 and 3.2. Step 1: Follow the instructions given in section 8.5 to de-install SYBASE and ENVOX software. Step 2: Upgrade your VAX or AXP system to OpenVMS V7.1 and DECwindows Motif version V1.
PAGE 70
Section 5 F Upgrading Software on Client-Server Systems 60 5.3 Upgrading ENVOX Version P3.4 to P4.0 Figure 5-2 shows the process for upgrading a client-server system from version P3.4 to SYBASE System 10.0.2.6 and ENVOX P4.0. The process consists of the following procedures: Note ... It is suggested that you upgrade your VAX and AXP system to OpenVMS 7.1 and DECWindows Motif V1.2.3 (for VAX) or V1.2.4 (for AXP) before proceeding with the upgrade.
PAGE 71
Upgrading Software on Client-Server Systems F Section 5 61 Start System Backup See Section 8 Backup Databases See ENVOX System Managers Guide List Database Statistics and Save See Subsection 5.3.1 PDX Dump Data from Databases See Subsection 5.3.2 Upgrade SYBASE Software See Subsection 5.3.3 Upgrade ENVOX Software See Subsection 5.3.3 Create ENVOXR Databases See Subsection 5.4 PDX Load Data into Databases See Subsection 5.4 System Backup See Section 8 End Figure 5-2. ENVOX P3.
PAGE 72
Section 5 F Upgrading Software on Client-Server Systems 62 5.3.1 Determining Database Structure and Statistics Before upgrading ENVOX version P3.4, determine the database structure and statistics of your system. This information is used to determine the size to make the new databases after the software upgrade. Determine the database structure and statistics as described in the steps below.
PAGE 73
Upgrading Software on Client-Server Systems F Section 5 Step 5: 63 Run the PDX utility in information mode on each ENVOX and Open database listed in the file show_dev_alloc.out. Enter the following commands at the DCL prompt: $ $ $ $ define sys$output DB.out mcr envox$application:pdx.exe -sv df ”SERVER” ”DB” ”sa_passwd” nl: deassign sys$output print DB.
PAGE 74
64 Section 5 F Upgrading Software on Client-Server Systems 5.3.2 Dumping Data from ENVOX and Open Databases — ENVOX P3.4 Dump the data from ENVOX and Open databases which are on ENVOX version P3.4 as described in the steps below: Step 1: If your system is not already running OpenVMS V7.1 and DECwindows Motif version V1.2-3(VAX system) and version V1.2-4(AXP system), then upgrade your VAX or AXP systems to these software versions.
PAGE 75
Upgrading Software on Client-Server Systems F Section 5 Step 5: 65 Move the cursor to INSTALL SYBASE and press Return. The following display appears: PDX dump or list database statistics. Move cursor to item and press PDX DUMP DATABASES LIST OUT DATABASE STATISTICS QUIT Step 6: Move the cursor to LIST OUT DATABASE STATISTICS and press Return.
PAGE 76
66 Section 5 F Upgrading Software on Client-Server Systems Step 8: Move the cursor to PDX DUMP DATABASES, and press Return. The following display appears: PDX dump a database or install. Move cursor to item and press PDX dump database PDX dump database PDX dump database . . . 5 INSTALL QUIT There is a PDX dump selection for every database which was listed in Step 6.
PAGE 77
Upgrading Software on Client-Server Systems F Section 5 67 Tape Characteristics -------------------1)Tape device filename = 2)Tape Capacity(Mb) = ENTER QUIT Step 12: Enter the tape device filename (for example, MKA100:ENVOXDB.PDX) and the tape capacity. Then, move the cursor to ENTER and press Return. The following display appears if you are dumping to tape: Checking tape characteristics Please wait... Followed by the next display: PDX dump of database dbname in progress Please wait...
PAGE 78
68 Section 5 F Upgrading Software on Client-Server Systems Step 14: Put the first tape that was used for this PDX dump into the tapedrive, and press Return. The PDX dump process will continue. If another tape is needed, the prompt is repeated. When the PDX dump has completed successfully, the following display appears: PDX dump of database dbname COMPLETE. . . . Press to continue, Ctrl-Z to exit. 5 See Appendix A for list of error conditions and corrective actions. Step 15: Proceed to Step 18.
PAGE 79
Upgrading Software on Client-Server Systems F Section 5 69 When you have completed the dump process for all of your databases, complete the upgrade process as described in subsection 5.3.3. 5.3.3 Completing the Upgrade Process Complete the upgrade process as described in the following steps: Note ... Before completing the upgrade process, it is recommended that you review the information in subsections 5.1.5, 3.1 and 3.2.
PAGE 80
70 Section 5 F Upgrading Software on Client-Server Systems The following display appears: Checking menu options Please wait... If there are no errors, the system displays the following: Options validated OK Move cursor to item and press PROCEED WITH INSTALLATION MODIFY OPTIONS 5 QUIT Step 4: Move the cursor to PROCEED WITH INSTALLATION and press Return to continue the sybase upgrade. The following display appears: start of inst_upg_sybase.com ---------------------------Installing SYBASE files...
PAGE 81
Upgrading Software on Client-Server Systems F Section 5 71 If there are no errors, the following display appears: Choose whether to install or de-install ENVOX. Move cursor to item and press INSTALL ENVOX DE-INSTALL SYBASE and ENVOX QUIT Step 6: Move the cursor to INSTALL ENVOX, and press Return to continue the SYBASE upgrade.
PAGE 82
72 Section 5 F Upgrading Software on Client-Server Systems Step 8: Move the cursor to PROCEED WITH INSTALLATION and press Return to continue the sybase upgrade. The following display appears: start of inst_upg_envox.com ---------------------------Deleting existing ENVOX files... Installing ENVOX files... upgrading master database upgrading database master to envox P4.
PAGE 83
Upgrading Software on Client-Server Systems F Section 5 5.4 73 Creating and Loading ENVOX and Open Databases After the Upgrade Note ... Upgrades from ENVOX P3.4 preserve logical devices. Upgrades from P2.x, P3.0, P3.2, and P3.3 systems delete logical devices, they must be re-created. The upgrade process does not create an empty ENVOX database. ENVOX databases must be created before loading ENVOX and OPEN databases using the PDX utility.
PAGE 84
74 Section 5 F Upgrading Software on Client-Server Systems To run the PDX utility to load from tape, log into the ENVOX account and type the following at the command line: $ mcr envox$application:pdx fd tape:filename “SERVERNAME” “DBNAME” “sapasswd” Example Command Fill in your tape:filename (for example, MKA100:envoxdb.pdx), server name, database name, and SA password. 5 The following example transfers the file contents of tran1.
PAGE 85
Upgrading Software on Client-Server Systems F Section 5 5.5 75 Reloading P4.0 ENVOX Software This subsection describes how you reload P4.0 ENVOX software. Two reasons you might need to reload ENVOX P4.0 software on a system already running P4.0 are: J J You are a customer who has an agreement with Fisher-Rosemount Systems to implement pre-release software products in controlled environments called Beta sites. These sites must then reload P4.0 when the final software version is released.
PAGE 86
76 Section 5 F Upgrading Software on Client-Server Systems Checking system Please wait... If there are no errors, the following display appears: Choose whether to install or de-install ENVOX. Move cursor to item and press . INSTALL ENVOX DE-INSTALL SYBASE and ENVOX 5 QUIT Step 4: Move the cursor to INSTALL ENVOX and press Return.
PAGE 87
Upgrading Software on Client-Server Systems F Section 5 77 If there are no errors, the upgrade continues to completion. During upgrade, the following display appears: start of inst_upg_envox.com ---------------------------Deleting existing ENVOX files... Installing ENVOX files... upgrading master database upgrading database master to envox P4.0 1997 12:46PM master upgrade complete DEC 12 DEC 12 1997 12:47PM UPDATING ENVOX DATABASES TO P4.0 ...
PAGE 88
78 Section 5 F Upgrading Software on Client-Server Systems 5 Blank page.
PAGE 89
Upgrading Software on Client-Only Systems F Section 6 79 Figure 6-Table 6 6 6 Upgrading Software on Client-Only Systems This section describes how to upgrade SYBASE and ENVOXr software for client-only systems. Unlike client-server systems, the client-only upgrade process is the same for any any ENVOX version which you are currently using. Figure 6-1 shows the procedure for upgrading a client-only system. You must upgrade your ENVOX and SYBASE software in the sequence shown in the figure.
PAGE 90
Section 6 F Upgrading Software on Client-Only Systems 80 Note ... System backup is extremely important before and after an upgrade. Always back up all disks on the system which contain ENVOX software, SYBASE software, databases, or transaction logs. A backup will ensure that all data can be recovered in case of an upgrade failure. Store backup tapes in an environmentally and physically protected area. 6.
PAGE 91
Upgrading Software on Client-Only Systems F Section 6 81 The following display appears: Choose whether to install or de-install SYBASE and ENVOX Move cursor to item and press . INSTALL SYBASE INSTALL ENVOX DE-INSTALL SYBASE and ENVOX QUIT Step 4: Move the cursor to INSTALL SYBASE and press Return. The following display appears: SYBASE Client-Only Upgrade 1)Tape device = ENTER QUIT Step 5: To upgrade from tape, enter the tape device name where the ENVOX software media is located.
PAGE 92
Section 6 F Upgrading Software on Client-Only Systems 82 Step 7: Move the cursor to PROCEED WITH INSTALLATION and press Return to continue the upgrade. If there are no errors, the upgrade continues to completion. During upgrade, the following display appears: start of inst_upg_sybase.com Deleting existing sybase files... Installing SYBASE files... Sybase install completed successfully on 12-DEC-1997 17:43.45 This completes the SYBASE Upgrade. See subsection 6.
PAGE 93
Upgrading Software on Client-Only Systems F Section 6 83 The following display appears: Choose whether to install or de-install SYBASE and ENVOX Move cursor to item and press . INSTALL SYBASE INSTALL ENVOX DE-INSTALL SYBASE and ENVOX QUIT Step 4: Move the cursor to INSTALL ENVOX and press Return. The following display appears: ENVOX Client-Only Upgrade 1)Tape device = ENTER QUIT Step 5: To upgrade from tape, enter the tape device name where the ENVOX software media is located.
PAGE 94
84 Section 6 F Upgrading Software on Client-Only Systems Step 7: Move the cursor to PROCEED WITH INSTALLATION and press Return to continue the upgrade. start of inst_upg_envox.com Deleting existing envox files... Installing ENVOX files... ENVOX install completed successfully on 21-DEC-1997 17:43.45 This completes the ENVOX client-only upgrade.
PAGE 95
Creating ENVOX User Accounts F Section 7 85 Figure 7-Table 7 7 7 Creating ENVOX User Accounts An ENVOXr user account on OpenVMS is created during ENVOX software installation. Additional accounts may be added by the system administrator. Three steps are required: J Set up the OpenVMS user account. J Set up the ENVOX user directory. J Copy the file ENVOX$DISK:[ENVOX]LOGIN.COM to the user directory. Note ... Each ENVOX user requires an OpenVMS system account. 7.
PAGE 96
86 Section 7 F Creating ENVOX User Accounts Step 2: Set the definition by entering the following command at the DCL prompt: $ set def sys$system Step 3: Run the Authorize utility by entering the following command at the DCL prompt: $ run authorize Step 4: Enter the parameters shown below at the UAF prompts. The dash (--) at the end of the line is the OpenVMS indicator for a continuation of the input line. If you enter incorrect data in a field, the system indicates the error.
PAGE 97
Creating ENVOX User Accounts F Section 7 87 Username: ENVOX Owner: Account: UIC: [17,1011] ([ENVOX]) CLI: DCL Tables: DCLTABLES Default: ENVOX$DISK:[ENVOX] LGICMD: LOGIN Login Flags: Primary days: Mon Tue Wed Thu Fri Secondary days: Sat Sun No access restrictions Expiration: (none) Pwdminimum: 6 Login Fails: 0 Pwdlifetime: (none) Pwdchange: 11-JUL-1990 11:02 Last Login: (none) (interactive), (none) (non-interactive) Maxjobs: 0 Fillm: 300(1) Bytlm: 65536(1) Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0 Maxdetach: 0
PAGE 98
Section 7 F Creating ENVOX User Accounts 88 Step 7: Exit the authorize program by entering the following command at the prompt: UAF> EXIT The following messages are displayed: %UAF-I-DONEMSG, system authorization file modified %UAF-I-RDBDONEMSG, rights data base modified 7.
PAGE 99
Backing Up, Restoring, and De-Installing Software F Section 8 89 Figure 8-Table 8 8 8 Backing Up, Restoring, and De-Installing Software This section describes the backup, restore, and de-installation procedures for ENVOXr and SYBASE software. Note ... All databases, including the master database, should be backed up periodically, especially after any change to the database. Instructions for backing up the master database are given in the The System Manager’s Guide to ENVOX Configuration Software, SM1.
PAGE 100
90 Section 8 F Backing Up, Restoring, and De-Installing Software Step 3: At the prompt for the device name, enter the name of the system disk. This action creates the standalone backup on disk. 8.1.
PAGE 101
Backing Up, Restoring, and De-Installing Software F Section 8 Step 4: 91 Enter the following command at the console-mode prompt (>>>) to display the list of device names: >>> SHOW DEVICE Step 5: Enter the following command to boot the backup routine: >>> B tapedrive where tapedrive is the name of the tape drive as listed in the SHOW DEVICE display. Step 6: Enter the date and time as indicated.
PAGE 102
Section 8 F Backing Up, Restoring, and De-Installing Software 92 8.3 Backing Up the System Caution ... Always backup and restore together all disks which contain ENVOX logical devices; do not reboot the system or allow the SYBASE SQL Server to restart during a backup or restore period. The logical device files contain information which must always be kept in step. If they are not, the ENVOX database can lose data.
PAGE 103
Backing Up, Restoring, and De-Installing Software F Section 8 Step 3: 93 A message saying that volume labels do not match may appear along with options for overwriting. If they do, select overwrite to continue the backup process. The process can take from 20 minutes to 2 hours, depending on the amount of data on the disk. If the data requires more than one tape (multi-volume), the system rewinds the current tape and asks you to install another tape.
PAGE 104
Section 8 F Backing Up, Restoring, and De-Installing Software 94 8.4 Restoring the System Caution ... Always backup and restore together all disks which contain ENVOX logical devices; do not reboot the system or allow the SYBASE SQL Server to restart during a backup or restore period. The logical device files contain information which must always be kept in step. If they are not, the ENVOX database can lose data.
PAGE 105
Backing Up, Restoring, and De-Installing Software F Section 8 Step 3: 95 When the tape that is being read reaches its end (except for the last tape in a set of tapes), several end-of-tape messages are displayed. %BACKUP-I-RESUME, Resuming operation on volume n %BACKUP-I-READWRITE, Mount column n on tapedrive: for reading Load the next tape. Make sure that you insert the backup tapes in the correct order.
PAGE 106
Section 8 F Backing Up, Restoring, and De-Installing Software 96 8.5 De-installing ENVOX and SYBASE Software The de-install process completely removes ENVOX and SYBASE software from your system. All SYBASE databases, files, and directories are deleted, all ENVOX files and directories are deleted, and all SYBASE and ENVOX accounts are deleted. You cannot choose to de-install SYBASE or ENVOX software separately.
PAGE 107
Backing Up, Restoring, and De-Installing Software F Section 8 97 One of the following displays appear: Choose which product to install or de-install SYBASE and ENVOX Move cursor to item and press . INSTALL SYBASE INSTALL ENVOX DE-INSTALL SYBASE and ENVOX QUIT If SYBASE and ENVOX have been installed, the following display appears: Choose whether to install or de-install ENVOX Move cursor to item and press .
PAGE 108
98 Section 8 F Backing Up, Restoring, and De-Installing Software Blank page.
PAGE 109
Retrieving Files from the Installation Tape F Section 9 99 Figure 9-Table 9 9 9 Retrieving Files from the Installation Tape If you have inadvertently deleted certain files from your ENVOX and SYBASE directories, you do not have to perform a re-installation to get these files. You can retrieve the files as described below. Table 9-1 lists the savesets which are stored on the installation media. They are stored in the order listed. Table 9-1.
PAGE 110
100 9.1 Section 9 F Retrieving Files from the Installation Tape Procedure for Retrieving Files To retrieve files from the installation tape, perform the following steps: Step 1: If you are not logged into the system account, log in by entering the user name SYSTEM and your password at the prompts: Username: SYSTEM Password: your_password The DCL prompt appears. 9 Step 2: Insert and make ready the installation media.
PAGE 111
Retrieving Files from the Installation Tape F Section 9 9.2 101 Examples of Retrieving Files Several examples are given below which describe how to retrieve various files. The first example recovers the ENVOX file, envox_main.exe, from the installation media which is inserted into tapedrive mka400:, places the file in envox$disk:[envox.executables], and sets the file ownership to ENVOX. $ set def envox$disk:[envox.executables] $ mount/for mka400: $ backup mka400:envox_d.bck *.*/select= envox_main.
PAGE 112
102 Section 9 F Retrieving Files from the Installation Tape The following example recovers all files with a file extension of EXE from the [sybase.bin] directory contained within the SYBASE saveset SYSTEM10_SERVER.C located on the installation media inserted into tapedrive mka400:, and sets the file ownership to SYBASE. $ set def SYBASE_DEVICE:[SYBASE.BIN] $ mount/for mka400: $ backup mka400:system10_server.C *.*/select= [sybase.bin]*.
PAGE 113
System Tuning F Section 10 103 Figure 10-Table 10 10 10 System Tuning You can change the number of concurrent ENVOX software, Control Desktop and Control Designer users. and the amount of memory allocated to the SYBASE SQL Server. However, you must leave enough memory for proper operation of SYBASE and ENVOX software. Refer to subsections 2.6 and 2.8 for memory requirements. You are prompted for the number of concurrent ENVOX software, Control Desktop, and Control Designer users.
PAGE 114
104 Section 10 F System Tuning Step 4: Enter a value determined as follows: J J If you do not have Control Desktop installed, enter 0. If you have Control Desktop installed, use Table 10-3 to help determine the number of Control Desktop users you may enter.
PAGE 115
System Tuning F Section 10 105 VAX/VMS Resources required for SYBASE.
PAGE 116
Section 10 F System Tuning 106 Enter Y if you wish to continue. Step 9: The following display appears: checking system parameters... initializing the SYBASE server with the new parameters... sybase_tune completed successfully on 12-JAN-1998 08:12 If sybase_tune does not proceed as expected, there is a log file which you can review to help you determine the cause. The file, sybase_tune.log, is produced in the sybase_device:[sybase.install] directory.
PAGE 117
System Tuning F Section 10 107 minimum amount of physical memory that must be allocated to the Sybase server to support a specific mix of concurrent ENVOX software, Control Desktop, and Control Designer users which you specify. Table 10-3 gives an approximate minimum amount of physical memory that must be allocated to the Sybase server to support a given total number of concurrent ENVOX software, Control Desktop, and Control Designer users. Table 10-3.
PAGE 118
108 Section 10 F System Tuning Blank page.
PAGE 119
Transferring Non-ENVOX Databases F Section 11 109 Figure 11-Table 11 11 11 Transferring Non-ENVOX Databases Section 5 of this installation manual shows how to use the installation menu system to upgrade databases to P4.0. The upgrade process will only work with ENVOXr databases. Any non-ENVOX databases will be completely deleted from the system. If you have Instrument Information System (IIS)t databases, you should refer to the IIS backup and restore procedures for information.
PAGE 120
110 Section 11 F Transferring Non-ENVOX Databases 11.1 Using the PDX Utility The following steps describe how to use the PDX utility to save the data in non-ENVOX databases. The same utility is used to reload the data into newly created databases on the server. More details on the PDX utility are given in the System Manager’s Guide, Section 9. Step 1: Run the PDX utility to write a file containing the non-ENVOX database data out to a disk or to tape: $ mcr envox$application:pdx.
PAGE 121
Transferring Non-ENVOX Databases F Section 11 11.2 111 PDX Failure and Reasons PDX was designed to be used with ENVOX type databases. It can fail with non-ENVOX databases. The following are validation checks that PDX will perform before creating a file of the database data. A Fatal error means that PDX has failed. A Warning message means that PDX will proceed but some data may be missing. The text of the warning message gives an indication of that data.
PAGE 122
112 11 Section 11 F Transferring Non-ENVOX Databases Check Unsupported types in syscolumns Message Fatal - Unsupported datatypes in syscolumns Reason Supported types are: int, smallint, tinyint, binary, varbinary, char, varchar, datetime, float Check Unsupported types in systypes Message Fatal - Unsupported datatypes in systypes Reason Supported types are: int, smallint, tinyint, binary, varbinary, char, varchar, datetime, float.
PAGE 123
Transferring Non-ENVOX Databases F Section 11 Check Tables with null column names Message Warning - Tables with NULL column names will not be transferred Check Tables with undefined datatypes Message Warning - Tables with columns of undefined type will not be transferred Check Grant with Grant Message Warning - GRANT with GRANT permissions will not be transferred Check Columns with internal-only usertypes Message Fatal - User tables with columns of internal datatype exist Check Column data
PAGE 124
114 Section 11 F Transferring Non-ENVOX Databases Blank page.
PAGE 125
Installing and Upgrading CDOS for Control Desktop F Section 12 115 Figure 12-Table 12 12 12 Installing and Upgrading CDOS for Control Desktop Control Desktop Open Server (CDOS) software interfaces ENVOXr Configuration Software to Type SW3311 Control Desktop client software. This section describes how to install and upgrade the CDOS software on DEC VAX and DEC AXP platforms. These platforms require that ENVOX software already be installed in client-server or client-only mode. 12.
PAGE 126
116 Section 12 F Installing and Upgrading CDOS for Control Desktop However, in practice the limit may be lower depending on CPU size, memory size, and the load imposed by other applications running on the system. Note ... CDOS can be installed on a workstation which has ENVOX software installed in Client-Server or Client-Only mode.
PAGE 127
Installing and Upgrading CDOS for Control Desktop F Section 12 12.3 117 Preparing for the Installation or Upgrade Several actions are required before you make any attempt to install or upgrade CDOS software. 12.3.1 Precautions Before you install or upgrade, you should understand the precautions listed below. They can save you time and can reduce the possibility of errors. J J J J J J J J J If you have previously installed a pre-release version of the CDOS P1.
PAGE 128
118 Section 12 F Installing and Upgrading CDOS for Control Desktop 12.3.2 Using the CDOS installation and Upgrade Menu The CDOS installation menu system is similar to that used for the installation of SYBASE and ENVOX software. The following information will help you navigate in the menu system: J J J When you install CDOS, a menu-driven, character-based interface is displayed on the screen.
PAGE 129
Installing and Upgrading CDOS for Control Desktop F Section 12 12.3.3 119 Verifying TCP/IP Installation The TCP/IP software should always be installed and configured, following the instructions in the vendor-supplied Installation and configuration manuals. The Troubleshooting subsection, 12.9, provides a guide to installing Multinet and UCX on OpenVMS system. Caution ... Do not omit the following verification procedures.
PAGE 130
120 Section 12 F Installing and Upgrading CDOS for Control Desktop 12.3.4 TCP/IP Entries for the Servers The CDOS installation automatically creates an entry in the interfaces file for the CDOS server and configures a TCP/IP entry for it. The entry for the SYBASE server can be optionally added during the ENVOX P4.0 installation. If the entry does not exist, it must be manually updated to add a TCP/IP entry. The update must be done after TCP/IP has been successfully installed and configured.
PAGE 131
Installing and Upgrading CDOS for Control Desktop F Section 12 121 On the PC running Control Desktop, the ServerSetup program should be run and the two server names defined. Assuming the names used in the example above, they would be entered in the list box at the top section of the program screen as: CDOS 129.76.21.146, 7010 SYBASE 129.76.21.146, 2025 In the bottom section of the screen, the CDOS Open Server name would be CDOS and the Default Sybase Server name would be SYBASE.
PAGE 132
122 Section 12 F Installing and Upgrading CDOS for Control Desktop 12.4 Licensing CDOS After Installation After installation, you must obtain license keys. The CDOS installation program creates a license file, cdos_system:[cdos]license.dat. This file lists the purchased Control Desktop licenses. The list is used by CDOS to identify when the number of licenses has been exceeded. The CDOS installation program also creates a license expiration file, cdos_system:[cdos]expiry.dat.
PAGE 133
Installing and Upgrading CDOS for Control Desktop F Section 12 12.5 123 Installing CDOS Installation is a stepped procedure, requiring several keyboard entries and selections during the process. Be sure to follow the procedure carefully. Note ... If your system is already installed with CDOS version P1.0 and you wish to upgrade CDOS to version P2.0, then proceed to subsection 12.6.
PAGE 134
124 Section 12 F Installing and Upgrading CDOS for Control Desktop Choose whether to install or de-install CDOS. Move cursor to item and press . INSTALL CDOS DE-INSTALL CDOS QUIT Step 4: Move the cursor to INSTALL CDOS and press Return.
PAGE 135
Installing and Upgrading CDOS for Control Desktop F Section 12 125 Step 7: For menu item 3), enter the UIC code for the CDOS account. The UIC code must be unique and of the form, group, member, where group and member are OCTAL numeric numbers in the range: group = [0 to 3776] and member = [0 to 177776]. A default of 17, 2010 is recommended and places the CDOS account in the same group as the CHIP account. Step 8: For menu item 4), enter the CDOS server name.
PAGE 136
126 Section 12 F Installing and Upgrading CDOS for Control Desktop Identify Sybase Servers to be accessed via CDOS Servers from interfaces file accessed via CDOS Servers to be 1) SYBASE ENTER QUIT Use to move server to/from CDOS server list Use left & right arrows to move between lists Use up & down arrows to move within lists Note ...
PAGE 137
Installing and Upgrading CDOS for Control Desktop F Section 12 127 If there are no errors, the installation continues to completion. During installation, the following display appears: start of inst_cdos.com ---------------------Deleting existing cdos files... Installing CDOS files... initialising server files. installing cdos Images. start cdos server Job CDOS_STARTUP(queue SYS$BATCH, entry 2) Started on SYS$BATCH checking for errors add servers CDOS installation completed successfully on date, time.
PAGE 138
128 Section 12 F Installing and Upgrading CDOS for Control Desktop 12.6 Upgrading CDOS P1.0 to P2.0 Before you can use ENVOX P4.0 with Control Desktop P2.0, you must upgrade CDOS to P2.0. The following procedure describes how. Note ... The following procedure applies to the released version of CDOS P1.0. If you are running a pre-released version, perhaps remaining from having been a beta test site, you must de-install the pre-released version and then install CDOS P2.
PAGE 139
Installing and Upgrading CDOS for Control Desktop F Section 12 129 Choose whether to install or de-install CDOS. Move cursor to item and press . INSTALL CDOS DE-INSTALL CDOS QUIT Step 4: Move the cursor to INSTALL CDOS press Return to continue the sybase upgrade. The following display appears: CDOS Upgrade -----------1)Tape device = ENTER Step 5: QUIT Enter the tape device (or full disk directory path) name. The following display appears: Checking menu options Please wait...
PAGE 140
130 Section 12 F Installing and Upgrading CDOS for Control Desktop start of inst_cdos.com ---------------------Deleting existing cdos files... Installing CDOS files... Installing cdos images start cdos server Job CDOS_STARTUP (queue SYS$BATCH), entry 3) started on SYS$BATCH checking for errors cdos install completed successfully on 26-FEB-1998 14:39:02.34 Step 7: Login as user Sybase and re-tune the Sybase dataserver by entering the commands: $ set def [sybase.install] $ @sybase_tune.com 12.
PAGE 141
Installing and Upgrading CDOS for Control Desktop F Section 12 131 A message is displayed stating that the database has not been upgraded and asking if it should be upgraded now. Step 2: Select Yes or No If “Yes” is selected, you are prompted to enter the password for the envoxutility Sybase server account. Step 3: Enter your password for the envoxutility account. On a newly installed system, the password is set to: envoxutility.
PAGE 142
132 Section 12 F Installing and Upgrading CDOS for Control Desktop The process takes a few minutes — typically less than 10 minutes and often less than 5 minutes, depending on the performance of the server machine and the load upon it. Caution ... Never add an envoxutility user from the ENVOX admin forms in an attempt to perform a database upgrade. Not only will the attempt fail, but database operation can be adversely affected. 12.8 Backup, Restore, and De-Install 12.8.
PAGE 143
Installing and Upgrading CDOS for Control Desktop F Section 12 133 CDOS De-installation Utility ---------------------------0 -- De-install CDOS 1 -- Help 2 -- Quit SELECT OPTION [0] This utility will completely de-install CDOS. All CDOS files, directories and accounts will be deleted. Do you wish to continue [N] ? Enter N if you wish to save any files or wish to first backup the system. Enter Y only if you are absolutely sure that you wish to continue.
PAGE 144
134 Section 12 F Installing and Upgrading CDOS for Control Desktop Checking menu options Please wait.... If there are no errors, the following display appears: Move cursor to item and press PROCEED WITH DE-INSTALLATION QUIT WARNING: Proceeding will cause a total de-installation of CDOS. Are you sure you want to proceed. Step 3: Move the cursor to PROCEED WITH DE-INSTALLATION and press Return to continue with de-installation. If there are no errors, the installation continues to completion.
PAGE 145
Installing and Upgrading CDOS for Control Desktop F Section 12 12.9.2 135 Multinet Installation The following guidelines use the example of installing Multinet Version 4.0 on AXP node, ORANGE, and a TCP/IP address of 129.36.21.146. Substitute the nodename, TCP/IP address, routing information, and multinet product name of your system in the applicable places below. Step 1: If you are not logged into the system manager’s account, log in by entering the user name SYSTEM and your password at the prompt.
PAGE 146
136 Section 12 F Installing and Upgrading CDOS for Control Desktop $ set default sys$sysdevice:[multinet.axp_common.multinet] $ @configure When the following display appears, fill in the applicable entries for your system: * System specific directory name: [dka200:[multinet.orange]]: * Enter your Internet host name: orange.pit.leicester.fisher.com * Enter the Internet(IP) Address for interface ESA0: 129.36.21.146 * Enter the subnet mask for interface ESA0: 255.255.255.
PAGE 147
Installing and Upgrading CDOS for Control Desktop F Section 12 Step 7: 137 Verify that Multinet is running and TCP/IP is operational by entering: $ show system The process MULTINET_SERVER should be displayed. $ Multinet ping/number_of_packets = 1 orange ...or whatever is the correct parameter for your system. If TCP/IP software is installed and running, the TCP/IP address of the host will be displayed. Step 8: Verify that the INET driver has been configured.
PAGE 148
138 Section 12 F Installing and Upgrading CDOS for Control Desktop When the following display appears, fill in the applicable entries for your system: *Do you want to purge files replaced by this installation [YES] YES PRODUCT: UCX PRODUCER: Digital Equipment Corporation VERSION: 4.0 Release Date: Oct-1995 * Does this product have an authorization key registered and loaded? YES No further questions will be asked during this installation. “ “ VMSINSTAL procedure done.
PAGE 149
Installing and Upgrading CDOS for Control Desktop F Section 12 139 Do you want to grant world read access to non-privileged uses: NO o Configure Interfaces Core environment ==>Interfaces *Do you want to configure SE0 YES Enter unqualified host name: ORANGE Enter Internet address for ORANGE: 129.36.21.146 Enter Internet network mask for ORANGE: 255.255.255.0 Enter broadcast mask for ORANGE[129.36.21.
PAGE 150
140 Section 12 F Installing and Upgrading CDOS for Control Desktop ...or whatever is the correct parameter for your system. If TCP/IP software is installed and running, the TCP/IP address of the host will be displayed. Step 8: Verify that the INET driver has been configured. At the prompt, enter: $ show dev INET0 If the INET driver has been configured then the following will be displayed: INET0: 12.9.
PAGE 151
Installing and Upgrading CDOS for Control Desktop F Section 12 12.10 141 Network Routing If you need to communicate with a host on a different IP network, then a default gateway should be set up. The following steps describe how to verify and configure a default gateway on a system installed with UCX and MULTINET. 12.10.
PAGE 152
142 Section 12 F Installing and Upgrading CDOS for Control Desktop 12.10.2 Routing using MULTINET To determine whether a default gateway has been configured on a system installed with MULTINET, enter the following: Step 1: If you are not logged into the systems manager’s account, log in by entering the user name SYSTEM and your password, at the prompt. Username: System Password: your_password The DCL prompt appears.
PAGE 153
Installing and Upgrading CDOS for Control Desktop F Section 12 12.11 143 CDOS Administration The administration functions for the CDOS open server and the task daemon are described below. The first two subsections are platform specific and the third is applicable to all supported platforms. 12.11.1 CDOS Directory and File Structure The CDOS directory and the file structure can be described by Figure 12-2.
PAGE 154
144 Section 12 F Installing and Upgrading CDOS for Control Desktop J cdos_system:[cdos]start_cdos_servername.out file. This file is re-created each time the CDOS server is started and so contains the log from the current run of the CDOS server only. If the CDOS server has started successfully, the following line is seen at the end of both files: date, time CDOS startup complete - going multi-threaded 12.11.
PAGE 155
Installing and Upgrading CDOS for Control Desktop F Section 12 145 $ startdd This command produces output to the diagnostic daemon log file. The file name is given in the diagnostic daemon configuration file (described in subsection 12.11.10). The default name is cdos_system:[cdos]dd.log. If the diagnostic daemon has started successfully, the following line is seen at the end of the diagnostic daemon log file. date, time Initialisation complete 12.11.
PAGE 156
146 Section 12 F Installing and Upgrading CDOS for Control Desktop ! ! cdos_server_name.cfg ! This is the configuration file for CDOS ! servername cdos_server_name vtf_directory cdos_system:[cdos.application] logfile cdos_system:[cdos]cdos_server_name.log ! 12.11.11 Task Daemon Configuration File The task daemon needs a configuration file for startup. The installation creates a configuration file called td.cfg in the application directory, with the following format: ! ! td.
PAGE 157
Installing and Upgrading CDOS for Control Desktop F Section 12 J 147 download_all Specifies that this task daemon is to perform the download function for all of the SYBASE servers known to CDOS. If this keyword is specified the download keyword cannot be used. J download Specifies that this task daemon is to perform the download function for the SYBASE server specified as the parameter. The name of the server is case sensitive.
PAGE 158
148 Section 12 F Installing and Upgrading CDOS for Control Desktop ! openserver cdos_server_name logfile cdos_system:[cdos]dr.log machine_name nodename ! 12.11.15 CDOS Quota File The CDOS quota file, cdos_system:[cdos.application]cdos_quota.dat, contains settings of VMS quotas required to run the CDOS server. This file has the same format as quota files used with the startserver command used by ENVOX software.
PAGE 159
Error Messages F Appendix A 149 Figure A-Table A Appendix A A Error Messages This appendix lists messages that can occur during various stages of the installation process. This section is organized as follows: A.1 J Pre SYBASE/ENVOX Error Messages — Subsection A.1 J SYBASE Error Messages — Subsection A.2 J ENVOX Error Messages — Subsection A.3 J PDX Dump Error Messages — Subsection A.4 J CDOS Error and Warning Messages — Subsection A.
PAGE 160
150 A Appendix A F Error Messages Message Please ensure MOTIF is installed Description One or more of the DECwindows Motif application files is missing. Ensure that DECwindows Motif V1.2-3 is correctly installed. Message DECnet must be installed and running before SYBASE. Description Ensure DECnet is installed and running before attempting the installation.
PAGE 161
Error Messages F A.2 Appendix A 151 SYBASE Error Messages This subsection contains error messages that can occur during the installation or upgrade of SYBASE software. Message sys$manager:inst_file.out does not exist Description sys$manager:inst_file.out is a temporary file created by the installation process. Check to see if this file can be created manually. Message SYBASE install failed on xxxx Description Determine the installation failure by examining sys$manager:sybase_envox_inst.
PAGE 162
152 Appendix A F Error Messages Message SYBASE requires xxx free blocks on xxx disk Description Verify that sufficient free blocks are available on the corresponding disk. Refer to Table 2-3 and Table 2-6 for disk sizing requirements. Message SYLOGIN.COM can not be found Description Ensure that SYLOGIN.COM exists and that the logical SYS$SYLOGIN is defined and points to the sylogin.com file.
PAGE 163
Error Messages F Appendix A Message value is not a valid number Description An illegal value has been entered for the number of ENVOX users. Enter a value within the range [1 to 32]. Message server memory of xx Mb can only support xx users Description Enter a lower value for the number of ENVOX users. Message This device does not exist Description An illegal value was entered for the SYBASE printer device. Enter a legal device value.
PAGE 164
154 A Appendix A F Error Messages Message You cannot allocate more than xxx mb to the Dataserver Description The maximum memory that can be allocated to the SQL server is half the available system memory. Message Unable to determine size of master device Description Ensure that a valid master database size has been entered.
PAGE 165
Error Messages F Appendix A Message tape_device must be terminated with a : Description The entered tape device must be terminated with a colon. Message The sybase logical, SYBASE_DEVICE is not defined Description Verify that either sys$sysroot:[sysmgr]sybase_disk_logicals.com exists or sys$common:[sysmgr]sybase_disk_logicals.com exists. Message The sybase logical, SYBASE_MASTER_DEVICE is not defined. Description Verify that either sys$sysroot:[sysmgr]sybase_disk_logicals.
PAGE 166
156 Appendix A F Error Messages Message The node name length must be in the range 1-6 characters. Description An illegal node name was specified during a SYBASE client installation. Specify a valid nodename where the SYBASE SQL server resides. Message Can’t find sys$manager:xxxxx Message sys$manager:xxxx file is missing Description The installation process was unable to locate the above file which is unloaded from syb_envox_inst.a saveset at the start of the installation.
PAGE 167
Error Messages F Appendix A Message Unknown installation error encountered. Description An internal error has occurred. Examine sys$manager:sybase_envox_inst.log and sys$manager:inst_file.in to determine the error. A.3 ENVOX Error Messages 157 This subsection contains error messages that can occur during the installation or upgrade of ENVOX software. Message SYBASE must be successfully installed before attempting ENVOX.
PAGE 168
158 A Appendix A F Error Messages Message envox & envoxsupport UICs are the same Description The UIC values for the envox and envoxsupport accounts must be different. Message Unable to determine the installation disk Description The installation disk is determined from the location of the file: sys$common:[sysmgr]inst_file.out. Verify that this files exists. Message The envox_disk_logicals.com file is missing Description envox_disk_logicals.com must exist for an ENVOX upgrade.
PAGE 169
Error Messages F Appendix A Message envox requires xxx blks free blocks on install disk = xxx Message envox requires xxx blks free blocks on envox$disk = xxx Message envox requires xxx blks free blocks on envox$log_disk = xxx Message envox requires xxx blks free blocks on envox$db_disk = xxx Description Install disk refers to the disk used for installation and is normally the system disk. ENVOX$DISK refers to the disk used for the ENVOX software.
PAGE 170
160 A Appendix A F Error Messages Message WARNING - CHIP should be installed before ENVOX Description Ensure CHIP is installed before installing ENVOX software. Message UIC is already in use Description Enter a valid unique UIC. Message UIC is not a valid UIC Description The UIC must be in the form, group,member, where group and member are OCTAL numeric values in the range; group = [0 to 37776] and member = [0 to 177776].
PAGE 171
Error Messages F Appendix A 161 Message tape_device is an invalid pathname Description An invalid directory pathname has been entered for the tape device. Message tape_device must be terminated with a : Description The entered tape device name must be terminated with a colon. Message Cannot read savesets Description The installation process has been unable to read the software from the installation media.
PAGE 172
162 Appendix A F Error Messages Message Unknown installation error encountered Description An internal error has occurred. Examine sys$manager:sybase_envox_inst.log and sys$manager:inst_file.in to determine the error. A.4 PDX Dump Error Messages This subsection contains error messages that can occur during dumps by the PDX utility. A Message Tape device is not defined Description An empty string has been entered. Please enter a valid tape device.
PAGE 173
Error Messages F Appendix A Message Size is not defined Description Please enter a valid pdx file size. Message Size is invalid Description The entered size contains non-numeric characters. Message WARNING — There may not be enough disk space for PDX file Description Increase the free disk space or choose a different disk. A.5 CDOS Error and Warning Messages 163 This subsection lists the CDOS specific messages that can occur during the various stages of the CDOS installation process.
PAGE 174
164 Appendix A F Error Messages Description The UIC must be in the form: group, member, where they are OCTAL numeric values in the range: group = [0 to 37776] and member = [0 to 177776]. Message Value is not a valid number. Description An illegal value has been entered for the number of CDOS users. Enter a value within the range [1 to 32]. Message server_name already in use. Description The server name is being used by a SYBASE server and is entered in the interfaces file.
PAGE 175
Transact-ISQL Reserved Words F Appendix B 165 Figure B-Table B Appendix B B Transact-ISQL Reserved Words The following words are reserved by Interactive Structured Query Language (ISQL) as keywords (command verbs) and cannot be used for the names of database objects such as databases, tables, rules, defaults, and so forth. Reserved words are used for the names of local variables and for stored procedure parameters.
PAGE 176
166 Appendix B F Transact-ISQL Reserved Words IDENTITY_INSERT IF IN INDEX INSERT INTERSECT INTO IS ISOLATION KEY KILL LEVEL LIKE LINENO LOAD MAX MIN MIRROR MIRROREXIT B NATIONAL NOHOLDLOCK NOT NOTCLUSTERED NULL NUMERIC_TRUNCATION OF OFF OFFSETS ON ONCE ONLY OPEN OPTION OR ORDER OVER PERM PERMANENT PLAN PRECISION PREPARE PRIMARY PRINT PRIVILEGES PROC PROCEDURE PROCESSEXIT PUBLIC RAISERROR READ READTEXT RECONFIGURE REFERENCES REPLACE RESERVED_PGS RETURN REVOKE ROLE ROLLBACK ROWCNT ROWCOUNT ROWS RULE SAVE
PAGE 177
Installation and Upgrade Logs F Appendix C 167 Figure C-Table C Appendix C C Installation and Upgrade Logs This appendix lists log files for the following installation and upgrade procedures: J SYBASE Client-Only Installation Log — Subsection C.1 J SYBASE Client-Server Installation Log — Subsection C.2 J SYBASE Client-Only Upgrade Log — Subsection C.3 J SYBASE Client-Server Upgrade Log — Subsection C.4 J ENVOXr Client-Only Installation Log — Subsection C.
PAGE 178
168 Appendix C F Installation and Upgrade Logs C.1 C SYBASE Client-Only Installation Log ************************************************************* ************************************************************* ENVOX version P4.0 INSTALLATION/UPGRADE STARTED ************************************************************* sybase_envox_inst.log 6-NOV-1997 14:53:53.97 PAINTD Start of pre_menu_checks.com ---------------------------SYBASE_ENVOX_INST.LOG 6-NOV-1997 14:54:35.
PAGE 179
Installation and Upgrade Logs F Appendix C C.2 169 SYBASE Client-Server Installation Log ************************************************************* ************************************************************* ENVOX version P4.0 INSTALLATION/UPGRADE STARTED ************************************************************* sybase_envox_inst.log 4-NOV-1997 15:40:40.98 PAINTD Start of pre_menu_checks.com ---------------------------SYBASE_ENVOX_INST.LOG 4-NOV-1997 15:41:07.
PAGE 180
170 C Appendix C F Installation and Upgrade Logs The required value of SWPOUTPGCNT is 512 The current value of PQL_MPGFLQUOTA is 32768 The required value of PQL_MPGFLQUOTA is 32768 The current value of PQL_MASTLM is 200 The required value of PQL_MASTLM is 200 The current value of PQL_DASTLM is 200 The required value of PQL_DASTLM is 200 The current value of PQL_DBIOLM is 200 The required value of PQL_DBIOLM is 200 The current value of PQL_DDIOLM is 200 The required value of PQL_DDIOLM is 200 The current
PAGE 181
Installation and Upgrade Logs F Appendix C 171 removing sybase from startup files form_syb_disk_logicals creating/updating accounts creating sybase directories modifying modparams.
PAGE 182
172 Appendix C F Installation and Upgrade Logs C.3 SYBASE Client Upgrade Log ************************************************************* ************************************************************* ENVOX version P4.0 INSTALLATION/UPGRADE STARTED ************************************************************* sybase_envox_inst.log 7-NOV-1997 16:47:31.72 PAINTD Start of pre_menu_checks.com ---------------------------SYBASE_ENVOX_INST.LOG 7-NOV-1997 16:47:47.
PAGE 183
Installation and Upgrade Logs F Appendix C C.4 173 SYBASE Client--Server Upgrade Log ************************************************************* ************************************************************* ENVOX version P4.0 INSTALLATION/UPGRADE STARTED ************************************************************* sybase_envox_inst.log 25-FEB-1998 14:31:57.34 JANUS Start of pre_menu_checks.com ---------------------------SYBASE_ENVOX_INST.LOG 25-FEB-1998 14:36:57.
PAGE 184
174 Appendix C F Installation and Upgrade Logs C.5 C ENVOX Client-Only Installation Log ************************************************************* ************************************************************* ENVOX version P4.0 INSTALLATION/UPGRADE STARTED ************************************************************* sybase_envox_inst.log 6-NOV-1997 15:00:48.31 PAINTD Start of pre_menu_checks.com ---------------------------SYBASE_ENVOX_INST.LOG 6-NOV-1997 15:01:02.
PAGE 185
Installation and Upgrade Logs F Appendix C C.6 175 ENVOX Client-Server Installation Log ************************************************************* ************************************************************* ENVOX version P4.0 INSTALLATION/UPGRADE STARTED ************************************************************* sybase_envox_inst.log 4-NOV-1997 10:09:34.82 PAINTD Start of pre_menu_checks.com ---------------------------SYBASE_ENVOX_INST.LOG 4-NOV-1997 10:10:04.
PAGE 186
176 Appendix C F Installation and Upgrade Logs C.7 ENVOX Client Upgrade Log ************************************************************* ************************************************************* ENVOX version P4.0 INSTALLATION/UPGRADE STARTED ************************************************************* sybase_envox_inst.log 7-NOV-1997 17:36:28.77 PAINTD Start of pre_menu_checks.com ---------------------------SYBASE_ENVOX_INST.LOG 7-NOV-1997 17:36:44.
PAGE 187
Installation and Upgrade Logs F Appendix C C.8 177 ENVOX Client--Server Upgrade Log ************************************************************* ************************************************************* ENVOX version P4.0 INSTALLATION/UPGRADE STARTED ************************************************************* sybase_envox_inst.log 25-FEB-1998 18:06:18.72 JANUS Start of pre_menu_checks.com ---------------------------SYBASE_ENVOX_INST.LOG 25-FEB-1998 18:08:21.
PAGE 188
178 Appendix C F Installation and Upgrade Logs C.9 C ENVOX P4.0 Reload Log ************************************************************* ************************************************************* ENVOX version P4.0 INSTALLATION/UPGRADE STARTED ************************************************************* sybase_envox_inst.log 7-NOV-1997 12:02:28.77 PAINTD Start of pre_menu_checks.com ---------------------------SYBASE_ENVOX_INST.LOG 7-NOV-1997 12:04:10.
PAGE 189
Installation and Upgrade Logs F Appendix C C.10 179 SYBASE Tune Log SYBASE_TUNE.LOG 12-JAN-1998 08:04:15.79 PAINTD DEC 3000 - M300X start of sybase_tune.
PAGE 190
180 Appendix C F Installation and Upgrade Logs The required value of PQL_MFILLM is 200 The current value of PQL_MBYTLM is 100000 The required value of PQL_MBYTLM is 100000 The current value of PQL_MENQLM is 300 The required value of PQL_MENQLM is 300 The current value of PQL_MWSDEFAULT is 1136 The required value of PQL_MWSDEFAULT is 1024 The current value of PQL_DWSDEFAULT is 1136 The required value of PQL_DWSDEFAULT is 1024 The current value of PQL_MWSQUOTA is 2304 The required value of PQL_MWSQUOTA is 2
PAGE 191
Installation and Upgrade Logs F Appendix C 181 Start of inter_menu_checks.com -----------------------------Checking sylogin Checking disk Checking Y/N Checking uic Checking server name Checking TCPIP_software Checking port_number Checking interfaces Checking current cdos disks Checking cdos diskspace Checking disk Checking tape device CDOS_INST.LOG 24-JUN-1997 15:51:04.56 EMMA VAXstation 4000-60 start of inst_cdos.com ----------------------CDOS installation setup sybase & cdos logicals.
PAGE 192
182 Appendix C F Installation and Upgrade Logs C.12 C CDOS Upgrade Log ************************************************************* ************************************************************* CDOS version P2.0 INSTALLATION/UPGRADE STARTED ************************************************************* cdos_inst.log 26-FEB-1998 14:34:54.12 JANUS Start of pre_menu_checks.
PAGE 193
Installation and Upgrade Logs F Appendix C C.13 183 CDOS De-installation Log ************************************************************* ************************************************************* CDOS version P1.0 INSTALLATION/UPGRADE STARTED ************************************************************* cdos_inst.log 24-JUN-1997 16:48:28.07 PAINTD Start of pre_menu_checks.
PAGE 194
184 Appendix C F Installation and Upgrade Logs Blank page.
PAGE 195
History 185 History The list below shows the documents available for released ENVOXR software versions. ENVOX P1.0 J J J Installing ENVOX Software and Migrating PROFLEXR Data PN4.14:SW3151 (Original — July 1990) D3P00481002 Installing ENVOX Software and Migrating PROFLEX Data PN4.14:SW3151 (Change 1 — December 1990) D3P00482012 Using ENVOX Configuration Software UM4:14:SW3151 (Original + Change 1 — December 1990) D2U00481012 ENVOX P1.1 J J J Installing ENVOX Software and Migrating PROFLEX Data PN4.
PAGE 196
186 History ENVOX P2.0 J J J J Installing ENVOX Software and Migrating PROFLEX Data PN4.3:SW3151 (Revision C — October 1992) D3P00481302 ENVOX Technical Reference TR1.0:SW3151 (Revision B — September 1992) D2R00481202 ENVOX Tutor TU4.14:SW3151 (Original — June 1991) D2T00481002 Using ENVOX Configuration Software UM4:14:SW3151 (Revision C — October 1992) D2U00481302 ENVOX P3.0 J J J J Installing ENVOX Software and Migrating PROFLEX Data PN6.
PAGE 197
History J J 187 ENVOX Tutor TU4.14:SW3151 (Original — June 1991) D2T00481002 Using ENVOX Configuration Software UM6.1:SW3151 (Revision F — December 1994) D2U00481602 ENVOX P3.3 J J J J J J J Installing ENVOX Configuration Software on DEC VAX and DEC AXP systems PN6.1:SW3151:VMS (Original — June 1995) D3P01461002 Installing ENVOX Configuration Software on HP-UX Systems PN6.2:SW3153:HPX (Revision A — June 1995) D3P01381102 Installing ENVOX Configuration Software on IBM AIX Systems PN6.
PAGE 198
188 History ENVOX P4.0 J J J J J Installing and Upgrading ENVOX Configuration Software on DEC VAX and DEC AXP Systems PN6.1:SW3151:VMS (Revision B — May 1998) D3P01461202 Installing and Upgrading ENVOX Configuration Software on HP-UX Systems PN6.2:SW3153:HPX (Revision C — May 1998) D3P01381302 The System Manager’s Guide to ENVOX Configuration Software SM1.0:SW3151 (Revision E — May 1998) D3R00501502 The Technical Reference for ENVOX Configuration Software TR1.
PAGE 199
Glossary 189 Glossary Algorithm A set of logical steps to solve a problem or accomplish a task. A computer program contains one or more algorithms. Many configurations of PROVOXr systems also contain algorithms, particularly in operations, procedures, and function sequence tables. Analog Input (AI) A PROVOX point type. An analog input point receives a single analog value, the process variable. Analog Output (AO) A PROVOX point type.
PAGE 200
190 Glossary configuration consists of responding to prompts in a series of console screen displays. For other PROVOX systems, configuration consists of creating and manipulating special ASCII text files. Configuration Source File A special ASCII text file that certain PROVOX systems use for configuration. Such a source file contains instructions and reference information for the controllers and other devices in the system.
PAGE 201
Glossary Dump Device A tape or disk device to which a database and its associated transaction log can be copied to usually for backup purposes. ED Acronym: Emergency Download Emergency Download A download from a special download file while the SYBASE server is not available or if the ENVOX database is suspect. Engineering Units (EU) The units of measurement for percentage values of an analog process variable. Possible examples are gallons per hour, degrees Celsius, and pounds per square inch.
PAGE 202
192 Glossary Group A PROVOX point type. A group point controls as many as 8 DCD points so that they work in unison. A Group point uses a Group template which contains up to 16 setpoints for driving DCD point setpoints. the user defines group templates as part of system configuration. Group Display A set of 12 point templates that appear together on a PROVOX console screen, so that an operator can see at a glance the most important information about 12 different points.
PAGE 203
Glossary Logical Device A designated area on a disk for databases and transaction logs. A database and its associated transaction log should be on separate physical devices, if possible. Logical devices are used on VMS systems, AIX systems, and some HP systems. Logical Volume Designated areas mapped by the operating system across one or more disks for databases and transaction logs. Logic Control Point (LCP) A PROVOX point type for an advanced batch or multifunction controller, such as a UOC or IFC.
PAGE 204
194 Glossary Plant Management Area (PMA) A collection of plant process areas (PPAs). A PMA controls the console point reporting load, and indirectly, central processing unit (CPU) loading. Plant Process Area (PPA) Within a process-control system, a collection of equipment that uses a common alarm strategy. PMA Acronym: Plant Management Area Point A set of process-control parameters and data.
PAGE 205
Glossary Setpoint (SP) An input variable that contains the desired value for a process variable. Control loop algorithms compare the process variable with the setpoint, to determine an appropriate output. Signal Value Analog (SVA) The analog floating point portion of the accumulator register in a controller FST. Signal Value Discrete (SVD) The discrete portion of the accumulator register in a controller FST.
PAGE 206
196 Glossary Tuning Parameter A parameter adjustable without reconfiguration; an operator adjusts such a parameter to alter control effects. Common examples are gain, rate, reset, and alarm trip points. Such parameters appear in detail displays. Unit 1. A defined group of specific process equipment that processes a particular batch. For control purposes, such a unit is one entity. 2. A PROVOX point type. A unit point has many attributes, enabling it to control the execution of a unit operation.
PAGE 207
Index 197 Index Symbols A “How do I ...
PAGE 208
198 Index booting standalone backup, VAX disk, 90 booting standalone backup, VAX tape, 90 booting the backup routine, 91 booting the backup utility, AXP, 91 bug fixes, 13 C CDOS de--installation log file, 183 error messages, 163 installation log file, 180 warning messages, 163 CDOS configuration file, 143, 148 CDOS log file, 117, 143, 148 CDOS port number, 125 CDOS software, replacing pre-release version, 117 character limit, open database name, 40 CHIP software and disk space requirements AXP system, 17
PAGE 209
Index reading installation script from media, 28, 34, 42, 45, 82 reading PDX utility, 57 reading PDX utility from media, 56 rebooting the system, 93, 95 restore system, 94 restoring from logical devices, 94 retrieving files from the installation tape, 100 running the isql utility, 51 SCSI ECO kit ftp transfer, 24 SCSI ECO kit installation, 23 SCSI ECO kit recovery from CDROM, 24 second disk initialization, 26 setting up ENVOX user directory, 88 sybase installation, 28 sybase installation script, 28 sybase
PAGE 210
200 Index DH6009, 13 DH6021, 13 DH6032, 13 DH6215/DH6219, 13 sybase client--only, 35 sybase client--server, 29 entering time and date, backup process, 91 disk mount command line position, 26 ENVOX client--only installation, 45 client--server installation, 42 installation script, 40 disk space usage, CDOS, 116 ENVOX account screen, 86 disk usage, 14, 16 ENVOX admin forms, 132 display list of device names, 91 ENVOX and sybase database, dumping quantity limit, 52 directories deleted and created dur
PAGE 211
Index 201 ENVOX_user account screen, 86 ENVOXSUPPORT account UIC code, 43, 46 H envoxutility account, 131 handling personal files during upgrade, 51 envoxutility password, 131 hardware requirements DEC AXP workstation versions, 12 DEC VAX workstation versions, 12 highway interface, 13 error and warning messages, CDOS occurrence, 118 error messages, 149 CDOS, 163 ENVOX software, 157–158 PDX dump, 162 SYBASE software, 151–152 error or warning messages, display, 27, 41, 53 help with your installation,
PAGE 212
202 Index sybase, 27 installations precautions, 20, 50 installing on other platforms, 12 interfaces file, 117, 120, 123, 126, 130, 140 isql, 131 ISQL reserved words, 165 isql utility command, 51 CDOS installation, 180 ENVOX software client upgrade, 176, 178, 179 client-server installation, 175 client-only installation, 174 SYBASE, client upgrade, 172 Sybase, client-server installation, 169 Sybase software, client-only installation, 168 logging in as system manager, 21, 22, 23, 26 logical devices, backup
PAGE 213
Index loading data, 110 location on tape, 57 reading from media, 56 running, 110 multinet installation, 119 N PDX utility read command, 57 non--ENVOX databases dumping, 109 upgrading, 49 using PDX utility, 52 using text files, 109 performance improvement, 14, 16 memory allocation, 31 PDX utility with non_ENVOX databases, 109 personal files, handling during upgrade, 51 null password, changed by system, 74 port number, interfaces file, 120, 148 number of ENVOX users, 103 port numbers, CDOS, 125 n
PAGE 214
204 Index restoring from logical devices, 94 special attention getters, 6 return key use for commands, 5 use for navigation, 27, 40, 53 starting multinet at bootup, 136 reverse video, 27, 41, 53 suggesting changes, 9 revision control of manual, 4 sybase client--only installation, 34 client--server installation, 28 installation script, 27, 53 S sa account, 131 sa password, 131 savesets, stored on installation tape, 99 screen dumps, printer selection, 30, 36 scripts ENVOX installation, 40 upgrade, 5
PAGE 215
Index sysgen parameters, location, 30, 36 SYSTARTUP_VMS.COM, 29, 35 system backup creating the routine, 89 importance, 80, 89 importance of, 20 system disk AXP, 16 VAX, 14 system navigator window, upgrading databases, 130 system performance, effect by users, 106 system performance improvement, 14, 16 205 third party software, TCP/IP communication, 116 time, backup process, 93 time and date, backup process, 91 time de--installation, 97 TK50 tape, 11 TK50 tapes, Vol.
PAGE 216
206 Index users, effect on system performance, 106 volume labels, 93 users cleared from target database, 74 using other platforms, 12 using return key for commands, 5 W warning message, definition, 111 V warning messages, CDOS, 163 validation checks, 111 verifying multinet installation, 119 verifying node and address name, 37 Y VMS quotas, settings, 148 year 2000 ECO kit determining existence, 22 installation, 22 VMS system resources list, 104 year 2000 ECO kit, 22 verifying ucx installation,
PAGE 217
Notes 207 Notes Installing and Upgrading ENVOXr Configuration Software on DEC VAX and DEC AXP Systems (Revision B — May 1998)
PAGE 218
208 Notes Notes Installing and Upgrading ENVOXr Configuration Software on DEC VAX and DEC AXP Systems (Revision B — May 1998)
PAGE 219
Blank page.
PAGE 220
PN6.