|
POLYCENTER Software Installation Utility Developer's
Guide
Order Number:
AA--Q28MF--TK
January 2005
This guide describes how to package software products using the
POLYCENTER Software Installation utility. It describes the product
description language, product description files, product text files,
and other relevant concepts.
Revision/Update Information:
This manual supersedes the POLYCENTER Software Installation Utility Developer's Guide, Version 7.3-2
Software Version:
OpenVMS I64 Version 8.2 OpenVMS Alpha Version 8.2
Hewlett-Packard Company Palo Alto, California
© Copyright 2005 Hewlett-Packard Development Company, L.P.
Confidential 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.
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.
Intel and Itanium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other
countries.
Motif and UNIX are registered trademarks of The Open Group.
NFS is a registered trademark of Sun Microsystems, Inc.
Printed in the U.S.
ZK5952
The HP OpenVMS documentation set is available on CD-ROM.
This document was prepared using DECdocument, Version V3.3-1e.
Preface
Intended Audience
This guide is intended for individuals who are responsible for
packaging software products. You do not need to be a programmer to
package kits for software products, but you do need to understand the
POLYCENTER Software Installation utility commands and concepts.
Document Structure
This guide is organized as follows:
- Chapter 1 provides an overview of the POLYCENTER Software Installation utility.
- Chapter 2 defines some key terms and concepts.
- Chapter 3 describes writing the product description file. It also
contains sample product descriptions.
- Chapter 4 describes writing the product text file. It also
contains sample product text files.
- Chapter 5 describes how to package your product and manipulate
the kit.
- Chapter 6 presents advanced topics such as use of command
procedures and testing.
- Chapter 7 provides detailed reference material on product
description language statements and functions.
- Appendix A contains information about migrating from the
VMSINSTAL utility to the POLYCENTER Software Installation utility.
- The Glossary lists and defines POLYCENTER Software Installation
utility terminology.
Related Documents
The HP OpenVMS System Manager's Manual describes the tasks that system managers perform using
the POLYCENTER Software Installation utility. It explains operations
such as software installation and removal.
For additional information about HP OpenVMS products and services,
visit the following World Wide Web address:
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
The following product names may appear in this manual:
- HP OpenVMS Industry Standard 64 for Integrity servers
- OpenVMS I64
- I64
All three names---the longer form and the two shorter forms---refer to
the version of the OpenVMS operating system that runs on the Intel®
Itanium® architecture.
The following typographic conventions may be used in this manual:
...
|
A horizontal ellipsis in examples indicates 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.
|
.
.
.
|
A vertical ellipsis indicates 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 choices in parentheses if you specify more than one.
|
[ ]
|
In command format descriptions, brackets indicate optional choices. You
can choose one or more items or no items. Do not type the brackets on
the command line. However, you must include the brackets in the syntax
for OpenVMS directory specifications and for a substring specification
in an assignment statement.
|
|
|
In command format descriptions, vertical bars separate choices within
brackets or braces. Within brackets, the choices are optional; within
braces, at least one choice is required. Do not type the vertical bars
on the command line.
|
{ }
|
In command format descriptions, braces indicate required choices; you
must choose at least one of the items listed. Do not type the braces on
the command line.
|
bold type
|
This typeface represents the introduction of a new term. It also
represents the name of an argument, an attribute, or a reason.
|
italic type
|
Italic type indicates important information, complete titles of
manuals, or variables. Variables include information that varies in
system output (Internal error
number), in command lines (/PRODUCER=
name), and in command parameters in text (where
dd represents the predefined code for the device type).
|
Example
|
This typeface indicates code examples, command examples, and
interactive screen displays. In text, this type also identifies URLs,
UNIX commands and pathnames, PC-based commands and folders, and certain
elements of the C programming language.
|
UPPERCASE TYPE
|
Uppercase type indicates a DCL command, a product description language
statement, the name of a file, a logical name, or the abbreviation for
a system privilege.
|
-
|
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.
|
|