Re: Job Triggering on FTP Completion

Michael recommends monitoring IFS activity, but this is safe only if you otherwise trust the one coming in. As you say, exit points are better - they let you stop activity at the door. There are 3 formats for FTP login and 1 for client requests - if the party should not be there at all, that can be controlled. And the kinds of things they do can be regulated. I seem to remember several classes of requests that are given to the exit program. Not all that hard to write, in principle - just a program call with a defined set of parameters and structures, after all. API documentation should cover the details satisfactorily. I'm giving what I vaguely remember and do not guarantee complete correctness here.

Perhaps a special subcommand string could be sent, which could be changed to the appropriate call to signal the end of transmission and do something then.

Vern

rob@xxxxxxxxx wrote:

James,
Exit points are the way to go for many things with FTP.
I will say that supported versions of the operating system do support the "limit capabilities" part of the user profile when using ftp commands.
ftp> QUOTE RCMD DSPJOB OUTPUT(*PRINT)
250 Command DSPJOB OUTPUT(*PRINT) successful.
ftp> QUOTE RCMD DSPPTF 5733L85 OUTPUT(*PRINT)
550-Error occurred on command DSPPTF 5733L85 OUTPUT(*PRINT).


Rob Berendt