Progress/400
Product Guide
The Client Schema Holder
The server schema on the AS/400 and the client schema holder are key components in the DataServer architecture. These components allow client Progress applications to access objects on the AS/400.
Creating a client schema holder involves the following general steps:
The schema holder need not reside on the client machine. For example, for ease of maintenance, you can locate the schema holder on a file server that multiple clients can access.
Creating an Empty Progress Database
The Progress/400 environment uses the empty database on the client to create a schema holder for your DB2/400 data definitions.
An empty database on the client machine serves as a schema holder that the Progress/400 DataServer uses to access the data definitions that you moved to the AS/400.
There are four ways to create an empty Progress database:
See the Progress Database Administration Guide and Reference for information on these techniques.
This section describes how to create an empty database with the Data Administration tool. Follow these steps to create and connect an empty Progress database on your client machine:
- Start Progress with no database connected and access the Data Administration tool.
- From the main menu, choose Database
Create. The Create Database dialog box appears:
![]()
- Type the schema-holder name (for example, as4sh) in the New Physical Database Name field.
- Activate the An EMPTY Database radio button.
- Choose OK. The Connect Database dialog box appears. By default, the name of the newly created database appears in the Physical Name field:
![]()
You do not need to provide any additional connection information. You can add connection parameters when you create the database or edit connection information later. See the online help for a complete description of the Connect Database dialog box.
If you choose to add a logical database name in the Logical Name field, use the logical database name to refer to the database in your programming applications. For more information on database names, see the database access chapter in the Progress Programming Handbook.
- Choose OK to connect the empty Progress database and return to the Data Administration main window.
Next, run the Create DataServer Schema utility, as the "Creating the Client Schema Holder" section describes.
Creating the Client Schema Holder
Before you can create the client schema holder, you must:
Follow these steps to create the schema holder:
- Connect to an empty Progress database.
- From the Data Administration main menu, select DataServer
DB2/400 Utilities
Create DB2/400 DataServer Schema. The following dialog box appears:
![]()
- Type the name of the library that contains the empty server schema in the Dictionary Library Name field.
- Enter the logical database name.
- In the Code-Page field, type the name of the code page that the DB2/400 database files that contain your Progress definitions use. By default, the code page is IBM037.
If your DB2/400 database files will use a code page that Progress does not support, you must supply conversion tables that translate between the Progress client code page and the code page that the DB2/400 database files use. Entries for these tables must be placed in the
CONVMAP.DAT
file for the client.See the "User-defined Collation Tables" section in "System Administration," for more information on how the DataServer handles code pages and code-page conversion tables. For a complete discussion of code pages, see the Progress Internationalization Guide and the Application System/400 National Language Support Planning Guide .
- Enter the information that your network protocol requires, as Table 3–4 describes.
See the "Connecting at Startup" section in "Remote Access to Progress/400 DataServer," for a description of the required and optional connection parameters.
This connection information is stored with the schema holder. Progress uses the parameters that you provide here whenever you connect to the schema holder though the Data Dictionary or Data Administration tool.
- Choose OK. The utility loads the definitions of the P__ files.
The Progress Data Administration tool provides a set of DB2/400 utilities that you can use to maintain a client schema holder. "Remote Client DB2/400 Utilities," describes these utilities.
Loading Progress Definitions and Data to the AS/400
The next step in moving a Progress database to the AS/400 is to load the data definitions and data. Progress provides utilities that load data definitions (.df) and data (.d) files to the AS/400 server schema.
Follow these steps on your client machine:
- Connect to the client schema holder and your Progress/400 server schema.
- From the Data Admin main menu, choose DataServer
DB2/400 Utilities
Progress/400 Data Dictionary.
- Choose the Modify Schema button.
- Choose Admin
Load Data & Definitions
Load Definitions (.df).
- Enter the name of the .df file that you want to load and choose OK.
The utility loads the data definitions into the P__ files in the server schema. In addition, for each table, it creates a physical file on the AS/400. For each index, it creates a logical file.
The Progress length of the combined fields that make up an index must be less than 200 bytes. The Progress/400 length is some number less than 200, depending on the number of key fields used.
- Choose Edit
Commit.
- Return to read-only mode.
- Choose Admin
Synchronize Progress/400 Client to synchronize the client schema holder. Select the full synchronization option.
- Choose Admin
Load Data & Definitions
Table Contents (.d).
- Enter the name of the data (.d) file that you want to load.
- Repeat until you have loaded all the data files you require.
The utility uses the definitions in the client schema holder to load the data from the .d files into the appropriate data files on the AS/400.
Deploying a Schema Holder
The guidelines and techniques that apply to deploying a Progress database apply to deploying a schema holder for DB2/400 database files. However, you must make changes to both the supporting database and the schema holder. For example, when you provide DDS or a SQL script to modify DB2/400 database files, you must also provide a new data definitions file or 4GL code to update the schema holder. Use the Synchronize Progress/400 Client utility to update your deployed schema holder.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |