Re: Need SQL To show updates to file from journal

On Aug 8, 2024, at 2:47 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

Just be aware that you're at minimum going to need to add
STARTING_RECEIVER_NAME
ENDING_RECEIVER_NAME

To the SQL statement, since it's not a current receiver nor even in the
current chain of receivers.

HTH,
Charles

On Thu, Aug 8, 2024 at 12:06 PM Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
wrote:

Charles,

Yes, the receivers for that long ago are long saved and removed from the
system, but they are saved, so now it's a matter of restoring them, getting
the data and removing them again. Since Mimix manages the receivers, the
only ones on the system are fairly current.

The more important issue was the SQL to get the data as opposed to using
IBM i commands to get it. In this case SQL is the definitive method.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On Thu, Aug 8, 2024 at 12:24 PM Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

That's 4 months ago...

Make sure that your journal receivers go back that far.

I don't think QSQJRN (automatic) would by default...

With manually configured journals, at prior employers I didn't keep them
more than 40-60 days.
At my current employer, we only keep them 3 days; too larg to save any
longer. But they get backed up so we can restore one older if needed.



Charles

On Thu, Aug 8, 2024 at 10:06 AM Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx>
wrote:

I need to show that three different users did not update a physical

table

for a specific set of dates. To explain more,

table mylib/abcd
journaled by QSQJRN
user1, user2, user3
dates between 4/1/24 and 4/5/24


Show what (if any) rows were updated by those users. Google is not

being

friendly today.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
--
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.

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