The database manager can provide DB2 Server for VSE 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. Installation instructions for HELP text is in the DB2 Server for VSE Program Directory 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. For online users, the first-level default is the LANGID supplied on the CIRB transaction. The second-level default is used for batch/ICCF users, and online users when LANGID is not specified. When one or more additional national languages have been installed, users can change the language from the default in the following ways:
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 103.
Figure 103. 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 21.
Table 21. 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 VSE operator cannot choose a double-byte character set (DBCS) language, as the VSE operator console does not support DBCS. The syntax of the SET LANGUAGE command is shown in Figure 104.
Figure 104. 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, you can specify only the LANGID. At startup, messages are displayed in the default national language.
The default language for ISQL in VSE is set using the LANGID parameter of
the CIRB transaction. If the LANGID parameter is not specified, the
default language for ISQL is the one specified in an internal table structure
called LANGBLK.
There is one LANGBLK table structure for each national language. The
database manager uses the language specified in the ARIMLBK TEXT
member.
A name is assigned to each LANGBLK table structure for each language, as
follows:
| Mixed case English | ARIMLBKD |
| Uppercase English | ARIMLBKU |
| French | ARIMLBKF |
| German | ARIMLBKG |
| Japanese | ARIMLBKJ |
| Simplified Chinese | ARIMLBKC |
To change the ISQL default language, rename the member for the language you want to use to ARIMLBKD, and relink-edit the ARISLKYD link book.
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.