POLYCENTER Software Installation Utility Developer's
Guide
The remove portion specifies commands to execute when the product is
removed. These commands are run before any product material is deleted
from the target disk. The EXECUTE...REMOVE statement has no effect when
the product is upgraded. To execute commands when the product is
upgraded by another version of the product, use the EXECUTE UPGRADE
statement.
Note
Previous versions of this manual incorrectly stated that EXECUTE
INSTALL...REMOVE commands are also run when the product is upgraded.
|
You specify the install and remove actions to perform by including one
or more DCL command lines in the EXECUTE INSTALL...REMOVE 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 INSTALL...REMOVE 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 INSTALL statement, specify them in
the USES option or in separate FILE statements. However, if you need
files for the EXECUTE REMOVE statement, you must provide them with FILE
statements so that they are available on the user's system for use when
the product is removed. Each file you specify with the USES option must
be present in the product material.
Note that 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 INSTALL...REMOVE statement causes the 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.
Note
The PCSI$SOURCE logical name is available only for the EXECUTE INSTALL
operation. You cannot use it for an EXECUTE REMOVE operation.
|
- 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 INSTALL...REMOVE statement is a utility directive and does
not specify a managed object.
See Also Section 6.1
EXECUTE ABORT
FILE
Example
|
file [SYSUPD]UNLOAD_LOADABLE_IMAGE.COM ;
execute
install "@PCSI$SOURCE:[SYSUPD]LOAD_LOADABLE_IMAGE.COM"
remove "@PCSI$DESTINATION:[SYSUPD]UNLOAD_LOADABLE_IMAGE.COM"
uses ([SYSUPD]LOAD_LOADABLE_IMAGE.COM) ;
|
In this example, the EXECUTE INSTALL...REMOVE statement sets up command
procedures to run when the product is installed and removed. The USES
option specifies the file name of the command procedure for use on
installation of the product. The file is deleted after use. The FILE
statement specifies the file name of the command procedure for use on
removal of the product. This file is placed in the user's destination
directory tree during installation and executed during removal.
EXECUTE LOGIN
The EXECUTE LOGIN statement displays a message when the product is
installed or reconfigured, informing the installer that the specified
commands need to be added to the login command procedure of every user
of this product.
Syntax
EXECUTE LOGIN (command,...) ;
Parameter
(command,...)
Indicates the commands that the utility displays in a message to the
user.
Description
The EXECUTE LOGIN statement displays a message when the product is
installed or reconfigured, advising the installer that the specified
commands need to be added to the login command procedure of every user
of this product. The specified commands are not run during the
installation or reconfiguration operation. The message is displayed
after the operation has completed successfully.
The EXECUTE LOGIN statement is a utility directive and does not specify
a managed object.
See Also Section 6.1
Example
|
execute login "$ @USER_START" ;
|
In this example, the EXECUTE LOGIN statement displays the following
message to users:
|
Users of this product require the following lines in their login procedure:
$ @USER_START
|
EXECUTE POSTINSTALL
The EXECUTE POSTINSTALL statement specifies commands to execute when
the product is installed or reconfigured. These commands are run after
any commands from EXECUTE INSTALL... and EXECUTE START... statements
are run.
Syntax
EXECUTE POSTINSTALL (command,...) [ INTERACTIVE ] [ USES
(file,...) ] ;
Parameter
(command,...)
Indicates the command 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 POSTINSTALL statement specifies commands to execute when
the product is installed or reconfigured. These commands are run after
any commands from EXECUTE INSTALL... and EXECUTE START... statements
are run.
You specify actions to perform by including one or more DCL command
lines in the EXECUTE POSTINSTALL 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 POSTINSTALL 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 POSTINSTALL 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.
Note that 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 POSTINSTALL 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.
|
