POLYCENTER Software Installation Utility Developer's
Guide
In this example, the EXECUTE REBOOT statement sets up the system
shutdown command procedure to run after successful product
installation, but before the utility exits the operation with the final
status code.
EXECUTE RELEASE
The EXECUTE RELEASE statement specifies commands to execute when the
product is installed or reconfigured. These commands are run after any
commands from EXECUTE INSTALL... statements are run.
Note
Starting with OpenVMS V7.3, the EXECUTE RELEASE statement is obsolete.
To support existing product kits that may have used this statment, the
POLYCENTER Software Installation utility continues to process this
statement in a backward compatible manner. However, Heweltt-Packard
recommends that you do not use the EXECUTE RELEASE statement in new or
revised product kits. Instead, use the EXECUTE UPGRADE, EXECUTE
INSTALL...REMOVE, or the EXECUTE POSTINSTALL statements, as
appropriate. Documentation of the EXECUTE RELEASE statement may be
discontinued in a future release of this manual.
|
Syntax
EXECUTE RELEASE (command,...) [ INTERACTIVE ] [ USES (file,...) ] ;
Parameter
(command,...)
Indicates the commands that the utility passes to the command
interpreter in the execution environment.
Options
INTERACTIVE
Allows communication between the user and the specified command or
command procedure executing in a subprocess.
USES (file,...)
Indicates the files required to execute the commands you specified in
the command parameter. Use a separate FILE statement to
specify required files that are permanently placed in the user's
destination directory tree; use the USES option to specify required
files that are placed in a temporary directory and deleted after use.
By default, this statement does not require files.
Description
The EXECUTE RELEASE statement specifies commands to execute when the
product is installed or reconfigured. These commands are run after any
commands from EXECUTE INSTALL... statements are run. The name of this
statement could imply that it only runs when a product is upgraded or
removed; however, this is not the case. The EXECUTE RELEASE statement
is run under the same situations that the EXECUTE INSTALL... statement
is run. Because of its misleading name and duplicate functionality,
EXECUTE RELEASE is now obsolete.
Use the EXECUTE UPGRADE statement or the REMOVE portion of the EXECUTE
INSTALL...REMOVE statement to perform actions when your product is
upgraded or removed. To perform actions when your product is installed
or reconfigured, use either the EXECUTE INSTALL... or EXECUTE
POSTINSTALL statement.
You specify actions to perform by including one or more DCL command
lines in the EXECUTE RELEASE statement. These commands are passed for
execution to the DCL interpreter running in a subprocess. Enclose each
action, whether specified as a single DCL command or a command
procedure, in double quotes (" "). If more than one action is given,
use parentheses to enclose the list.
If you want your commands to prompt the user and accept the user's
input, specify the EXECUTE RELEASE statement with the INTERACTIVE
option. The INTERACTIVE option causes all output from DCL to be
displayed, unless you prevent it. In contrast, when the INTERACTIVE
option is not specified, output generated by DCL commands is displayed
only for lines that are interpreted as DCL messages, that is, those
beginning with a percent sign (%) in column one.
If you need files for the EXECUTE RELEASE statement, specify them in
the USES option or in separate FILE statements. Each file you specify
with the USES option must be present in the product material.
The USES option will not cause the listed files to be placed
permanently in your file system. As soon as the installation operation
completes, the files listed with the USES option are deleted. For this
reason, you must use the FILE statement for this execute operation and
any other operation in which you want your execute command procedures
placed permanently in your file system.
The EXECUTE RELEASE statement causes the POLYCENTER Software
Installation utility to define logical names for use by the subprocess
that executes the specified commands. The commands should use these
logical names to reference files, as follows:
- PCSI$SOURCE is a subdirectory in the root format under the user's
login directory that points to the location of the files specified by
the USES option. This logical name is defined for the subprocess in
which product-supplied commands execute. It is not the same PCSI$SOURCE
logical name that can be defined by a user, in the user's process,
pointing to the location of a product kit.
- PCSI$DESTINATION is a root directory specification that points to
the root directory for the current scope where product material will be
placed.
- PCSI$SCRATCH is a subdirectory under the user's login directory
that can be used by commands for temporary working space. This
directory and any files placed in it are automatically deleted at the
end of the operation.
The EXECUTE RELEASE statement is a utility directive and does not
specify a managed object.
See Also Section 6.1
EXECUTE INSTALL...REMOVE
EXECUTE POSTINSTALL
EXECUTE UPGRADE
FILE
Example
|
execute release "@pcsi$source:[sysupd]config.com" uses [sysupd]config.com ;
|
In this example, the EXECUTE RELEASE statement sets up a command
procedure to run when the product is installed or reconfigured. The
USES option specifies the file name of the command procedure that is
deleted after use.
EXECUTE START...STOP
The EXECUTE START...STOP statement is a compound statement that
performs two distinct actions:
- The "start" portion either specifies commands to execute when the
product is installed for the first time or upgrades a previously
installed version of the product.
- The "stop" portion specifies commands to execute when the product
is either removed or upgraded by another version of the product.
The EXECUTE START...STOP statement also displays a message at the
successful conclusion of the operation, advising the user to add the
specified commands to the appropriate systemwide startup or shutdown
command procedure.
Note
The STOP part of the statement is required syntax even if there are no
commands you want to execute when the product is removed. To indicate
no command, use
stop ""
.
|
Syntax
EXECUTE START (command,...) STOP (command,...) [
INTERACTIVE ] ;
Parameter
(command,...)
Indicates the commands that the utility displays in a message to the
user and also passes to the command interpreter in the execution
environment.
Option
INTERACTIVE
Allows communication between the user and the specified command or
commands executing in a subprocess.
Description
The EXECUTE START...STOP statement is a compound statement consisting
of a "start" portion and a "stop" portion.
The "start" portion either specifies commands to execute when the
product is installed for the first time or upgrades a previously
installed version of the product. These commands are run after any
EXECUTE INSTALL... statements have been processed, but before any
EXECUTE POSTINSTALL statements. In addition, a message is displayed at
the end of the operation telling users to add these commands to their
SYSTARTUP_VMS.COM file.
The "stop" portion specifies commands to execute when the product is
either removed or upgraded by another version of the product. These
commands are run before any product material is deleted from the target
disk and before any EXECUTE...REMOVE statements are processed. In
addition, a message is displayed at the end of the operation telling
users to add these commands to their SYSHUTDWN.COM file.
If you need files for the EXECUTE START...STOP statement, you must
provide them with FILE statements so that they are available on the
user's system for use after the installation completes.
If you want your commands to prompt the user and accept the user's
input, specify the EXECUTE START statement with the INTERACTIVE option.
The INTERACTIVE option causes all output from DCL to be displayed,
unless you prevent it. In contrast, when the INTERACTIVE option is not
specified, output generated by DCL commands is displayed only for lines
that are interpreted as DCL messages, that is, those beginning with a
percent sign (%) in column one.
The EXECUTE UPGRADE statement causes the POLYCENTER Software
Installation utility to define a logical name for use by the subprocess
that executes the specified commands.
It defines PCSI$DESTINATION as a root directory specification that
points to the root directory for the current scope where product
material will be placed.
The EXECUTE START...STOP statement is a utility directive and does not
specify a managed object.
See Also Section 6.1
EXECUTE ABORT
FILE
Examples
| #1 |
file [SYS$STARTUP]PRODUCT_STARTUP.COM ;
file [SYS$STARTUP]PRODUCT_SHUTDOWN.COM ;
execute
start "@sys$startup:product_startup.com"
stop "@sys$startup:product_shutdown.com" ;
|
In this example, the EXECUTE START...STOP statement displays a message
to users about command procedures they should run to start and stop the
product:
Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM:
@SYS$STARTUP:PRODUCT_STARTUP.COM
Insert the following lines in SYS$MANAGER:SHUTDOWN.COM:
@SYS$STARTUP:PRODUCT_SHUTDOWN.COM
|
|
