Re: SQL of Journal Entries

Of course, as soon as I click send, I think of a scenario.
I have to remember you're doing it over journal entries. So maybe I'm
wrong. Is RID a column name, or, is it a relative record number? Is there
a chance the file was reorganized in between the two updates so RID 27 has
different data than RID 27 used to have?
I could go on and on about this, and I am starting to circle around.
Just make sure you determine whether or not you need to quote the column.

On Mon, Feb 10, 2025 at 2:18 PM Rob Berendt <robertowenberendt@xxxxxxxxx>
wrote:

I have some other questions but let's address the elephant in the room
first.
rid is a reserved word starting a few releases of the OS back. Since at
least release 7.1
https://www.ibm.com/docs/en/i/7.5?topic=functions-rid

There is NO possible way to have the same relative record number, in the
same table, with two different values of bdt.
You might have to quote that column name to get the one you really want.

On Mon, Feb 10, 2025 at 1:13 PM Art Tostaine, Jr. <atostaine@xxxxxxxxx>
wrote:

Yes I have examples of both. I use EXPJRNE written by Thomas Raddatz <
thomas.raddatz@xxxxxxxxxxx> that exports the tables whole record format.

On Mon, Feb 10, 2025 at 12:53 PM Rob Berendt <robertowenberendt@xxxxxxxxx

wrote:

If you break it down into bite size chunks do you get anything?
select * from
wrkart/jrnhdr00 f
where f.bdt = '0001-01-01'
;
select * from
wrkart/jrnhdr00 t
where t.bdt <> '0001-01-01';

And, how did you export it to get all the columns available?

On Mon, Feb 10, 2025 at 12:31 PM Art Tostaine, Jr. <atostaine@xxxxxxxxx

wrote:

I'm trying to find what program changed BDT Date. I have exported the
journal entries into JRNHDR00. This SQL returns zero results. Am I

doing

it right? RID is the key of the table I journaled.

select * from
wrkart/jrnhdr00 f
*left* join wrkart/jrnhdr00 t on f.*rid* = t.*rid*
where f.bdt = '0001-01-01'
and t.bdt <> '0001-01-01'
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related

questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related

questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.