Multimedia Services for OpenVMS Alpha Installation Guide Order Number: AA-QN8KB-TE July 1996 This guide describes how to install the Multimedia Services for OpenVMS Alpha run-time environment and the developer's kit on AlphaStation workstations running the OpenVMS Alpha operating system. Revision/Update Information: This document supercedes the Multimedia Services OpenVMS Alpha Installation Guide, Version 1.4. Operating System: OpenVMS Alpha Version 6.2 or higher Software Version: MMS Version 2.0 for OpenVMS Alpha Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ July 1996 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. © Digital Equipment Corporation 1995, 1996. All rights reserved. The postpaid Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: Alpha, AlphaStation, Bookreader, CDA, DDIF, DEC, DECpresent, DECvoice, DECwindows, DECwrite, Digital, Digital UNIX, LiveLink, NAS, OpenVMS, POLYCENTER, TURBOchannel, VAX, VAX DOCUMENT, VMScluster, and the DIGITAL logo. The following are third-party trademarks: Microsoft is a registered trademark and Windows and Windows NT are trademarks of Microsoft Corporation. PostScript is a registered trademark of Adobe Systems Incorporated. This document is available on CD-ROM. This document was prepared using VAX DOCUMENT Version 2.1. ________________________________________________________________ Contents Preface.................................................. vii 1 Preparing for Multimedia Services for OpenVMS Installation 1.1 Registering Your Software License ........... 1-1 1.2 Required Operating System Components and Software..................................... 1-2 1.3 Special Checks and Requirements for Installing Multimedia Services Version 2.0 for OpenVMS Alpha............................ 1-2 1.4 Installation Requirements.................... 1-3 1.4.1 Privileges............................... 1-3 1.4.2 Process Account Quotas................... 1-3 1.4.3 System Parameters........................ 1-4 1.4.4 Disk Space............................... 1-5 1.4.5 Backing Up Your System Disk.............. 1-6 1.5 Standard System Maintenance Procedures....... 1-6 1.5.1 Checking and Setting Process Account Quotas................................... 1-6 1.5.2 Checking System Parameter Values......... 1-7 1.5.3 Calculating the Values for Global Pagelets and Global Sections............. 1-7 1.5.4 Changing System Parameter Values with AUTOGEN.................................. 1-8 1.5.5 Setting Dynamic Parameter Values......... 1-9 iii 2 Installing Multimedia Services for OpenVMS Alpha 2.1 Preparing to Install Multimedia Services V2.0 for OpenVMS Alpha............................ 2-1 2.1.1 Extracting and Printing the Product Release Notes............................ 2-1 2.2 Software Installation Overview............... 2-2 2.2.1 Software Kit Names....................... 2-2 2.2.2 Starting the Installation................ 2-3 2.2.2.1 Displaying the Copyright Message....... 2-4 2.2.2.2 Determining System Information......... 2-4 2.2.2.3 Verifying Sufficient Allocation for the GBLPAGES Value......................... 2-4 2.2.2.4 Rebooting the System................... 2-4 2.2.2.5 Installing the Product................. 2-5 2.2.2.6 Continuing the Installation............ 2-5 2.2.2.7 Executing the Installation Procedure... 2-6 2.3 Recovering from Errors....................... 2-7 3 After Installation 3.1 Running the IVP Separately from Installation................................. 3-1 3.2 Editing the System Files..................... 3-2 3.3 Modifying System Parameters.................. 3-3 3.4 Making the Product Usable on a VMScluster System....................................... 3-3 3.5 Setting User Account Requirements............ 3-4 3.5.1 Privileges............................... 3-4 3.5.2 User Account Quotas...................... 3-4 A Sample Listings A.1 Sample Installation Dialog .................. A-1 A.2 Sample Installation Verification Procedure... A-2 iv B Files Installed on Your System B.1 Installed Files.............................. B-1 B.2 Logical Names................................ B-6 C Recovering from Errors C.1 Failures During Product Installation ........ C-1 C.2 Failures During Product Use.................. C-1 Tables 1-1 Process Account Quotas for the Installing Account.................................. 1-4 1-2 Minimum Required System Parameter Values................................... 1-5 1-3 Disk Space Requirements.................. 1-5 v ________________________________________________________________ Preface This guide contains instructions for installing the Multimedia Services for OpenVMS Alpha run-time environment and Multimedia Services for OpenVMS Alpha development kit on AlphaStation workstations running the OpenVMS operating system. The installation procedure installs all files in subdirectories under the following directories: SYS$COMMON:[SYS$LDR] SYS$COMMON:[SYSEXE] SYS$COMMON:[SYSLIB] SYS$COMMON:[SYSHLP.EXAMPLES.MMOV] SYS$COMMON:[MMOV_INCLUDES] Keep this guide with your distribution kit. You will need it to install maintenance updates or to reinstall Multimedia Services for OpenVMS Alpha, if necessary. Intended Audience This guide is for OpenVMS system managers and others who install layered products on OpenVMS systems. In addition, system managers must have experience with the following OpenVMS utilities: o System Generation utility (SYSGEN) o Authorize utility (AUTHORIZE) The release notes are intended for all users of Multimedia Services for OpenVMS Alpha. The release notes are located in: SYS$HELP:MMOV-V2_0.RELEASE_NOTES vii Document Structure This document contains the following: Chapter 1 describes the hardware and software requirements for Multimedia Services for OpenVMS Alpha installation and related procedures that you must complete before installing Multimedia Services for OpenVMS Alpha. Chapter 2 describes how to install Multimedia Services for OpenVMS Alpha. Chapter 3 describes the Installation Verification Procedure (IVP), how to remove Multimedia Services for OpenVMS Alpha from your system, and the files that you need to run Multimedia Services for OpenVMS Alpha applications. Appendix A contains sample listings for interactive Multimedia Services for OpenVMS Alpha installation and Installation Verification Procedure. Appendix B lists the files installed for Multimedia Services for OpenVMS Alpha on your system. Related Documents For more information on: o Installing OpenVMS layered products, see the OpenVMS installation guide for your processor o OpenVMS system management, see the OpenVMS System Manager's Manual o OpenVMS system disk backup, see the OpenVMS System Management Utilities Reference Manual o Using the License Management Facility, see the OpenVMS License Management Utility Manual o Motif, see the OpenVMS DECwindows Motif Installation Guide viii Conventions This document uses the following conventions: Every use of Multimedia Services for OpenVMS means Multimedia Services Version 2.0 for OpenVMS Alpha. Convention Description boldface Boldface text indicates data structures, text data types, and field names, and user input in interactive examples. New terms also appear in boldface text the first time they are introduced. italic text Italic text indicates function arguments and emphasizes important information. monospaced Monospaced type is used in code segments type and programming examples, and to indicate function names and chunk names. literalString Literal strings that appear in text, examples, and syntax descriptions must be entered exactly as shown. Multimedia Services for OpenVMS Alpha Documentation In addition to this guide, the Multimedia Services for OpenVMS Alpha documentation set includes the following: o The Multimedia Services for OpenVMS Alpha Programmer's Guide, which contains information about using the Multimedia Services for OpenVMS Alpha application programming interface (API) to develop applications that use multimedia features. o The Multimedia Services for OpenVMS Alpha Run-Time Environment Guide, which contains instructions for using the utilities included in the Multimedia Services for OpenVMS Alpha run-time-only environment. The run-time-only environment is bundled free with all Alpha workstations running the OpenVMS Alpha operating system. ix o The Multimedia Services for OpenVMS Alpha Release Notes, which are installed during the software installation. The release notes contain information that you may need before developing programs using the Multimedia Services for OpenVMS Alpha API. The release notes are located in: SYS$HELP:MMOV-V2_0.RELEASE_NOTES x 1 ________________________________________________________________ Preparing for Multimedia Services for OpenVMS Installation 1.1 Registering Your Software License If you are installing Multimedia Services Version 2.0 for OpenVMS Alpha on a newly licensed node or cluster, you must first register a License Product Authorization Key (License PAK) using the License Management Facility (LMF). The License PAK may be shipped along with the kit if you ordered the license and media together; otherwise, it is shipped separately to a location on your license order. If you are installing Multimedia Services Version 2.0 for OpenVMS Alpha as an update on a node or cluster already licensed for this software, you must register the Service Update PAK (SUP) that is included in your Service Update Kit. If you already registered a License PAK or a SUP for this product on this node or cluster, you do not need to register the SUP. If you are installing an update of Multimedia Services Version 2.0 for OpenVMS Alpha but lack a service contract, call your Digital representative for instructions on how to get a License PAK. If you are installing prerequisite or optional software along with Multimedia Services Version 2.0 for OpenVMS Alpha, review the PAK status and install the PAKs for any prerequisite or optional software before you install Multimedia Services Version 2.0 for OpenVMS Alpha. You must register and load your license for Multimedia Services Version 2.0 for OpenVMS Alpha before you start the installation in order to run the Installation Verification Procedure (IVP) and use the software. Preparing for Multimedia Services for OpenVMS Installation 1-1 Preparing for Multimedia Services for OpenVMS Installation 1.1 Registering Your Software License To register a license under the OpenVMS operating system, first log in to the system manager's account, SYSTEM. You then can choose one of two ways to perform the registration: o Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your License PAK. o At the DCL prompt, enter the LICENSE REGISTER command with the appropriate qualifiers that correspond to License PAK information. If you plan to use Multimedia Services Version 2.0 for OpenVMS Alpha on more than one node in a VMScluster system, you need to perform a license load on the other nodes after you complete this installation. For complete information on using the LMF, see the OpenVMS License Management Utility Manual. 1.2 Required Operating System Components and Software The OpenVMS operating system comes with a variety of support options, or classes. Classes include such features as networking and RMS journaling. Multimedia Services Version 2.0 for OpenVMS Alpha requires OpenVMS Alpha Version 6.2 or higher. If you are installing any device options or the multimedia development kit, you need both the OpenVMS required save set and the programming support save set. For a complete list of the required classes, see the Software Product Description (SPD). The SPD contains a complete list of prerequisite and optional software and their required version numbers. 1.3 Special Checks and Requirements for Installing Multimedia Services Version 2.0 for OpenVMS Alpha The product "DEC AXPVMS VMS V6.2" must be registered in the POLYCENTER software installation database. To determine if the product is registered, enter the following command line: $product show product 1-2 Preparing for Multimedia Services for OpenVMS Installation Preparing for Multimedia Services for OpenVMS Installation Installing Multimedia Services Version 2.0 for OpenVMS Alpha If the product is not registered, use the following command: $product register product VMS/source=SYS$COMMON:[000000] 1.4 Installation Requirements This section describes the requirements for installing Multimedia Services Version 2.0 for OpenVMS Alpha (process account quotas, system parameters, disk space, and so on). Standard procedures for checking and setting various parameters are described in Section 1.5. 1.4.1 Privileges To install Multimedia Services Version 2.0 for OpenVMS Alpha, you must be logged in to an account that has SETPRV or at least the following privileges: o CMKRNL o WORLD o SYSPRV 1.4.2 Process Account Quotas The account you use to install Multimedia Services Version 2.0 for OpenVMS Alpha must have sufficient quotas to enable you to perform the installation. Table 1-1 summarizes the requirements. Preparing for Multimedia Services for OpenVMS Installation 1-3 Preparing for Multimedia Services for OpenVMS Installation 1.4 Installation Requirements Table 1-1 Process Account Quotas for the Installing Account ___________________________________________________________ Account Quota Value ___________________________________________________________ ASTLM 250 BIOLM 150 BYTLM 64,000 DIOLM 150 ENQLM 2000 FILLM 100 PGFLQUO 50,000 PRCLM 10 JTTQUOTA 4096 WSEXTENT 16,400 WSDEF 2000[1] WSQUO 4000 [1]The_values_for_WSEXTENT_and_WSQUO_must_be_equal_to_or__ greater than the WSDEF value. __________________________________________________________ 1.4.3 System Parameters Table 1-2 lists the minimum required system parameter values for the installation. Depending on the kinds of programs and applications running at your site, you might need higher values for some settings. 1-4 Preparing for Multimedia Services for OpenVMS Installation Preparing for Multimedia Services for OpenVMS Installation 1.4 Installation Requirements Table 1-2 Minimum Required System Parameter Values ___________________________________________________ System Parameter Minimum Value --------------------------------------------------- GBLPAGES[1] 20,000 GBLPAGFIL 4096 GBL sections[1] 600 MAXBUF[2] 8200 PQL_DASTLM[2] 24 PQL_DBIOLM[2] 32 PQL_DDIOLM[2] 32 VIRTUALPAGECNT 500,000 WSMAX 65,600 [1]These values represent the number of free global pagelets and global sections required for the installation, not the total number you need to run your system and other software. [2]These dynamic system parameters must be set permanently to values equal to or greater than the values listed. Do not lower these values after the installation. __________________________________________________________ 1.4.4 Disk Space Table 1-3 summarizes the storage requirements for all options for Multimedia Services Version 2.0 for OpenVMS Alpha. Table 1-3 Disk Space Requirements __________________________________________________________ Blocks Options Required ---------------------------------------------------------- Multimedia Services Version 2.0 for OpenVMS Alpha 18,038 Run-Time Multimedia Services Version 2.0 for OpenVMS Alpha 5,611 Development Kit Multimedia Services Version 2.0 for OpenVMS Alpha 28,777 Sample_Clips______________________________________________ Preparing for Multimedia Services for OpenVMS Installation 1-5 Preparing for Multimedia Services for OpenVMS Installation 1.4 Installation Requirements To determine the number of free disk blocks on the current system disk, enter the following command at the DCL prompt: $ SHOW DEVICE SYS$SYSDEVICE 1.4.5 Backing Up Your System Disk Digital recommends that you do a system disk backup before installing any software. Use the backup procedures that are established at your site. For details on performing a system disk backup, see the section on the Backup Utility in the OpenVMS System Management Subkit. 1.5 Standard System Maintenance Procedures This section explains how to do various standard procedures: o Check and set process account quotas o Check system parameter values o Calculate values for global pagelets and global sections o Change parameter values with the OpenVMS AUTOGEN command procedure o Set dynamic parameter values with the OpenVMS System Generation utility (SYSGEN) 1.5.1 Checking and Setting Process Account Quotas User account quotas are stored in the file SYSUAF.DAT. Use the OpenVMS Authorize Utility (AUTHORIZE) to verify and change user account quotas. First set your directory to SYS$SYSTEM and then run AUTHORIZE: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> At the UAF> prompt, enter the SHOW command with an account name to check a particular account. For example: UAF> SHOW SMITH 1-6 Preparing for Multimedia Services for OpenVMS Installation Preparing for Multimedia Services for OpenVMS Installation 1.5 Standard System Maintenance Procedures To change a quota, enter the MODIFY command. The following example changes the FILLM quota for the SMITH account and then exits from the utility: UAF> MODIFY SMITH /FILLM=50 UAF> EXIT After you exit from the utility, the system displays messages indicating whether or not changes were made. Once the changes have been made, you must log out and log in again for the new quotas to take effect. For more information on modifying account quotas, see the description of the Authorize utility in the OpenVMS System Management Subkit. 1.5.2 Checking System Parameter Values To check the values of your system parameters, enter the following command at the DCL prompt to invoke the System Generation utility (SYSGEN): $ RUN SYS$SYSTEM:SYSGEN SYSGEN> At the SYSGEN> prompt, enter the SHOW command to display the value of a system parameter. The following example displays the value for the WSMAX system parameter: SYSGEN> SHOW WSMAX After checking the parameters with the SHOW command, enter the EXIT command at the SYSGEN> prompt to return to DCL level. 1.5.3 Calculating the Values for Global Pagelets and Global Sections To install and run Multimedia Services Version 2.0 for OpenVMS Alpha, you must have sufficient free global pagelets and global sections. You must first find out how many free global pagelets and sections you have on your system. Then, use AUTOGEN if you need to increase the global pagelets and global sections system parameters. Preparing for Multimedia Services for OpenVMS Installation 1-7 Preparing for Multimedia Services for OpenVMS Installation 1.5 Standard System Maintenance Procedures You can use the WRITE command with the F$GETSYI lexical function to find the number of free global pagelets and global sections. The following example shows how to get this information at your terminal (the default for SYS$OUTPUT): $ WRITE SYS$OUTPUT F$GETSYI("CONTIG_GBLPAGES") 15848 $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") 24 If the values displayed by the system are greater than the values in Table 1-2, you do not need to increase the values for these parameters. If the values of free global pagelets or global sections are less than the values in Table 1-2, you must increase the system parameter setting. Section 1.5.4 describes the procedures for increasing these values using AUTOGEN. 1.5.4 Changing System Parameter Values with AUTOGEN Use the AUTOGEN command procedure to change system parameters. AUTOGEN automatically adjusts values for parameters that are associated with the values you reset manually. To change system parameters with AUTOGEN, edit the SYS$SYSTEM:MODPARAMS.DAT file. To change a parameter value listed in the SYS$SYSTEM:MODPARAMS.DAT file, delete the current value associated with that parameter and enter the new value. To add a new parameter to the SYS$SYSTEM:MODPARAMS.DAT file, add a line that includes both the name of the parameter and its value. For example: WSMAX = 8096 To modify incremental parameters such as free global pagelets and global sections, use ADD_. The following example increases the global page setting by 2000: ADD_GBLPAGES = 2000 1-8 Preparing for Multimedia Services for OpenVMS Installation Preparing for Multimedia Services for OpenVMS Installation 1.5 Standard System Maintenance Procedures When you set the page file quota, do not use a value that exceeds the amount of page file space available on the system. After you make all your changes, exit from the editor and execute the AUTOGEN procedure to recalculate your system parameters. The following command recalculates your system parameters and reboots the system: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT When you specify REBOOT, AUTOGEN performs an automatic system shutdown and then reboots the system. Any users logged in to the system are immediately disconnected during the shutdown. The automatic reboot puts the new parameter values into effect. The AUTOGEN utility automatically adjusts some of the SYSGEN parameters based on the consumption of resources since the last reboot. If you do not want to take advantage of this automatic adjustment, include the NOFEEDBACK qualifier on the AUTOGEN command line. For more information about using AUTOGEN, see the OpenVMS System Management Subkit. 1.5.5 Setting Dynamic Parameter Values Use the System Generation utility (SYSGEN) to set dynamic parameter values. Dynamic parameters changed with the SYSGEN WRITE ACTIVE command become active immediately without any need to reboot your system. Rebooting returns the dynamic parameter values to their previous settings. After you change the dynamic parameter values, complete the installation before rebooting the system. After you finish with the installation, you can reset the dynamic parameters to their previous values or let them be reset automatically when you next reboot your system. The dynamic parameter values for Multimedia Services for OpenVMS Alpha are listed in Table 1-2. If the dynamic parameter values on your system are less than the values in Table 1-2, use the following series of commands to change the values. This example changes the MAXBUF value to 8192: Preparing for Multimedia Services for OpenVMS Installation 1-9 Preparing for Multimedia Services for OpenVMS Installation 1.5 Standard System Maintenance Procedures $ RUN SYS$SYSTEM:SYSGEN SYSGEN> USE ACTIVE SYSGEN> SET MAXBUF 8192 SYSGEN> WRITE ACTIVE SYSGEN> EXIT 1-10 Preparing for Multimedia Services for OpenVMS Installation 2 ________________________________________________________________ Installing Multimedia Services for OpenVMS Alpha This chapter describes how to install Multimedia Services for OpenVMS Alpha using the POLYCENTER Software Installation utility. Multimedia Services Version 2.0 for OpenVMS Alpha supports POLYCENTER software installations using the DIGITAL Command Language (DCL) interface. Refer to the OpenVMS System Manager's Manual for complete details about installing and managing software products on your system. 2.1 Preparing to Install Multimedia Services V2.0 for OpenVMS Alpha Before you initiate the installation procedure, perform the following tasks: o Extract the Multimedia Services Version 2.0 for OpenVMS Alpha release notes. o Notify system users that you are about to install the product. 2.1.1 Extracting and Printing the Product Release Notes To extract a copy of the Multimedia Services Version 2.0 for OpenVMS Release Notes, enter the PRODUCT EXTRACT RELEASE_NOTES command followed by the product name MMOV, at the DCL prompt: $PRODUCT EXTRACT RELEASE_NOTES MMOV/source=kit location/file=filename Once you extract the release notes to a file, then you can print the file. Note that you do not need to install the product before you extract the release notes. Installing Multimedia Services for OpenVMS Alpha 2-1 Installing Multimedia Services for OpenVMS Alpha 2.2 Software Installation Overview 2.2 Software Installation Overview The sections that follow describe the stages of installing Multimedia Services Version 2.0 for OpenVMS Alpha using the POLYCENTER Software Installation utility. See Chapter 1 for information about account quotas, disk space, and system parameters. Refer to the OpenVMS System Manager's Manual for complete information about responding to questions that the POLYCENTER Software Installation utility asks during product installation. For example, when you respond to questions, you can do the following: o Enter a value and press the Return key to select options. o Press the Return key to accept default values. o Confirm your responses. After you respond to questions by selecting options or accepting default values, the installation utility displays a summary of your answers. Then a question is displayed, asking whether you are satisfied with your answers and whether you want to continue with the installation. If you decide to change your responses, type No and press the Return key. You can then reenter your responses or answer No and exit from the installation utility. o Stop the installation by pressing Ctrl/Y. This option is not recommended. 2.2.1 Software Kit Names The name of the Multimedia Services for OpenVMS kit is DEC-AXPVMS-MMOV-V0200--.1.PCSI. When you install Multimedia Services for OpenVMS, the installation procedure looks for the product kits in the PCI$SOURCE directory. If PCI$SOURCE is not defined, the current directory is used. 2-2 Installing Multimedia Services for OpenVMS Alpha Installing Multimedia Services for OpenVMS Alpha 2.2 Software Installation Overview ________________________Note ________________________ The PCSI_INSTALLATION.COM command procedure determines the system and version on which you are installing the Multimedia Services software. See Section 2.2.2 for information about this command procedure. _____________________________________________________ 2.2.2 Starting the Installation Run the PCSI_INSTALLATION.COM procedure, which is part of the POLYCENTER software installation save set, at the DCL level to start the installation. Enter the following command at the DCL prompt: $PRODUCT INSTALL MMOV /SOURCE=kit location This command procedure includes the following phases of the installation: o Running preinstallation procedures o Installing the save sets o Running postinstallation procedures The sections that follow discuss the steps and activities that take place once you execute the PCSI_INSTALLATION command procedure. As the installation progresses, the installation utility displays a percentage that indicates how much of the installation is completed. For example: Portion Done: 0%...10%...20%...30%... When the installation is successfully completed, an informational message is displayed by the installation procedure. The following information is displayed after Multimedia Services for OpenVMS is successfully installed: Portion Done: 0%..10%..20%..30%...50%...70%..80%..90%..100% The following product has been installed: DEC AXPVMS MMOV V2.0 Installing Multimedia Services for OpenVMS Alpha 2-3 Installing Multimedia Services for OpenVMS Alpha 2.2 Software Installation Overview 2.2.2.1 Displaying the Copyright Message The installation utility displays the following copyright message: *** DEC AXPVMS MMOV V2.0: Multimedia Services Version 2.0 for OpenVMS Alpha *** Copyright Digital Equipment Corporation 1996. All rights reserved. 2.2.2.2 Determining System Information The installation utility checks and stores information about the supported versions of your OpenVMS Alpha system. For example: **** DEC AXPVMS VMS V6.2 [Available] **** Refer to Section 1.2 for information about system prerequisites. The information that is displayed if your version of the OpenVMS operating system does not meet the criteria depends on the OpenVMS system. On OpenVMS Alpha systems, the following warning is displayed: WARNING: This kit may be installed only on OpenVMS Alpha Version 6.2 systems or higher 2.2.2.3 Verifying Sufficient Allocation for the GBLPAGES Value The installation utility informs you if adequate values are allocated for the GBLPAGES system parameter. Check Table 1-2 for a list of adequate values for Multimedia Services Version 2.0 for OpenVMS Alpha. 2.2.2.4 Rebooting the System In this step of the installation, the installation utility tells you if it is necessary to reboot the system. If you are reinstalling the Multimedia Services for OpenVMS kit, you also need to reinstall the driver and reboot the system. If a system has a Microsoft Windows or compatible sound card, the system needs to be rebooted to load the correct driver for this card, MMOV$MSBDRIVER. Also, if the product has been reinstalled, a reboot is required to reload the sound and video drivers. If system parameters need to be 2-4 Installing Multimedia Services for OpenVMS Alpha Installing Multimedia Services for OpenVMS Alpha 2.2 Software Installation Overview changed, a reboot is required for the new parameters to take effect. 2.2.2.5 Installing the Product The POLYCENTER Software Installation utility then installs the Multimedia Services for OpenVMS software. The utility displays messages and asks a series of questions. On OpenVMS Alpha systems, the following message is displayed if the installation utility cannot locate the Multimedia Services software in the PSCI$SOURCE directory: %PCSI-E-OPENIN, error opening PCSI$SOURCE:[SYSMGR]*-*-*-%%%%%-*-*.PCSI*; as input -RMS-F-DEV, error in device name or inappropriate device type for operation %PCSI-E-S_OPFAIL, operation failed %PCSIUI-E-ABORT, fatal error encountered - operation terminated When you enter the correct directory specification, the installation utility locates the software and proceeds with the installation. If you press Ctrl/C, the following message displays: Terminating installation of MMOV V2.0 for OpenVMS Alpha 2.2.2.6 Continuing the Installation Once the installation utility locates the kit, the procedure asks whether you want to continue with the installation. Do you want to continue? [Yes] If you enter Yes (default) and press Return, the installation procedure displays the following information, which includes previously displayed copyright information. Note that this example shows the message that is displayed on OpenVMS Alpha systems: *** DEC AXPVMS MMOV V2.0: Multimedia Services Version 2.0 for OpenVMS Alpha Copyright Digital Equipment Corporation, 1996. All rights reserved. Digital Equipment Corporation This product uses the PAK: MMOV-RT Do you want all the default values for this product? [YES] Installing Multimedia Services for OpenVMS Alpha 2-5 Installing Multimedia Services for OpenVMS Alpha 2.2 Software Installation Overview Multimedia Services run-time support files [YES] Do you want to view the values? [NO] If you answer Yes to view the default values, the following information is displayed, followed by a question asking whether you are satisfied with these default values (default is Yes): *** DEC AXPVMS MMOV V2.0: Multimedia Services Version 2.0 for OpenVMS Alpha Sample Audio and Video Clips: [Yes] Kit to develop multimedia applications (MMOV-DV PAK Required): [No] Are you satisfied with the values? [Yes] If you are not satisfied with the values, type No in response to the question: Are you satisfied with the values? Then press Return; you can now change your responses to these questions. 2.2.2.7 Executing the Installation Procedure Once you select the programming and translated-image support options, the installation utility begins the software installation. A message is displayed that shows you when the product installation begins and when it is completed, as in the following example: %PCSIUI-I-DONEASK, execution phase starting The following product will be installed: DEC AXPVMS MMOV V2.0 %PCSIUI-I-VOLINFO, estimated space information for volume DISK$AXPVMS071 -PCSI-I-VOLSPC, 39771 required; 585648 available; 545877 net Portion Done: 0%..10%..20%..30%..50%...70%..80%..90%..100% The following product has been installed: DEC AXPVMS MMOV V2.0 2-6 Installing Multimedia Services for OpenVMS Alpha Installing Multimedia Services for OpenVMS Alpha 2.3 Recovering from Errors 2.3 Recovering from Errors An error during installation can occur if one or more of the following conditions exists: o The operating system version is incorrect. o The prerequisite software version is incorrect. o Quotas necessary for successful installation are inadequate. o Process quotas required by the installation utility are inadequate. o The OpenVMS Help library is currently in use. Installing Multimedia Services for OpenVMS Alpha 2-7 3 ________________________________________________________________ After Installation This chapter explains what you need to do after the installation to make Multimedia Services for OpenVMS Alpha ready for use. You can perform the following tasks after Multimedia Services for OpenVMS Alpha is installed: o Run the Installation Verification Procedure (IVP) separately o Edit the system startup and shutdown files o Modify system parameter settings o Make the product usable on a VMScluster system o Set user account quotas 3.1 Running the IVP Separately from Installation You usually run the Installation Verification Procedure (IVP) during installation. If you have system problems and want to run the IVP separately to ensure the integrity of installed files, use the following command: $ @sys$test:mmov$ivp The Multimedia Services for OpenVMS Alpha Installation Verification Procedure is located at SYS$TEST:MMOV$IVP.COM. The installation procedure checks for an installed audio device and plays audio clips included with the kit. To hear the audio test, turn on your speakers or put on headphones. The IVP automatically puts the volume at 50%. After Installation 3-1 After Installation 3.1 Running the IVP Separately from Installation When the audio testing is completed, the IVP runs the video test. The test plays the AVI clips that come with the kit. Your workstation must be running DECwindows so that a window session can be opened to play the clips. The first clip has an audio track. If you have installed an audio device, turn on your speakers or put on your headphones. If the server cannot be started, the IVP will not run. This occurs if you are reinstalling the kit and you need to reboot your system. Once your system is rebooted, execute the IVP to run the tests. Refer to Section A.2 for a sample script of the Multimedia Services for OpenVMS Alpha Installation Verification Procedure. 3.2 Editing the System Files You must edit the system startup and shutdown files to provide for automatic startup and shutdown of Multimedia Services for OpenVMS Alpha when your system is rebooted. Add the command line that starts Multimedia Services for OpenVMS Alpha to the system startup file, SYS$MANAGER:SYSTARTUP_ VMS.COM. You must position this new command line after the line that invokes the network startup command procedure. The following example shows the network startup command line followed by the Multimedia Services for OpenVMS Alpha startup command line: $ @SYS$MANAGER:STARTNET.COM . . . $ @SYS$STARTUP:MMOV$STARTUP.COM Add the following command line to the system shutdown file, SYS$MANAGER:SYSHUTDWN.COM: $ @SYS$STARTUP:MMOV$SHUTDOWN.COM 3-2 After Installation After Installation 3.3 Modifying System Parameters 3.3 Modifying System Parameters The installation for Multimedia Services for OpenVMS Alpha requires that you raise the values of the GBLPAGES system parameter. Once the installation is complete, lower this value to ensure efficient system performance. Table 1-2 contains the value for the parameter under normal operations. 3.4 Making the Product Usable on a VMScluster System If you want to run Multimedia Services for OpenVMS Alpha on multiple nodes of a VMScluster system, first check to see that you have the appropriate software license (see Section 1.1). Then, perform the following steps after you install Multimedia Services for OpenVMS Alpha: 1. Enter the LICENSE LOAD command to activate the license on each node in the VMScluster system on which Multimedia Services for OpenVMS Alpha is to be executed. 2. The startup files on each node in the cluster should be edited, as described in Section 3.2. 3. Use the OpenVMS SYSMAN utility to execute a set of commands on all cluster nodes, whether or not the nodes are licensed to use Multimedia Services for OpenVMS Alpha; failure to do so may cause unexpected errors for users. ________________________Note ________________________ If you are using a dual-architecture (VAX and Alpha systems) heterogeneous cluster, before executing these commands, make sure the appropriate logical names have been set to define the scope of the SYSMAN DO commands. For more information, see the OpenVMS system management documentation. _____________________________________________________ While logged in as SYSTEM, or as another user name that has the SETPRV privilege or the CMKRNL and SYSPRV privileges, use the SYSMAN utility to update the cluster environment as follows: After Installation 3-3 After Installation 3.4 Making the Product Usable on a VMScluster System $ RUN SYS$SYSTEM:SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER %SYSMAN-I-ENV, current command environment: Clusterwide on local cluster Username SYSTEM will be used on nonlocal nodes SYSMAN> DO @SYS$STARTUP:MMOV$STARTUP.COM %SYSMAN-I-OUTPUT, command execution on node NODE1 %SYSMAN-I-OUTPUT, command execution on node NODE2 The SYSMAN utility will cause each DO command to be executed on all nodes of the local cluster. 3.5 Setting User Account Requirements To work with Multimedia Services for OpenVMS Alpha, user accounts on your system must have certain privileges and quotas. 3.5.1 Privileges To use Multimedia Services for OpenVMS Alpha, each account must have at least the TMPMBX and NETMBX privileges. Use the OpenVMS Authorize utility to determine whether users have the privileges they require. 3.5.2 User Account Quotas You must make sure that the appropriate user accounts have sufficient quotas to be able to use Multimedia Services for OpenVMS Alpha. See Table 1-1 for the required user account quotas. Section 1.5.1 describes how to verify and change account quotas. 3-4 After Installation A ________________________________________________________________ Sample Listings This appendix provides a sample listing for an instal- lation of Multimedia Services Version 2.0 for OpenVMS Alpha. A.1 Sample Installation Dialog The following example shows the script for the instal- lation of Multimedia Services Version 2.0 for OpenVMS Alpha: $ product install mmov /source=dka300:[000000] The following product has been selected: DEC AXPVMS MMOV V2.0 Do you want to continue? [YES] *** DEC AXPVMS MMOV V2.0: MMultimedia Services Version 2.0 for OpenVMS ALPHA Copyright Digital Equipment Corporation 1996. All rights reserved. Digital Equipment Corporation This product uses the PAK: MMOV-RT If installing the Development Kit, the PAK is MMOV-DV Do you want all the default values for this product? [YES] Do you want to view the values? [NO] y DEC AXPVMS MMOV V2.0: Multimedia Services Version 2.0 for OpenVMS Alpha DEC AXPVMS VMS V6.2 [Available] Sample Audio and Video clips : YES Kit to develop multimedia applications (MMOV-DV PAK Required): NO Are you satisfied with the values? [NO] Sample Listings A-1 Sample Listings A.1 Sample Installation Dialog %PCSIUI-I-DONEASK, execution phase starting The following product will be installed: DEC AXPVMS MMOV V2.0 %PCSI-I-VOLINFO, estimated space information for volume DISK$AXPVMS061 -PCSI-I-VOLSPC, 46552 required; 815331 available; 768779 net Portion Done: 0%...10%...20%...30%...50%...70%...80%...90%...100% The following product has been installed: DEC AXPVMS MMOV V2.0 *** DEC AXPVMS MMOV V2.0: Multimedia Services Version 2.0 for OpenVMS Alpha Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM: @SYS$STARTUP:MMOV$STARTUP.COM Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM: @SYS$STARTUP:MMOV$SHUTDOWN.COM This product requires the following SYSGEN parameters: GBLPAGFIL minimum 4096 Release notes are available at SYS$HELP:MMOV-V2_0.RELEASE_NOTES Please be sure your system parameters are properly set. It may be necessary to reboot your system for the software to take effect. The Server and IVP can not run until you reboot your system. $ A.2 Sample Installation Verification Procedure The following example shows the Installation Verification Procedure (IVP) script for Multimedia Services V2.0 for OpenVMS Alpha:: $@sys$test:mmov$ivp Multimedia Services Version 2.0 for OpenVMS Alpha IVP starting. Starting audio test... You have an AUDIO device installed on your system. This command procedure will wait thirty seconds while you turn on your speakers, and/or put your headphones on to listen to the clips. During the test the volume will be set at various levels for both the right channel and left channel this is normal, and is part of the test. A-2 Sample Listings Sample Listings A.2 Sample Installation Verification Procedure Setting volume to 50% on your audio device. Playing audio clip MMOV$EXAMPLES:[SAMPLE]PROPS1.WAV. Setting volume to 50% right channel 40% left channel. Playing audio clip MMOV$EXAMPLES:[SAMPLE]PROPS2.WAV. Setting volume to 40% right channel 50% left channel. Playing audio clip MMOV$EXAMPLES:[SAMPLE]PROPS3.WAV. Setting volume to 30% on both channels. Playing audio clip MMOV$EXAMPLES:[SAMPLE]TROPIC1.WAV. Setting volume to 50% on both channels. Playing audio clip MMOV$EXAMPLES:[SAMPLE]WORLD2.WAV. Starting video test... This command procedure will play the two AVI clips that come with the kit. The first clip has an audio track and if you have a sound card you will be able to hear the sound track. If you do not have a sound card installed then you need to dismiss the window's error box stating this fact. Playing video clip MMOV$EXAMPLES:[SAMPLE]COUNTDOWN-JPEG2.AVI. Playing video clip MMOV$EXAMPLES:[SAMPLE]AMERICA3-JPEG.AVI. Multimedia Services Version 2.0 for OpenVMS Alpha IVP complete. $ Sample Listings A-3 B ________________________________________________________________ Files Installed on Your System The Multimedia Services Version 2.0 for OpenVMS Alpha installation procedure installs a number of files on your system and defines some logical names. B.1 Installed Files The following list contains the names of all the directories and files installed on your system when Multimedia Services is installed: [MMOV_INCLUDES]AVIEASY.H [MMOV_INCLUDES]AVIFMT.H [MMOV_INCLUDES]CMM.H [MMOV_INCLUDES]CMMFUNCPROTO.H [MMOV_INCLUDES]CMMFUNCS.H [MMOV_INCLUDES]CMMMD.H [MMOV_INCLUDES]CMMOS.H [MMOV_INCLUDES]CMMOSDEFS.H [MMOV_INCLUDES]CMMPROTO.H [MMOV_INCLUDES]CMM_API.H [MMOV_INCLUDES]CMM_LIB.H [MMOV_INCLUDES]COLOR_UTILS.H [MMOV_INCLUDES]COMMON.H [MMOV_INCLUDES]COMPDDK.H [MMOV_INCLUDES]COMPMAN.H [MMOV_INCLUDES]COPYRIGHT.H [MMOV_INCLUDES]CURSORFONT.H [MMOV_INCLUDES]DEVIO.H [MMOV_INCLUDES]DIGITALV.H [MMOV_INCLUDES]DLFCN.H [MMOV_INCLUDES]DRAWDIB.H [MMOV_INCLUDES]ENDIAN.H [MMOV_INCLUDES]ERRNO.H Files Installed on Your System B-1 Files Installed on Your System B.1 Installed Files [MMOV_INCLUDES]EXTUTIL.H [MMOV_INCLUDES]IF.H [MMOV_INCLUDES]IOCTL.H [MMOV_INCLUDES]IOCTL_COMPAT.H [MMOV_INCLUDES]IP.H [MMOV_INCLUDES]IPC.H [MMOV_INCLUDES]LMF.H [MMOV_INCLUDES]MACHLIMITS.H [MMOV_INCLUDES]MACHPARAM.H [MMOV_INCLUDES]MALLOC.H [MMOV_INCLUDES]MCIAVI.H [MMOV_INCLUDES]MCIWND.H [MMOV_INCLUDES]MMAN.H [MMOV_INCLUDES]MMAUTH.H [MMOV_INCLUDES]MMBASIC.H [MMOV_INCLUDES]MMDDK.H [MMOV_INCLUDES]MME_API.H [MMOV_INCLUDES]MME_PUBLIC.H [MMOV_INCLUDES]MMREG.H [MMOV_INCLUDES]MMSYSTEM.H [MMOV_INCLUDES]MSACM.H [MMOV_INCLUDES]MSVIDDRV.H [MMOV_INCLUDES]MSVIDEO.H [MMOV_INCLUDES]OSDEP.H [MMOV_INCLUDES]PARAM.H [MMOV_INCLUDES]PLATFORM.H [MMOV_INCLUDES]READAVI.H [MMOV_INCLUDES]SECDEFINES.H [MMOV_INCLUDES]SHM.H [MMOV_INCLUDES]SMT.H [MMOV_INCLUDES]SMTINT.H [MMOV_INCLUDES]SMTSTR.H [MMOV_INCLUDES]STANDARDS.H [MMOV_INCLUDES]STATS.H [MMOV_INCLUDES]STRINGS.H [MMOV_INCLUDES]TIME.H [MMOV_INCLUDES]TIMERS.H [MMOV_INCLUDES]TTYCHARS.H [MMOV_INCLUDES]TTYDEFAULTS.H [MMOV_INCLUDES]TTYDEV.H [MMOV_INCLUDES]UIO.H [MMOV_INCLUDES]UTSNAME.H [MMOV_INCLUDES]VM_TYPES.H B-2 Files Installed on Your System Files Installed on Your System B.1 Installed Files [MMOV_INCLUDES]X.H [MMOV_INCLUDES]XATOM.H [MMOV_INCLUDES]XAUTH.H [MMOV_INCLUDES]XEXT.H [MMOV_INCLUDES]XFUNCPROTO.H [MMOV_INCLUDES]XLIB.H [MMOV_INCLUDES]XLIBINT.H [MMOV_INCLUDES]XMM.H [MMOV_INCLUDES]XOS.H [MMOV_INCLUDES]XOSDEFS.H [MMOV_INCLUDES]XPROTO.H [MMOV_INCLUDES]XRESOURCE.H [MMOV_INCLUDES]XSHM.H [MMOV_INCLUDES]XUTIL.H [SYS$LDR]MMOV$MSBDRIVER.EXE [SYS$LDR]MMOV$VIDRIVER.EXE [SYS$STARTUP]MMOV$SHUTDOWN.COM [SYS$STARTUP]MMOV$STARTUP.COM [SYSEXE]MMOV$ALPHAVCR.EXE [SYSEXE]MMOV$AUDIOCONTROL.EXE [SYSEXE]MMOV$AUDIODEVICES.EXE [SYSEXE]MMOV$AUDIOPLAY.EXE [SYSEXE]MMOV$AUDIORECORD.EXE [SYSEXE]MMOV$AUDIOSELECTPORTS.EXE [SYSEXE]MMOV$AUDIOSETVOLUME.EXE [SYSEXE]MMOV$AVIRECORD.EXE [SYSEXE]MMOV$DECSOUND.EXE [SYSEXE]MMOV$JPEGCONVERT.EXE [SYSEXE]MMOV$SERVER.EXE [SYSEXE]MMOV$VIDDUALRECORD.EXE [SYSEXE]MMOV$VIDEOODYSSEY.EXE [SYSEXE]MMOV$VIDPLAY.EXE [SYSEXE]MMOV$VIDRECORD.EXE [SYSEXE]MMOV$VIDSTREAMIN.EXE [SYSEXE]SYSTEM.INI Files Installed on Your System B-3 Files Installed on Your System B.1 Installed Files [SYSHLP.EXAMPLES.MMOV.AUDIO]AUDIODEVICES.C [SYSHLP.EXAMPLES.MMOV.AUDIO]AUDIODEVICES_VERSION.H [SYSHLP.EXAMPLES.MMOV.AUDIO]AUDIOPLAY.C [SYSHLP.EXAMPLES.MMOV.AUDIO]AUDIOPLAY_VERSION.H [SYSHLP.EXAMPLES.MMOV.AUDIO]AUDIORECORD.C [SYSHLP.EXAMPLES.MMOV.AUDIO]AUDIORECORD_VERSION.H [SYSHLP.EXAMPLES.MMOV.AUDIO]AUDIOSELECTPORTS.C [SYSHLP.EXAMPLES.MMOV.AUDIO]AUDIOSELECTPORTS_VERSION.H [SYSHLP.EXAMPLES.MMOV.AUDIO]AUDIOSETVOLUME.C [SYSHLP.EXAMPLES.MMOV.AUDIO]AUDIO_README.TXT [SYSHLP.EXAMPLES.MMOV.AUDIO]BUILD_AUDIO.COM [SYSHLP.EXAMPLES.MMOV.AUDIO]MMC_CMDLIN.H [SYSHLP.EXAMPLES.MMOV.COMMON]BUILD_COMMON.COM [SYSHLP.EXAMPLES.MMOV.COMMON]COMMON_README.TXT [SYSHLP.EXAMPLES.MMOV.COMMON]MMC_BUFFERS.C [SYSHLP.EXAMPLES.MMOV.COMMON]MMC_BUFFERS.H [SYSHLP.EXAMPLES.MMOV.COMMON]MMC_CMDLIN.C [SYSHLP.EXAMPLES.MMOV.COMMON]MMC_CMDLIN.H [SYSHLP.EXAMPLES.MMOV.COMMON]MMC_COLOR.C [SYSHLP.EXAMPLES.MMOV.COMMON]MMC_COLOR.H [SYSHLP.EXAMPLES.MMOV.COMMON]MMC_MEMORY.C [SYSHLP.EXAMPLES.MMOV.COMMON]MMC_MEMORY.H [SYSHLP.EXAMPLES.MMOV.COMMON]MMC_MESSAGES.C [SYSHLP.EXAMPLES.MMOV.COMMON]MMC_MESSAGES.H [SYSHLP.EXAMPLES.MMOV.COMMON]MMC_UTILS.C [SYSHLP.EXAMPLES.MMOV.COMMON]MMC_UTILS.H [SYSHLP.EXAMPLES.MMOV.COMMON]MMC_WAVE.C [SYSHLP.EXAMPLES.MMOV.COMMON]MMC_WAVE.H [SYSHLP.EXAMPLES.MMOV.COMMON]MMC_WAVE_FILE.H [SYSHLP.EXAMPLES.MMOV.COMMON]MMC_WAVE_FORMAT.C [SYSHLP.EXAMPLES.MMOV.COMMON]MMC_WAVE_FORMAT.H [SYSHLP.EXAMPLES.MMOV.COMMON]MMC_WAVE_IN_FILE.C [SYSHLP.EXAMPLES.MMOV.COMMON]MMC_WAVE_OUT_FILE.C [SYSHLP.EXAMPLES.MMOV.COMMON]STUBS.C [SYSHLP.EXAMPLES.MMOV.SAMPLE]AMERICA3-JPEG.AVI [SYSHLP.EXAMPLES.MMOV.SAMPLE]CLIP.MPG [SYSHLP.EXAMPLES.MMOV.SAMPLE]COUNTDOWN-JPEG2.AVI [SYSHLP.EXAMPLES.MMOV.SAMPLE]PROPS1.WAV [SYSHLP.EXAMPLES.MMOV.SAMPLE]PROPS2.WAV [SYSHLP.EXAMPLES.MMOV.SAMPLE]PROPS3.WAV [SYSHLP.EXAMPLES.MMOV.SAMPLE]TROPIC1.WAV [SYSHLP.EXAMPLES.MMOV.SAMPLE]WORLD2.WAV B-4 Files Installed on Your System Files Installed on Your System B.1 Installed Files [SYSHLP.EXAMPLES.MMOV.VIDEO]AVICOMPRESS.C [SYSHLP.EXAMPLES.MMOV.VIDEO]AVIEASY.C [SYSHLP.EXAMPLES.MMOV.VIDEO]AVIRECORD.C [SYSHLP.EXAMPLES.MMOV.VIDEO]BUILD_VIDEO.COM [SYSHLP.EXAMPLES.MMOV.VIDEO]COLOR_UTILS.C [SYSHLP.EXAMPLES.MMOV.VIDEO]COMMON.C [SYSHLP.EXAMPLES.MMOV.VIDEO]JPEGCONVERT.C [SYSHLP.EXAMPLES.MMOV.VIDEO]READAVI.C [SYSHLP.EXAMPLES.MMOV.VIDEO]RIFFSHOW.C [SYSHLP.EXAMPLES.MMOV.VIDEO]VIDDUALRECORD.C [SYSHLP.EXAMPLES.MMOV.VIDEO]VIDEO_README.TXT [SYSHLP.EXAMPLES.MMOV.VIDEO]VIDFRAMEIN.C [SYSHLP.EXAMPLES.MMOV.VIDEO]VIDFRAMEOUT.C [SYSHLP.EXAMPLES.MMOV.VIDEO]VIDPLAY.C [SYSHLP.EXAMPLES.MMOV.VIDEO]VIDPLAYOUT.C [SYSHLP.EXAMPLES.MMOV.VIDEO]VIDRECORD.C [SYSHLP.EXAMPLES.MMOV.VIDEO]VIDSCREENOUT.C [SYSHLP.EXAMPLES.MMOV.VIDEO]VIDSTREAMIN.C [SYSHLP.EXAMPLES.MMOV.VIDEO]VIDSTREAMOUT.C [SYSHLP]MMOV-V2_0.RELEASE_NOTES [SYSLIB]AUDIOCONTROL.DAT [SYSLIB]AUDIOEDITOR.DAT [SYSLIB]MMOV$ALPHAVCR.UID [SYSLIB]MMOV$AUDIOCONTROL.UID [SYSLIB]MMOV$DECSOUND.UID [SYSLIB]MMOV$DIVA_WIDGET.UID [SYSLIB]MMOV$ICBM.EXE [SYSLIB]MMOV$JV2VIDEO.EXE [SYSLIB]MMOV$JV3VIDEO.EXE [SYSLIB]MMOV$MSBAUDIO.EXE [SYSLIB]MMOV$SOFTJPEG.EXE [SYSLIB]MMOV$VIDEOODYSSEY.UID [SYSLIB]MMOV.OLB [SYSTEST]MMOV$IVP.COM [SYSUPD]MMOV$PCSI_INSTALL.COM Files Installed on Your System B-5 Files Installed on Your System B.2 Logical Names B.2 Logical Names The following logical names are entered into the system logical name table when Multimedia Services Version 2.0 for OpenVMS Alpha is installed. These names are stored in the product's startup file. They are automatically entered into the system logical name table whenever the system reboots or whenever the software is invoked. o MMOV$INCLUDE Contains header files for developing multimedia applications. o MMOV$EXAMPLES:[000000] Contains examples for developing multimedia applica- tions and sample audio and video clips. B-6 Files Installed on Your System C ________________________________________________________________ Recovering from Errors This appendix provides information to help you deal with failures or errors that might occur during product installation or product use. C.1 Failures During Product Installation If errors occur during the installation, the system displays failure messages. Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect. o The prerequisite software version is incorrect. o There is insufficient disk space. o The system parameter values for successful installation are insufficient. For descriptions of error messages generated by these conditions, see the OpenVMS Alpha documentation on system messages, recovery procedures, and software installation. For information on system software requirements, see Section 1.2. C.2 Failures During Product Use If an error occurs while Multimedia Services for OpenVMS Alpha is in use and you believe the error is caused by a problem with the product, take one of the following actions: o If you have a Software Product Services Support Agreement, contact your Customer Support Center (CSC) by telephone or by using the electronic means provided with your support agreement (such as DSNlink). The CSC Recovering from Errors C-1 Recovering from Errors C.2 Failures During Product Use provides telephone support for high-level advisory and remedial assistance. When you initially contact the CSC, indicate the following: - The name and version number of the operating system you are using - The version number of Multimedia Services for OpenVMS Alpha you are using - The hardware system you are using (such as a model number) - A brief description of the problem (one sentence, if possible) - The critical nature of the problem o If you have a Self-Maintenance Software Agreement, you can submit a Software Performance Report (SPR). o If you do not have any type of software services support agreement and you purchased Multimedia Services for OpenVMS Alpha within the past year, you can submit an SPR if you think the problem is caused by a software error. When you submit an SPR, take the following steps: 1. Describe as accurately as possible the circumstances and state of the system when the problem occurred. Include the description and version number of the Multimedia Services for OpenVMS Alpha being used. Explain the problem with specific examples. 2. Reduce the problem to its elements. 3. Remember to include listings of any command files, include files, relevant data files, and so forth. 4. Provide a listing of the program. 5. If the program is longer than 50 lines, submit a copy of it on machine-readable media (floppy diskette or magnetic tape). If necessary, also submit a copy of the program library used to build the application. For information about submitting media, see the OpenVMS System Management Utilities Reference Manual. C-2 Recovering from Errors Recovering from Errors C.2 Failures During Product Use 6. Report only one problem per SPR. This will facilitate a faster response. 7. Mail the SPR package to Digital. If the problem is related to Multimedia Services Version 2.0 for OpenVMS Alpha documentation, you can do one of the following: o Report the problem to the CSC (if you have a Software Product Services Support Agreement and the problem is severe). o Fill out the Reader's Comments form (in the back of the document that contains the error), and send the form to Digital. Be sure to include the section and page number where the error occurred. Recovering from Errors C-3