Re: Saving Spool Files for a Migration

[Bryan Dietz <BDietz@xxxxxxxxxx>]

This has worked for me:

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

on the old system create one like:
CRTOUTQ OUTQ(QGPL/SEND2NEW)
        RMTSYS(*INTNETADR)
        RMTPRTQ(NEW)
        AUTOSTRWTR(1)
        CNNTYPE(*IP)
        TRANSFORM(*NO)
        INTNETADR('11.22.33.44')  <== 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
need
> to move around a 1,000 spoolfiles to te new box. We need to make sure
that
> all the external attributes are restored as well, so a simple copy to a
pf
> 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