HP 3000 Manuals HP 3000 Manuals
Native Language Support
ALLBASE/NET is localizable to a variety of other languages, including
languages using 8-bit and 16-bit character sets. In MPE/iX, the default
language is called NATIVE-3000. A list of supported languages can be
found by running NLUTIL.PUB.SYS.
The ALLBASE/NET utility, NETUtil, has native language support for the
following:
* The alias name in the AliasDB file
* The DBEnvironment name in the AliasDB file (HP-UX DBEnvironments
only)
* Messages and prompts
* Yes/no responses
* Time and date formats
With the exception of the alias name, HP-UX DBEnvironment name, and
yes/no responses, all NETUtil commands and responses must be typed as
ASCII characters. All language sets have ASCII as a subset.
The DBEnvironment name in the AliasDB file can contain 8-bit or 16-bit
characters if the DBEnvironment it defines resides on an HP-UX system.
This is independent of the operating system of the client system where
the AliasDB file resides. For example, a NETUtil user on an MPE/iX
system can enter a 16-bit character string for the DBEnvironment name if
the DBEnvironment being accessed resides on an HP-UX server.
DBEnvironment names on MPE/iX are restricted to ASCII characters because
MPE/iX does not support names containing 8-bit and 16-bit characters,
whereas HP-UX does.
NETUtil does not prohibit users from entering 16-bit characters in node
names, login names, or DBEnvironment names. However, when the user
attempts to connect to a remote DBEnvironment from an ALLBASE/SQL
application, the connection fails if the operating system doesn't support
16-bit characters in node names.
To get localized messages, prompts, and yes/no responses for NETUtil, you
must have the appropriate ALLBASE/SQL message catalog installed for the
desired language. On MPE/iX, set the job control word "NLUSERLANG" to
the desired language number.
ALLBASE/NET has no effect on ALLBASE/SQL native language support. The
server process inherits the native language of its remote client process.
The language of the DBEnvironment itself is determined at create time by
the "LANG"= option of the START DBE NEW command, which must always be
invoked local to the server machine. The user's native language and the
language of the DBEnvironment should be the same. For additional
information about ALLBASE/SQL native language support, refer to the
ALLBASE/SQL Reference Manual.