Document revision date: 19 July 1999

The execute abort statement specifies commands that execute when the install, configure, or reconfigure operation aborts before normal completion.

Syntax

execute abort (command,...) [ interactive ] [ uses (file,...) ] ;

Parameter

(command,...)

Indicates the command that the utility passes to the command interpreter whenever the operation fails.

Option

interactive

Allows communication between the user and specified command or commands 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 abort statement specifies commands that execute whenever the install, configure, or reconfigure operation fails after another execute command has been run. You specify actions by entering a command line, which the utility passes to the DIGITAL Command Language (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 listed, use parentheses.

Note The scope statement has no control over the execution of the commands specified with execute abort. Enclosing the statement in the scope group frame has no effect on the way the commands are executed.

If you want your commands to prompt the user and accept the user's input, specify the execute abort 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 abort 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 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 abort 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$DESTINATION is a root directory specification that points to the root directory where product material will be placed. The PCSI$DESTINATION logical is available except when the execute abort statement is called when the execute preconfigure statement fails. The PCSI$DESTINATION logical is not available until the configuration phase.
• 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$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 abort statement is a utility directive and does not specify a managed object.

Example

execute install "@PCSI$SOURCE:[SYSUPD]EXEC_INSTALL.COM" 
             remove "" uses [SYSUPD]EXEC_INSTALL.COM ; 
execute abort "@PCSI$SOURCE:[SYSUPD]EXEC_ABORT.COM" 
             uses [SYSUPD]EXEC_ABORT.COM ; 
 
      

In this example, the execute abort statement sets up a command procedure to run whenever the operation fails after the execute install command has been executed. It is intended to clean the user environment in case the commands supplied by execute install have left the user's system modified. The uses option specifies the file name of the command procedure that is deleted after use.

The execute install statement specifies commands that you want to execute when the product is installed. The remove part of the statement indicates commands you want to execute when the product is removed from the execution environment or is upgraded to a new version of the product.

Note The remove part of the statement is required even if there are no commands you want to execute when the product is removed. To indicate no command, use remove "".

Syntax

execute install (command,...) remove (command ,...) [ interactive ] [ uses (file,...) ] ;

Parameter

(command,...)

Indicates the command that the utility passes to the command interpreter in the execution environment.

Option

interactive

Allows communication between the user and specified command or commands 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 install...remove statement specifies commands that you want to execute when the product is installed. The remove part of the command indicates commands that execute when the product is removed from the execution environment. You specify actions by entering a command line, which the utility passes to the DIGITAL Command Language (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 listed, use parentheses.

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.

The scope statement controls the execution of the commands; the commands execute once in each scope.

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, they must be specified 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.

If you specify the execute install...remove statement in your PDF along with other types of execute statements, the statements are processed in the following order:

1. execute preconfigure
2. execute ...stop (if an upgrade)
3. execute install...
4. execute release
5. execute start...
6. execute postinstall
7. execute test

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.

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.

The execute login statement displays a message to users that they should execute the specified commands when the product is made available to a process.

Syntax

execute login (command,...) ;

Parameter

(command,...)

Indicates the command that the utility displays in a message to the user.

Description

The execute login statement displays a message to users that they should execute the specified commands when the product is made available to a process. You can use this statement to advise users of commands they should add to their login files.

The execute login statement does not specify a managed object.

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 
      

The execute postinstall statement specifies commands that execute after the product is made available to the system.

Syntax

execute postinstall (command,...) [ interactive ] [ uses (file,...) ] ;

Parameter

(command,...)

Indicates the command that the utility passes to the command interpreter in the execution environment.

Option

interactive

Allows communication between the user and 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 that execute after the product is made available to the system. You specify actions by entering a command line, which the utility passes to the DIGITAL Command Language (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 listed, use parentheses.

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.

The scope statement controls the execution of the commands; the commands execute once in each scope.

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.

If you specify the execute postinstall statement in your PDF along with other types of execute statements, the statements are processed in the following order:

1. execute preconfigure
2. execute ...stop (if an upgrade)
3. execute install...
4. execute release
5. execute start...
6. execute postinstall
7. execute test

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.

The execute postinstall statement is a utility directive and does not specify a managed object.

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.

The execute preconfigure statement specifies commands that execute before the user configuration phase of the install, configure, or reconfigure operations begins.

Syntax

execute preconfigure (command,...) [ interactive ] [ uses (file,...) ] ;

Parameter

(command,...)

Indicates the command that the utility passes to the command interpreter in the preconfiguration environment.

Option

interactive

Allows communication between the user and specified command or commands 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 preconfigure statement specifies commands that execute before the user configuration phase of the product being installed, configured, or reconfigured begins. You specify actions by entering a command line, which the utility passes to the DIGITAL Command Language (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 listed, use parentheses.

Note The scope statement has no control over the execution of the commands specified with execute preconfigure. Enclosing the statement in the scope group frame has no effect on the way the commands are executed.

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 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 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:

Note The PCSI$DESTINATION logical is not available until the configuration phase.

• 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$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 preconfigure statement is a utility directive and does not specify a managed object.

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.

	privacy and legal statement
5952PRO_007.HTML