Hi Steve,

 SS>    What is should do is, sit and wait for a semafore (flag) file, and
 SS> when it finally exists, exit with an errorlevel. This way, it can
 SS> constantly look for someting to do, and then exit back to it's calling
 SS> .CMD file for it to execute events.

I suggest you look at using OS/2's REXX, it is ideal for doing this type of
work. I use it to serialize events that MUST happen in a particular
sequence, or when 2 different events CANNOT happen together. When using the
REXX SysSleep() call to wait for a flag, exactly 0 CPU cycles are consumed.


Then look into using SEMAPHORES or PIPES for triggering the events rather
than flag files. This means SysSleep() becomes redundant and your system
becomes a true event triggered environment.

Good luck..........pk.


--- Maximus/2 3.01