With DB2 RXSQL you can use any one of several national languages for messages and HELP information. (The HELP information is not supported for non-DB2 Server for VM application servers or when using the DRDA protocol.) During installation, one language is established as a system default. The default can be changed.
The HELP information is provided by the RXSQLHLP EXEC. This EXEC retrieves DB2 RXSQL HELP text for DB2 RXSQL-specific topics and DB2 Server for VM HELP information. The DB2 Server for VM HELP information is the same text that ISQL provides. The information is retrieved in the language that you define as your default during the installation of DB2 RXSQL. If you do not specify a default language, it is provided in the system default language. You can overwrite this default to specify your own language. Define your DB2 RXSQL and DB2 Server for VM default languages using the RXSQLANG EXEC. This EXEC verifies and stores the specified DB2 RXSQL and DB2 Server for VM language defaults in your LASTING GLOBALV file.
If you have installed a national language support feature (for example, Kanji or French), and have decided to delete it, use the ELODNLS EXEC. For a full description of the ELODNLS EXEC, see "The ELODNLS EXEC".
The HELP text is stored internally in DB2 Server for VM tables, and can be retrieved and manipulated just like any data stored in the database. The RXSQLHLP EXEC issues SELECT statements on these tables. The tables used for DB2 RXSQL HELP text are created at DB2 RXSQL installation time. A list of the tables and a brief description of each is given in Figure 41.
Figure 41. Database Tables Used for DB2 RXSQL HELP Text
| Table Name | Definition | Description |
|---|---|---|
| SQLDBA.ELOOPTIONS | This table has the same definition as the SYSTEM.SYSOPTIONS catalog table. The only difference is the name of the first column: instead of SQLOPTION, the ELOOPTIONS table has RXSQLOPTION. The other two columns have the same names and definitions. | Holds the system default language for DB2 RXSQL HELP information (SYSTEM.SYSOPTIONS holds the system default language for DB2 Server for VM HELP information). |
| SQLDBA.ELOLANGUAGE | This table has the same column names and definitions as the SQLDBA.SYSLANGUAGE catalog table. | This table contains a row for each language installed for RXSQL. |
| SQLDBA.ELOTEXT1 | This table has the same column names and definitions as the SQLDBA.SYSTEXT1 table. | It also has the same usage as the SYSTEXT1 table. |
| SQLDBA.ELOTEXT2 | This table has the same column names and definitions as the SQLDBA.SYSTEXT2 table. | It also has the same usage as the SYSTEXT2 table. |
Refer to the DB2 Server for VSE & VM Database Administration manual for more information on the contents of the DB2 Server for VM tables and the relationships between them.
RXSQL acquires enough space at installation time for four or five languages. You may have to check the number of active data pages for the RXSQL DBSPACE RXSQHELP. To do this, type the following command from CMS:
RXSELECT DBSPACENAME,NACTIVE FROM SYSTEM.SYSDBSPACES WHERE DBSPACENAME = 'RXSQHELP'
If the NACTIVE value is close to 170 (256 less the index pages allowance), consider making the RXSQHELP DBSPACE larger by moving the HELP text to a larger dbspace. Refer to the DB2 Server for VSE & VM Database Administration manual for more information on expanding dbspaces.
The RXSQL ELODNLS EXEC deletes the CMS HELP files, the HELP text from a DB2 Server for VM application server, and the message repository for one or more languages. Delete American English HELP text only if absolutely necessary.
The HELP text is not supported for non-DB2 Server for VM application servers or when using the DRDA protocol.
To run the ELODNLS EXEC, you must have:
SQLINIT DBNAME(SQLDBA)
To run the ELODNLS EXEC, you must have:
>>-ELODNLS----+--------------------------+---------------------><
'-CONnect(SQLDBA/password)-'
|
When you run the ELODNLS EXEC, it prompts you to:
After the EXEC displays a list of the currently installed languages, you are prompted for the language keys of the languages to be deleted. You must specify the languages to delete. You can separate the language keys with commas or blanks.
Each time you make a selection and press ENTER, the language is flagged on the screen. When you complete your selections, press ENTER to process them.
When the current default language, as specified in the ELOOPTIONS table, is flagged for deletion, a list of the remaining languages and keys is displayed. Specify the key for the new default language and press ENTER.
If only one language remains on the system, it becomes the new default language.
Delete the flagged languages displayed on the screen from the database. To delete the languages, type Yes.
To exit from the procedure without deleting any HELP text languages, type No.
If you type Yes, the RXSQL HELP text for all languages marked for deletion is deleted from the database before you are prompted for deletion of the CMS HELP text and the message repository for each language.
If you want to delete the CMS HELP text for the current language, type Yes. You are prompted to type the disk information of the CMS HELP files of the current language. Be sure to give the correct information or you may delete the HELP text for another language.
If you do not want to delete the CMS HELP text for the current language, or you know that CMS HELP text does not exist for the current language, type No or QUIT to bypass the processing for this language. Processing continues for the next language flagged for deletion.
Prompts are issued for each language marked for deletion. The first prompts you to specify where the CMS HELP text is installed in your system.
The EXEC then displays the following defaults for the minidisk or SFS directory of the current language.
For minidisks the defaults are:
For SFS directories the defaults are:
You must either accept these default values or supply different values. If you decide to bypass the deletion and go to the next language, type QUIT.
If the ELODNLS EXEC is not successful: An error message identifies the problem. Correct the error and rerun the EXEC.
| Note: | The error message output is spooled to the printer. |
If the ELODNLS EXEC is successful: The summary message displays the status of all the languages marked for deletion. Check that:
Notes: