|
I think a save is the key. In both of my cases the files had been savedsince last changed.
Save/Restore information:
Save date/time . . . . . . . . . . . : 03/10/18 11:18:41
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
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: Rob Berendt <rob@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 03/22/2018 10:40 AM
Subject: Re: Object changed date different in 7.2 -or- 7.3
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Too bad the file has never been journaled. If it had been you could have
checked the journal to see if any operations were performed on it in
addition to the basic CRUD.
On my 7.3 system I ran
DSPOBJD OBJ(ROB/A) OBJTYPE(*FILE)
Change date was old.
upddta rob/a
I inserted one row.
DSPOBJD OBJ(ROB/A) OBJTYPE(*FILE)
Change date is updated.
DSPJRN JRN(#MXJRN/USERS) FROMTIME(032218 102650)
Sequence Code Type Object Library Job Time
1983386 R PT A ROB ROBS1 10:27:14
1983387 U 00 EDH_H1_SND 10:27:14
So, did the first action update the change date,
or did the flag used by Quick-EDD to say it's been processed change the
change date? Then again, there's nothing in that second journal entry
which specifically mentions that file. Therefore why would it change the
change date?
So this should confuse everyone. Now Jeff is probably wondering why my
system updates DSPOBJD and his doesn't.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
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: Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 03/22/2018 10:20 AM
Subject: Re: Object changed date different in 7.2 -or- 7.3
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
That UPDDTA thing I did and posted about a few messages back?
I went onto the 7.1 system, did the exact same thing to a file in a *TEST
library that has never been journaled.
It caused the changed date to change.
On Thu, Mar 22, 2018 at 10:15 AM, Rob Berendt <rob@xxxxxxxxx> wrote:
<snip>system.
Maybe check your journals and see if there's something else happening in
addition to the row operation.
</snip>
That's a good idea. I know he journals.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
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: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 03/22/2018 10:07 AM
Subject: RE: Object changed date different in 7.2 -or- 7.3
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
I can't explain what you're seeing. All I can say is check out the IBM
doc I just posted. It covers 6.1 thru 7.3.
Maybe check your journals and see if there's something else happening in
addition to the row operation.
-----Original Message-----
From: Jeff Crosby [mailto:jlcrosby@xxxxxxxxxxxxxxxx]
Sent: Thursday, March 22, 2018 8:53 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Object changed date different in 7.2 -or- 7.3
What kind of change happens with your tables? Simple CRUD operations
don’t change the "Change date/time" on the object.
Yes they do in 7.1.
I still have access to the old 7.1 system via the console. I updated a
single record in a file via UPDDTA, then changed that record back. The
object change date got changed.
Then I did the exact same thing to the exact same file on the 7.3
The object change date did NOT get changed.skipped
So 7.1 and 7.3 are different in that regard. No idea of 7.2 as we
it entirely.list
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
direct.dilgardfoods.com
The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.