General Information

A migration mission defines the migration path (from media to media) along which the report migrates during its entire life.

Migration missions can be specified on any basis that is meaningful at your site. For example, separate migration missions may be designated for:

• Various retention periods (MIG0007YR, MIG30MON)
• Various storage patterns (MIGISFTK, MIGCART)
• Various report categories (MIGSALES, MIGPARTS)
• Various access frequencies (MIGHEAVY, MIGLIGHT)
• Reports that migrate one time only (MIGONCE)
• A combination of retention period and category (MIGTAX7Y, MIG10YW2)

Note: Only one migration mission name should be specified for each report file (CDAM file). If more than one migration mission is specified in the decollation definition, a report file is migrated by the first migration mission whose name is encountered in the decollation process. If the decollation process detects more than one migration mission name, a warning message is issued to the IOA Log file and the decollation process terminates with a status of "ENDED OK – WITH WARNINGS."

For information about the migration process, see the Control-D and Control-V chapter in the INCONTROL for z/OS Administrator Guide. For information about migrated CDAM data sets, see Migrated CDAM Datasets.