Utility Statements › CONVERT PAGE › Examples › Example 1

Example 1

The first step in converting an area's page range is to define the new segment with all changes. This new segment could be included in the current DMCL if its name is different from the old segment, if the page group and page ranges are different from the old ones, and if the ddnames are different from the old ones.

After the DMCL is updated, the required syntax to do all conversions would be:

CONVERT PAGE IN SEGMENT EMPDEMO TO NEWDEMO;

The CONVERT PAGE utility scans both segments and determines which areas are being changed. Because the output files have unique ddnames, they do not need to be identified, but all three files that are in the EMPDEMO segment are converted, even if the changes do not affect all files.

To restrict the process, you could code the following:

CONVERT PAGE IN SEGMENT EMPDEMO TO NEWDEMO
   FILE EMPDEMO-FILE, ORGDEMO-FILE;

This syntax would only convert the EMPDEMO and ORGDEMO files. If the INSDEMO file were not affected by any changes, then this would be all that would be needed. However, if the INSDEMO file were affected, it could be converted with a separate job as follows:

CONVERT PAGE IN SEGMENT EMPDEMO TO NEWDEMO
   FILE INSDEMO-FILE;

This works because all changes were identified to both jobs, because all changes are contained in the single segment.

When completed, the DMCL would have to be modified a second time to remove the old segment definition and to possibly rename the new segment to the old one, to possibly change the new page group to the old page group, and to possibly change the ddnames back to the old ones.