 |
POLYCENTER Software Installation Utility Developer's
Guide
The EXECUTE POSTINSTALL statement is a utility directive and does not
specify a managed object.
See Also Section 6.1
EXECUTE ABORT
FILE
Example
|
execute
postinstall "@pcsi$source:[sysupd]product_cleanup.com"
uses [sysupd]product_cleanup.com ;
|
In this example, the EXECUTE POSTINSTALL statement sets up a command
procedure to run after the product is installed. The USES option
specifies the file name of the command procedure that is deleted after
use.
EXECUTE POST_UNDO
The EXECUTE POST_UNDO statement specifies commands to execute when one
or more patch kits are uninstalled by executing the PRODUCT UNDO PATCH
command. These commands are run after all directories, files, and
modules are processed.
Syntax
EXECUTE POST_UNDO (command,...) [ INTERACTIVE ] [ USES
(file,...) ] ;
Parameter
(command,...)
Indicates the commands that the utility passes to the command
interpreter after uninstalling patch kits indicated in the recovery
data set being processed.
Options
INTERACTIVE
Allows communication between the user and the specified command or
commands executing in a subprocess.
USES (file,...)
Indicates the files required to execute the commands you specified in
the command parameter. The files listed with the USES option
are saved in the recovery data set. When the UNDO PATCH operation is
executed, these files are moved to a temporary directory for processing
and deleted after use.
Description
The EXECUTE POST_UNDO statement specifies commands to execute when one
or more patch kits are uninstalled by executing the PRODUCT UNDO PATCH
command. These commands are run near the end of operation, after all
directories, files, and modules are processed. This statement is useful
for automatically running a command procedure to perform cleanup or
restore the system environment after one or more patch or mandatory
product updates have been removed.
You specify actions to perform by including one or more DCL command
lines in the EXECUTE POST_UNDO 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.
Enclosing the EXECUTE POST_UNDO statement in a scope group (consisting
of SCOPE and END SCOPE statements) has no effect on the way EXECUTE
POST_UNDO commands are processed.
If you want your commands to prompt the user and accept the user's
input, specify the EXECUTE POST_UNDO 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 POST_UNDO statement, you must specify
each one of them with the USES option. Files listed with the USES
option are placed in the recovery data set (the [PCSI$UNDO_001]
directory tree) when the patch kit is installed and retrieved during
the PRODUCT UNDO PATCH operation.
There are certain restrictions on the use of the EXECUTE POST_UNDO
statements:
- They can be packaged in a product kit only if the product is of a
patch or mandatory update type.
- Only one EXECUTE POST_UNDO statement is allowed per product.
The DCL commands supplied with the EXECUTE POST_UNDO statement are not
executed during the product installation; they are merely registered in
the patch recovery data set description file for use in the PRODUCT
UNDO PATCH operation.
The EXECUTE POST_UNDO 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.
- PCSI$DESTINATION is a root directory specification that points to
the root directory where the patch or mandatory update product material
was placed in the installation operation.
- PCSI$SCRATCH is a subdirectory under the user's login directory
that commands can use for temporary working space. The utility
automatically deletes this directory and any files placed in it at the
end of the operation.
The EXECUTE POST_UNDO statement is a utility directive and does not
specify a managed object.
See Also Section 6.1
FILE
Example
|
execute post_undo "@PCSI$SOURCE:[SYSUPD]EXEC_POST_UNDO.COM"
uses [SYSUPD]EXEC_POST_UNDO.COM ;
|
In this example, the EXECUTE POST_UNDO statement sets up a command
procedure to run after the patch kit files are removed from the system
as a result of the PRODUCT UNDO PATCH command execution. The USES
option specifies the file name of the command procedure that is deleted
after use.
EXECUTE PRECONFIGURE
The EXECUTE PRECONFIGURE statement specifies commands to execute after
the user has selected the product for installation or reconfiguration,
but before the user is asked to select options for the product.
Syntax
EXECUTE PRECONFIGURE (command,...) [ INTERACTIVE ] [ USES
(file,...) ] ;
Parameter
(command,...)
Indicates the commands that the utility passes to the command
interpreter in the preconfiguration environment.
Options
INTERACTIVE
Allows communication between the user and the specified command or
commands executing in a subprocess.
USES (file,...)
Indicates the files required to execute the commands you specified in
the command parameter. Files for the EXECUTE PRECONFIGURE
statement cannot be supplied by a separate FILE statement because
EXECUTE PRECONFIGURE is processed before files are copied to the target
disk.
Description
The EXECUTE PRECONFIGURE statement specifies commands to execute after
the user has selected the product for installation or reconfiguration,
but before the user is asked to select options for the product. This
statement is useful for automatically running a command procedure in
preparation for installing your product. This command procedure is
packaged in the kit and is run before the standard configuration dialog
with the user begins. The EXECUTE PRECONFIGURE statement gives you the
ability to do such things as probe the system environment, ask the user
questions, and define logical names for use later in the processing of
LOGICAL NAME functions. The ability to conditionally provide product
material, or to perform other actions based on decisions made at the
very start of the operation, is a powerful and flexible mechanism.
Note
If you want to use LOGICAL NAME functions, the logical names must be
either defined by the action of EXECUTE PRECONFIGURE statements, or by
the user before the installation or reconfiguration operation is
initiated. The processing of an EXECUTE PRECONFIGURE statement cannot
be conditionalized by including it within an IF group that is
controlled by a LOGICAL NAME function. In such a case, the EXECUTE
PRECONFIGURE statement is always executed.
|
You specify actions to perform by including one or more DCL command
lines in the EXECUTE PRECONFIGURE 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.
Enclosing the EXECUTE PRECONFIGURE statement in a scope group
(consisting of SCOPE and END SCOPE statements) has no effect on the way
EXECUTE PRECONFIGURE commands are processed.
If you want your commands to prompt the user and accept the user's
input, specify the EXECUTE PRECONFIGURE 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 PRECONFIGURE statement, specify them
in the USES option. Each file you specify with the USES option must be
present in the product material.
Note that the USES option does 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.
The EXECUTE PRECONFIGURE 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 commands can use for temporary working space. The utility
automatically deletes this directory and any files placed in it at the
end of the operation.
|
