Re: Job Triggering on FTP Completion

I'll add another suggestion:
As others have said - do the exit pgm & do not allow command execution.
Also, to make sure you have a complete file, I would suggest the spec
require some sort of trailer record, or totals, or if xml a final <something>.
The exit pgm can kick of your processor pgm, which can open & read the file
(after a reasonable delay), then verify final record is there, and only then
process the file. I usually move the file out of the directory the customer
put the file in, to a processing directory (so they cannot overwrite the file).
You won't be able to mov it till ftp has completed it's part.
Process it, and then move it again to an archive directory.
Another option to the exit pgm kicking off the processor is to read the dir
every xx seconds for new files. Since you clean out the rcv directory, it's very
fast. I've used something like this for several scenarios. Scott Klement's IFS
stuff for RPGLE work great and is free.
Jim Franz

----- Original Message ----- From: "Pete Massiello" <pmassiello-ml@xxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, January 07, 2010 4:37 PM
Subject: RE: Job Triggering on FTP Completion

I would create an exit point on this, and I have done this for a few
accounts where they needed additional security. We were able to control
based upon userid's which directory that they could put a file into, insure
that no one did "gets", and no one could execute a command. Using the 2
exit points we also kicked off a command at the end of a customer's ftp to
then process the data that was uploaded. In this case, we were always in
control of what program was executed.

Pete

Pete Massiello
iTech Solutions
http://www.itechsol.com

Add iTech Solutions on Facebook:
http://www.facebook.com/group.php?gid=126431824120
Add iTech Solutionw on LinkedIn: http://www.linkedin.com/groups?gid=2206093





-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Thursday, January 07, 2010 4:15 PM
To: Midrange Systems Technical Discussion
Subject: Re: Job Triggering on FTP Completion

Dennis Lovelady wrote:

Any advice would be appreciated.

The easiest is to request that the sender code a QUOTE RCMD
SomeCmD to activate the job after [e.g. using SBMJOB], or to notify

I would be *VERY*CAREFUL* about allowing some outside agency (not in my
control) to run applications and commands on my system!!!! I'd also

advise

against making them responsible for ensuring that some process runs on my
system.

Then again, they're already being trusted to open an FTP connection, so
the only way to exercise caution is to be AWARE that they can execute
commands through an FTP connection, and LIMIT what they can do.

I just ran a test in which I created a non-prived, "limited" user, and
two commands that would do something observable in batch (in this case,
their CPPs were simple CLs that did a DSPLIB of two different
publicly-readable libraries). I locked the user out of one of the
commands, then signed on as that user via FTP.

I could execute the command the user wasn't locked out of, but when I
tried the same with the command I'd locked the user out of, it threw:

550-Error occurred on command tst07ja10.
550 Error found on TST07JA10 command..

So yes, be cautious with ANY outsider being allowed ANY unsupervised
access to your FTP port!

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.