Progress/400
Product Guide


Creating a Database Using Existing DB2/400 Data

This section explains how to create a database when your Progress/400 application uses existing data files; for example, from an RPG application. For more information, see Creating the Progress/400 Environment."

Follow these steps:

  1. Create an empty server schema on the AS/400 by running the DUPPRODB utility. Table A–2 notes the required DUPPRODB parameter values; additional parameters are optional.
  2. Table A–2: DUPPRODB Parameter Values Required for Using Existing Data  
    Parameter
    Option
    NEWDB(library name)
    Enter a library name or *CURLIB.
    FRMDB(*PROEMPTY)
    Use this empty server schema.
    OBJLIB(library name)
    Enter the library where data files defined with the Progress/400 Data Dictionary will be located. The default is *NEWDB, which puts the data files in the same library as the server schema. To put the data files in a separate library from the server schema, enter a library name.
    CRTLKT(*NO)
    Enter *YES if you want Progress locking behavior. Enter *NO if you want OS/400 locking behavior. You typically assign *NO if you are accessing existing AS/400 data files with this server schema and those files are used with other non-Progress data files.

    See "AS/400 Utilities," for more information on the DUPPRODB utility.

  3. Add the existing data files to the Progress/400 server schema by running the Progress/400 CHGPRODCT utility. Table A–3 notes CHGPRODCT parameter values to use.
  4. Table A–3: CHGPRODCT Parameter Values for Using Existing Data  
    Parameter
    Option
    PRODCT(library name)
    Enter a library name where the server schema is located or *CURLIB.
    FRMFILLST
    Enter a list of the data PFs that you want to access, or enter *ALL to access all files in a specific library. The utility automatically picks up the related logical files based on the Include Database Relations in this table.
    From Library(s)
    Enter a specific library name or enter *LIBL if the data files are in multiple libraries.
    Include Database Relations
    Enter *YES, the default, to preserve the logical file dependencies.
    FRCCHG
    Enter *YES to overwrite any Progress-specific attributes that you defined from the client ADE.

    Enter *NO to preserve the Progress attributes if a selected file was last updated from the Progress client. The utility does not update these files and returns an error message indicating that it did not update them.
    ERRLIMIT
    Enter *NOMAX to specify that the utility continue to run when an error occurs.

    When using this utility, note the following:

    • If you enter a specific library name for the From Library(s) parameter and want to add files from other libraries to the server schema, run CHGPRODCT again for each additional library.
    • If you enter *YES to Include Database Relations, CHGPRODCT automatically picks up related logical files in other libraries without specifying the other library names.
  5. Create a client schema holder for the server schema. See "Remote Client DB2/400 Utilities," for more information on client utilities.

Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095