C InfoServer_Monitor____________________________2 Installation and User's GuideD This manual explains how to install and use theC InfoServer Monitor, a sample system management; application for the InfoServer system.> InfoServer Monitor software is written inD VAX BASIC, utilizing system service and libraryH calls to obtain device information and mount disks.F Users are free to modify the supplied source code8 to suit environment-specific needs.A InfoServer Monitor software is not supportedD by Digitial Equipment Corporation. However, theH software has been tested and performs the functions. described in this manual.G Revision/Update Information: This is a new manual.E Operating System and Version: VMS Version 5.4 or7 laterD Software Version: InfoServer Monitor= Version 1.3  H __________________________________________________________ November 1992C The information in this document is subject to changeH without notice and should not be construed as a commitmentA by Digital Equipment Corporation. Digital EquipmentG Corporation assumes no responsibility for any errors that* may appear in this document.H The software described in this document is furnished underD a license and may be used or copied only in accordance- with the terms of such license.3 © Digital Equipment Corporation 1992.? The following are trademarks of Digital Equipment> Corporation: DEC, DIGITAL, OpenVMS, VAX, and the DIGITAL logo.D This document was prepared using VAX DOCUMENT, Version 2.0.  E ________________________________________________________________E ContentsE Preface.................................................. v& 1 InfoServer Monitor DescriptionE 1.1 Devices Selected and Actions Taken.............. 1-2E 1.2 Event Logging................................... 1-3E 1.3 InfoServer Monitor Files........................ 1-4. 2 Installing InfoServer Monitor SoftwareE 2.1 Disk Space Requirements......................... 2-1E 2.2 Disk Mounting Requirements...................... 2-1E 2.3 Installation Procedure.......................... 2-1E 2.3.1 Installation Questions ....................... 2-2E 2.3.2 Informational Messages ....................... 2-3E 2.3.3 Completing the Installation Procedure ........ 2-4E 2.3.4 Error Recovery ............................... 2-44 3 After Installing InfoServer Monitor Software9 3.1 Starting InfoServer Monitor from the SystemE Startup Procedure............................... 3-1E 3.2 Service Names................................... 3-1 A Sample InstallationE iii  Index ExamplesH 1-1 InfoServer Monitor Log File .................. 1-3 TablesH 1-1 InfoServer Monitor Files ..................... 1-5 iv  H ________________________________________________________________H Preface Purpose of This GuideC This guide explains how to install and use InfoServerA Monitor software on processors that are running the' OpenVMS operating system.E Keep this document with your distribution kit. You willD need it to install maintenance updates or to reinstall6 InfoServer Monitor for any other reason. Intended AudienceF This guide addresses the system manager who installs and/ uses InfoServer Monitor software. Document Structure1 This guide is organized as follows:B o Chapter 1 describes InfoServer Monitor functions.D o Chapter 2 describes installation and error recovery procedures.B o Chapter 3 describes post-installation procedures.D o Appendix A shows an installation procedure listing. Related DocumentsC The following documents provide information about the InfoServer system:3 o InfoServer System Operations Guide> o InfoServer 100 Installation and Owner's GuideH v  > o InfoServer 150 Installation and Owner's Guide? o InfoServer Client for OpenVMS Utilities Manual Conventions? The following conventions are used in this guide:B UPPERCASE TEXT Uppercase letters indicate that youA must enter a command (for example,6 @SYS$UPDATE:VMSINSTAL).G system output This typeface is used in interactive andG code examples to indicate system output.H boldface text This bold typeface is used in interactiveE examples to indicate typed user input.A In procedures, a key name is shownD enclosed to indicate that you press a3 key on the keyboard. vi  H 1H ________________________________________________________________H InfoServer Monitor DescriptionF InfoServer services can become inaccessible for a number of reasons:F o A compact disc is replaced with a new disc that has a( different volume label.H When compact discs are routinely updated (for instance,E Online Documentation Library Discs, OpenVMS softwareF kits) the volume label changes with each new version.F The InfoServer Monitor regularly checks volume labels@ and remounts disks using the new volume labels.@ o Connection is broken between OpenVMS client and" InfoServer systemG This condition can be caused by network failure, powerC outage, or by rebooting the InfoServer system. TheH InfoServer Monitor ensures that all InfoServer services1 are remounted after such events.A o Data has been written to an InfoServer hard diskH When an InfoServer hard disk is accessed for write, allC read connections are terminated. These connectionsA must be manually reestablished using the OpenVMSG command MOUNT. The InfoServer Monitor regularly checksF InfoServer hard disks and remounts any disks that areE found to be inaccessible because of a previous write access.H The InfoServer Monitor ensures that all InfoServer devicesC remain accessible to users when such events occur. AsD described in Section 1.1, the Monitor takes actions onH specific devices and creates a log file like that shown in Example 1-1.H 1-1  & InfoServer Monitor DescriptionD The Monitor runs as a detached process on each OpenVMSB node on which InfoServer disk access is desired. TheA process is usually created during system startup by? running the InfoServer Monitor startup procedure.H InfoServer services must be bound (using the OpenVMS LADCPD utility) but do not need to be mounted. The InfoServer7 Monitor can handle all mounting of disks.. 1.1 Devices Selected and Actions TakenG A device is selected for InfoServer Monitor action if all- the following criteria are met:1 o The device name begins with DAD.D On OpenVMS systems, all InfoServer compact disc and7 hard disk device names begin with DAD.) o The device is read-only.B A writable InfoServer device is one that has beenE created with the LADCP command BIND /WRITE. MountingB such a device would disconnect all read access toB the service mounted under another device name, soD the device should never be mounted systemwide. ThisE condition would exist if someone had bound a serviceG for write and had not yet mounted it or had logged off- before unbinding the device.- o The device is not allocated.E The InfoServer Monitor ignores any InfoServer device3 that is allocated to another user.E If these criteria are met, the InfoServer Monitor takes$ the following actions:F o If the device is mounted, InfoServer Monitor attempts@ a read of the device to determine whether it is accessible.F - If the read fails, InfoServer Monitor remounts the7 device with the known volume label.D - If the remount fails because the volume label isD different, the device is mounted to find the newE volume label and then mounted systemwide with the% new volume label. 1-2  H InfoServer Monitor DescriptionH 1.1 Devices Selected and Actions TakenE o If the device is not mounted, the disk is mounted toC find the volume label and then mounted systemwide.E By default, InfoServer Monitor checks devices every tenF minutes. If you want to change this interval, define theC system logical name INFO_INTERVAL to be the number ofB minutes between checks. For example, if you want theD Monitor to check every two minutes, define the logical name as follows:- $ DEFINE/SYSTEM INFO_INTERVAL 2E Note that because the Monitor checks the value of INFO_D INTERVAL after each cycle, you can change the interval= without having to stop and restart the Monitor. 1.2 Event LoggingH InfoServer Monitor records device mounting and dismounting> activity in a log file like that in Example 1-1.5 Example 1-1 InfoServer Monitor Log File( InfoServer Monitor V1.3 1E 28-FEB-1992 13:52:37 CDDOC02JAN21 mounted on _DAD2: 2B 28-FEB-1992 13:52:48 CDDOC02JAN22 mounted on _DAD3:A 28-FEB-1992 13:52:55 VMS_DOCS_HD mounted on _DAD4:B 28-FEB-1992 13:53:03 CDBIN02JAN21 mounted on _DAD5:B 28-FEB-1992 13:53:13 CDBIN02JAN22 mounted on _DAD6:B 28-FEB-1992 13:53:20 CDBIN02JAN23 mounted on _DAD7:B 28-FEB-1992 13:53:26 CDBIN02JAN24 mounted on _DAD8:B 28-FEB-1992 13:53:32 VMS_KITS_HD1 mounted on _DAD9:C 28-FEB-1992 13:53:38 VMS_KITS_HD2 mounted on _DAD10:C 28-FEB-1992 13:53:45 NETWORK_DATA mounted on _DAD11:H (continued on next page)H 1-3  & InfoServer Monitor Description 1.2 Event Logging= Example 1-1 (Cont.) InfoServer Monitor Log FileI 29-FEB-1992 06:04:46 VMS_DOCS_HD dismounted from _DAD4: 3A 29-FEB-1992 06:04:50 VMS_DOCS_HD mounted on _DAD4:I 11-MAR-1992 19:15:17 CDBIN02JAN21 dismounted from _DAD5: 4B 11-MAR-1992 19:15:28 CDBIN04MAR21 mounted on _DAD5:G 11-MAR-1992 19:15:43 CDBIN02JAN22 dismounted from _DAD6:B 11-MAR-1992 19:16:12 CDBIN04MAR22 mounted on _DAD6:G 11-MAR-1992 19:16:27 CDBIN02JAN23 dismounted from _DAD7:B 11-MAR-1992 19:16:48 CDBIN04MAR23 mounted on _DAD7:G 11-MAR-1992 19:17:03 CDBIN02JAN24 dismounted from _DAD8:B 11-MAR-1992 19:17:23 CDBIN04MAR26 mounted on _DAD8:C 1 InfoServer Monitor software version running on the system.F 2 The next ten lines show ten InfoServer devices, boundA with LADCP during system startup, that are being3 mounted by the InfoServer Monitor.E 3 These two lines show an InfoServer hard disk serviceE being dismounted and remounted after a write access.B 4 The remaining lines show four compact discs beingF remounted with new volume labels after a new versionsG of OpenVMS Consolidated Distribution compact discs are- placed in InfoServer drives.$ 1.3 InfoServer Monitor FilesF Table 1-1 lists files included in the InfoServer Monitor- kit and created on your system. 1-4  H InfoServer Monitor DescriptionH 1.3 InfoServer Monitor FilesH Table_1-1_InfoServer_Monitor_Files________________________H File____________________________Description_______________C INFOSERVER_MONITOR.BAS+ VAX BASIC source codeF INFOSERVER_MONITOR.COM+ ++ DCL command procedure to9 run MonitorC INFOSERVER_MONITOR.EXE++ Executable InfoServer5 MonitorG INFOSERVER_MONITOR.LOG++ Log of Monitor activitiesD INFOSERVER_MONITOR.INCLUDE+ VAX BASIC include fileC INFOSERVER_MONITOR.OBJ+ VAX BASIC object codeF INFOSERVER_MONITOR_STARTUP.COM+ DCL command procedure toE ++ start Monitor at system5 startupD KITINSTAL.COM+ VMSINSTAL installation7 procedureH +Included_in_kit__________________________________________! ++Created on systemH __________________________________________________________F If you want to modify source code files, you can extractE the files from the savset supplied in the [INFOMON.KIT] directory.H 1-5  H 2H ________________________________________________________________G Installing InfoServer Monitor SoftwareC This chapter describes installation prerequisites andB explains how to install InfoServer Monitor software.# 2.1 Disk Space RequirementsG Installing the Monitor requires 27 blocks of disk storageH on the system disk. Additional minimal space is needed forF the log file after the Monitor starts to run. Space usedF by the log file depends on how much activity the MonitorC performs but would typically be a few blocks per day.& 2.2 Disk Mounting RequirementsA If you mount InfoServer devices before starting theH InfoServer Monitor, specifiy the /NOMOUNT_VERIFY qualifierB to the OpenVMS command MOUNT. This qualifier enablesH quick determination of which devices need to be remounted.E The InfoServer Monitor always mounts devices with mount$ verification disabled." 2.3 Installation Procedure@ The installation procedure consists of a series ofG questions and informational messages and should take less than five minutes.A To start the installation, you invoke the VMSINSTALF command procedure from a privileged account, such as the SYSTEM account.D To abort the installation procedure at any time, pressG Ctrl/Y. When you press Ctrl/Y, the installation procedureC deletes all files it has created up to that point and? exits. You can then start the installation again.H 2-1  . Installing InfoServer Monitor Software" 2.3 Installation ProcedureB The following example displays the command to invokeE VMSINSTAL to install InfoServer Monitor from tape drive, MUA0: and the system response.% $ @SYS$UPDATE:VMSINSTALJ VAX/VMS Software Product Installation Procedure Vn.n-n) It is dd-mmm-yyyy at hh:mm.= Enter a question mark (?) at any time for help.$ 2.3.1 Installation QuestionsE This section discusses the questions that appear duringH the installation. See Appendix A for a sample installation procedure.A Each question in the installation is marked with anG asterisk (*) at the beginning of the line. Some questionsG show the default response in brackets, for example [YES].H If you want to give the default response, press the RETURN key. 1 System backupE VMSINSTAL asks if you are satisfied with your systemE backup. If you are satisfied with the backup of yourB system disk, press RETURN. Otherwise, enter NO toA discontinue the installation. Because only threeA files are added to the system startup directory,C there is no need to perform a system backup before" the installation.O * Are you satisfied with the backup of your system disk [YES]? 2 Device nameH The device where the InfoServer Monitor kit is located.F Specify the tape name or disk and directory where theD kit is located. You may also specify a logical nameC pointing to that device or directory. For example,F if the InfoServer Monitor kit is on InfoServer device3 DAD2, use DAD2 as the device-name.G * Where will the distribution volumes be mounted: DAD2 3 Product nameH Enter the name of the product you are installing. Enter INFOMON. 2-2  G Installing InfoServer Monitor SoftwareH 2.3 Installation ProcedureF VMSINSTAL displays the list of products that you have chosen.[ Enter the products to be processed from the first distribution volume set:$ * Products: INFOMON 4 OptionsE For information on additional VMSINSTAL options, seeD the OpenVMS documentation on Software Installation.1 o Choosing installation optionsQ * Enter installation options you wish to use (none): D VMSINSTAL now begins the installation procedure.= The following products will be processed:" INFOMON Vn.nG Beginning installation of INFOMON Vn.n at hh:mmH %VMSINSTAL-I-RESTORE, Restoring product saveset A...( o Choosing to purge filesA You have the option to purge files from previousC versions of InfoServer Monitor that are supersededG by this installation. Purging is recommended; however,E if you need to keep files from the previous version,6 enter NO in response to the question.[ * Do you want to purge files replaced by this installation [YES]? $ 2.3.2 Informational MessagesB At this point, the installation procedure displays aA number of informational messages that report on the@ progress of the installation. There are no further? questions. If the installation procedure has beenE successful up to this point, VMSINSTAL moves the new orE modified files to their target directories and displays% the following messages:\ %VMSINSTAL-I-MOVEFILES, files will now be moved to their target directories...H 2-3  . Installing InfoServer Monitor Software" 2.3 Installation Procedure3 2.3.3 Completing the Installation ProcedureG The following messages indicate that the entire installa-) tion procedure is complete:@ Installation of INFOMON Vn.n completed at hh:mm2 VMSINSTAL procedure done at hh:mm< You can now log out of the privileged account: $ LOGOUT> SYSTEM logged out at dd-mmm-yyyy hh:mm:ss.ss 2.3.4 Error Recovery@ If errors occur during the installation, VMSINSTAL5 displays the following failure message:P %VMSINSTAL-E-INSFAIL, The installation of INFOMON Vn.n has failed.D Errors can occur during the installation if any of the) following conditions exist:; o The operating system version is incorrect.> o A prerequisite software version is incorrect.A o Quotas necessary for successful installation are insufficient.H o System parameter values for successful installation are insufficient.G For descriptions of the error messages generated by theseA conditions, see the OpenVMS documentation on systemA messages, recovery procedures, and OpenVMS softwareA installation. If you are notified that any of theseF conditions exist, you should take the appropriate actionF as described in the message. For example, you might needD to change a system parameter or increase an authorized quota value. 2-4  H 3H ________________________________________________________________H After Installing InfoServer Monitor SoftwareA This chapter describes operations you perform after5 installing InfoServer Monitor software.? 3.1 Starting InfoServer Monitor from the System Startup ProcedureF The InfoServer Monitor installation procedure starts theG Monitor but does not provide for automatic startup of the/ Monitor when your system reboots.G The InfoServer Monitor installation places the InfoServerH Monitor system startup file INFOSERVER_MONITOR_STARTUP.COME in the SYS$MANAGER directory. To start the Monitor with5 each system reboot, proceed as follows:E o If you start up your system with the SYSMAN utility,. enter the following commands:( $ RUN SYS$SYSTEM:SYSMANT SYSMAN> STARTUP ADD FILE SYS$MANAGER:INFOSERVER_MONITOR_STARTUP.COM SYSMAN> EXITR o Otherwise, add the following line to SYS$MANAGER:SYSTARTUP_V5.COME or the appropriate startup command procedure at your site:: $ @SYS$MANAGER:INFOSERVER_MONITOR_STARTUP 3.2 Service NamesE By default, the InfoServer system creates service namesD for most volumes, using the volume label (for example,E CDDOC04MAR21) as the service name. Specifying a genericF service name for the volume (for example, VMSDOC) allowsD the same service name to be used when the volume labelE changes. See the InfoServer System Operations Guide for; information about the CREATE SERVICE command.H 3-1  4 After Installing InfoServer Monitor Software 3.2 Service NamesB When used in conjunction with generic service names,D InfoServer Monitor frees you from the need to know the6 volume labels of any InfoServer devices.H To take advantage of this feature, remove from your systemB startup procedure any commands that mount InfoServer@ devices. Because the Monitor mounts all InfoServerF devices it finds, you need only enter LADCP BIND /SYSTEME commands. This feature saves time during system startupH and eliminates the need to hard-code volume labels in your( system startup procedures. 3-2  H AH ________________________________________________________________H Sample Installation% $ @SYS$UPDATE:VMSINSTALJ VAX/VMS Software Product Installation Procedure V5.5( It is 6-MAR-1992 at 12:35.= Enter a question mark (?) at any time for help.L %VMSINSTAL-W-ACTIVE, The following processes are still active: NIXON FORD CARTER REAGAN BUSH6 * Do you want to continue anyway [NO]? YU * Are you satisfied with the backup of your system disk [YES]? Z * Where will the distribution volumes be mounted: kits:[infomon013] X Enter the products to be processed from the first distribution volume set.! * Products: infomonK * Enter installation options you wish to use (none): 7 The following products will be processed: INFOMON V1.3E Beginning installation of INFOMON V1.3 at 12:36D %VMSINSTAL-I-RESTORE, Restoring product save set A ...X * Do you want to purge files replaced by this installation [YES]? B All questions necessary for the installation8 of INFOMON V1.3 have been answeredB %INFOMON-I-LINK, Linking InfoServer Monitor image...H A-1   Sample InstallationT The following command should be inserted in the system startupW command procedure SYS$MANAGER:SYSTARTUP_V5.COM or the appropriate6 command procedure for your site:E @SYS$MANAGER:INFOSERVER_MONITOR_STARTUPM Or, you may use SYSMAN to start the InfoServer Monitor:5 $ RUN SYS$SYSTEM:SYSMANU SYSMAN> STARTUP ADD FILE INFOSERVER_MONITOR_STARTUP.COM* SYSMAN> EXIT% %VMSINSTAL-I-MOVEFILES,L Files will now be moved to their target directories..., Starting InfoServer Monitor...K %RUN-S-PROC_ID, identification of created process is 00004EBBE Installation of INFOMON V1.3 completed at 12:38W Enter the products to be processed from the next distribution volume set." * Products: 7 VMSINSTAL procedure done at 12:38 A-2  E ________________________________________________________________E Index? C Installation (cont'd)> ___________________________ sample listing, A-18 Check interval starting, 2-1; adjusting, 1-3 time needed, 2-1E D__________________________ M__________________________7 Device Messages, 2-3< actions taken, 1-2 MOUNT command, 2-1B mounting, 2-1 mount verification, 2-1D selection criteria, 1-2 /NOMOUNT_VERIFY qualifier3 Disk , 2-1? mounting, 2-1 Mounting devices, 2-1 Disk space requirements,E 2-1 S__________________________; E Service name, 3-1E ___________________________ Starting InfoServer Monitor1 Error recovery, 2-4 , 3-1 Event logging, 1-3E F V__________________________; ___________________________ Volume label, 3-1 Files included in kit, 1-4 I__________________________ Installation aborting, 2-1 completing, 2-4 disk mounting requirements, 2-1 disk space requirements, 2-1 questions, 2-2E Index-1