Previous Topic: Using the PUNCH StatementNext Topic: For SQL-Defined Entities


Using the Mapping Compiler and Mapping Utility

Steps

There are three steps to migrate maps between dictionaries (whether under the same CA IDMS/DB or DC/UCF system or not):

  1. Decompile the maps from the source dictionary.

    For this step, use the decompile function of the mapping utility (RHDCMPUT). You can decompile one or several maps in a single execution:

    PROCESS=DECOMPILE
    MAP=map1-name
    MAP=map2-name
     .
     .
     .
    

    The output of the decompilation consists of the source form of the maps, typically stored in a temporary file.

  2. Compile the maps into the target dictionary.

    For this step, use the file of decompiled maps from the previous step as input to the mapping compiler (RHDCMAP1). The mapping compiler places a source description of the map in the DDLDML area of the target dictionary.

  3. Generate the load modules for the maps in the target dictionary.

    For this step, use either the online mapping facility or the load function of the mapping utility (RHDCMPUT). If you use the load function of the mapping utility, you can generate multiple load modules in a single execution:

    PROCESS=LOAD
    MAP=map1-name
    MAP=map2-name
     .
     .
     .
    

Specify Source and Target Dictionary

The source and target dictionaries are typically part of multiple dictionary environments. Consequently, you must indicate which of the dictionaries the mapping compiler and mapping utility should run against. There are several techniques for specifying a particular dictionary in a multiple dictionary environment.

Note: For more information, see Chapter 25, “Dictionaries and Runtime Environments”.