|
|
|
|
|
The migration mission name is specified in the DO MIGRATE statement of a report’s decollation mission. A report retains its original migration mission name for its entire lifetime. Each migration mission defines all stages in the migration path for all reports whose decollation mission contains a DO MIGRATE statement specifying that migration mission’s name.
The user can modify the migration path and other parameters in a migration mission at any time. When a migration mission is modified, the migration of all reports whose decollation mission specifies that migration mission’s name are affected by the modification.
The retention period of each report is stored with the report. If the retention period of all reports previously migrated by a migration mission must be changed uniformly, modify parameter RETENTION DAYS in that migration mission and set parameter FORCE to Y (Yes). This causes $SYSDATA records created by previous runs of this migration mission to be updated with the new retention period during the next run of the modified migration mission. If parameter FORCE is not set to Y, only subsequently migrated reports receive the new retention period.
If the retention period of the previously migrated reports must be selectively changed, use utility CTDUPBKP.
Specify only one migration mission for each report. If more than one migration mission is specified in the decollation mission definition, a report’s files are migrated by that migration mission whose name is first encountered in the decollation process. Warning messages are generated if all CDAM files associated with a report do not have the same migration mission name.
If the decollation process detects more than one migration mission name, a warning is issued to the IOA Log file and the decollation process terminates with a status of ENDED OK – WITH WARNINGS. If $SYSDATA records created by different decollation missions for the same report contain more than one migration mission name, a warning is issued by utility CTDDELRP.
Parent Topic |