|
|
|
|
|
This utility separates the Migrated User Report List file to different partitions based on the CDAM creation date. The file can be implemented as one or as several IOA Access Method files, where each of these files is a separate partition of the Migrated User Report List file. With the ability to physically separate the file to different partitions, you can
Separating the existing Migrated User Report List file to different partitions should be done in several steps, as shown below:
Use the CTDUFDBF job in the Control-D JCL library to allocate and format new Migrated User Report List file partitions.
Modify the CTDUFMDV job according to the number of partitions you have allocated and formatted.
If the process of separating to partitions is performed first, the CTDUFMDV job should be submitted with the ACT (MIG / HST) parameter in order to propagate the CDAM creation date to all report entries that were created in releases earlier than version 6.3.xx.
Separate the existing Migrated User Report List file to the new Migrated User Report List file partitions according to the CDAM creation date.
The CTDUFMDV job must be submitted with the PART parameter.
If you continued working with Migrated User Report List file during the separation process, submit the CTDUFMDV job with the COPYNEW parameter to copy the NOTE records, which were created or updated during the separation process, to the new Migrated User Report List file.
Update the IOADSNL, ALCCTDJB, ALCCTV, and ALCDOLV members in the IOA PARM library, in accordance with the new Migrated User Report List partitions.
After the new partitions are created, new running migration missions and CTDDELRP will copy reports to the corresponding MUF partition according to the CDAM creation date.
For more information about the CTDUFMDV utility, see the INCONTROL FOR z/OS Utilities Guide.
Parent Topic |