The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →To use UTF-8 with TSM on AIX, first identify which process you are changing. A TSM client uses the AIX locale supplied through its LANG environment variable; TSM server messages use the server’s LANGUAGE option. Choose a UTF-8 locale that is actually installed on the host, configure the setting for the right process, and verify it in the process’s real startup environment.
Client or server: choose the right setting
These settings are not interchangeable. IBM’s TSM 7.1.3 UNIX/Linux client guide describes client language selection through the operating-system locale and LANG. IBM’s TSM 7.1.8 AIX server installation guide describes a separate LANGUAGE option for server messages. The instructions below are specific to those documented releases; check the documentation and supported language mappings for your installed version.
| Process | Setting | What to verify |
|---|---|---|
TSM client, such as dsmc |
AIX locale in the process environment, commonly selected with LANG |
Effective locale, terminal encoding for interactive use, and handling of representative filenames |
TSM server, dsmserv |
Server LANGUAGE option; for documented foreground startup, matching LC_ALL |
Supported server language value, required language package, messages, and date, time, and number formatting |
Check which UTF-8 locale AIX provides
On the target AIX host, run locale -a and choose an installed UTF-8 locale appropriate to the desired language. Locale names vary across operating systems, so do not assume a Linux or Solaris spelling will work on AIX. IBM’s APAR IT00934 gives EN_US.UTF-8 as an AIX environment example, but the output of locale -a is the practical check for your host.
After choosing a candidate, run locale in the environment that will launch TSM to inspect the effective locale settings. A locale available on the system is not necessarily the locale inherited by a scheduler or service.
Recommended Free Tools
#1 Best Overall
Set UTF-8 for a TSM client
- Set the environment before starting the client. In the shell or launch configuration that starts the client, set
LANGto the exact installed locale name. For example, iflocale -alistsEN_US.UTF-8, the corresponding shell assignment isexport LANG=EN_US.UTF-8. IBM documentsLANGas the way to specify the UNIX/Linux client language; use the locale available on your own AIX system. - Align interactive terminal encoding. When using an interactive client, configure the terminal to use a character set consistent with the selected locale. The locale, terminal character set, and filename encoding need to agree for non-ASCII names to display and be entered correctly.
- Test client behavior. Run the client through the same startup path that will be used in production. Check non-ASCII output and try representative filenames. IBM warns that names containing characters invalid in the selected DBCS or UTF-8 locale may be unenterable or may be skipped during wildcard backups.
Set UTF-8 for TSM server messages
For TSM 7.1.8 on AIX, IBM’s installation guide directs administrators to set the server’s LANGUAGE option in the server options file to the desired locale. The guide’s language table lists EN_US for English (UTF-8), along with other UTF-8 language values. Use the table for the installed server release rather than assuming a client locale name is also a valid server option.
- Check the release-specific language mapping. Confirm the exact
LANGUAGEvalue supported by your server version in its installation guide. - Set the option. Add or update
LANGUAGEin the server options file using the supported value. - Match the foreground environment when applicable. The TSM 7.1.8 guide says that when starting the server in the foreground, set
LC_ALLto match the value in the options file. Do not assume this instruction applies identically to every release or startup method. - Check language packages. If another server language package is needed, the guide describes using IBM Installation Manager’s Modify function to install a language package and its Update function to update installed packages. Confirm the package and locale mapping for your release before changing an older or newer installation.
A successful server locale initialization affects message language and date, time, and number formatting. IBM says that if initialization fails, the server uses U.S. English message files and formats.
Rank #2
Make sure scheduled and service-started processes inherit the setting
Changing a variable in an interactive shell does not establish that a daemon or scheduler receives it. Inspect the actual service or scheduler launch configuration and, where possible, the running process environment. IBM documented a case involving TSM client scheduler/CAD processes that started before LANG and LC_ALL were defined; that report concerns Red Hat Linux and IBM cautions that other Unix variants may behave differently. Treat it as a reason to check AIX’s actual launch environment, not proof of an identical AIX defect.
Troubleshoot locale and encoding problems
- The locale is rejected or appears to fall back: compare its spelling with
locale -a. IBM notes that locale names differ among operating systems. - Server messages remain in English: verify that the server
LANGUAGEvalue is supported, the relevant language package is installed, and—if using foreground startup—LC_ALLmatches the server option. Failed initialization can result in U.S. English messages and formatting. - Manual client runs work but scheduled runs do not: inspect the scheduler or service’s launch configuration and effective environment rather than relying on the interactive shell’s settings.
- Non-ASCII names are garbled, cannot be entered, or are omitted from wildcard backups: check the locale, terminal character set, and filename encoding together. IBM warns that characters invalid for the selected UTF-8 or DBCS locale can cause these problems.
IBM references and version limits
The client guidance cited here is for TSM 7.1.3 on UNIX/Linux, and the AIX server installation guidance is for TSM 7.1.8. IBM APAR IT00934 includes the historical note, “You must also set UTF-8 locale on the terminal along with “LANGuage AMENG” in the dsmserv.opt,” and shows LANG=EN_US.UTF-8 and LC_ALL=EN_US.UTF-8 as an AIX example. Treat that support record as historical context and confirm the correct option and locale for the target release.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallQuick Recap
Best Value
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
