Work data sets used by the MIG function

The Db2 Admin Tool migrate (MIG) function creates and uses data sets.

The following table lists the data sets that the migrate function creates and uses.
Table 1. Work data sets for MIG
Default data set name Description Template keyword
prefix.worklist.DDL DDL and DML that is constructed from the catalog MISQL
prefix.worklist.DDDL DROP statements for drop objects MISDROP
prefix.worklist.COL Identity column information MICOL
prefix.worklist.CMD Rebind output MIGCMD
prefix.worklist.MIGVARS Partitioned data set for ISPF tables that are required for generating the MIG jobs in batch MIGSHVR
prefix.worklist.ADB28W1U Work statement list (WSL) data set MIUCONV
prefix.worklist.ADB28W3U WSL data set MIUOTHR
prefix.worklist.ADB28WDD WSL elements MI2WDD
prefix.worklist.ADB28W2T Input data set for the merge program MIMLSIN
prefix.worklist.ADB28W2U Intermediate data set used by the merge program MIMLSOT

The migrate function also uses data sets for the unloaded data, LOAD control statements, and converted LOAD control statements. The naming convention for the data sets differ depending on whether the Db2 UNLOAD utility or Db2 High Performance Unload is used to unload the data.

The following table lists the data sets for migrations with Db2 UNLOAD.

Table 2. Work data sets for MIG with Db2 UNLOAD
Default data set name Description Template keyword
prefix.worklist.CNT.Sn LOAD utility control statements, where Sn is a string assigned to the object by Db2 Admin Tool, with n beginning with 1 PUNCHDDN1
prefix.worklist.ULD Data sets for unloaded data UNLDDN2
prefix.worklist.CNC.Sn Converted LOAD utility control statements, where Sn is a string assigned to the object by Db2 Admin Tool, with n beginning with 1 MICTLOV (for table spaces

MICTLOU (for tables)
Note:
  1. A utility template. A template statement is not generated in the JCL. Db2 Admin Tool uses the utility template to generate regular JCL to perform the unload.
  2. A utility template. A template statement is generated in the JCL. When you use your own copy of utility template UNLDDN, Db2 Admin Tool does not delete any of the data sets that are created by the template after they are used. You must delete them. Also, the transfer data set list in jobs SST4XF and xxxxSE do not include the data set names, and you must transfer them.

Image copy uses the regular utility template.

The following table lists the data sets for migration with HPU.
Table 3. Work data sets for MIG with HPU
Default data set name Description Template keyword
prefix.worklist.CNT.Tn LOAD utility control statements, where Tn is a string assigned to the object by Db2 Admin Tool, with n beginning with 1 MICTLIU
prefix.worklist.ULD.Tn Unload data sets for a non-partitioned object, where Tn is a string assigned to the object by Db2 Admin Tool, with n beginning with 1 MIDTVNP
prefix.worklist.ULD.Tn.Pm Unload data sets for a partitioned object, where Tn is a string assigned to the object by Db2 Admin Tool, with n beginning with 1, and Pm is a string that identifies the object's partition number, with m beginning with 0001 MIDATVP
prefix.worklist.CNC.Tn Converted LOAD utility control statements, where Tn is a string assigned to the object by Db2 Admin Tool, with n beginning with 1 MICTLOU

The relationship between the table name and Tn and the relationship between the table space name and the Sn are listed as comments in the beginning of the generated job or WSL.

The migrate function deletes these data sets when they are no longer needed.