RE: Codestudio

["Bob Cozzi" <cozzi@xxxxxxxxx>]

Doug,

Thanks for test it. I just sort of made up that code as I wrote the message.
Glad it will work. Now, is the QTEMP accessible from FTP? If so, is it the
same QTEMP for each FTP command? I hope so!  Right now, we're having
difficulty with the CPYSPLF command. As we do a compile then try to download
the compile listing, we can't because *LAST doesn't work for the CPYSPLF
command when we try to copy the spool file to a database file, then download
it. The compile seems to run in its own job, the CPYSPLF it its own job,
etc.  I'm a little confused on this one.

Bob Cozzi

http://www.RPGIV.com




> -----Original Message-----
> From: owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]On
> Behalf Of Douglas Handy
> Sent: Monday, August 09, 1999 11:32 PM
> To: RPG400-L@midrange.com
> Subject: Re: Codestudio
>
>
> Bob,
>
> >Maybe a CL source member that gets
> >uploaded to do a copy from source to physical file. Then we could just do
> >the download.
> >
> >  CPYF  mysrclib/mysrcfile  frommbr( rpgsrc ) tofile(qgpl/phys_src)
> >ombr( *frommbr) crtfile(*YES) MBROPT(*REPLACE)
>
> FWIW, I tested this and it does work, provided you do *not* specify
> FMTOPT(*CVTSRC) as you did not in your sample.
>
> It wouldn't even need the CL uploaded first; you could just use QUOTE
> RCMD from within FTP to issue the CPYF first, then GET the member from
> the data file.  And it works the other direction too, updating SRCDAT
> and SRCSEQ from the data member.  You can even use SRCOPT(*SEQNBR) to
> renumber the source but restore the source dates.
>
> I don't think you'd want to put the file in QGPL though, because of
> potential problems with multi-developer sites.  But from within FTP,
> you'd probably be safe using QTEMP for both the RCMD and GET or PUT.
>
> You are adding an extraneous copy operation, but the timing should be
> fairly fast for all but monolithic behemoths, and even then the member
> may still be in main storage for the second phase copy.
>
> I wish FTP would let use do it directly, but this may be a good
> work-around.
>
> Doug
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---END
>
>

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---END