Progress/400
Product Guide


Creating a Copy of an ALTLIB Database Structure

This section explains how to create a copy of a database with an ALTLIB structure, where data files (physical files and logical files) reside in one or more alternate libraries. The resulting copy also uses multiple libraries.

To use this method, follow these steps:

  1. Run the appropriate OS/400 commands to copy data files from the original library (where the data files are) to the library that will contain the copies.
  2. If data exists in multiple libraries, repeat Step 1 for each library.
  3. Run the DUPPRODB utility to create an empty server schema. Table A–5 notes DUPPRODB parameter values to use.
  4. Table A–5: DUPPRODB Parameter Values for Empty Server Schema  
    Parameter
    Option
    NEWDB(new library name)
    Enter a library name or *CURLIB.
    FRMDB(old library name)
    Enter the library name containing the existing server schema.
    COPYOPT(copy selection)
    Enter *FULLCOPY to copy data files with data, or enter *EMPTYCOPY to copy data files with no data. Either option creates all copies in the server schema library, regardless of where the original copies are located.
    OBJLIB(*NEWLIB)
    Locate your Progress/400 Data Dictionary data files here. Select the default option, *NEWDB, which places the data files in the same library as the server schema.

  5. Run the CHGPRODCT utility for each library created in Step 1. Table A–6 notes CHGPRODCT parameter values to use.
  6. Table A–6: CHGPRODCT Parameter Values for ALTLIB Database Structure  
    Parameter
    Option
    PRODCT(library name)
    Enter a library name where the server schema is located or enter *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.
    RTNPROATR
    Enter *YES to preserve Progress data-file properties.
    FRCCHG
    Enter *YES to preserve non-Progress data-file properties such as select/omit.
    ERRLIMIT
    Enter *NOMAX to specify that the utility continue to run when an error occurs.

    NOTE: If you run CHGPRODCT against data files that were created using Progress or that contain Progress-specific properties, you must specify the RTNPROATR parameter to retain these properties.

  7. 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