Gary_Cherlet

Changing Segments with the RELOAD utility

Discussion created by Gary_Cherlet on May 15, 2011
Latest reply on May 16, 2011 by Gary_Cherlet
Hi, we are trying to use the EZREORG Tool to separate areas that are now in one segment into two separate segments. The new segment will be in a new page group. The issue is in the CA Reload process which EZREORG uses. We create a dmclold that has the original dmcl to run the unload. This runs fine.
The dmcl for the reload has the new version of the original segment(minus the areas moved) and the new segment. These 2 segments are in 2 different page groups. This is how the DMCL and segments would look when we are done.
The RELOAD process is split to run by step. The first RELOAD step is the Sort1 and the IDMSDBL2 which appears to run fine:
[color=#0307FD] RELOAD STEP SORT1;
UT010002 BEGINNING PROCESSING FOR STEP SORT1
UT009001 IDMSDBLY RELEASE 17.0 TAPE GJH01B SORT STARTED
UT009002 162,637,115 RECORDS WERE READ FROM SYS002
UT009003 162,637,115 RECORDS WERE WRITTEN TO SYS004
UT009004 IDMSDBLY RELEASE 17.0 SORT COMPLETED SUCCESSFULLY
UT010003 STEP SORT1 HAS COMPLETED SUCCESSFULLY
UT010001 DATABASE RELOAD STEP HAS COMPLETED SUCCESSFULLY
Status = 0 SQLSTATE = 00000[color]
The problem comes in the IDMSDBLX process we get the following warning/error:
[color=#0307FD]UT008010 MAPPING ERROR ON INDEX SET IX-INAPHONE
UT008012 OWNER DBKEY FFFFFFFF, OLD MEMBER DBKEY 22646C58, MEMBER
SEQUENCE -2,141,867,632[color]
The IDSMDBL3 in the Reload step gives us the error:
[color=#0307FD]UT001006 Program IDMSDBL3 processed 346,000,000 records
NEXT POINTER FOR SET IN RECORD (ID=6095) AT 6,614,894:09
IS INVALID BECAUSE TARGET RECORD NOT UNLOADED ORIGINAL DBKEY WAS 3,360,389:69 MISSING TARGET DBKEY IS 14,954,039:05
UT001006 Program IDMSDBL3 processed 346,500,000 records
NEXT POINTER FOR SET IN RECORD (ID=6095) AT 4,293,329:17 IS I NVALID BECAUSE TARGET RECORD NOT UNLOADED
ORIGINAL DBKEY WAS 2,389,904:36 MISSING TARGET DBKEY IS 15,035,106:04
PRIOR POINTER FOR SET IN RECORD (ID=6110) AT 15,887,241:04 IS INVALID BECAUSE TARGET RECORD NOT UNLOADED
ORIGINAL DBKEY WAS 15,887,241:01 MISSING TARGET DBKEY IS 15,035,106:04[color]
Are we trying to do something that you cannot do with the Reload tool? The original segment is now divided into two segments in the New DMCL. The manual says that you cannot use mixed page groups with the reload utility.
Has anyone had this experience before? How was it accomplished?
Thanks, Tonya Hunley

Outcomes