Re: Re[2]: Trigger after FTP

[Gade_R_Reddy@xxxxxxxxxxxxxxxxxx]

Appreciate for all your suggestions.

Thanks.
Gade.






Jodi_Walker@ccmail.columbia.com (Jodi Walker)@midrange.com on 06/12/2000
06:42:58 PM

Please respond to RPG400-L@midrange.com

Sent by:  owner-rpg400-l@midrange.com


To:   "'RPG400-L@midrange.com'" <RPG400-L@midrange.com>
cc:
Subject:  Re[2]: Trigger after FTP



quote rcmd sbmjob cmd(call pgm(crossapps/process))
if there are parameters to call
quote rcmd sbmjob cmd(call pgm(crossapps/process) parm('Parm1' 'Parm2'))

you can even go so far as to specify job names, descriptions, queues, etc,
even
the library list, such as:
quote rcmd sbmjob cmd(call pgm(crossapps/process)) job(pcftp)
jobd(qgpl/pcftpjobd) jobq(qgpl/planning) inllibl(*job)

enjoy
jw


______________________________ Reply Separator
_________________________________
Subject: RE: Trigger after FTP
Author:  "Hatzenbeler; Tim" <thatzenbeler@clinitech.net> at Internet
Date:    06/12/2000 4:04 PM


I'll jump in on this one...

What ftp command do I issue to run the program  'Process' in Library
'CrossApps'?

Thanks for any input...

tim


> -----Original Message-----
> From: Rob Berendt [SMTP:rob@dekko.com]
> Sent: Monday, June 12, 2000 3:16 PM
> To:   RPG400-L@midrange.com
> Subject:      Re: Trigger after FTP
>
> Have them submit a command to process on your 400 when they've finished
> sending the file.  Our customers do.
>
>
>
>
> Gade_R_Reddy@consecofinance.com on 06/12/2000 05:04:23 PM
> Please respond to RPG400-L@midrange.com@Internet
> To:   RPG400-L@midrange.com@Internet
> cc:
> Fax to:
> Subject:      Trigger after FTP
>
>
> Hello.
>
> Our company gets a ftp file from an other company on daily basis.
>
> I need to write a program which should kick off whenever the FTP process
> is
> done.
>
> Please suggest what would be best to program so that it waits & kick off
> only if the ftp process is done.
>
> Thanks.
> Gade.
>
> +---
> | 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
+---



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