I reported something similar a while ago. I think it is due to the fact that input is not allowed during a trigger subroutine. As as you are in the debugger, input is required to step through the program you are debugging, when the trigger fires the input is trapped. I think this is a bug, U2 should be able to determine the difference between this type of input, or, it should step over the trigger, executing it, but not allowing debugging of it, so at least you can debug the rest of your program. I wonder if you compile the trigger with the -I flag? so that it cannot be debugged if that would fix the problem?
Cheers, Phil Walker +64 27 5336294 +64 3 3120352 [EMAIL PROTECTED] Gnosys Consulting Limited 25 Roscrea Place, Mandeville North, RD2 Kaiapoi, North Canterbury 8252, NEW ZEALAND DISCLAIMER: This electronic message together with any attachments is confidential. If you are not the intended recipient, do not copy, disclose or use the contents in any way. Please also advise us by return e-mail that you have received the message and then please destroy. Gnosys Consulting Limited is not responsible for any changes made to this message and / or any attachments after sending by Gnosys Consulting Limited. We use virus scanning software but exclude all liability for viruses or anything similar in this email or any attachment. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Woodward Sent: Thursday, March 17, 2005 7:09 AM To: U2-Users List Subject: [U2] Write in debug breaks on trigger Hi Folks. I'm trying to debug a program using the UniDebugger in UV 10.1 but when the program goes to do a WRITE to a file that a trigger on it, it's breaking with the following message. Program "LABEL.BUILD.PICK.REPRINT": Line 578, Error performing trigger for "PMCF". Program "LABEL.BUILD.PICK.REPRINT": Line 578, WRITE failure. >T Verb "T" is not in your VOC. The line it's breaking on is: 578: WRITEV '0' ON PMCF,"LABEL.COUNTER*":CO:"*":SHIP.DATE,1 ; * RESET LABEL COUNTER TO ZERO It appears to be any type of WRITE statement as it was breaking on an earlier WRITE to the PMCF file that wasn't a WRITEV. In testing, I commented out that first WRITE to get past it but then hit the same error on this statement, WRITEV. If I run the program, I do not have this error and the writes are performed and the data updated. If I take off the triggers for this file, it runs and debugs properly. I'm needing to run this program in our LIVE system in debug so I need to also have the triggers running. Anyone have any idea what would cause triggers to behave differently while debugging? I'm stumped! TIA. BobW ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
