6 DRD-Safe Packaging Changes

6.1 The is_drd_safe Attribute

The is_drd_safe fileset attribute is introduced in HP-UX 11i v2.

Attribute: fileset.is_drd_safe

•Status: For HP-created HP-UX software—optional for HP-UX 11i v2, required for 11i v3

•Description: Indicates that the fileset can be managed (installed, removed, verified and unconfigured) in a runcmd environment without affecting the running system environment; defaults to false (except for HP-UX 11i v2 patches as explained in the table below). A fileset can only be considered DRD-safe if both the fileset and product control scripts are DRD-safe. If a product level control script is not DRD-safe, all of the filesets for that product must be listed as unsafe (that is, the is_drd_safe attribute for each fileset in the product is set to false). If any fileset is selected for management (install, remove, verify, or unconfigure) and that fileset does not have is_drd_safe set to true, that fileset will be excluded from the list of software to be managed in a runcmd environment. This includes any filesets selected due to dependencies.

•Values:

ofalse: The fileset cannot be managed safely in a runcmd environment. o true: The fileset can be managed safely in a runcmd environment.

To be safely managed in a runcmd environment, the fileset should adhere to the guidelines in the other sections of this document.

•Policy:

General policy: Though it is possible for different filesets within a product to have different

is_drd_safe values, this should not be done. (For example, one fileset has true and another has false.) Doing this reduces the overall usefulness of DRD and can create problems for the system administrator. Therefore, as a DRD policy, all filesets within a product should have the same value (true or false) for the is_drd_safe attribute.