|
POLYCENTER Software Installation Utility Developer's Guide
if ( < software DEC AXPVMS VMS version below V6.2 > ) ;
error UNSUPP_VMS_VER abort ;
else ;
-- include your PDL statements here
end if ;
|
If you do use the SOFTWARE statement, you should expect the following
results:
- If the installed version of OpenVMS is different than the one
specified by the SOFTWARE statement, and the OpenVMS product kit is not
available, an error message prompting the user to terminate the session
is issued. This might be the result you are trying to achieve, but the
SOFTWARE function is still the better choice.
- If the installed version of OpenVMS is different than the one
specified by the SOFTWARE statement, and an OpenVMS product kit
satisfying the software reference criteria is available, the utility
may attempt an upgrade of the operating system.
- If the installed version of OpenVMS is within constraints specified
by the SOFTWARE statement, the installation of the layered product may
complete successfully, but a permanent software reference is made in
the database from the layered product to the OpenVMS operating system.
This can lead to software reference conflicts if the OpenVMS operating
system is upgraded in the future.
Another drawback is that a
significantly greater amount of memory is consumed and additional
processing is done to check for software reference conflicts when
processing the SOFTWARE statements, which leads to diminished
performance.
See Also APPLY TO
IF
PRODUCT
UPGRADE
Examples
#1 |
software HP VAXVMS FORTRAN
version minimum V3.0 version maximum V5.0 ;
|
The SOFTWARE statement in this example specifies that this product
requires HP Fortran software. The version must be between 3.0 and 5.0.
#2 |
software HP VAXVMS FORTRAN version below V5.0 ;
|
The SOFTWARE statement in this example specifies that this product
requires HP Fortran software. The version must be less than (but not
equal to) 5.0.
#3 |
if ( < software HP AXPVMS COOL_PRODUCT
version minimum V3.0 kit accessible > ) ;
software HP AXPVMS COOL_PRODUCT version minimum V3.0 ;
else if ( < option NO_COOL_REFERENCE default YES with helptext > ) ;
file [SYSEXE]COOL_SUBSTITUTE.EXE ;
else ;
error MISSING_COOL ;
end if ;
|
In this example, the SOFTWARE function is used to search the source
directory for the COOL_PRODUCT kit. If the POLYCENTER Software Installation utility finds the
software package with Version 3.0 or higher on the system, the
reference to it is created with a separate SOFTWARE statement.
If the COOL_PRODUCT V3.0 or higher is not found, an option to install
its substitute (
file [SYSEXE]COOL_SUBSTITUTE.EXE]
) is offered to the user. If the user declines to accept the substitute
image, an error is issued and the user is prompted to either terminate
or continue the current session.
SYSTEM PARAMETER
The SYSTEM PARAMETER statement allows you to display a message to users
that expresses system parameter requirements for your product.
Note
The utility does not change system parameters.
|
Syntax
SYSTEM PARAMETER name { { CONSUME | REQUIRE }
value | MAXIMUM value | MINIMUM
value | <MINIMUM value MAXIMUM value
} ;
Parameter
name
Indicates the name of the system parameter. The parameter you specify
must be valid on the system where the product executes.
Options
CONSUME value
Indicates that the system parameter must be increased by the specified
value. Use this option when the product consumes a resource that is
controlled by the system 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 options.
MAXIMUM value
Indicates that the system 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 system 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 system 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 options.
Description
The SYSTEM PARAMETER statement displays a message to users about system
parameter requirements for your product after the installation. Note
that the utility does not adjust system parameters.
See Also INFORMATION
PROCESS PARAMETER
Example
|
system parameter vaxcluster require 1 ;
system parameter tty_classname require "TT" ;
system parameter pagedyn consume 200 ;
|
The statements in this example display the following messages:
|
This product requires the following system parameters
VAXCLUSTER value 1
This product requires the following system parameters
TTY_CLASSNAME value TT
This product requires the following system parameters
PAGEDYN add 200
|
UPGRADE
The UPGRADE statement specifies the versions of the product that can be
upgraded by the product kit being installed. If the product is
currently installed but its version does not meet the version selection
criteria in the UPGRADE statement, the installation is terminated. The
UPGRADE statement has no effect when the product is being installed for
the first time.
The UPGRADE function tests whether a version of the product in the
specified range is being upgraded by the current operation. If a
version of the product in the specified range is currently installed,
the function returns true; otherwise it evaluates to false. If no
version criteria are given, the function tests whether any version of
the product is currently installed.
Statement Syntax
UPGRADE { VERSION ABOVE version | VERSION BELOW
version | VERSION MAXIMUM version | VERSION
MINIMUM version | VERSION REQUIRED version |
VERSION ABOVE version VERSION BELOW version |
VERSION ABOVE version VERSION MAXIMUM version |
VERSION MINIMUM version VERSION BELOW version |
VERSION MINIMUM version VERSION MAXIMUM version
} ;
Function Syntax
< UPGRADE { VERSION ABOVE version | VERSION BELOW
version | VERSION MAXIMUM version | VERSION
MINIMUM version | VERSION REQUIRED version |
VERSION ABOVE version VERSION BELOW version |
VERSION ABOVE version VERSION MAXIMUM version |
VERSION MINIMUM version VERSION BELOW version |
VERSION MINIMUM version VERSION MAXIMUM version
} ] >
Options
VERSION ABOVE version
Establishes a lower version limit. The version identifier must be a
single quoted or unquoted string. Use this option to specify that the
product version must be greater than (but not equal to) the specified
version. You cannot use this option with either the VERSION MINIMUM or
VERSION REQUIRED option. By default, there is no lower version limit.
VERSION BELOW version
Establishes an upper version limit. The version identifier must be a
single quoted or unquoted string. Use this option to specify that the
product version must be less than (but not equal to) the specified
version. You cannot use this option with either the VERSION MAXIMUM or
VERSION REQUIRED option. By default, there is no upper version limit.
VERSION MAXIMUM version
Establishes an upper version limit. The version identifier must be a
single quoted or unquoted string. Use this option to specify that the
product version must be less than or equal to the specified version.
You cannot use this option with either the VERSION BELOW or VERSION
REQUIRED option. By default, there is no upper version limit.
VERSION MINIMUM version
Establishes a lower version limit. The version identifier must be a
single quoted or unquoted string. Use this option to specify that the
product version must be greater than or equal to the specified version.
You cannot use this option with either the VERSION ABOVE or VERSION
REQUIRED option. By default, there is no lower version limit.
VERSION REQUIRED version
Establishes a required version. The version identifier must be a single
quoted or unquoted string. Use this option to specify that the product
version must be equal to the specified version. You cannot use this
option with either the VERSION ABOVE, VERSION BELOW, VERSION MAXIMUM,
or VERSION MINIMUM option. By default, there is no required version
constraint.
Description
|