Re: Detecting that a submitted batch job is ending from w/in an RPG program.

That exit program is unlike any other's I've seen. Like you said it is
only executed when the command is executed. Which brings us back to the
NEP. A useful parameter, but just not in the context of avoid a NEP.

One of the problems with using a NEP to read a directory and post a file
based on it's existence is that the file may exist, but still be in the
process of being wrote to. We ran into this problem when trying to use
ftp exit points to trap that a file has been put and should now be posted.
The ftp exit points were designed to check permission, not process data
that's already been posted. Think of it as the exit program to check
stream file open's, not close's. So, in FTP land, we did all sorts of
strange stuff like after you PUT the real data you PUT a dummy file and we
flagged that as go process the real data. Or you ran the RCMD to post the
data. Some customers were flexible - others told us to go defecate in our
hats and pull it down over our ears.

Rob Berendt