In a previous life, we used a vendor product called FTPALERT. It was
marketed by William Data Systems. They are now Syncsort and the product is Zen
FTP Monitor. This product operates by providing (or replacing) the standard FTP
exits; including FTPOSTPR. The product provided a GUI where the user could
configure email notifications or batch jobs to be executed upon completion of
most FTP commands. I thought that the product was quite useful!!
In my current position, we are more of a Connect:Direct shop, so FTP is
kind of frowned upon in production..
So yes, I think that it is a very feasible and useful idea.
Given the expen$e of most proprietary file transfer software, I don’t
understand why something like this is not more popular!!!!
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of John McKown
Sent: Monday, August 14, 2017 12:58 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: any interest: FTOSTPR exit (z/OS FTP server exit).
On Mon, Aug 14, 2017 at 11:40 AM, Paul Gilmartin <
0000000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Mon, 14 Aug 2017 08:25:18 -0500, John McKown wrote:
>
> >On Sun, Aug 13, 2017 at 10:34 PM, Paul Gilmartin wrote:
> >
> >> On Sun, 13 Aug 2017 17:27:24 -0500, John McKown wrote:
> >> >
> >> >Looking at
> >> > https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/
> com.ibm.zos.v2r2.halz002/ftp_cfg_opt_user_exits.htm
> >> > [URL repaired, I think. Grrr.]
> >> >It looks like something could possible be done using the FTOSTPR exit.
> >> This
> >> >appears to get control after a number of commands, namely RETR
> >> >(send
> file
> >> >to remote), STOR (get file from remote), STOU (store unique), APPE
> (append
> >> >to existing file on z/OS), DELE (delete z/OS DSN or file), RTNO
> >> >(Rename z/OS file or DSN).
> >> >
> >> >I was thinking that this might be a way to "do something" when one
> >> >of
> these
> >> >events occurs. Some of my ideas were along the lines of sending: a
> email
> >> >that a file has been received; sending a email when a remote user
> downloads
> >> >a file; run a batch job or UNIX script when a specific DSN/file
> >> >was
> uploaded.
> >> >
> >> When is the exit entered? When the command begns? When it completes?
> Both?
> >>
> >Exit runs _after_ the command completes. It has a parameter which
> >indicates the "return code" for the function. I've not looked closely
> >at the various values which might be in this "return code".
> >
> >Perhaps I should have included this link as well:
> >https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/
> com.ibm.zos.v2r2.halz001/ftpostpruserexit.htm
> >
> I RTFM. That one is entered after; (most?) others before.
>
> Also, with what UID are tne exits entered? I assume that after
> password validitation the server does fork(); setuid(); so are
> subsequent exits entered with the UID of the server (parent) or of the
> child?
>
Good question. I have not written any code at yet, so I don't know. I was
asking mainly to get feedback as to whether it is even a reasonable idea to
look at. So far, other than yourself, it seems to be a "big yawn".
>
> Wild idea: How about an exit in ~$LOGNAME/.ftpexit, execued for each
> command after the setuid()? This could be authored by the user with
> no need for admin privilege. I suppose ths is equivalent to
> FILETYPE=JES, ssh, or Co:Z in that each provides a way to execute code
> remotely.
>
Sounds like a really interesting idea. Basically that's what I was hoping for
- ideas about "what to do", and whether anybody was interested at all.
>
> -- gil
>
>
--
If you look around the poker table & don't see an obvious sucker, it's you.
Maranatha! <><
John McKown
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
