This worked great with a minor gotcha... on 5.2 and below if you don't 
qualify the lib the outq is in it assumes QUSRSYS and if it is there then 
everything's works. ON 5.3 you need to qualify the lib even if the outq is 

Thanks for everyone's suggestion. 
Kirk Goins CCNA
Systems Engineer, Manage Inc.
IBM Certified iSeries Solutions Expert
IBM Certified iSeries e-Business Infrastructure
IBM Certified Designing IBM e-business Solutions 
Office 503-353-1721 x106 Cell 503-577-9519

There are 10 types of people in the world:
Those that understand binary, and those that don't.

Bryan Dietz <BDietz@xxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
10/15/2004 02:44 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>

Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>

Re: Saving Spool Files for a Migration

This has worked for me:

Finish the migration so that all the user profiles are on the new box. 
on the new box create an outq called NEW and make sure the LPD server is

on the old system create one like:
        INTNETADR('')  <== Change to meet you needs

Then just move the spool files into that outq and away they go.

They must be in *READY state so the ones on hold or save need released.
And since the profiles are on the new system all the spool files are still
associated with the original profiles.

Bryan Dietz
Aktion Associates

midrange-l-bounces@xxxxxxxxxxxx wrote on 10/15/2004 04:03:24 PM:

>  I have a client on a 620 running 5.2 moving to an i5 running 5.3. We
> to move around a 1,000 spoolfiles to te new box. We need to make sure
> all the external attributes are restored as well, so a simple copy to a
> and restore isn't going to cut it. This will be a once or maybe twice
> deal.
> I don't need something very fancy, but functional since it's a 1 time
> deal.  What has the group here used? Will BRMS at 5.2 handle spoolfiles?
> I've heard that the spoolfile restore is terrible in BRMS, at least time
> wise.
> Thanks
> _____________________
> Kirk Goins CCNA

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2015 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact