×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Well, that is one method of intersystem communication. :-)
The biggest problem with that method is trying to queue via "event". When
you use a real queue, like a message queue or a data queue, your local
program that is waiting on the queue wakes up upon an entry in the queue,
or an event. When you check for a file you have to check on a periodic
basis. Then you also have to check that not only is the file there but is
the whole file there and not still being written from the sending process.
To avoid the periodic basis, or the lock issue, you could look at
WRKREGINF
Exit
Exit Point
Point Format Registered Text
QIBM_QPWFS_FILE_SERV PWFS0100 *YES File Server
QIBM_QP0L_SCAN_CLOSE SCCL0100 *YES Integrated File System Scan o
QIBM_QP0L_SCAN_OPEN SCOP0100 *YES Integrated File System Scan o
I wonder if one of these can be put to the test?
The first one seems to be a "before" thing used to see if one should allow
the request. Doesn't sound like a good fit.
http://publib.boulder.ibm.com/infocenter/systems/scope/i5os/topic/rzaii/rzaiimstexfile.htm
I think the third one is also that way.
However that second one shows promise.
http://publib.boulder.ibm.com/infocenter/systems/scope/i5os/topic/apis/ifscloseexit.htm?resultof=%22%53%43%43%4c%30%31%30%30%22%20
This exit point is commonly used by products like Bytware's Standguard
Antivirus
http://www.bytware.com/products/av/index.html
Rob Berendt
midrange.com
