Ensuring that InfoSphere DataStage users have the correct localization settings (AIX® Solaris Linux)

If you installed globalization support (NLS), ensure that IBM® InfoSphere® DataStage® users have the correct settings specified for localization.

About this task

On most systems, the locale for individual users is set by using a system-wide default. For example, on Linux® systems, this default is defined in the /etc/sysconfig/i18n file. If the user who performed the installation used this default and all InfoSphere DataStage users are expected to inherit the same default, then you do not need to perform the steps that are described in this task.

However, in some cases, the locale that is set for an InfoSphere DataStage user might be different from the locale that was set during installation. For example, this problem might occur if the user who performed the installation used a locale that was not the default, or if a user set a private locale (for example, in their $HOME/.profile directory).

To ensure that InfoSphere DataStage users have the correct locale and environment settings, you can edit the environment variables in the dsenv file. The environment variables in the dsenv file affect the entire InfoSphere DataStage environment.

To define the environment variables on a per-project or per-job basis, use the IBM InfoSphere DataStage and QualityStage® Administrator client or the IBM InfoSphere DataStage and QualityStage Designer client.

Perform this task as soon as possible after installation, before any jobs are stored or compiled.

Procedure

  1. Log in to the operating system as the user who ran the installation program.
  2. Determine the locale and encoding name to use.
    The encoding must correspond to one of the encodings that InfoSphere DataStage supports.
    To determine the current locale that is set for the server operating system, use the locale command:
    locale
  3. Locate the following section in the dsenv file. By default, this file is located in /opt/IBM/InformationServer/Server/DSEngine. 
    #LANG="langdef";export LANG
#LC_ALL="langdef";export LC_ALL
#LC_CTYPE="langdef";export LC_CTYPE
#LC_COLLATE="langdef";export LC_COLLATE
#LC_MONETARY="langdef";export LC_MONETARY
#LC_NUMERIC="langdef";export LC_NUMERIC
#LC_TIME="langdef";export LC_TIME
#LC_MESSAGES="langdef"; export LC_MESSAGES
  4. Replace the occurrences of langdef with the locale and encoding name that were specified during installation.
    For example, the following settings specify that the locale is ja_JP and the encoding is UTF-8:
    LANG="ja_JP.utf8";export LANG
LC_ALL="ja_JP.utf8";export LC_ALL
LC_CTYPE="ja_JP.utf8";export LC_CTYPE
LC_COLLATE="ja_JP.utf8";export LC_COLLATE
LC_MONETARY="ja_JP.utf8";export LC_MONETARY
LC_NUMERIC="ja_JP.utf8";export LC_NUMERIC
LC_TIME="ja_JP.utf8";export LC_TIME
LC_MESSAGES="ja_JP.utf8"; export LC_MESSAGES
  5. Remove the comment marker (#) that is at the beginning of each line. Save the file.
  6. Restart the InfoSphere Information Server engine.

What to do next

Before performing any work from the InfoSphere DataStage command line, InfoSphere DataStage users must issue the following command:
. $DSHOME/dsenv