Migration Mission Workflow

A migration mission consists of the following steps:

• Ordering one migration mission adds a MIG mission to the Active Missions file (if its scheduling criteria are satisfied) and adds a MSM mission to the Active Missions file (if its scheduling criteria are satisfied). The MIG mission migrates reports from DASD to the stage 01 target media. The MSM mission migrates reports from the media on which they currently reside (stage n‑1) to the target media of stage n.
• If MIG and MSM missions with the same name exist concurrently, the status of both missions is "IN PROCESS" but the Control‑D and Control‑V monitor ensures that job MSM is not created and submitted before job MIG ends.
• The MIG mission scans $SYSDATA records in the Active User file and the MSM mission scans $SYSDATA records in the Migrated User file to find records for all reports that need to be migrated by the migration mission. This process produces a list of datasets to migrate.
• The Control‑D and Control‑V monitor looks for the primary migration skeleton job in the library referenced by DD statement DADSKL of the Control‑D and Control‑V monitor. The member name must be the same as the primary migration mission name (for example, MIG0007Y).
• If secondary media values are specified in a migration mission stage, the Control‑D and Control‑V monitor looks for the secondary migration skeleton job in the library referenced by DD statement DADSKL of the Control‑D and Control‑V monitor. The member name must be the same as the secondary migration mission name specified in parameter SECONDARY NAME in the Migration Mission Definition screen.
• Primary and secondary migration skeletons are tailored to produce jobs that perform the appropriate migrations and analyze the results. For MSM, the MIGRAT step is automatically duplicated for each migration stage that must be included in the migration job.
• The age of each report is calculated by subtracting the ODATE of its decollation mission from the ODATE of the migration mission that controls its migration. This calculation method permits testing whether a report will migrate on a future date, by specifying that date in the migration mission’s ODATE parameter. (An installation parameter enables calculating the age of each report by subtracting the ODATE of its decollation mission from the current installation date. This calculation method does not permit such testing.)
• If a report does not currently reside on the media specified for its age (as calculated in the previous step), it is migrated to the specified media by the migration mission. If a report migrated by a migration stage has resided on a media for the number of days specified in parameter REFRESH EVERY for that stage, the media is refreshed by the migration mission.

  When the migration job is ready for submission, control is passed to User Exit CTDX010. This exit can add, delete or modify JCL statements in the job. Exit CTDX010 returns one of the following return codes:      

  • 0 – submit the job
  • 4 – do not submit the job

    This return code is normally used when the job must be submitted by Control‑M or another production control system.

    Instead of using exit CTDX010, you can define parameter BKPJOBST=N in CTDPARM, which means “Do not submit the job.”

• The migration job JCL is written to the library referenced by DD statement DADJOB of the Control‑D and Control‑V monitor with a name identical to the name of the migration mission. Therefore, this library must not be the skeleton library referenced by DD statement DADSKL.
• If %COND% is specified in the migration skeleton, the resolved condition is added to the IOA Conditions file. Depending on the return code from User Exit CTDX010, the job is or is not submitted. If Control‑M is installed, submission of the job can be triggered by the condition added by a %COND% statement.
• If the migration target media is OSS (DataWare/ROSs/OSS or compatible), the migration job begins with step SRVD, which releases an OSS device, and step OSSDBEXT, which creates the OSS Extract Dataset using information from the OSS Database.
• The migration process creates and/or updates $SYSDATA records in the Migrated User file with target media, target prefix, timestamp, and other migration parameters for both primary and secondary migration. All $SYSDATA records pointing to a migrated report are updated with the new migration information.
• For migration stages whose target media is CART, Control‑V records the VOLSER of the last used tape. This enables the next invocation of that migration mission to use the same tape.
• The original copy of each report that expires or moves to another physical media is marked for deletion. Actual deletion is performed during the next run of utility CTVCLMIG. This utility must be run periodically.
• When the job finishes executing, the Control‑D and Control‑V monitor is notified by the ANALYZE step and the migration mission’s post‑processing parameters (OUT and SHOUT) are processed.

Example: Multi-stage Migration Mission Workflow

The cumulative retention period for reports in this example is 8 years.

Table 170 Multi-stage Migration Mission Workflow Example

The following figure illustrates an Optical media that is refreshed after six months and a CART media that is refreshed after 4 years. This multi-stage migration mission is specified in the migration mission definition.

Figure 60 Multi-stage Migration Mission Workflow

Figure 61 Migration Mission Definition

  ---- Control‑V CATEGORY MIGOS1C7          MIG MISSION MIGOS1C7 --------(M.S)

  COMMAND ===>                                                 SCROLL===> CRSR

  +‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑+

  ======= >>>>>>>>>>>>>>>> TOP OF CATEGORY PARAMETERS <<<<<<<<<<<<<<<<<< =====

    CATEGORY MIGOS1C7                          MISSION MIGOS1C7                 

    OWNER    M15           TASKTYPE MSM        GROUP                            

    DESC                                                                        

    ===========================================================================

                          STAGE 01 SCHEDULING PARAMETERS                        

    DAYS                                                          DCAL          

                                                                       AND/OR   

    WDAYS                                                         WCAL          

    MONTHS  1‑ Y 2‑ Y 3‑ Y 4‑ Y 5‑ Y 6‑ Y 7‑ Y 8‑ Y 9‑ Y 10‑ Y 11‑ Y 12‑ Y

    DATES                                                                       

    CONFCAL          SHIFT   RETRO N MAXWAIT 00                                 

    MINIMUM          PDS                                                        

    ===========================================================================

    IN        MIG-DASD-TO-OSS-11M ODAT                                          

    TIME FROM      TO      NOT LATER THAN      PRIORITY                         

    ===========================================================================

    OUT                                                                         

    SHOUT WHEN NOTOK                               TO OPER             URGN R

     MSG MIGOS1C7 STAGE 01 ENDED NOT OK                                         

    SHOUT WHEN                                     TO                  URGN     

     MSG                                                                        

    ===========================================================================

    RETENTION DAYS 02922         FORCE          SECONDARY SKELETON  MICOS1C7    

    ===========================================================================

    STAGE 01 PRIMARY   MEDIA NAME OSS      AGE 00030 REFRESH EVERY 00183        

             PREFIX                                                             

             SECONDARY MEDIA NAME CART              REFRESH EVERY 01460         

    ===========================================================================

                        MIGRATION PATH SCHEDULING PARAMETERS                    

    DAYS                                                          DCAL          

                                                                       AND/OR   

    WDAYS   0,6                                                   WCAL          

    MONTHS  1‑ Y 2‑ Y 3‑ Y 4‑ Y 5‑ Y 6‑ Y 7‑ Y 8‑ Y 9‑ Y 10‑ Y 11‑ Y 12‑ Y

    DATES                                                                       

    CONFCAL          SHIFT   RETRO N MAXWAIT 00                                 

    MINIMUM          PDS                                                        

    ===========================================================================

    IN        MIG-OSS-TO-CART-7Y ODAT                                           

    TIME FROM      TO      NOT LATER THAN      PRIORITY                         

    ===========================================================================

    OUT                                                                         

    SHOUT WHEN NOTOK                           TO OPER              URGN R

     MSG MIGOS1C7 STAGE 02 ENDED NOT OK                                         

    ===========================================================================

    STAGE 02 PRIMARY   MEDIA NAME CART    AGE 00365 REFRESH EVERY 01460         

             SECONDARY MEDIA NAME                   REFRESH EVERY               

    STAGE 03 PRIMARY   MEDIA NAME          AGE      REFRESH EVERY               

             SECONDARY MEDIA NAME                   REFRESH EVERY               

    ===========================================================================

======== >>>>>>> END OF MIGRATE MISSION PARAMETERS OF THIS CATEGORY <<<<<< =====

PLEASE FILL IN MISSION PARAMETERS. USE "SHPF" TO SEE PFK DEFINITION    11.04.10