Relocatable applications packaging

The application packaging must support relocatable installation.

The following are recommended guidelines:
  • A relocatable application package cannot deliver (write) inventory objects outside of its root install location.
  • A relocatable application package cannot deliver (write) data using packaging customization outside of its root install location.
  • The relocatable application package must contain the RELOCATABLE extended packaging attribute for each relocatable fileset. The fileset is the smallest installable unit that can be relocated.
  • The relocatable application package cannot have requisites that are located in external relocated paths. It can have requisites to filesets installed in the default install path or in its own install path.

Relocatable requisites

A new packaging semantic indicates relocatable requisite location. A packager can specify that a given requisite should be found in the default install path or in the relocated install path.

The following are the new requisite semantics that apply:
prereq_ r
prereq in relocated install path
ifreq_r
ifreq in relocated install path
coreq_r
coreq in relocated install path
instreq_r
instreq in relocated install path
The currently defined requisites types (prereq, ifreq, coreq, and instreq) are all default requisites (requisites that apply to the default install location).

TOC changes for relocatable packages

The following is a sample of the new requisite sections in the TOC file:
sscp.rte.1.0.0.5.U.PRIVATE.bff 4 R S sscp {
sscp.rte 01.00.0000.0005 1 N B En_US Sscp
[
*coreq bos.games 1.1.1.1  <-- default requisite in default requisite section
*prereq bos.rte 1.1.1.1   <-- default requisite in default requisite section
%
/usr/bin 20
/etc 20
INSTWORK 72 40
%
%
%
IY99999  1 APAR text here.
%
RELOCATABLE <-- attribute tag to denote relocatable package
%
*prereq bos.rte 1.1.1.1 <-- default requisite in relocated requisite section
*coreq_r bos.games 1.1.1.1 <-- relocated requisite in relocated requisite section
]
}
  • If the relocatable requisite section is present during a relocated installation, it is used as the requisite section for the installation.
  • If the relocatable requisite section is not present during a relocated installation, the default requisite section is used. This means all requisites will be default requisites.
  • A default installation (non-relocated) does not use the relocatable requisite section.