RE: copy outq across diff iseries

What Vengoal suggested (LPR) is the same thing I was saying. LPR happens to be 
what is used when you print through a remote outq with an active writer 
(STRRMTWTR is one way to start it).

TRANSFORM(*NO), as you found, must be set on the source (remote OUTQ). I'd said 
that but not as clearly. On the target, it is meaningless, unless that target 
OUTQ is also a remote OUTQ.

Glad it worked. It is very cool!

Vern

-------------- Original message -------------- 
From: "Rhett Hermer" <rhetth@xxxxxxxxxxxxxxxx> 

> Hi, 
> 
> Thanks a million! It helped. Mind that TRANSFORM(*NO) needs to be applied to 
> source machine (A) aswell. And CNNTYPE(*IP) as well. 
> 
> Rhett 
> 
> 
> 
> -----Original Message----- 
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jan Megannon 
> Sent: 20 February 2006 15:36 
> To: Midrange Systems Technical Discussion 
> Subject: Re: copy outq across diff iseries 
> 
> 
> Rhett, 
> 
> 
> On Machine B (target): 
> CRTOUTQ OUTQ(QUSRSYS/JAN) TRANSFORM(*NO) 
> On Machine A (source): 
> CRTOUTQ OUTQ(QUSRSYS/JAN) RMTSYS(*INTNETADR) RMTPRTQ('qusrsys/jan') 
> INTNET 
> ADR(NNN.NNN.NNN.NNN) 
> 
> On Machine A: 
> STRRMTWTR OUTQ(QUSRSYS/JAN) 
> WRKOUTQ QUSRSYS/JAN on both systems. 
> 
> Move some spool files over to that queue and check that it is working as 
> desired 
> HTH 
> 
> Jan. 
> 
> 
> Rhett Hermer wrote: 
> > So: 
> > 
> > A is source iSeries. 
> > B is destination iSeries. 
> > 
> > On A, CRTOUTQ, define RMTSYS paramter to IP of B. 
> > 
> > On B, crt LPR device? 
> > 
> > 
> > Or STRRMTWTR on A and on B configure as? 
> > 
> > I am not so sure how to define the OUTQ on B to receive splfs. 
> > 
> > 
> > -----Original Message----- 
> > From: midrange-l-bounces@xxxxxxxxxxxx 
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vengoal Chang 
> > Sent: 20 February 2006 11:27 
> > To: Midrange Systems Technical Discussion 
> > Subject: Re: copy outq across diff iseries 
> > 
> > 
> > You could set a Remote Outq which specified to another iSeries Outq, 
> > then use LPR to send local outq spooled to the remote outq. 
> > 
> > Best regards, 
> > 
> > Vengoal 
> > 
> > 
> > Rhett Hermer wrote: 
> > 
> > 
> >>Sounds a good idea of using remote OUTQ to copy the splfs from A to B. 
> >>It's one time deal so I'll manage to send thousands of splfs instead of 
> >>saving the one OUTQ on A and restore on B *sigh* 
> >> 
> >>-----Original Message----- 
> >>From: midrange-l-bounces@xxxxxxxxxxxx 
> >>[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of 
> >>vhamberg@xxxxxxxxxxx 
> >>Sent: 16 February 2006 19:51 
> >>To: Midrange Systems Technical Discussion 
> >>Subject: Re: copy outq across diff iseries 
> >> 
> >> 
> >>Not sure what you want to do. If you want things in an OUTQ on machine 
> >>A to go to machine B, use a remote OUTQ. And be sure not to have host 
> >>print transform turned on on the remote OUTQ. User names need to match, 
> >>in order to preserve that relationship - otherwise the spooled files 
> >>end up under some system user. BTW, writer has to be active on the 
> >>remote OUTQ. 
> >> 
> >>Or do you want the spooled files on both machines? I guess I'd still 
> >>use the remote OUTQ but set the spooled files to SAVE(*YES) - then they 
> >>stay, in SAVE status, on machine A, as well as get "printed" to machine 
> >>B. 
> >> 
> >>Eh? 
> >> 
> >>-------------- Original message -------------- 
> >>From: "Rhett Hermer" 
> >> 
> >> 
> >> 
> >> 
> >>>Hi, 
> >>> 
> >>>What's the best and painless method to copy whole OUTQ across between 
> >>>two iseries? 
> >>> 
> >>>Thanks, 
> >>> 
> >>>-- 
> >>>This is the Midrange Systems Technical Discussion (MIDRANGE-L) 
> >>>mailing 
> >>> 
> >>> 
> >> 
> >>list 
> >> 
> >> 
> >> 
> >>>To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> >>>To subscribe, unsubscribe, or change list options, 
> >>>visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> >>>or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> >>>Before posting, please take a moment to review the archives 
> >>>at http://archive.midrange.com/midrange-l. 
> >>> 
> >>> 
> >>> 
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list 
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, 
> or change list options, 
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> Before posting, please take a moment to review the archives 
> at http://archive.midrange.com/midrange-l. 
> 
> 
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list 
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options, 
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> Before posting, please take a moment to review the archives 
> at http://archive.midrange.com/midrange-l. 
>