Kbase 16390: As/400: synchronisation of Server Schema and Client Schema Holder.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/21/2003 |
|
Status: Unverified
GOAL:
Description of synchronisation of Server Schema and Client Schema Holder.
FACT(s) (Environment):
AS/400
FIX:
Using Progress/400 requires the use of a Server Schema and a Client Schema Holder. The Server Schema is a DB2/400 library that contains physical and logical files designed to hold specific information that Progress needs to "know" about the actual database on the AS/400.
The Client Schema Holder is an empty Progress database that resides either on an individual client or on a network drive. This Schema Holder contains information that the Progress client needs to "know" about the actual database on the AS/400. These two Schemas must be in balance, or Synchronized, in order to function properly. The Synchronize function is done in two phases, Synchronize and
Verify. The first phase is the Synchronize. This assures that all pertinent database information is contained in both Schemas. The second phase is the Verify. The Verify process, which is optional, compares the information housed in the Server Schema against the actual DB2/400 database objects. If there are differences, Anomalies, they will be written to an error log that bears the Schema Holders name with the ".e" extention.
The Synchronize process, in a Client/Server environment, is initiated from the Client. The option is available from the Data Adminstration screen, Data Servers/DB2-400 V7 Utilities/Synchronize Progress-400 Client or from within the Progress/400 Data Dictionary in the Admin menu. Synchronize can also be done from within an application by incorporating the procedure as4sync.p into the application.