HP OpenVMS Systems Documentation

POLYCENTER Software Installation Utility Developer's Guide

The BOOTSTRAP BLOCK statement updates the bootstrap block on the system disk to reference the bootstrap file.

Note As of OpenVMS Version 7.3, the BOOTSTRAP BLOCK statement is obsolete and its use is reserved for Hewlett-Packard. This statement is to be used by an operating system product, not by a layered product or other application. Documentation of the BOOTSTRAP BLOCK statement may be discontinued in a future release of this manual.

Syntax

Parameters

name

Indicates the bootstrap file specification. You must provide this file with a FILE statement. You must also ensure that the file has bootstrap scope and product or assembly lifetime (using the SCOPE statement).

IMAGE source

Indicates the file specification of the file that contains the bootstrap block image. You must provide this file with a FILE statement, and it must also have product scope and product lifetime.

Description

The BOOTSTRAP BLOCK statement specifies the file that the bootstrap block references and updates the bootstrap block on the system disk.

The BOOTSTRAP BLOCK statement also specifies a bootstrap block managed object that has the following characteristics:

• It is unnamed and unique within the bootstrap scope.
• It has operating lifetime and bootstrap scope.
• Managed object conflict is not recoverable.

Example

scope bootstrap;
  file [sysexe]vmb.exe;
end scope;
file [sysexe]bootblock.exe;
   .
   .
   .
bootstrap block [sysexe]vmb.exe image [sysexe]bootblock.exe ;

      

This example uses the BOOTSTRAP BLOCK statement to point the bootstrap block to the bootstrap file ([SYSEXE]VMB.EXE).

The DIRECTORY statement creates the specified directory if it does not already exist.

Syntax

Parameter

name

Indicates the directory name.

Options

[NO] ACCESS CONTROL (access-control-entry...)

Indicates the minimum access control entries (ACEs) that the directory will have. You must specify the ACEs as a quoted string. By default, directories have no added ACEs.

OWNER name

Indicates the account name that owns the directory. By default, the directory 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 directory protection to (S:RWE, O:RWE, G:E, W:E) so that users have execute access.

PROTECTION PRIVATE

Sets the directory protection to (S:RWE, O:RWE, G, W) so that users have no access.

PROTECTION PUBLIC

Sets the directory protection to (S:RWE, O:RWE, G:RE, W:RE) so that users have read and execute access. This is the default.

[NO] VERSION LIMIT maximum

Indicates the maximum number of file versions in the directory as an unsigned integer from 1 through 32767. The default is no version limit.

Description

The DIRECTORY statement creates the specified directory if it does not already exist. You use the DIRECTORY statement to create a directory, and to specify characteristics about the directory such as ownership and protection. However, use of the DIRECTORY statement is optional because the FILE statement will implicitly create a directory, if it does not already exist, to contain the file it provides.

The DIRECTORY statement specifies the name of a directory managed object. Check the other statements in your PDF to make sure the name you specify is unique among all directory, file, and link managed objects in all scopes.

The scope and lifetime of the directory managed object depend on whether it is lexically contained in a SCOPE, END SCOPE pair, as shown in Table 7-3. (See the SCOPE statement for additional information.)

Table 7-3 Directory Managed Object Scope and Lifetime

Type of Scope Group	Lifetime	Scope
Product	Product	Product
Global	Assembly	Global
Bootstrap	Operating	Bootstrap
Processor	Operating	Processor

If you use the access control option, the DIRECTORY statement specifies one access control entry (ACE) managed object that references the directory managed object for each entry specified with the ACCESS CONTROL option. The ACE managed object has the following characteristics:

• It is unnamed.
• It has operating lifetime.
• It has the same scope as the directory.

Examples

directory [SYSHLP.EXAMPLES.FMS.MESSAGE] protection private
     access control ("(IDENTIFIER=[FMS], ACCESS=READ)");

      

This example specifies the directory [SYSHLP.EXAMPLES.FMS.MESSAGE]. The PROTECTION PRIVATE option specifies that no users have access to this directory. The ACCESS CONTROL option grants the user FMS read access to the directory.

directory [AL] owner PCSI$TEST version limit 3;
      

In this example the directory [AL] is owned by the account PCSI$TEST and holds the maximum of three file versions.

directory [JIM] owner "[11,7]";
      

This example specifies the directory [JIM] owned by the account whose UIC is [11,7].

The END statement terminates a statement group.

Syntax

Parameters

None

Options

None

Description

The END statement terminates a statement group. See the statement referenced by the END statement for information about the statement group.

Example

product HP AXPVMS TEST V1.0 full ;
    .
    .
    .
end product ;

      

The END PRODUCT statement identifies the end of the product group.

The ERROR statement displays an error message during an installation or reconfiguration operation. The text is from a PTF text module.

Note The ERROR statement must be contained within an IF group.

Syntax

Parameter

name

Indicates, as a quoted or unquoted string, the name of the associated PTF text module. The name you specify can be from 1 to 31 characters in length and must be unique among all names in the same product description.

Option

ABORT

Forces an unconditional termination of the operation when the ERROR statement is executed. See Section 7.1 for usage constraints.

Description

The ERROR statement specifies a text module you want to display during an installation or reconfiguration operation. The ERROR statement must be contained within an IF group.

The utility processes ERROR statements in lexical order. The utility displays both prompt and help text during the validation phase. The validation phase occurs before and after the configuration of a product.

During execution of an ERROR statement that does not contain an ABORT option, the utility prompts the user to continue or terminate the operation. If the ABORT option is present, or the operation is executed in batch mode, the ERROR statement causes the operation to terminate unconditionally.

The ERROR STATEMENT is a utility directive and does not specify a managed object.

You must supply text in the associated product text module. The module must contain an =prompt directive line.

Examples

1. Suppose the PDF for a product contains the following lines:

   ---

   Previous

   Next

   Contents

   Index