Hi, I just found out about this forum and figured I should reply, since I used to teach the IBM courses. I know which problem you're referring to, and I thought until recently that it had been corrected, but it hasn't. STRMONOND does work with directories, but the problem is that as soon as it sees a .ind file it looks for the associated .out file. That means that there can be a timing problem -- the Kofax release script sends the files, and the .ind file can end in error (and the file changed to .err) before the .out file reaches the directory. One of the ptf cover letters seemed to imply that this was no longer true, so that's probably the information you saw. What the cover letter was referring to, however, was a file locking problem with the .ind file. I know because I had a PMR on this issue. The arsload program works differently -- it looks for an .ard file (not an .ind file), which is not sent by the release script until both the .ind and .out files have been sent.
Based on your note, I'm going to submit a request for the STRMONOND program to be changed so it will work the same way as the arsload program.
You CAN use the STRMONOND program on a directory if you schedule it so that it's run only when users are not scanning -- at the end of the day, for example. Then it works quite well.