Re: R: CL variables in FTP commands

[booth@xxxxxxxxxxxx]

Make an RPG program to show a PF of some arbitrary record length that fits 
on your screen. Display that PF and allow a to be written so that ever 
evolving script changes can be made.
 
Since your rule is always the same you could then write an RPG program to 
copy the PF's data  to a similar file in QTEMP that has the member name 
FTPCMDS and watch for the line that needs to have the variable added.  Do 
it there.  RPGIV  is much easier to do this than CL in my opinion.

_______________________
Booth Martin
Booth@MartinVT.com
http://www.MartinVT.com
_______________________




Finucci Domenico <Domenico.Finucci@Fiditalia.it>
Sent by: owner-midrange-l@midrange.com
01/26/2001 07:53 AM
Please respond to MIDRANGE-L

 
        To:     "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com>
        cc: 
        Subject:        R: CL variables in FTP commands

I'm interested too !
Sincerely.
Domenico Finucci
Fiditalia , Milano, 02- 4301-2494


-----Messaggio originale-----
Da: Simone Pacciarini [mailto:spacciarini@yahoo.com]
Inviato: venerdì 26 gennaio 2001 12.34
A: MIDRANGE-L@midrange.com
Oggetto: Re: CL variables in FTP commands


I would be very interested.

Simone



--- Phil Groschwitz <sublime78ska@yahoo.com> wrote:
> Yes, I'd be very interested.
> 
> Phil
> --- Scott Klement <klemscot@klements.com> wrote:
> > 
> > Normally input to a batch FTP session is done by
> > overriding the input to
> > a file.  Since a file is not a CL program, you
> can't
> > use CL variables in
> > them.
> > 
> > I think the normal way of writing this would be to
> > have a RPG (or some
> > other HLL) create the file with the input commands
> > immediately prior to
> > running the script.  so:
> > 
> >    1) You'd use RTVOBJD or equivalent to get the
> > change date.
> >    2) You'd create your FTP input file, writing
> the
> > contents of the
> >           date into the appropriate place in the
> > file.
> >    3) You'd OVRDBF FILE(INPUT) to the newly
> created
> > file.
> >    4) run FTP
> >    5) analyze the output from the FTP program,
> > looking for errors.
> > 
> > Personally, I don't like this method because of
> step
> > 5, above.  Trying to
> > figure out if an error occurred, if the
> transmission
> > was successful, etc
> > is a nightmare!
> > 
> > I've been working on an FTP service program
> (written
> > in RPG IV) which 
> > just uses sockets to do FTP directly, rather than
> > going through IBM's
> > FTP client. 
> > 
> > If people on the list are interested, maybe I'll
> > turn this service program
> > into an open source project, and others can help
> > with it, use it, etc...
> > Anyone interested?
> > 
> > 
> > On Thu, 25 Jan 2001, Ray, Adam wrote:
> > 
> > > Good afternoon everyone.
> > > I was wondering if it is possible to use CL
> > variables in a batch FTP
> > > session. I need to transfer a file from our
> AS/400
> > to one of our NT servers
> > > without any user intervention. The file to be
> put
> > on the server is to be
> > > named using the files last change date. So the
> PUT
> > command would look
> > > something like this
> > >            put mylib/myfile.mymbr mmddyyyy.raw
> > > 
> > > I know I can get the files change date using the
> > CL command RTVOBJD,
> > > something like this:
> > >            RTVOBJD    OBJ(MYLIB/MYFILE) OBJTYPE(*FILE)
> > CHGDATE(&CHGDATE)
> > > And I know the FTP commands would be contained
> in
> > a source physical file. 
> > > 
> > > So can I use the CL variable &CHGDATE in the PUT
> > command contained in the
> > > PF? My guess is it would look like this:
> > >            put mylib/myfile.mymbr &CHGDATE.raw
> > > 
> > > Can you do that? If not, is there another way to
> > do this? Any input is
> > > appreciated.
> > > 
> > > 
> > > Adam Ray
> > > Applications Programmer
> > > Family Health Partners
> > > Voice: 816-855-1822
> > > Fax: 816-855-1890
> > > Cell: 913-221-8685
> > > Email: aray@fhp.org <mailto:aray@fhp.org> 
> > > 
> > > 
> > 
> > +---
> > | This is the Midrange System Mailing List!
> > | To submit a new message, send your mail to
> > MIDRANGE-L@midrange.com.
> > | To subscribe to this list send email to
> > MIDRANGE-L-SUB@midrange.com.
> > | To unsubscribe from this list send email to
> > MIDRANGE-L-UNSUB@midrange.com.
> > | Questions should be directed to the list
> > owner/operator: david@midrange.com
> > +---
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Auctions - Buy the things you want at great
> prices. 
> http://auctions.yahoo.com/
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to
> MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to
> MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list
> owner/operator: david@midrange.com
> +---


__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - Buy the things you want at great prices. 
http://auctions.yahoo.com/
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to 
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to 
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: 
david@midrange.com
+---




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