HPlogo ALLBASE/SQL Message Manual: HP 3000 MPE/iX Computer Systems > Chapter 1 Introduction

Native Language Support

» 

Technical documentation

Complete book in PDF
» Feedback

 » Table of Contents

If your system has the proper message files installed, ALLBASE/SQL displays prompts, messages and banners in the language you select; and it displays system dates and time according to local customs. In addition, ISQL accepts responses to its prompts in the native language selected. However, regardless of the native language used, the syntax of ISQL and SQL commands--including punctuation--remains in ASCII. Note that MPE/iX does not support native language file names nor DBEnvironment names.

In order to use a native language other than the default, you must follow the steps below:

  1. Make sure your I/O devices support the character set you wish to use.

  2. Set the MPE job control word NLUSERLANG to the number (LangNum) of the native language you wish to use. Use the following MPE/iX command:

       SETJCW NLUSERLANG = LangNum

    This language then becomes the current language. (If NLUSERLANG is not set, the current language is NATIVE-3000.)

  3. Use the LANG = LanguageName option of the START DBE NEW command to specify the language of a DBEnvironment when you create it. Run the MPE/iX utility program NLUTIL.PUB.SYS to determine which native languages are supported on your system. Here is a list of supported languages, preceded by the LangNum for each:

          0 NATIVE-3000         9 ITALIAN            52 ARABICW
          1 AMERICAN           10 NORWEGIAN          61 GREEK
          2 C-FRENCH           11 PORTUGUESE         71 HEBREW
          3 DANISH             12 SPANISH            81 TURKISH
          4 DUTCH              13 SWEDISH           201 CHINESE-S
          5 ENGLISH            14 ICELANDIC         211 CHINESE-T
          6 FINNISH            41 KATAKANA          221 JAPANESE
          7 FRENCH             51 ARABIC            231 KOREAN
          8 GERMAN

Resetting the LANG variable while you are connected to a DBEnvironment has no effect on the current DBE session.

Feedback to webmaster