Kbase P3861: How to access existing DB2/400 Database
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
7/6/2005 |
|
Status: Verified
GOAL:
How to access existing DB2/400 Database
FACT(s) (Environment):
IBM AS/400 (RISC)
Progress/400 DataServer
FIX:
Should the existing DB2/400 database (files) be accessed through Progress/400 DataServer and be "visible" for the 4GL client, the following steps need to be performed:
- Establish basic connectivity between the client PC and the AS/400.
- Back up your DB2/400 database files.
- If the DB2/400 database files use a code page other than IBM037, make sure that you have the appropriate ALTSEQ tables to handle case issues. See the ?User-defined Collation Tables? section in Chapter 8, ? System Administration,? for a discussion of issues to consider.
- Run DUPPRODB to create the empty server schema on the AS/400 machine.
- Run CHGPRODCT to populate the schema files with data definitions for the DB2/400 database files.
- Create and synchronize a client schema holder.
- Adjust your code to account for differences in behavior between the Progress RDBMS and DB2/400.
- Decide how you will maintain the DB2/400 data definitions: either through DDS on the AS/400 machine or through the Progress/400 Data Dictionary on the client PC. Do not mix the two methods.
- If you use DDS to maintain data definitions, update the server schema with CHGPRODCT to reflect any modifications that you make to the DB2/400 definitions.
- Update the schema holder by doing a synchronization