|
Doesn't that require you retain your journals for quite some time?
Our journal receiver library is, by far, our biggest library on our
system.
Rob Berendt
-- Group Dekko Dept 1600 Mail to: 2505 Dekko Drive Garrett, IN 46738 Ship to: Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com From: Jim Oberholtzer <midrangel@xxxxxxxxxx> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> Date: 04/07/2011 12:52 PM Subject: Re: Find last date updated using SQL Sent by: midrange-l-bounces@xxxxxxxxxxxx Dave, By far and away the easiest way to do that is to run Journals on those files you care about and pull the information from the journals. Another way would be to use auditing but that my not provide you with the level of information you need. Jim Oberholtzer Chief Technical Architect Agile Technology Architects On 4/7/2011 11:02 AM, Dave Boettcher wrote:> On a somewhat regular basis, we need to determine whether or not thedata in tables in a schema have been updated. There are about 100 tables
in this schema and an update is run daily. Not all tables are necessarily
updated each day. I have been just doing a DSPFD and scrolling down to
the member list and looking at the last change date and time for the
member.
> This morning I thought there must be a way to find this using the SYS*tables created when you create a schema so that I could automate this
checking process. I have looked at QADBXREF and QADBIFLD but have only
found when the table itself was last changed, not when the data changed.
So I ran DSPFD *MBRLIST to an out file and of course it's there as last
change date. But isn't there a place on the system provided tables where
it would be also?
>stuff.
> All help is appreciated.
>
> TIA,
>
> Thanks,
>
> Dave B
>
> Two rules to eliminate stress:
> 1. Don't sweat the small stuff. 2. It's all small
>
As an Amazon Associate we earn from qualifying purchases.
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.