× 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.



Joe - yes, I appreciate your approach... my thinking is very similar (they have a name for that).

This was my other SQL statement (the RRN came from WRKJOB)
select * from oeordlod where rrn(oeordlod) =34707

Since the issue can no longer be repeated, I'm resigned to the assumption of memory corruption. However, I have not identified a "suspect" in this case.
This is a very simple call stack...

CL Program with a Display file (for parameters)
SMBJOB of the RPGLE program... there are 4 parameters: CHAR(3), CHAR(15), CHAR(3), CHAR(8). Each of those are defined in the display file.
The RPGLE program makes successive calls (based on criteria) to another RPGLE program.

While I would like to know what happened, I'm not sure I do much now that the issue as disappeared.

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Thursday, September 05, 2019 5:30 PM
To: rpg400-l@xxxxxxxxxxxxxxxxxx
Subject: Re: Value in field does not match database????

I was just being really thorough (others would use another word) - you
showed us an SQL select but there was no RRN on it.  I just wondered if
you added the RRN() to the SQL select statement if it would match the
RRN you saw in the WRKJOB.

I know it almost certainly will, but it's those kinds of things that
sometimes make a light bulb go on.  Short of that, I'm inclined to agree
with Jon about memory corruption.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.