|
||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||
|
 |
 |
HP OpenVMS systems documentation |
|
| Previous | Contents | Index |
The PRODUCT_STARTUP.COM command procedure is executed during the installation. The PRODUCT_SHUTDOWN.COM command procedure is executed during the REMOVE operation or during a product upgrade.
| #2 |
|---|
file [SYS$STARTUP]ABS_STARTUP.COM ;
execute
start "@sys$startup:abs_startup.com"
stop "" ;
|
In this example, the EXECUTE START...STOP statement displays a message to users about command procedures they should run to start the product. Note that there are no commands executed when the product is stopped. The command procedure ABS_STARTUP.COM executes during the INSTALL operation, then the following message is issued:
Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM: @SYS$STARTUP:ABS_STARTUP.COM
The EXECUTE TEST statement specifies an installation verification procedure (IVP) to run after the product has been successfully installed or reconfigured to perform a functional test of the product.
(command,...)
Indicates the commands that the utility passes to the command interpreter in the execution environment.
INTERACTIVE
Allows communication between the user and the specified command or command procedure executing in a subprocess.
The EXECUTE TEST statement specifies an IVP to run after the product has been successfully installed or reconfigured to perform a functional test of the product. Prior to running this test, the product database is updated and closed. The product remains installed or reconfigured even if the functional test fails.See Also Section 6.1The user can prevent the running of the IVP by specifying the /NOTEST qualifier on the PRODUCT INSTALL or PRODUCT RECONFIGURE command.
You specify test actions to perform by including one or more DCL command lines in the EXECUTE TEST 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 need files for the EXECUTE TEST statement, you must provide them with FILE statements.
If you want your commands to prompt the user and accept the user's input, specify the EXECUTE TEST 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 TEST 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 TEST statement is a utility directive and does not specify a managed object.
file [SYSTEST]PROD$IVP.COM ;
execute
test "@sys$test:prod$ivp.com" ;
|
In this example, the EXECUTE TEST statement runs a command procedure to perform an installation verification test of the product.
The EXECUTE UPGRADE statement specifies the commands to execute when the product is upgraded by another version of the product.
(command,...)
Indicates the commands that the utility passes to the command interpreter in the execution environment.
INTERACTIVE
Allows communication between the user and the specified command or command procedure executing in a subprocess.
The EXECUTE UPGRADE statement specifies the commands to execute when the product is upgraded by another version of the product. These commands are run for the version of the product that is being replaced, not for the new version of the product. To run commands when the product is removed (but not upgraded by another version), use the remove portion of the EXECUTE INSTALL...REMOVE statement to specify the commands.See Also Section 6.1If you need files for the EXECUTE UPGRADE statement, you must provide them with FILE statements so that they are available on the user's system when the product is upgraded.
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 UPGRADE statement is a utility directive and does not specify a managed object.
file [sysupd]UPG_TASKS.COM ;
execute upgrade "@PCSI$DESTINATION:[SYSUPD]UPG_TASKS.COM" interactive ;
|
In this example, the FILE statement places the command procedure UPG_TASKS.COM on the destination disk during the product installation. The EXECUTE UPGRADE statement specifies that this command procedure is run only when this product is upgraded by the installation of the same or different version of the product. In the future, if an upgrade of the product is performed, this command procedure is run before any product material is deleted from the destination disk. Use of the INTERACTIVE option on the EXECUTE UPGRADE statement allows the command procedure to interact with the user via the SYS$INPUT and SYS$OUTPUT I/O channels.
The FILE statement creates a file on the target disk. If a file of the same name already exists, the POLYCENTER Software Installation utility may replace the file, depending on the options specified.
[ [NO] ACCESS CONTROL (access-control-entry...) ]
[
[NO] ARCHIVE ]
[ ASSEMBLE EXECUTE (command,...) [
ASSEMBLE USES (file,...) ] ]
[ [NO] GENERATION
generation ]
[ IMAGE LIBRARY ]
[ OWNER
owner ]
[ PROTECTION { EXECUTE | PRIVATE | PUBLIC } ]
[ RELEASE MERGE ]
[ RELEASE NOTES ]
[ SIZE size
]
[ SOURCE source ]
[ [NO] WRITE ] ;
name
Specifies the name of the file object to install on the user's system. The name consists of a relative file directory specification, file name, and file type. The file version is ignored because the utility determines the file version to use at installation time.
[NO] ACCESS CONTROL (access-control-entry...)
Indicates the minimum access control entries (ACEs) that the file will have. By default, files have no added ACEs (no access control).[NO] ARCHIVE
Allows you to preserve existing files during an upgrade. The POLYCENTER Software Installation utility appends _OLD to the end of the file type. For example, if you archived an existing file named STARTUP_TEMPLATE.SYS, the utility would rename it STARTUP_TEMPLATE.SYS_OLD. Note that the utility does not keep track of archived files as managed objects, or delete them when the product is upgraded or removed.If there are several versions of the existing file, the utility renames the latest file type before deleting all of the remaining file versions. By default, the POLYCENTER Software Installation utility does not preserve existing file versions (no archive). You cannot use this option with the RELEASE MERGE or WRITE option.
ASSEMBLE EXECUTE (command,...)
Establishes the contents of the file by executing the specified commands. Specify the command lines as quoted or unquoted strings.ASSEMBLE USES (file,...)
Indicates a list of additional files required by the ASSEMBLE EXECUTE option. You must include the relative file specification. Files specified with this option are placed in a temporary directory for use by the ASSEMBLE EXECUTE option and are automatically deleted after use. By default, the ASSEMBLE EXECUTE option does not require additional files.[NO] GENERATION generation
Indicates that the file has an explicit generation number. Specify the number as an unsigned integer in the range 0 through 4294967295. See the Description section for the meaning of this value. By default, the file does not have an explicit generation number (no generation), which is equivalent to 0.IMAGE LIBRARY
Indicates that the file's symbols are inserted into the system shareable image symbol table library. The file must be a shareable image.OWNER owner
Indicates the account name that owns the file. By default, the file is owned by the SYSTEM account. If you specify a numeric value for name, you must enclose the string in quotation marks, for example "[11,7]" .PROTECTION EXECUTE
Sets the file protection to (S:RWED, O:RWED, G:E, W:E) giving general users execute access.PROTECTION PRIVATE
Sets the file protection to (S:RWED, O:RWED, G, W), giving general users no access.PROTECTION PUBLIC
Sets the file protection to (S:RWED, O:RWED, G:RE, W:RE), giving general users read and execute access. This is the default.RELEASE MERGE
Indicates that library modules propagate during a version upgrade. If modules are present in the existing library but not in the new library, they are propagated to the new library. The file you specify with the name parameter must be a library. You cannot use this option with the ARCHIVE, RELEASE REPLACE, or WRITE option.RELEASE NOTES
Indicates that the file is a release notes file. Users can extract the release notes to a file using the DCL command PRODUCT EXTRACT RELEASE_NOTES. The release notes are created in the file DEFAULT.PCSI$RELEASE_NOTES in the current directory, or in the file specified by the user with the /FILE qualifier.SIZE size
Do not specify this option in your PDF. When you package your product, the utility calculates the size (in blocks) of the files you specify and provides this option in the output PDF. If you specify this option in the input PDF to a PRODUCT PACKAGE command, the option is ignored.SOURCE source
Specifies the name of the file to package that supplies the contents for the file specified in the name parameter of the file statement.
Previous Next Contents Index