RE: CPYSPLF PARMS

Eric,

we to a cpysplf then cpytopcd to get it in ascii so that they can play
with it in Word...they wanted a no dollar real cheap quick and dirty
solution, and were happier than a pig in ....:)

Don in DC...

------

On Tue, 12 Dec 2000, Eric DeLong wrote:

>      I'll second that notion. I also want to point out that if your 
>      objective is to send the spoolfile (ie. option 1), then the command 
>      to use is SNDNETSPL. 
>      
>      Eric
> 
> 
> ______________________________ Reply Separator
> _________________________________
> Subject: Re: CPYSPLF PARMS
> Author:  "Don" <SMTP:dr2@cssas400.com> at EXCHANGE
> Date:    12/12/00 9:51 AM
> 
> 
> Bob,
>      
> better yet, why not just send the splf at the time it's created?  Add the 
> cpysplf xxxx splnbr(*last) right after the pgm call....  We do this for 
> sending fiche to a european div for a client via the net...
>      
> Don in DC
>      
> ------
>      
> On Tue, 12 Dec 2000, Bob Buettel wrote:
>      
> >
> >      I send a user a SPOOL file using option 1  SEND   WRKJOB 
> > OPTIONS(SPLF).
> >      I want the CLP to do the CPYSPLF without the user having to fill in 
> > the JOBNAME/USER/NUMBER
> >      When I look at the spool it is a job called QPRTJOB/PERSON/093515. 
> >      How can I get these parms into CPYSPLF
> >
> >       Spooled file . . . . . . . . . . 
> >       To data base file  . . . . . . .
> >         Library  . . . . . . . . . . .               *LIBL
> >       JOBANME. . . . . . . . . . . . xxxxxxxxxxxxx            * 
> >
> >         USERr . . . . . . . . . . . . .  xxxxxxxxxxxxx 
> >
> >         NUMBER . . . . . . . . . . . . xxxxxxx
> >       Spooled file number  . . . . . .             *ONLY 
> >       To member  . . . . . . . . . . .             *FIRST
> >       Replace or add records . . . . .             *REPLACE 
> > +---
> > | 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 
> > +---
> >
>      
> +---
> | 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 
> +---
> +---
> | 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
> +---
> 

+---
| 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
+---