[an error occurred while processing this directive]

HP OpenVMS Systems Documentation

Content starts here HP DECwindows Motif for OpenVMS Alpha

HP DECwindows Motif
for OpenVMS Alpha

Installation Guide

Order Number: AA--RT26B--TE


October 2003

This manual provides step-by-step instructions for installing DECwindows Motif for OpenVMS Alpha Version 1.3-1.

Revision/Update Information: This manual supersedes DECwindows Motif for OpenVMS Installation Guide Version 1.3.

Operating System: HP OpenVMS Alpha Version 7.3--2

Software Version: HP DECwindows Motif for OpenVMS Alpha Version 1.3-1



Hewlett-Packard Company Palo Alto, California


© Copyright 2003 Hewlett-Packard Development Company, L.P.

Motif, OSF/1, UNIX, and the "X" device are registered trademarks and The Open Group is a trademark of The Open Group in the U.S. and other countries.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Proprietary computer software. Valid license from HP required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

ZK6434

This document was prepared using VAX DOCUMENT, Version V3.2n.

Contents Index


Preface

Intended Audience

This manual is intended for anyone who plans to install the DECwindows Motif for OpenVMS Alpha Version 1.3-1 software.

Document Structure

This manual contains the following chapters and appendixes:

  • Chapter 1 discusses how to prepare for installing DECwindows Motif software.
  • Chapter 2 discusses how to install DECwindows Motif using the POLYCENTER Software Installation utility.
  • Chapter 3 provides startup procedures. This chapter also includes a sample Installation Verification Procedure (IVP).
  • Chapter 4 discusses customizing the environment, and reporting errors.
  • Appendix A presents a sample DECwindows Motif installation using the POLYCENTER Software Installation utility on an OpenVMS Alpha Version 7.3--2 system.
  • Appendix B shows how to obtain a list of the software components for the DECwindows Motif product using the POLYCENTER Software Installation utility.

Related Documents

In addition to this manual, the following documents are useful when installing the DECwindows Motif software:

  • HP DECwindows Motif for OpenVMS Alpha New Features
  • HP DECwindows Motif for OpenVMS Alpha Release Notes
  • Guide to the HP DECwindows Motif for OpenVMS Alpha CD--ROM
  • Getting Started With the New Desktop
  • Managing DECwindows Motif for OpenVMS Systems
  • OpenVMS System Manager's Manual
  • OpenVMS System Management Utilities Reference Manual

For additional information about OpenVMS or DECwindows Motif products and services, visit the following web site:


http://www.hp.com/go/openvms

Reader's Comments

HP welcomes your comments on this manual. Please send comments to either of the following addresses:

Internet openvmsdoc@hp.com
Mail Hewlett-Packard Company
OSSG Documentation Group, ZKO3-4/U08
110 Spit Brook Rd.
Nashua, NH 03062-2698

How To Order Additional Documentation

For information about how to order additional documentation, visit the following World Wide Web address:


http://www.hp.com/go/openvms/doc/order

Conventions

DECwindows Motif contains a graphical user interface that is derived from the Common Desktop Environment (CDE). This interface is referred to throughout this document as the New Desktop.

Unless otherwise specified, references to OpenVMS Clusters, VMSclusters, or clusters in this document are synonymous with HP OpenVMS Clusters.

All uses of DECwindows and DECwindows Motif refer to the HP DECwindows Motif for OpenVMS Alpha software; and all uses of X server and X display server refer to the HP DECwindows X11 Display Server. Additionally, all uses of DECwindows XUI (X User Interface) refer to the DECwindows product prior to DECwindows Motif Version 1.0.

The following conventions are also used in this manual:

Ctrl/ x A sequence such as Ctrl/ x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button.
[Return] In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.)

In the HTML version of this document, this convention appears as brackets, rather than a box.

... Horizontal ellipsis points in examples indicate one of the following possibilities:
  • Additional optional arguments in a statement have been omitted.
  • The preceding item or items can be repeated one or more times.
  • Additional parameters, values, or other information can be entered.
.
.
.
Vertical ellipsis points indicate the omission of items from a code example or command format; the items are omitted because they are not important to the topic being discussed.
( ) In command format descriptions, parentheses indicate that you must enclose the choices in parentheses if you choose more than one.
[ ] In command format descriptions, brackets indicate optional elements. You can choose one, none, or all of the options. (Brackets are not optional, however, in the syntax of a directory name in an OpenVMS file specification or in the syntax of a substring specification in an assignment statement.)
| In command format descriptions, vertical bars separating items inside brackets indicate that you choose one, none, or more than one of the options.
{ } In command format descriptions, braces surround a required choice of options; you must choose one of the options listed.
text style This text style represents the introduction of a new term or the name of an argument, an attribute, or a reason.

In the HTML version of this document, this convention appears as italic text.

italic text Italic text indicates important information, complete titles of manuals, or variables. Variables include information that varies in system messages (Internal error number), in command lines (/PRODUCER= name), and in command parameters in text (where dd represents the predefined code for the device type).
UPPERCASE TEXT Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege.
Monospace type Monospace type indicates code examples and interactive screen displays.

In the C programming language, monospace type in text identifies the following elements: keywords, the names of independently compiled external functions and files, syntax summaries, and references to variables or identifiers introduced in an example.

- A hyphen at the end of a command format description, command line, or code line indicates that the command or statement continues on the following line.
numbers All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal radixes---binary, octal, or hexadecimal---are explicitly indicated.


Chapter 1
Preparing to Install the Software

This chapter describes the preparation and requirements for installing DECwindows Motif for OpenVMS Alpha Version 1.3-1 software using the POLYCENTER Software Installation utility.

Note

HP strongly recommends that you read the release notes before proceeding with the installation. The DECwindows Motif product provides online release notes. See Section 2.2 for instructions on how to access this information.

This chapter presents information about the following topics:

1.1 License Registration

Before you install and run DECwindows Motif software 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 is provided along with the kit if you ordered the license and media together; otherwise, it is provided separately to a location based on your license order.

If you are installing DECwindows Motif software as an update on a node or cluster already licensed for this software, you have already completed the License PAK registration requirements.

You must register and load your license for DECwindows Motif before you run the Installation Verification Procedure (IVP) and use the software.

To register a license, log in to the system manager account (SYSTEM). Then choose one of the following options to register the license:

  • Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When the procedure prompts you for information, respond with data from your License PAK.
  • At the DCL prompt, enter the LICENSE REGISTER command with the appropriate qualifiers that correspond to License PAK information.

If you plan to use DECwindows Motif software on more than one node in a VMScluster, load the license on the other nodes after you complete this installation.

For complete information about using LMF, see the OpenVMS License Management Utility Manual.

1.2 Supported Hardware

DECwindows Motif for OpenVMS Alpha Version 1.3-1 software can be installed on any supported Alpha processor. For a complete list of supported hardware, see the HP OpenVMS Alpha Version 7.3--2 and DECwindows Motif for OpenVMS Alpha Version 1.3-1 Software Product Descriptions (SPDs).

1.3 Prerequisites for the Installation Procedures

Before you can install and configure DECwindows Motif software, you must have the required version of the OpenVMS operating system software, sufficient memory, and a license. (Refer to Section 1.1 for information about registering a License Product Authorization Key [PAK].)

Use the POLYCENTER Software Installation utility to install your DECwindows Motif software according to the operating system information provided in Section 1.4.

1.4 Required Operating System Software

The DECwindows Motif for OpenVMS Alpha Version 1.3-1 software requires that the OpenVMS Alpha Version 7.3--2 operating system be installed with the DECwindows support options described in Table 1-1. OpenVMS Alpha Version 7.3--2 is the only operating system version that supports DECwindows Motif Version 1.3-1.

If your system is not running a supported version of OpenVMS before you attempt to install DECwindows Motif, the installation fails.

A minimum of 64 MB of memory is required; at least 128 MB of memory is highly recommended.

The OpenVMS operating system provides two subsets of components to support DECwindows Motif. To use DECwindows Motif software, your system must be running a version of the OpenVMS system that includes the following components, as described in Table 1-1.

Table 1-1 DECwindows Motif Support Options for OpenVMS
Option Description
DECwindows Motif network transport and base system support This component is required to install DECwindows Motif and to run DECwindows Motif applications. During the installation of OpenVMS, you are prompted to specify whether you want to install this option.

To determine whether this option was installed during the installation of OpenVMS, check for the existence of the following file:

SYS$LIBRARY:DECW$TRANSPORT_COMMON.EXE

See Section 4.2 for information on adding DECwindows base support files after OpenVMS has been installed.

DECwindows X11 Display Server, fonts, and device drivers This component is necessary to display DECwindows Motif applications or any other X Window applications on your system. During the installation of OpenVMS, you are prompted to specify whether you want to install this option.

To determine whether this option was installed during the installation of OpenVMS, check for the existence of the following file:

SYS$SYSTEM:DECW$SERVER_MAIN.EXE

If the DECW$SERVER_MAIN.EXE file is not on your system, you cannot display DECwindows Motif or other X Window applications on your local system 1. The DECwindows Motif installation procedure asks whether you want to continue the installation without workstation support.

See Section 4.2 for information on adding DECwindows device support files and 75- or 100-dpi font files after OpenVMS has been installed.


1If this component is not installed locally, note that you can run DECwindows Motif applications and redirect their display to a remote system that does have the DECwindows X11 Display Server installed.

Note

See the release notes and cover letter for the version of the OpenVMS operating system that you are running for more information about the DECwindows X11 Display Server.

1.5 OSF/Motif Release 1.1.3 and XUI Programming Support

The X Window System and OSF/Motif libraries that are provided with DECwindows Motif software are incompatible with those libraries provided with versions of DECwindows Motif prior to Version 1.2. Run-time compatibility is preserved, but the earlier OSF/Motif Release 1.1.3 and XUI programming environments are not compatible with the later OSF/MOTIF Release 1.2 programming environment.

Programming in the XUI and OSF/Motif Release 1.1.3 environments that were provided in previous versions of DECwindows Motif is no longer supported in the DECwindows Motif product. However, the installation procedure gives you the option of saving the XUI and OSF/Motif Release 1.1.3 programming files that already exist on your system. If you choose to save these programming files, they are moved to subdirectories where you can access them for programming. Specifically, the installation creates a subdirectory called [.DECW$113] in each of the directories listed in Table 1-2 and moves the previous files into the new [.DECW$113] subdirectory.

Table 1-2 Directories for Previous XUI or OSF/Motif Programming Environments
Directory Contents New Location
DECW$INCLUDE C header files SYS$SYSROOT:[DECW$INCLUDE.DECW$113]
SYS$SYSTEM UIL compiler SYS$SYSROOT:[SYSEXE.DECW$113]
SYS$LIBRARY Non-C language bindings SYS$SYSROOT:[SYSLIB.DECW$113]

Note

The process for using the saved programming environment is documented in Section B.2 of the release notes.

1.6 Saving Customized Bookreader Files

The installation procedure replaces the following file with a new version:

SYS$SYSROOT:[DECW$BOOK]LIBRARY.DECW$BOOKSHELF

If you customized this file and want to save it, copy the file to another directory or rename the file prior to the installation of DECwindows Motif software so that it is not deleted.

To copy your customized file to another directory, create the directory and define a global symbol in the file DECW$PRIVATE_APPS_SETUP.COM.

To create a Bookreader directory called SYS$COMMON:[DECW$BOOK_LOCAL], perform the following steps:

  1. Create the directory and assign world read access as follows:


    $ CREATE/DIRECTORY/PROTECTION=WORLD:R -
    _$ SYS$COMMON:[DECW$BOOK_LOCAL]
    
  2. Copy the LIBRARY.DECW$BOOKSHELF file to the new directory as follows:


    $ COPY SYS$SYSROOT:[DECW$BOOK]LIBRARY.DECW$BOOKSHELF -
    _$ SYS$COMMON:[DECW$BOOK_LOCAL]*/LOG
    
  3. If the SYS$MANAGER directory does not contain the DECW$PRIVATE_APPS_SETUP.COM command file, copy the template file to a command file as follows:


    $ COPY SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE -
    _$ SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM/LOG
    
  4. Edit the DECW$PRIVATE_APPS_SETUP.COM file and define the global symbol DECW$BOOK to point to your Bookreader directory by adding the following line to the file:


    $ DECW$BOOK == "SYS$COMMON:[DECW$BOOK_LOCAL]"
    
  5. Restart DECwindows Motif using the following command if you performed step 4 after installing the product and after DECwindows had been started (for example, after a reboot):


    $ @SYS$MANAGER:DECW$STARTUP RESTART
    

For more information about customizing your DECwindows Motif environment, see Managing DECwindows Motif for OpenVMS Systems.

1.7 Installation Procedure Requirements

This section discusses the requirements for installing the DECwindows Motif software using PCSI.

The installation procedure checks the following:

  • Whether any other users are logged in to the system
  • Whether you have the minimum required system account quotas and limits
  • Whether you have the minimum required disk space
  • Whether you have the minimum required system parameter values

1.7.1 Process Account Quotas

The installation procedure requires that the installation account has the minimum quotas shown in Table 1-3.

Table 1-3 Process Quotas for the Installation Account
Quota Name Value
ASTLM 250
BIOLM 150
BYTLM 64,000
DIOLM 150
ENQLM 2,000
FILLM 100

Use the OpenVMS AUTHORIZE utility to verify and to change process quotas for the installation account in the user authorization file (UAF). (Some sites may restrict the use of the AUTHORIZE utility to certain accounts or users.) For example, to change the BYTLM quota for the account-name installation account, enter the following commands:


$ SET DEFAULT SYS$SYSTEM
$ RUN AUTHORIZE
UAF> SHOW account-name
UAF> MODIFY account-name /BYTLM = 64000
UAF> SHOW account-name
UAF> EXIT
$ LOGOUT

After you change the quotas for the installation account, log out of the installation account and log in again for the new quotas to take effect. You can then proceed with the installation.

User account quotas are stored in the file SYS$SYSTEM:SYSUAF.DAT. For more information about modifying account quotas, see the description of the AUTHORIZE utility in the OpenVMS System Management Utilities Reference Manual.

1.7.2 Disk Space

Use Table 1-4 to determine the amount of free disk space that is required on the system disk to install DECwindows Motif components. However, because you can choose not to install all the components, your actual disk space requirement may be less.

To determine the number of free blocks on the system disk, enter the following command at the DCL prompt:


$ SHOW DEVICE SYS$SYSDEVICE

The installation procedure checks for free disk space on the system disk. If sufficient space is not available, the installation procedure provides the following options:

  • Install fewer optional files.
  • Terminate the installation, create more free disk space on the system disk, and restart the installation.
  • Continue the installation and risk running out of disk space.

Note

If you run out of free disk space during the installation, the installation procedure fails.

Table 1-4 Required Disk Space by Component (in Blocks)
Component/Subcomponent Requirement Subtotals Totals
Installation overhead: 40,000 1 40,000 40,000
LBX support: 990 990 990
Client software:      
  Client base kit 57,030 57,030  
  Desktop support      
    New Desktop 43,620    
    DECwindows desktop 7,850    
    Manual pages for
New Desktop
2,810    
    Desktop subtotal   54,280  
  Programming environment      
    C, C++ 7,890    
    FORTRAN 2,070    
    Pascal 3,060    
    New Desktop 150    
    Programming subtotal   13,020  
  Example programs      
    Sound examples 1,550    
    Programming examples 10,290    
    New Desktop examples 1,250    
    Examples subtotal   13,090  
  Translated image support 28,330 28,330  
  Client total     165,780
Total for all components:     206,740

1Includes excess disk space allocation (dependent on disk cluster size), PCSI overhead, and log files. The value shown is for the combined installation of LBX and the client software.


Next Contents Index