Progress/400
Product Guide
Duplicate Progress/400 Database (DUPPRODB)
Use the DUPPRODB utility to perform the following tasks:
- Create a Progress/400 server schema.
- Duplicate an existing Progress/400 server schema and DB2/400 database files, with or without data. See the "Creating Test and Production Environments" section in "System Administration," for a detailed description of using the DUPPRODB utility to duplicate dictionaries.
- Create a schema image.
NOTE: All of the files in the dictionary that you want to copy should have *OBJEXIST, *OBJMGT, *OBJOPR, and *READ authority to the user performing DUPPRODB operations.Table 10–9 describes the DUPPRODB parameters.
Table 10–9: DUPPRODB Parameters Parameter Keyword Value New Progress/400 DB Name NEWDB Enter the name for the new library that the utility creates or *CURLIB to specify the current library. From Progress/400 DB Name FRMDB Enter *PROEMPTY to duplicate an empty Progress/400 server schema in the new library.Enter the name of an existing Progress/400 server schema.Enter *PROSPORT or *PRODEMO to duplicate the server schema of the Progress demonstration database. Dictionary Copy Option CPYOPT This option appears only if you do not enter *PROEMPTY in the FRMDB option. If it appears, enter one of the following options:- Enter *FULLCPY to create the server
schema in NEWDB and duplicate the
objects defined in the server schema in
the library specified at the Database
Object Library parameter. The new
objects contain the data stored in the
existing objects.- Enter *EMPTYCPY to copy only the
objects contained in a Progress/400
Data Dictionary and no data. It creates
the server schema in the NEWDB from
the FRMDB and the objects defined in
the server schema. The new objects do
not contain data. If you want the objects
to be created in a library other than the
library that contains the server schema,
specify that library at the Database
Object Library option. The utility creates
the empty object in the OBJLIB and
updates the references to that library in
the server schema.- Enter *DCTONLY to copy only the
server schema from the FRMDB to the
NEWDB and no objects or data. If your
NEWDB already has a server schema
defined, enter *YES at the Overwrite
Existing Dictionary option.If the utility encounters a failure, it backs out any duplications and restores the NEWDB library to its prior state. Create Schema Image CRTSCHIMG Enter *YES to create a schema image. The schema image automatically synchronizes with the server schema. The default value for this parameter is *NO. Case Sensitive
Altseq Table ALTSEQ Enter *NONE if the DB2/400 database files that you are accessing use the IBM037 code page. If the objects use any other code page, you must provide the names of the object files and libraries for the alternate collation and case tables. See "System Administration," for a discussion of code pages and for descriptions of alternate sequence tables. Case Insensitive
Altseq Table ALTSEQCI Enter the name of the case-insensitive alternate collating sequence table. The case-insensitive alternate collating sequence table parameter ensures the case-insensitive behavior that is consistent with Progress. The OS/400 is case sensitive by default. Enter *NONE if you require case sensitivity. Upper Case Table UPCASE Enter the name and library for the uppercase table that your DB2/400 database files use. Lower Case Table LOCASE Enter the name and library for the lowercase table that your DB2/400 database files use. Word Break Table SEPTABLE Enter the name and library of the word break table for your Progress/400 word indexes. DataServer Database Code Page DBCODPAG Enter the name of the code page that your DB2/400 database files use.By default, this parameter is set to *SYSVAL, the code page that your system uses. Your DB2/400 database files might use a different code page; enter its name here. The name must correspond to the name of the Case Sensitive Altseq Table on the AS/400 and to the name of a code page listed in theCONVMAP.DAT
file on the client. If the code-page name is not listed, you can add an entry for it. The client handles all code-page conversions; it converts only those fields that an application requests.See the character-processing chapter in the Progress Internationalization Guide for instructions. See the AS/400 National Language Support Planning Guide for more information on code pages. Dictionary Library Description TEXT Specify information to store in the P__DB description file. Overwrite Existing Srvr Schema OVRWRTDCT Enter *YES to overwrite an existing server schema in a library with the same name as the new Progress/400 dictionary. This is the default.Enter *NO to not overwrite the existing server schema. Database Object Library OBJLIB Enter *NEWDB to use the same library to contain both the Dictionary and the database files.Enter a library name or enter *CURLIB to specify the current library. If the library exists, the utility uses it to contain the database files. If the library does not exist, the utility creates it and places the database files in it. Create Progress Lock Table CRTLKT Enter *NO if you want OS/400 locking behavior. See "Common Product Information," for a comparison of Progress and OS/400 locking.Enter *YES if you want locking behavior that is compatible with Progress locking. The default is 500 locks. If more locks are needed, use CRTPROLKT.
The utility creates the server schema in the Progress/400 Dictionary Library. It contains the OS/400 files listed in Table 10–10.
The utility also creates the OS/400 objects listed in Table 10–11.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |