On Sun, Aug 13, 2017 at 10:34 PM, Paul Gilmartin <
[email protected]> 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
> >
> >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?
> For a dropbox-type upload, it should be possible to rename the file into a
> protected
> directory as soon as the transfer begins.  This does not terminate the
> transfer --
> the descriptor remains valid, identifying a valid inode.  As soon as the
> rename is
> complete (a minuscule timing window) neither the sender nor anyone else can
> stat(), open(), or unlink() it.
>

​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



>
> -- 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 [email protected] with the message: INFO IBM-MAIN

Reply via email to