Re: More, Re: Weird problem with times. -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

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

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.