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

I didn't (and won't) say that the system-supplied security settings are
ideal. Thankfully I am not the designer nor the one to blame about such
matters! And if your system is not secure, ... well, that's probably
something you shouldn't announce on this list.

One of the first changes I make to any system for which I gain
responsibility, is to put in an exit program so that, even though the OS
*allows for* such activity, it cannot be executed. It will be logged and
stopped. The next step is to ensure that someone will see that log.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"A good storyteller is a person who has a good memory and hopes other people
haven't."
-- Irvin S. Cobb