If you have the dataset that is the Image Copy from the old tablespace, you can use DSN1COPY to put the data into a new tablespace.

The new tablespace and the new tables will have different OBIDs (Object Identifiers). The DSN1COPY utility will have to be told to translate (XLAT) the OBIDs on the Image Copy dataset to the OBIDs of the new objects.

My recollection is that you can run DSN1COPY without specifying the XLAT inpout and the utility will tell you what the OBIDs are – something like “you are trying to load (old number) into (new number)” – and with that info you can then populate the XLAT.

Here is an OLD sample of DSN1COPY.

//**   COPY  AN IMAGE COPY DATA SET                             *       
//**         TO A DIFFERENT TABLESPACE THAN THE ONE IT CAME     *       
//**         FROM.  TABLES LOOK THE SAME, BUT DB, TS, AND TBLS  *       
//**         MUST ALL BE TRANSLATED.                                    
//**------------------------------------------------------------*       
//**                                                                    
//DSN1COPY EXEC PGM=DSN1COPY,                                           
//         PARM='CHECK,NUMPARTS(0),OBIDXLAT,FULLCOPY,RESET'             
//**   PARM='CHECK,FULLCOPY,NUMPARTS(10),OBIDXLAT,RESET' <-- CHANGE     
//SYSPRINT DD  SYSOUT=*                                   * O/P REPORT  
//SYSABEND DD  SYSOUT=*                                                 
//SYSUDUMP DD  SYSOUT=*                                                 
//SYSUT1   DD  DSN=DB2T.IC1.DSNDB06.SYSDBASE.G0239V00,       * I/P      
//             DISP=OLD                                                 
//SYSUT2   DD  DSN=DB2T.DSNDBD.DSNDB04.TABAUTH.I0001.A001,   * O/P      
//             DISP=OLD                                                 
//SYSXLAT  DD  *                                                        
6,4    
9,177  
32,267 
20,250 
/*

What happens with the SYSXLAT data is the first set of numbers (“6,4″) says change the DBID from 6 to 4, the second set says change the tablespace id from 9 on the Image Copy to 177, and the rest are for the tables within the tablespace.

It has been a long time since I ran anything like this. Some experimentation will be needed.

Good luck.

The dataset that is the Image Copy may still exist. It may be catalogued.

If the Image Copy dataset still exists, you can use DSN1COPY to put the data into a newly defined table and tablespace. The new objects will have different OBIDs and so you will have to use the XLAT (translate) parms of DSN1COPY.

//**   COPY  AN IMAGE COPY DATA SET                             *       
//**         TO A DIFFERENT TABLESPACE THAN THE ONE IT CAME     *       
//**         FROM.  TABLES LOOK THE SAME, BUT DB, TS, AND TBLS  *       
//**         MUST ALL BE TRANSLATED.                                    
//**------------------------------------------------------------*       
//**                                                                    
//DSN1COPY EXEC PGM=DSN1COPY,                                           
//         PARM='CHECK,NUMPARTS(0),OBIDXLAT,FULLCOPY,RESET'             
//**   PARM='CHECK,FULLCOPY,NUMPARTS(10),OBIDXLAT,RESET' <-- CHANGE     
//SYSPRINT DD  SYSOUT=*                                   * O/P REPORT  
//SYSABEND DD  SYSOUT=*                                                 
//SYSUDUMP DD  SYSOUT=*                                                 
//SYSUT1   DD  DSN=DB2T.IC1.DSNDB06.SYSDBASE.G0239V00,       * I/P      
//             DISP=OLD                                                 
//SYSUT2   DD  DSN=DB2T.DSNDBD.DSNDB04.TABAUTH.I0001.A001,   * O/P      
//             DISP=OLD                                                 
//SYSXLAT  DD  *                                                        
 6,4     
 9,177   
 32,267  
 20,250  
 21,255  
 25,264  
 23,253  
 26,265  
 27,266  
 24,256  
 22,251  
 33,252  
 28,254  
 18,191  
 19,193  
 17,192  
 /*      

Now that is a *real* old sample. I have not done this in years. My recollection is that you can execute DSN1COPY without the XLAT and the utility will yell, scream and fail; but it will tell you that you need to XLAT from this number to that.

Or, you can use DSN1PRNT to print parts of the Image Copy dataset to see what the OBIDs are on the tape or disk file. For this you will have to dig to find the layout of the header pages for each object. My memory just cannot locate that information right now.

Some info is in the Utility Guide. Maybe in the Admin Guide. Maybe in the Diagnostic Guide?

Sorry I cannot help more.