Progress/400
Product Guide
Accessing an Existing DB2/400 Database
These are the tasks involved in creating the Progress/400 environment on the AS/400 and preparing your DB2/400 objects for access by the Progress client through the DataServer:
- 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 "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.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |