Progress/400
Product Guide
Maintaining DB2/400 Data Definitions
The Progress/400 environment is not a static one. It supports two techniques for modifying the DB2/400 data definitions:
CAUTION: Do not use the Progress/400 Data Dictionary if your DB2/400 database files contain DDS definition attributes that are not supported by the Progress/400 DataServer. Any attributes that are not supported will be lost.- From the client using the Progress/400 Data Dictionary. Use this technique only from Progress clients running in MS-Windows. UNIX clients do not support the Progress/400 Data Dictionary. See "Remote Client DB2/400 Utilities," for information on using the Progress/400 Data Dictionary.
- On the AS/400 using DDS or SQL. Use this technique if your DB2/400 database files contain data that both Progress and AS/400 high-level languages (HLL) applications access.
When you make changes with DDS or SQL, do the following to make sure that the changes are reflected throughout the Progress/400 environment:
- Run the CHGPRODCT utility to update the Progress/400 environment with those changes. You must run this utility even if the only change you make is to move a DB2/400 file to another library.
- On the client machine, run the Synchronize Progress/400 Client utility to synchronize the client schema holder so that it reflects the changes that you made on the AS/400, or incorporate the
as4sync.p
procedure into your application. You must do this for each client.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |