RE: More, Re: Weird problem with times.

Try saving the file that the trigger is on.

Sharon

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Thursday, March 19, 2009 1:53 PM
To: RPG programming on the IBM i / System i
Subject: Re: More, Re: Weird problem with times.

Haas, Matt (CL Tech Sv) wrote:

Something else I just thought of: Have you tried recompiling the
trigger? If the program object is messed up, you can get weird
problems like this. We got bit by a DRDA bug a long time ago (I think
it was soon after we went to V5R1) that would overwrite the space the
program code of one external stored procedure was kept in. This would
eventually cause the program to get all sorts of weird errors.
Restoring the program would fix it for a while.

It's been recompiled perhaps as many as a dozen times since the problem
began.

And it's our V4R4 box, the highest OS level box we have with full
development tools. Is there anybody left at IBM who will even talk to us

about a V4R4 box?

No DRDA or SQL involved here; everything is strictly native, and so far,

I haven't been able to make the malfunction occur in anything else.

Still nothing odd shows up in a GO LICPGM, nor in the QSYSOPR message
queue, nor in the history log. How else would I look for damaged system
objects?

--
JHHL