RE: Transferring spool files to another system

["Jones, John (US)" <John.Jones@xxxxxxxxxxxxxxxxxxxxxxx>]

Why not use a remote outq? 


John A. Jones
Americas Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787 F: +1-312-601-1782
John.Jones@xxxxxxxxxxxxxxxxxxxxxxx

-----Original Message-----
From: Pete Helgren [mailto:pete@xxxxxxxxxx] 
Sent: Tuesday, July 27, 2004 1:49 PM
To: Midrange Mailing List
Subject: Transferring spool files to another system

I have a customer with a brand spankin' new i5 that I need to move spool
files to from the 720 they are retiring (there are a lot of spool files
that have been saved as archives of month end closings, payroll and W2
runs that go back 4 or 5 years....).  Both machines are at V5R3M0.  They
are physically on the same network segment (logically too).  I looked
around the archives for solutions and stumbled across an old TAATOOL
that saved and restored spool files.  It works slick, except it saves
the spool files in *USRSPC objects and there are some spool files that
easily exceed the 16m maximum size (like 40m in size.....)

So the question is:  Is there another approach that I can use to
accomplish this one time movement of spool files?  What I really liked
about the SAVSPLF/RSTSPLF utilities was that 1. They are FREE.  2. They
restored the spool files in the users outq on the new system.  Sweet!

Any ideas would be appreciated.

Pete Helgren
Value Added Software,Inc.
801.581.1154 x202



This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior permission.  
We have taken precautions to minimize the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any attachment 
to this message.  We cannot accept liability for any loss or damage caused by 
software viruses.  The information contained in this communication may be 
confidential and may be subject to the attorney-client privilege. If you are 
the intended recipient and you do not wish to receive similar electronic 
messages from us in future then please respond to the sender to this effect.