Bundles

1. Overview
2. Fields
   1. Common
   2. HP-specific
   3. HP instant ignition

Overview

Fields

Common

tag

The short identifier for the bundle. It appears in the Software Selection window as the basic name for the bundle.

For bundles which represent orderable products, the tag must be the CPL product/option string. The options must be in alphabetic order and under-bar separated. For example:

B3018A_AAH_APG

See SIDO's documentation for explicit rules on creating this product/option string.

limit 16 characters. Type tag_string/version_component

title

The one-line, more detailed name for the bundle. It appears in the Software Selection window.

This attribute will be seen often, so it should clearly and concisely describe the bundle. For bundles which represent orderable products this should be the same as the product description from the CPL entry. For bundles which are for trial-use software the title should include the word Trial.

limit 80 characters. Type one_line_string

description

A file or text string describing the bundle. The free-form ASCII style allows for a detailed description of your software.

limit 2kB characters. limit 72 characters/line. Do not use <TAB> characters. Type multi_line_string

revision

The revision (release) number of the bundle.

Follow the same policies as product.revision.

Type revision_string/version_component

architecture

The target system for which this bundle is intended. Summarizes the supported hardware and operating systems.

There are three parts of the architecture attribute: OS, OS revision, and machine type. The attribute is structured like:

<OS>_<OS revision>_<machine type>

The OS is always "HP-UX".

The OS revision is different for ISU and Core software. For Core software (BSU's and CSU's) the OS revision is identical to the revision attribute, so the architecture attribute changes for each HP-UX release. For ISU software the OS revision is the minimum OS revision necessary to run the software. For example, if the software runs on 10.00 and 10.10, then you would specify B.10.00.

The machine type can only have three values:

700	runs on series 700 only
800	runs on series 800 only
700/800	runs on either series 700 or series 800

limit 80 characters. Type one_line_string/version_component

machine_type

machine types on which the bundle will run (uname -m). May use shell pattern matching to cover a range of machine types. Some examples:

9000/7??	series 700 only
9000/[68]??	series 800 only
9000/[678]??	series 700 and series 800

limit 64 characters. Type uname_string

os_name

OS'es on which the bundle will run (uname -s)

HP-UX

limit 32 characters. Type uname_string

os_release

OS releases on which the bundle will run (uname -r). May use shell pattern matching to cover a range of releases. Some examples:

?.10.*	any 10.0 release
?.10.*|?.11.*	any 10.0 or 11.0 release

limit 32 characters. Type uname_string

os_version

OS versions on which the product will run. May use shell pattern matching to cover a range of releases.

*	Allow all versions

limit 32 characters. Type uname_string

category

The identifier for the bundle category. Visible to users only when they specify a software specification to select a class of bundles from the command line.

OrderedApps	for separate ordered application software bundles or IHUs
TrialUseApps	for trial use versions of orderable CPL products
OrderedHP-UX	for HP-UX ordered core bundles
HPUXEnvironments	for HP-UX operating environment bundles
UserLicenses	for multi-user license bundles
HPUXAdditions	for additional HP-UX functionality bundles

limit 16 characters. Type tag_string/version_component

category_title

The one-line, more detailed name for the bundle category which appears in the Select Bundles View dialog. There is a one-to-one relationship between category and category_title attributes.

OrderedApps	Ordered Software Applications
TrialUseApps	Trial Use Software Applications
OrderedHP-UX	Ordered HP-UX Bundles
HPUXEnvironment	HP-UX Operating Environments
UserLicenses	Multi-User Licenses
HPUXAdditions	Additional HP-UX Functionality

This attribute is automatically set by mkpkg based on the value of the category attribute.

Limit 80 characters. Type one_line_string

is_protected

Boolean attribute that is TRUE if the bundle requires a code word to unlock it before installation. This should only be the case if the bundle represents an orderable product.

Setting this attribute to TRUE does not force all filesets in the bundle to be encrypted, but at least one of the filesets should have the is_secure set to TRUE.

If any fileset in the bundle has is_secure set to TRUE, then is_protected must also be TRUE.

Type boolean

is_reference

A boolean which is true iff the bundle represents an orderable product. This attribute is automatically inferred by mkbdl based on the value of the category attribute. It is set to TRUE if the category is OrderedApps, OrderedHP-UX, or UserLicenses.

Type boolean

contents

This is a list of software specifications for products, sub-products, and filesets that are contained in the bundle. Each software specification should be fully specified and should explicitly list the revision, architecture, and vendor. Note that the revision is always the product revision not the fileset revision. For example:

X11.Development,r=B.10.00,a=HP-UX_B.10.00_700,v=HP

Type software_specification

HP-specific fields

hp_srdo

This field is composed of three sub-fields.

type

This field has the following possible values:

B	for BSU and CSU partners
I	for ISU partners
J	bundle goes only onto Japanese System Environment CD
K	bundle goes only onto Korean System Environment CD
S	bundle goes only onto Simplified Chinese System Environment CD or Traditional Chinese System Environment CD
O	bundle does not go onto any CD product

user

This field has the following possible values:

I	internal-only
T	trade-only
B	both

buntype

This field has the following possible values:

C	orderable product
O	all other bundle types

associated_bundles

This is a list of software specifications of bundles which will be contained in this bundle. This attribute is used by HP/SIDO when building mother bundles. It is a handy way of specifying distributions.

Mkbdl will automatically query the reference_depot for the contents of each associated bundle, and will automatically insert all the contents into the mother bundle.

Instant Ignition

factory_integrate

TRUE

title

The instant ignition identifier for the bundle. It should not be a duplicate of the bundle tag. The title should be unique, descriptive, and contain no white space.

limit 16 characters.

desktop

A boolean which specifies the bundle's compatibility with Desktop HP-UX.

swap

The minimum amount of swap space required for usable execution of the bundle software.

integer value of MB of swap space.

kernel_include

A list of device drivers and tunable kernel parameters to be added to the /stand/system file. The kernel is builtusing this file prior to performing the swinstall option on this bundle.

Note that this is for the factory integrated kernel.

corequisite

The tag of a bundle which is always to be loaded with this bundle when the instant ignition system is built.

locale

set_parms and VUE use this to display localized information. If this field is not set, both set_parms and VUE will default to English test, messages, and help screens.

This is required for all non-English Runtime and Desktop bundles. Should not be used in other bundles.

alt_prod_num

When a bundle can be ordered with two different product numbers, this field should specify the product number which is not the bundle's tag. The alt_prod_num field may only contain a single product number.

For example, if a bundle has two different product numbers, say B3531CA and B3945AA_APS_ABA, then the bundle tag should be B3531CA and the alt_prod_num should be B3945AA_APS_ABA.