Defining naming conventions for MIG work data sets

You can use templates to create your own naming conventions for the work data sets that are created by the migrate (MIG) function.

Procedure

To create naming conventions for the work data sets that are created by the migrate function:

  1. On the Migrate Parameters (ADB28M) panel, specify YES in the Generate template statements field.
  2. Specify the TU primary command to manage the templates for the work data sets.
    (Alternatively, you can specify Option 5 on the DB2 Administration Menu (ADB2) panel.)
    Use the following variables to specify the data set name pattern for a migrate work data set template:
    Functional variables:
    &ADB28PRE.
    Prefix for data sets specified on the Migrate Parameters (ADB28M) panel
    &DB2SYS.
    The Db2 subsystem ID.
    &WORKLIST.
    The work list name that is specified on the Migrate Parameters (ADB28M) panel.
    Variables for Db2 utility template processing:
    The following list is a subset of the variables that are supported for normal Db2 utility template processing. The other variables that are supported for Db2 utility processing are not valid for migrate work data sets.
    &DB.
    Database name
    &TS.
    Table space name
    &PART.
    The value is ALL with these exceptions:
    • For template UNLDDN, Db2 resolves the variable to a 5-byte string (nnnnn) that represents the partition number. For a non-partitioned object, the value of the string is '00000'. For a partitioned object, the value of the string is '00001', '00002', and so on.
    • For template MIDATVP with parallel processing specified, Db2 Admin Tool resolves the variable to a 4-byte string (nnnn) that represents the partition number. The value of the string is '0001', '0002', and so on.
    &USERID.
    Batch user ID
    &DATE.
    YYYYDD
    &TIME.
    HHMMSS
    &JDATE.
    YYYYDDD
    &YEAR.
    YYYY
    &MONTH.
    MM
    &DAY.
    DD
    &JDAY.
    DDD
    &HOUR.
    HH
    &MINUTE.
    MM
    &SECOND.
    SS
    Restriction: The following restrictions apply when specifying variables:
    • For the data set names to which Db2 Admin Tool appends Sn, Tn or Tn.Pmmmm , the number n starts with 1 and ends with the number of objects that you want to migrate. The total length of a data set name should not exceed 44 bytes
    • The only variables that can be specified for UNLDDN (used when using Db2 UNLOAD) are &DB., &TS., &USERID., and &PART..

      A work list name can be a very important part of the data set name when migrating objects. To specify a work list name as part of UNLDDN template data set name to maintain a consistent naming convention with other data set names, explicitly specify a value in the template instead of using the variable &WORKLIST, which cannot be specified.

    • The only variables that can be specified for MIDTVNP and MIDATVP (used when using HPU) are &DB., &TS., &USERID., &WORKLIST., and &PART.. If you specify &PART. for MIDATVP, you must specify it as the last part of the name (for example, &USERID..&TS..ULDULD.P&PART.); otherwise, parallelism will not be performed.