Migrating maps

Edit online

Use the Map Migration utility to move your virtual table maps from a development environment to a test or production environment or from one release to another.

Before you begin

Before using the Map Migration utility, make sure that the following prerequisites have been met:

  • IBM Data Virtualization Manager studio requirements
    If migrating DB2 virtual tables, target systems used by each table must be defined in the target server using one of the following definitions:
    • If you want to use the same target system name, define the target system name on the target server.
    • If you want to use a different target system name, then define the new target system name, and use the TSYS=OLD_TSYS,NEW_TSYS parameter in the AVZGNMPM batch migration utility.
  • Data Virtualization Manager server requirements

    Make sure that both the origin and destination servers have been started.

  • Data Virtualization Manager server security requirements

    The following table summarizes the security permissions required to use the migration utility:

    Table 1. Security permissions required to use the migration utility
    JCL libraryMap export PDSServer map data set
    The location where the JCL resides. The PDS library to which the exported metadata objects are unloaded. The AVZMAPP DD data set, which must be the first data set in the concatenation if the parameter NEW MAP DSN is not set.
    Batch user ID UPDATE CREATE

    READ

    		 N/A
    Server user ID N/A UPDATE UPDATE

    READ

About this task

The Map Migration utility facilitates change control of the virtual table maps. Change control is the process of moving the virtual table maps defined in a development environment to a test or production environment or from one release to another.

You can use the AVZGNMPM member located in your hlq.SAVZCNTL data set for migrating virtual table maps. See the AVZGNMPM member for a list of parameters available for use when migrating virtual table maps.

You can use the AVZGNMPM member to perform the following tasks:
  • Migrate one or multiple virtual table maps from one server to another.
  • Change the virtual table map definition using the optional parameters. See the comments in the sample job for more details.

Procedure

  1. Customize the migration utility job, AVZGNMPM, for the requirements at your site.
  2. Submit the AVZGNMPM batch job. Utility job AVZGNMPM extracts the contents of the maps, stores the metadata objects in the map export PDS library, and creates the batch job that is used to rebuild the maps on the target server.
  3. Submit the batch JCL that was created in the previous step to rebuild the maps on the target server.

Results

The utility extracts the content of the map export PDS and rebuilds the map on the target server.