Re: AW: Trigger weirdness with L-Date fields

Joe Pluta wrote:

Which makes no sense. Unless, of course, you aren't really running the trigger program you think you are running. Which is why you should check the message, check the job stack, etc. Look for programs with QRPLOBJ as the library name.

That must have been it. I started with everything fresh on the customer box, and started with the trigger program completely inert. No data mapping error.

I could have sworn that I did a RCLRSC every time I updated the trigger program yesterday, but then again, I've seen RCLRSC fail before.

And likewise, usually, I've found that merely having an active resolution to a trigger program is enough to put an exclusive lock on it, but then again, the box in question doesn't compile in batch jobs, so that might not have caught anything.

At any rate, I noticed that when I was putting the record image back into the trigger buffer, it looked suspiciously like I was one byte off in my positioning. So I made a slight change before activating that line.

Works fine now.

--
JHHL