HP-UX Reference (11i v3 07/02) - 1M System Administration Commands N-Z (vol 4)

s
swask(1M) swask(1M)
Environment Variables
The environment variables that affect the
swask command are:
LANG Determines the language in which messages are displayed. If LANG is not specified or
is set to the empty string, a default value of
C is used. See lang(5) for more informa-
tion.
NOTE: The language in which the SD agent and daemon log messages are displayed is
set by the system configuration variable script,
/etc/rc.config.d/LANG
.For
example,
/etc/rc.config.d/LANG
, must be set to
LANG=ja_JP.SJIS
or
LANG=ja_JP.eucJP
to make the agent and daemon log messages display in
Japanese.
LC_ALL Determines the locale to be used to override any values for locale categories specified by
the settings of
LANG or any environment variables beginning with
LC_.
LC_CTYPE Determines the interpretation of sequences of bytes of text data as characters (e.g.,
single-versus multibyte characters in values for vendor-defined attributes).
LC_MESSAGES
Determines the language in which messages should be written.
LC_TIME Determines the format of dates (create_date and mod_date) when displayed by swlist.
Used by all utilities when displaying dates and times in
stdout, stderr, and log-
ging
.
TZ Determines the time zone for use when displaying dates and times.
Environment variables that affect scripts:
SW_CATALOG
Holds the path to the Installed Products Database (IPD), relative to the path in the
SW_ROOT_DIRECTORY
environment variable. Note that you can specify a path for the
IPD using the
installed_software_catalog
default option.
SW_CONTROL_DIRECTORY
Defines the current directory of the script being executed, either a temporary catalog direc-
tory, or a directory within in the Installed Products Database (IPD). This variable tells
scripts where other control scripts for the software are located (e.g. subscripts).
SW_CONTROL_TAG
Holds the tag name of the control_file being executed. When packaging software, you can
define a physical name and path for a control file in a depot. This lets you define the
control_file with a name other than its tag and lets you use multiple control file definitions
to point to the same file. A control_file can query the SW_CONTROL_TAG
variable to
determine which tag is being executed.
SW_LOCATION
Defines the location of the product, which may have been changed from the default product
directory. When combined with the
SW_ROOT_DIRECTORY
, this variable tells scripts
where the product files are located.
SW_PATH
A PATH variable which defines a minimum set of commands available for use in a control
script (e.g.
/sbin:/usr/bin).
SW_ROOT_DIRECTORY
Defines the root directory in which the session is operating, either "/" or an alternate root
directory. This variable tells control scripts the root directory in which the products are
installed. A script must use this directory as a prefix to
SW_LOCATION to locate the
product’s installed files. The configure script is only run when SW_ROOT_DIRECTORY is
/.
SW_SESSION_OPTIONS
Contains the pathname of a file containing the value of every option for a particular com-
mand, including software and target selections. This lets scripts retrieve any command
options and values other than the ones provided explicitly by other environment variables.
For example, when the file pointed to by SW_SESSIONS_OPTIONS is made available to
a request script, the targets option contains a list of software_collection_specs for all targets
specified for the command. When the file pointed to by SW_SESSIONS_OPTIONS is
HP-UX 11i Version 3: February 2007 − 6 − Hewlett-Packard Company 445