Upgrade Guide for DB2 UDB for z/OS and OS/390 > Upgrading a Database from the Midtier >

Transferring Dedup Files

Upgrades: All upgrades.

Environments: Development (midtier-centric) environment.

This topic is part of an upgrade process. See How to Perform the Upgrade.

During upgphys processing, one of the last steps (Generate dedup jcl files for 390) is generating the dedup files (dedup.jcl and dedup_prod.jcl) that you are going to use for your production environment upgrade. Once upgrep has generated these dedup files (by default, in the DBSRVR/DB2390/DBOUTPUT/UPGRADE directory), transfer them to the same directory on the Siebel Enterprise Server that you are going to use for your production environment upgrade.

NOTE:  These dedup.jcl and dedup_prod.jcl files are similar to files that you generate during the Prepare for Production upgrade process, which is also run before starting the production environment upgrade. Since both processes use the same information when generating the files, you can use the dedup files from either the upgphys process or Prepare for Production process.