The database manager can provide DB2 Server for VM messages and HELP text in several national languages. Messages and HELP text come with the product tape. For more information on HELP text, see the DB2 Server for VSE & VM Database Administration manual.
When the national language feature tape has been installed, national language support works this way:
The national language tape provided contains the following languages:
When the database manager is installed, you specify a default national language. This is a second-level default. The first-level default is the current CMS language setting. If that language is unavailable in the database manager, the second-level default is used. When one or more additional national languages have been installed, users can change the language from the default in the following ways:
If the language is installed on the database manager and in CMS, the user can issue SET LANGUAGE for that language in CMS. If the language is installed on the database manager but is not supported in CMS, the user cannot issue SET LANGUAGE for that language in CMS. When ISQL is being started, the user will receive messages in the current language setting in CMS (if the current language setting in CMS is unavailable in the database manager, the DB2 Server for VM default language is used). After ISQL has been started, the user can change the language for messages and HELP text.
The following paragraph only applies if you have VSE guest sharing:
The VSE online users can also choose the language they receive messages in by specifying the LANGID parameter on the CIRB transaction. For an explanation of the CIRB transaction, see Starting the Online Resource Adapter -- The CIRB Transaction.
National languages are identified to the database manager by a language name, and a LANGID (language identifier). These values are in the SQLDBA.SYSLANGUAGE table. If you have English and French installed on the database manager, the SQLDBA.SYSLANGUAGE table can look like the example in Figure 107.
Figure 107. Sample SQLDBA.SYSLANGUAGE Table
LANGUAGE LANGKEY REMARKS LANGID -------------- ------- --------------------------------------- -------- ENGLISH S001 ENGLISH VERSION OF HELP TEXT AMENG FRANCAIS S003 TEXTE D'AIDE FRANCAIS FRANC |
For the LANGUAGE and REMARKS columns, you can choose values appropriate for your organization.
For the LANGKEY and LANGID columns, you should keep the values supplied by the database manager.
The language keys (LANGKEY) and language identifiers (LANGID) used by the database manager are shown in Table 24.
Table 24. Language Keys and Language Identifiers
| LANGUAGE | LANGKEY | LANGID |
|---|---|---|
| ENGLISH (mixed case) | S001 | AMENG |
| ENGLISH (uppercase) | S002 | UCENG |
| FRENCH | S003 | FRANC |
| GERMAN | S004 | GER |
| JAPANESE | D001 | KANJI |
| CHINESE_SIMPLIFIED | D003 | HANZI |
You should not use the language keys and language identifiers (LANGID) shown above for other purposes. In addition, the language keys S007-S500 and D003-D500 are reserved for IBM use.
The language key is used to internally identify HELP text for a language. The LANGID can be used to choose a language for messages and HELP text. You can also specify the name of the language, as it is stored in the LANGUAGE column of the SQLDBA.SYSLANGUAGE table.
In ISQL, and on the operator console, you can specify a language or a LANGID on the SET LANGUAGE command. The syntax of the SET LANGUAGE command is shown in Figure 108.
Figure 108. The SET LANGUAGE Command
>>-SET LANGuage----+-language----+-----------------------------><
'-+--------+--'
'-langid-'
|
The language or LANGID you specify must match a value in the SYSLANGUAGE table, and must be installed. If your installation uses a double-byte character set, you should consider setting the DBCS option to YES. For information on the DBCS option, see Using Double-Byte Character Set (DBCS).
When using the LANGID parameter on the CIRB transaction, (if you have VSE guest sharing), or in CMS, you can specify only the LANGID. The LANGIDs used by the database manager are consistent with CMS LANGIDs. When a national language is not supported by CMS, but it is supported by the database manager, the database manager uses its own LANGID for the language. In ISQL, on the operator console, or when using the CIRB transaction (for guest sharing), you can use any LANGID shown in Table 24 if the language is installed on the database manager.
| Note: | Not all LANGIDs are supported in all operating systems. |
When you install the database manager, you are prompted for a location in which to install the CMS HELP text files. If you specify the production minidisk address (195), CMS HELP text in languages other than American English will be unavailable. If you install messages in more than one national language, you need a separate minidisk for each national language. Ensure that the minidisk (or minidisks) used cannot be accessed by other user IDs, including the database machine.
When installing the CMS Help files, you must use the disk known by the VM system for that language. The address of this disk is identified by the LANGMERG control file. For additional information on the LANGMERG control file, see the VM/ESA: CMS Command Reference manual.
If you have VSE guest sharing, you should install all languages on the VSE guest that you want to support on VSE. Users who use the DBS utility and the preprocessors from the VSE guest should specify the library containing the desired language in the LIBDEF statement of the job control.