Custom Distribution Mastering Toolkit

Component script environment variables

The following environment variables are available for use in ccs and cqs scripts:

SSO_SHARED_ROOT

absolute pathname to the root of the /opt area for the component; available to both ccs and cqs scripts.

SSO_CLIENT_ROOT

absolute pathname to the root of the /var/opt area for the component; available only to ccs scripts in all phases after LOAD.

SSO_EXPORT_TARGET

target directory of an export (/usr, unless otherwise specified); available only to ccs scripts in the EXPORT phase.

CCS_PERSISTENT_STORAGE

absolute pathname to a directory that is guaranteed to exist across invocations of the ccs, once the LOAD phase completes; available to both ccs and cqs scripts. For example, use this directory to pass parameters from the cqs to the ccs.

Note the following restrictions when using CCS_PERSISTENT_STORAGE:

This variable is component- and version-specific, thus you cannot use it to pass parameters between components.
Do not use this variable to store permanent data for administration utilities of the component outside the software management operation. Use the /var/opt area of the SSO instead.
Do not use the directory specified by CCS_PERSISTENT_STORAGE to store data for use between an installation and a remove operation. Use the /var/opt area of the SSO instead.
The component must create the CCS_PERSISTENT_STORAGE directory structure because custom(ADM) does not impose any usage policy on this directory.
The actual value of this variable might change between software management phases, so components should not expect this directory to be located in the same place throughout the installation. However, the files in the directory remain untouched and are copied without changes.

SSO_UPGRADE_COMPONENTS

list of existing components to be upgraded; available to both cqs and all phases of the ccs scripts. SSO_UPGRADE_COMPONENTS lists only components to be upgraded, not packages.

See ccsSetup(CDMT) for the variables set in ccsSetup library.

The following keywords are passed to the ccs and cqs scripts:

OLD_CUSTOM_UPGRADE: keyword that specifies that this is an upgrade from an old (perms-list) component to a new (SSO-based) component; available to the cqs and all phases of the ccs scripts. The cqs should not run interactively when it receives the OLD_CUSTOM_UPGRADE keyword. Instead, cqs should save any configuration information to the CCS_PERSISTENT_STORAGE directory.
UPGRADE: keyword that specifies that this is an upgrade from an old version of an SSO-based component to a new version of an SSO-based component; available to the cqs and all phases of the ccs scripts.