Strange. We've been using triggers for a while now for both Aix and Windows servers. The triggers are created on files that are not SQL compliant (although occasionally programs use an SQL compliant pointer). I haven't seen anything like you describe.
Is it the same trigger program? You're not trying to update the "trigger" file within the trigger right? Maybe check the readme's for the latest versions and see if you see anything that might jump out. Colin Alfke Calgary, Canada >-----Original Message----- >From: Charlie Rubeor > >Hopefully, this message will reach the list. We recently >converted to Lotus Notes and emails from the list have been >hit or miss. > >I am running into issues with file triggers. Specifically, it >seems to happen on files with names that are not >sql-compliant. For example, using a very simple trigger, >which opens a dir type file and writes a test record into the >dir type file. On a file called TEST_FILE, it works just >fine, writing both the test record and the TEST_FILE record. >On a file called TEST-FILE, the trigger writes the test >record, but does not write the TEST-FILE record. I've checked >the EXECSTAT variable, along with the usual return codes. >I've removed the triggers, deleted and re-created the files, >recompiled and recataloged, etc. Nothing jumped out at me. >Our versions are Unidata 6, hpux 11.11. > >Now, just to add another wrinkle, if you remove the trigger >from TEST-FILE, setfile TEST_FILE as a pointer to TEST-FILE >and create the trigger on TEST_FILE, it seems to work just >fine. Hopefully, I'm overlooking something simple. > >Charlie Rubeor ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
