Well, I don't have anything concrete to suggest so let me offer couple of
WAGs.
- Have you signed off/signed back on since you've recompiled your trigger
program? Perhaps DB is working with the copy out of QRPLOBJ.
- When you single step through debug, can you zero in on a particular line
of code after which your local variables become corrupt?
Elvis
Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400
www.centerfieldtechnology.com
-----Original Message-----
Subject: Re: Erratic behavior in trigger program, since unscheduled shutdown
lastnight.
bvining wrote:
Whether this fixes up your problem or not, I have no idea. But the code
is
wrong as provided.
Yes, and the individual who published the code just made a public
apology on the sister thread on the RPG list. No joy, however.
And Elvis, I also tried your idea of making the receiver one byte longer
than the picture-string. Again, no joy.
It seems that when I removed and reestablished the trigger, the place
where the CPF1850 occurs DOES move. So to speak.
After IPL, the exception is thrown by the first TIME statement following
a call to the published MailDate procedure. (Incidentally, the MailDate
procedure is in the same module.)
But after removing and reestablishing the trigger, it's thrown by the
first TIME statement encountered, period.
More detail in my latest message on the RPG-list sister thread.
--
JHHL
midrange.com
