Kbase 15929: How to Correctly Setup a 6.4B DBE Double Byte Database
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
How to Correctly Setup a 6.4B DBE Double Byte Database
PURPOSE:
-----------------------------------------------------------
To illustrate how to set up a Double Byte Enabled
Database and System Environment to ensure data and index
integrity.
HOW TO:
-----------------------------------------------------------
How to needs to be broken down into 3 seperate topics:
HARDWARE, ENVIRONMENT, DATABASE
HARDWARE:
-----------------------------------------------------------
Two (2) types of terminal/terminal emulators are supported
by Progress Version 6.4B, they are: Scholar Terminals, and
Unison-Tymlab's Business Session for Windows.
Scholar Terminals-with the following names 41041, c1010,
c1010j, c1010k, c1010t and c1010c are supported. The 41041
is the generic name and the c1010* are specific aliases for
each language. You will need to set up the NLIO
(Native Language Input/Output), Environment Variables,
parity, and stty configurables. See your Scholar Terminal
Manuals and Double Byte Enabled Progress Manual (Prod. Code
3202) on how to set up.
Business Session for Windows-terminal emulators for
Traditional Chinese (version 3.45) and Japanese (version
3.45J) are supported. When you start a Business Session
you must again set Environment Variables, parity, and stty
configurables, but you must also turn off the Asian Key
Processing switch (AKI mode) and choose a Business Session
Font. See your Business Session Manuals and Double Byte
Enabled Progress Manual (Prod. Code 3202) on how to set up.
ENVIRONMENT VARIABLES:
-----------------------------------------------------------
The following Variables MUST BE SET to ensure data and
index integrity.
PROLANG, PROTERM, PROCOLL.
These Environment Variables determine the language
characteristics that Progress uses and is also applied to
databases. For example, these variables determine the
lead-byte and trail-byte ranges that Progress uses and the
collation table used to sort indexes. It is absolutely
necessary to have these variables properly configured.
The available settings are:
PROLANG=japanese; export PROLANG
PROLANG=korean; export PROLANG
PROLANG=chinese-t; export PROLANG
PROLANG=chinese-s; export PROLANG
PROLANG=chinese-t; export PROLANG
PROLANG=chinese-s; export PROLANG
PROTERM=70094; export PROTERM -> Business Session
PROTERM=41041; export PROTERM -> Scholar Terminals
PROCOLL=$DLC/dbcs/procoll.hpj; export PROCOLL
(Japanese collation)
PROCOLL=$DLC/dbcs/procoll.hpk; export PROCOLL
(Korean collation)
PROCOLL=$DLC/dbcs/procoll.hpt; export PROCOLL
(traditional Chinese collation)
PROCOLL=$DLC/dbcs/procoll.hps; export PROCOLL
(simplified Chinese collation)
*******
SPECIAL NOTE: Patch 6.4B04 ensures that PROCOLL is
reasonably configured. If PROCOLL is not set properly,
Progress will not allow access by the user into the
database. Improper access to the database may cause data
and index corruption, so upgrading to this patch level is
STRONGLY recommended.
*******
DATABASE:
-----------------------------------------------------------
There are two (2) empty databases supplied by Progress -
empty.db and emptya.db.
The empty.db is the standard database supplied with all
progress and uses an internal collation table and uses an
ibm850 codepage.
The emptya.db is sent with DBE Progress and does not use an
internal collation table, instead it always uses the
collation table set by the PROCOLL variable. The emptya.db
also uses an undefined codepage allowing it to work with
multiple languages, and will rely on PROLANG to set the
input and output of data.
Progress 6.4B users should always use the emptya.db with
prodb to create their double-byte databases. [Protecting
the integrity of DBE database can be accomplished by
installing the 6.4B04 patch.]
(Refer to the Double Byte Enable Progress Manual.)
SUMMARY:
-----------------------------------------------------------
These are the steps to ensure data and index integrity
in a Version 6.4B DBE database.
1) Make sure that EVERY user sets PROLANG, PROTERM, PROCOLL
appropriately.
2) Create databases based on emptya.
3) Upgrade to 64b04.
If you are having any indexing problems with an existing
Asian db, we strongly recommend you verify that all users
have been setting the variables correctly, and also check
script files that may change a user's environment.
Upgrading to 6.4b04 will help you detect situations where
users do not have their environment set properly.
If the above steps are followed and Patch level 6.4B04 is
added, then your database will function as expected in
Double Byte Mode.
REFERENCE:
-----------------------------------------------------------
Double Byte Enable Progress Manual (Prod Code 3202), Chpt 5
Progress Software Technical Support Note # 15929