HP OpenVMS Systems Documentation
Content starts here

POLYCENTER Software Installation Utility Developer's Guide

Previous Contents Index

The EXECUTE PRECONFIGURE statement is a utility directive and does not specify a managed object. See Also Section 6.1
EXECUTE ABORT
FILE

Example


execute preconfigure "@PCSI$SOURCE:[SYSUPD]EXEC_PREC.COM"
        uses [SYSUPD]EXEC_PREC.COM ;

In this example, the EXECUTE PRECONFIGURE statement sets up a command procedure to run before the product configuration begins. The USES option specifies the file name of the command procedure that is deleted after use.

EXECUTE PRE_UNDO

The EXECUTE PRE_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 before any directories, files, and modules are processed.

Syntax

EXECUTE PRE_UNDO (command,...) [ INTERACTIVE ] [ USES (file,...) ] ;

Parameter

(command,...)

Indicates the commands that the utility passes to the command interpreter prior to 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 PRE_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 before any directories, files, and modules are processed. This statement is useful for automatically running a command procedure in preparation for uninstalling one or more patch or mandatory product updates. The EXECUTE PRE_UNDO statement gives you the ability to do such things as ask the user questions, probe, or set the system environment before a patch kit is uninstalled.

You specify actions to perform by including one or more DCL command lines in the EXECUTE PRE_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 PRE_UNDO statement in a scope group (consisting of SCOPE and END SCOPE statements) has no effect on the way EXECUTE PRE_UNDO commands are processed.

If you want your commands to prompt the user and accept the user's input, specify the EXECUTE PRE_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 PRE_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 PRE_UNDO statements:

  • They can be packaged in a product kit only if the product is a patch or mandatory update type.
  • Only one EXECUTE PRE_UNDO statement is allowed per product.

The DCL commands supplied with the EXECUTE PRE_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 PRE_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 PRE_UNDO statement is a utility directive and does not specify a managed object.

See Also Section 6.1
FILE

Example


execute pre_undo "@PCSI$SOURCE:[SYSUPD]EXEC_PRE_UNDO.COM"
        uses [SYSUPD]EXEC_PRE_UNDO.COM
        interactive ;

In this example, the EXECUTE PRE_UNDO statement sets up a command procedure to run before 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. The INTERACTIVE option allows dialog between the user and the command procedure.

EXECUTE REBOOT

The EXECUTE REBOOT statement specifies commands that initiate a system reboot procedure at the conclusion of the PRODUCT INSTALL or PRODUCT RECONFIGURE operations.

Syntax

EXECUTE REBOOT (command,...) [ INTERACTIVE ] [ MANDATORY ] ;

Parameter

(command,...)

Indicates the commands that the utility passes to the command interpreter after completing product installation or reconfiguration, but just before exiting the operation with final status.

Options

INTERACTIVE

Allows communication between the user and the specified command or command procedure executing in a subprocess.

MANDATORY

Indicates that the system must be rebooted after the product installation or reconfiguration. If the MANDATORY option is not present, the system reboot is not required.

Regardless of whether this option is specified, the user is prompted in the configuration phase as to whether a reboot will be allowed at the end of the operation. If the MANDATORY option is set and the user does not want to perform a system reboot, the operation terminates before any product files are handled. If the MANDATORY option is not specified, and the user does not want to perform a system reboot, the operation is not terminated and continues until successful conclusion. No system reboot is performed.

Description

The EXECUTE REBOOT statement specifies commands to execute at the conclusion of the PRODUCT INSTALL or PRODUCT RECONFIGURE commands. These commands can perform any action the product developer desires, but the last one should invoke the system shutdown procedure.

You specify actions to perform by including one or more DCL command lines in the EXECUTE REBOOT 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 quotation marks (" "). If more than one action is desired, use parentheses to enclose the list.

Enclosing the EXECUTE REBOOT statement in a scope group (consisting of SCOPE and END SCOPE statements has no effect on the way EXECUTE REBOOT commands are processed.

If you want your commands to prompt the user and accept the user's input, specify the EXECUTE REBOOT 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 want to force a system reboot at the end of your product installation, you must use the MANDATORY option. Whether this option is present or not, the user is warned that the system shutdown may take place at the end of the operation and is prompted to accept it. If the MANDATORY option is set, the following message is issued: 


* Product DEC AXPVMS EXRT V1.0 requires a system reboot.

If the MANDATORY option is not used, the following message is issued: 


* Product DEC AXPVMS EXRT V1.0 recommends a system reboot.

In either case, the message is followed by this prompt: 


* Can the system be REBOOTED after the installation completes? [YES]

If the MANDATORY option is set and your response to the prompt is No, the operation terminates. If the MANDATORY option is not set and your response to the prompt is No, the operation continues, but the EXECUTE REBOOT statement will not be processed.

The EXECUTE REBOOT 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$DESTINATION is a root directory specification that points to the root directory where the product material was placed in the installation operation.

The EXECUTE REBOOT statement is a utility directive and does not specify a managed object.

See Also Section 6.1
FILE

Example


execute reboot "@SYS$COMMON:[SYSEXE]SHUTDOWN.COM"
              interactive ;

Previous Next Contents Index