 
| Subject: | |
| From: | |
| Reply To: | F. Alfredo Rego |
| Date: | Wed, 24 Nov 1999 18:34:07 -0700 |
| Content-Type: | text/plain |
| Parts/Attachments: |
|
|
Tony Gil <[log in to unmask]> wrote:
>We've recently completed our Y2K upgrades on our HP3000 Series 969-320 (OS
>version C.05.08). When running DBUTIL on an Image database created some
>time ago, I received the following message:
>
>" This database has been created before support of Native Languages.
> The language is NATIVE-3000."
>
>What ramifications, if any, exist for any of the HP INTRINSIC dB calls on
>this database, as opposed to a IMAGE database which
>displays as:
>
>" The language is 0 - NATIVE-3000."
There are no (practical) ramifications. The only difference is that
the "old" database's RootFile has a 16-bit HalfWord filled with two
ASCII blanks instead of a 16-bit-integer language ID, which would be
0 on "newer" databases. Your "old" database also has several blanks
instead of a language mnemonic (the default language mnemonic is
"NATIVE-3000").
There are no ramifications because, when the IMAGE run-time
intrinsics detect a language ID = octal 020040, they assume -- on the
fly -- the default "NATIVE-3000" language.
DBUTIL's message should also say that IMAGE's run-time modules have
assigned the language ID 0 to your database, but it doesn't say so.
Even more, as soon as IMAGE detects that it is dealing with an old
database, IMAGE should just update the blanks in the RootFile and
should permanently "make a note" of the *default* run-time values so
that they become the *permanent* RootFile values. You would then see
DBUTIL's message only once. Oh, well...
>Thanks for your responses and ...HAPPY THANKSGIVING!
You are welcome. Happy Thanksgiving to you, too.
_______________
| |
| |
| r | Alfredo [log in to unmask]
| e | http://www.adager.com
| g | F. Alfredo Rego +1 208 726-9100
| a | Manager, R & D Labs Fax +1 208 726-2822
| d | Adager Corporation
| A | Sun Valley, Idaho 83353-3000 U.S.A.
| |
|_______________|
|
|
|
