HP OpenVMS Systems Documentation

POLYCENTER Software Installation Utility Developer's Guide

The rest of this chapter describes each PDL statement in detail and provides examples of its use. The PDL statements are presented in alphabetical order. Certain statements can be used as functions in the evaluation of an IF statement. The functional form of a statement is documented along with the definition of the statement.

The ACCOUNT statement uses a command procedure to create a system account.

Syntax

Parameters

name

Indicates the user name of the account as a 1- to 12-character string. The user name is passed to the command procedure as P1.

WITH (parameters,...)

Indicates the list of parameters that are passed to the command procedure that creates the account. Each parameter must be a single unquoted or quoted string that specifies P2 through P8, in order. If there are no qualifiers to pass, specify a null string (" "). Refer to the Description section for the meaning of the parameters.

Description

The ACCOUNT statement uses a command procedure (SYS$UPDATE:PCSI$CREATE_ACCOUNT.COM) to create an account. The parameters that you pass to the command procedure that creates the accounts are:

• P1 specifies the user name of the account (using the name parameter).
• P2 specifies general AUTHORIZE qualifiers. If there are no qualifiers to pass, specify a null string (" ").
• P3 specifies a comma-separated list of rights identifiers to grant to the user name. These identifers must already exist, or be created with a separate RIGHTS IDENTIFIER statement.
• P4 through P8 specify other general AUTHORIZE qualifiers.

Certain AUTHORIZE qualifiers must be used with care. For example, /DIRECTORY=dir-name assigns a default directory name to be used by the account. However, the POLYCENTER Software Installation utility does not create this directory for you; you must make sure that it exists.

When you remove a product that created accounts, the utility uses a command procedure (SYS$UPDATE:PCSI$DELETE_ACCOUNT.COM) to delete accounts associated with your product. This happens regardless of whether the SYSUAF.DAT file is shared by another system disk.

Note In a future version, the utility may create and delete these managed objects directly without the use of command procedures. If this is the case, these statements will continue to function, but the command procedures may not be maintained or shipped with future versions of the utility.

The ACCOUNT statement specifies an account managed object that has the following characteristics:

• Its name is the value of the name parameter. The name must be unique among all account names.
• It has operating lifetime.
• Managed object conflict is not recoverable.

Example

account TEST with ("/priv=(tmpmbx, netmbx)",(1) "PCSI_TEST",(2) "/account=PCSI",(3) "/astlm=500/biolm=200/bytlm=96000", "/wsdefault=4000", "/flags=(nodisuser,genpwd)", "/pwdminimum=8");

In this example, the ACCOUNT statement creates the TEST account.

1. Parameter P2 specifies the TMPMBX and NETMBX privileges to be assigned to the TEST account.
2. Parameter P3 is a rights identifier. This name must exist on the system prior to executing the ACCOUNT statement. It can be created with a RIGHTS IDENTIFIER statement.
3. Parameters P4 to P8 assign certain values to the TEST account.

The APPLY TO statement specifies a product or product version that you want to update with a patch or mandatory update kit.

Note You must include an APPLY TO statement in a patch or mandatory update PDF to identify the product that is being updated. This statement is not valid in other types of PDFs.

Syntax

Parameters

producer

Indicates the legal owner of the software product. This parameter must be a single quoted or an unquoted string.

base

Indicates the base hardware/software system on which the product is intended to be installed. This parameter must be a single quoted or an unquoted string. By convention, the string I64VMS denotes an OpenVMS Itanium product, the string AXPVMS denotes an OpenVMS Alpha product, VAXVMS denotes an OpenVMS VAX product, and VMS denotes a product applicable for either OpenVMS Alpha or VAX.

name

Indicates the name of the product. This parameter must be a single quoted or an unquoted string. The combination of producer, base, and name parameters must be unique among products installed on the system.

Options

VERSION ABOVE version

Establishes a lower version limit. The version identifier must be a single quoted or an unquoted string. Use this option to specify that the product version must be greater than (but not equal to) the specified version. You cannot use this option with either the VERSION MINIMUM or VERSION REQUIRED option. By default, there is no lower version limit.

VERSION BELOW version

Establishes an upper version limit. The version identifier must be a single quoted or an unquoted string. Use this option to specify that the product version must be less than (but not equal to) the specified version. You cannot use this option with either the VERSION MAXIMUM or VERSION REQUIRED option. By default, there is no upper version limit.

VERSION MAXIMUM version

Establishes an upper version limit. The version identifier must be a single quoted or an unquoted string. Use this option to specify that the product version must be less than or equal to the specified version. You cannot use this option with either the VERSION BELOW or VERSION REQUIRED option. By default, there is no upper version limit.

VERSION MINIMUM version

Establishes a lower version limit. The version identifier must be a single quoted or an unquoted string. Use this option to specify that the product version must be greater than or equal to the specified version. You cannot use this option with either the VERSION ABOVE or VERSION REQUIRED option. By default, there is no lower version limit.

VERSION REQUIRED version

Establishes a required version. The version identifier must be a single quoted or an unquoted string. Use this option to specify that the product version must be equal to the specified version. You cannot use this option with either the VERSION ABOVE, VERSION BELOW, VERSION MAXIMUM, or VERSION MINIMUM option. By default, there is no required version constraint.

Description

The APPLY TO statement specifies the name of an installed product that a patch or mandatory update kit modifies. You can use options on this statement to limit the application of the patch or mandatory update either to a specific version of the product or to a range of versions. If you do not use version constraints, then you can modify any version of the product by installing a patch or mandatory update kit.

The APPLY TO statement is a utility directive and does not specify a managed object.

Example

product HP VAXVMS CSCPAT57 V1.0 patch ;
    apply to HP VAXVMS FORTRAN version required V2.0 ;
    patch image [SYSEXE]FORTRAN.EXE with [000000]CSCPAT57.PAT ;
end product ;
      

This example shows part of the product description for a patch to HP Fortran. As shown in the APPLY TO statement, you must have HP Fortran Version 2.0 installed to apply this patch.