|
POLYCENTER Software Installation Utility Developer's
Guide
PROCESS PARAMETER
The PROCESS PARAMETER statement displays a message to users about
process parameter requirements.
Note
The utility does not adjust process parameters.
|
Syntax
PROCESS PARAMETER name { { CONSUME | REQUIRE }
value | MAXIMUM value | MINIMUM
value | MINIMUM value MAXIMUM value } ;
Parameter
name
Indicates the process parameter name. The name you specify must be
valid on the system where the product executes.
Options
CONSUME value
Indicates that the process parameter must be increased by the specified
value. Use this option when the product consumes a resource that is
controlled by the process parameter. The value must be a single
unquoted string that specifies an unsigned integer value. You cannot
use this option with either the MAXIMUM, MINIMUM, or REQUIRE option.
MAXIMUM value
Indicates that the process parameter must have a value less than or
equal to the specified value. The value must be a single unquoted
string that specifies an integer value.
MINIMUM value
Indicates that the process parameter must have a value greater than or
equal to the specified value. The value must be a single unquoted
string that specifies an integer value.
REQUIRE value
Indicates that the process parameter must have the specified value. The
value must be a single string that specifies a value of the parameter's
type. This option is valid for any parameter data type. You cannot use
this option with either the MAXIMUM, MINIMUM, or CONSUME option.
Description
The PROCESS PARAMETER statement displays a message to users after the
installation about process parameter requirements. Note that the
utility does not adjust process parameters.
See Also INFORMATION
SYSTEM PARAMETER
Example
|
process parameter ASTLM minimum 6;
process parameter BYTLM require 32768;
process parameter PRCLM consume 2;
process parameter FILLM maximum 40;
|
These statements display a message to users that a process that
executes the product must have the following process parameters:
ASTLM greater than or equal to 6
BYTLM set to 32768
PRCLM increased by 2
FILLM less than or equal to 40
PROCESS PRIVILEGE
The PROCESS PRIVILEGE statement displays a message to users about
process privilege requirements.
Note
The utility does not adjust process privileges.
|
Syntax
PROCESS PRIVILEGE (name[,...]) ;
Parameter
name
Indicates the process privilege names as a list. The privileges you
specify must be valid on the system where the product executes.
Description
The PROCESS PRIVILEGE statement displays a message to users after the
installation about process privilege requirements. The utility does not
adjust process privileges.
Example
|
process privilege (group, oper, tmpmbx, sysnam) ;
|
The statement in this example displays a message to the user that
processes using the product must have the GROUP, OPER, TMPMBX, and
SYSNAM privileges.
PRODUCT
The PRODUCT statement specifies product identification and other
descriptive information about the product. The PRODUCT and END PRODUCT
statements form a PRODUCT group.
Syntax
PRODUCT producer base name version kittype ;
[ PDL-statements ]
END PRODUCT ;
Parameters
producer
Indicates the legal owner of the software product. This parameter must
be a single quoted or unquoted string.
base
Indicates the base hardware and operating system combination on which
the product is intended to be installed. This parameter must be a
single quoted or unquoted string. By convention, the string AXPVMS
denotes an OpenVMS Alpha product, VAXVMS denotes an OpenVMS VAX
product, and VMS denotes a product applicable for either OpenVMS Alpha
or VAX.
Although any base system name can be used when you package a product,
Hewlett-Packard recommends that you use the names AXPVMS, VAXVMS, and
VMS when developing products for use on OpenVMS.
name
Indicates the name of the product. This parameter must be a single
quoted or unquoted string. The combination of the producer,
base, and name parameters must be unique among
products installed on the system.
version
Indicates the version of the product. This parameter must be a single
quoted or unquoted string.
kittype
Indicates the kit type of the product through use of one of the
following keywords or keyword phrases:
- FULL--a complete description of a layered product (application
software) that can be used to install or upgrade the product.
- OPERATING SYSTEM--a complete description of an operating system
that can be used to install or upgrade the product. Only one product or
operating system type can be installed on the system.
- PARTIAL--a partial (incomplete) description of a product that can
be used only to upgrade an existing version of the same product.
Installation of a partial kit changes the version number of the product
and can upgrade a product of type full, operating system, or platform.
A partial kit must contain an UPGRADE statement and have the same
producer-base-name identification string as the product it upgrades.
- PATCH--a partial (incomplete) description of a product that can be
used only to update an existing version of a product. Installation of a
patch kit does not change the version number of the product and can
update a product type: full, operating system, or platform. A patch kit
must contain an APPLY TO statement and have a different
producer-base-name identification string than the product it updates.
- PLATFORM--a complete description of a suite of products that can be
used to install or upgrade the entire set of products.
- TRANSITION--a complete or incomplete description of a product that
was installed on the system by another installation method, such as
VMSINSTAL. A transition kit is used only to register a previously
installed product; it does not contain any product material.
Registration using a transition kit defines the name of a product and
its managed objects in the POLYCENTER Software Installation product
database. After a product is registered, the utility can use this
information to satisfy software dependency requirements that other
products may have on the availability of this product.
The keyword
TRANSITION used alone denotes a layered product; the keyword phrase
TRANSITION OPERATING SYSTEM denotes an operating system.
- MANDATORY UPDATE--functionally identical to a patch kit. Its type
implies that the patch must be applied to the product it updates.
See Section 3.5 for a more detailed description of kit types and
example PDFs.
Option
PDL-statements
Any product description language statement or a group of statements
described in this reference section, except the PRODUCT and END PRODUCT
statements.
Required Terminator
END PRODUCT ;
Description
The PRODUCT statement specifies product identification and other
descriptive information about the product. The PRODUCT and END PRODUCT
statements form the product group. A product description file consists
of a product group and any other PDL statements that this group might
enclose.
The PRODUCT statement is a utility directive and does not specify a
managed object.
See Also APPLY TO
SOFTWARE
UPGRADE
Examples
#1 |
product HP VAXVMS FMS V2.4 full ;
file [sysmsg]fdvshr.exe image library ;
file [sysmsg]fmsmsg.exe ;
file [sysexe]fmsfed.exe ;
file [sysexe]fmsfaa.exe ;
file [sysexe]fmsfte.exe ;
directory [systest.fms] ;
file [systest.fms]ivp.exe ;
file [systest.fms]samp.flb ;
end product ;
|
The PRODUCT statement in this example identifies the product as FMS
version 2.4 that is intended to be installed on an OpenVMS VAX system.
#2 |
product HP AXPVMS INTERNET_PRODUCTS V1.1 platform ;
.
.
.
end product ;
|
The PRODUCT statement in this example identifies INTERNET_PRODUCTS
Version 1.1 as a suite of products (that is, a platform) for
installation on an OpenVMS Alpha system.
|