Re: Saving and restoring spool files V4R5->V5R3

[Luis Rodriguez <luis.rodriguez2@xxxxxxxxx>]

Buck,

Thanks for your answer. When I try to use the CPYSPLF method suggested (*FCFC) 
the file gets written to the spool but without the proper spacing and/or 
pagination. Maybe I'm missing something...

On the other hand, I think I'll go through the SNDTCPSPLF route and, if our 
users complain about the original job attributes (number, date and such) maybe 
they will be a little more careful creating spool outputs in the future :-)

Thanks to all for your help,

Luis Rodriguez




message: 8
date: Mon, 02 Oct 2006 14:29:35 -0400
from: Buck 
subject: Re: Saving and restoring spool files V4R5->V5R3

> (Wayne, thanks for your suggestion, but: I need to respect 
> the original format and am afraid the CPYSPLF
> method does not allow this)

Sure it does, if you do a little more work.  You need to create another 
file; this one containing spooled file attributes.  Then use the spooled 
file APIs and retrieve the spooled file attributes and store them in the 
attribute file.  Then CPYSPLF to a PF.  Now you can move those two files 
over to the other system and do the reverse:

Read a record from the attributes file, create the appropriate OVRPRTF 
and then CPYF from the spooled PF to QSYSPRT.

Be advised that when you have done all this, you _still_ have a 
different job, user and ID than the spooled file on the original system 
had.  If the user ID or job name matters you can submit the job with the 
proper name and user ID, but I know of no way to force the job number to 
match the original.
   --buck





Luis Rodriguez

IBM Certified Systems Expert
eServer i5 iSeries Technical Solutions
                
---------------------------------
Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ 
countries) for 2¢/min or less.