Re: Checking object create dates -- MIDRANGE-L

Trrevor:

If you save and restore a *FILE to a different library, then the File Level IDentifier will likely change, but this is not used for "Level Checks" -- for that, the system uses the Record Format Level Identifier. If you change anything that would change the record layout (format), then the record format Level IDentifier will likely be changed. (There are a few very subtle cases where you can make certain changes, for example, changing the order of two fields in a record, without actually causing the Record Format Level ID to change -- but this only happens for example with two adjacent fields, both defined as the same length and decimal places; very rare -- the "hash" algorithm for computing the Record Format Level ID will not catch such a change.)

If you issue CHGPF to change the SIZE or other parameters / attributes of the *FILE, this will not change the Record Format Level ID.

Hope that helps,

Mark S. Waterbury

> On 2/13/2014 5:32 PM, Briggs, Trevor (TBriggs2) wrote:

I'm sure that changing something in a file will change its identifier, but I'm not sure the reverse is true. I.e. the file may not change but the identifier might. This was true, I seem to recall (but many moons ago), that some actions, such as a save/restore or recreating a file on a different OS release could cause the identifier to change even though the file, for all practical purposes, was identical.

Trevor Briggs
Analyst/Programmer
Lincare, Inc.
(727) 431-1246
TBriggs2@xxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Wiant
Sent: Thursday, February 13, 2014 4:32 PM
To: Midrange Systems Technical Discussion
Subject: RE: Checking object create dates

dspfd, and near the bottom:

Record Format Level
Format Fields Length Identifier
XXXXXXX 16 169 38E9B2B3E4B71 <---

My understanding is that if anything changes in the record layout, this will get a different identifier. I read somewhere how it's determined but I don't have that reference anymore. This btw is the value that causes level checks in programs because the program object stores the file record identifier values when compiled. Changing the *file* identifier (e.g. CPYF will do that) doesn't bother the program, but the record level identifier does.

Cheers

James P. Wiant
Test System Administrator
FOODSTUFFS
NORTH ISLAND LIMITED

DD: 09 621 0774 | M: 027 463 4159| P: 09 621 0600
DX Box CX 15021 or PO Box 27480 Mount Roskill, Auckland 1440, New Zealand
Fast is fine. Accuracy is everything
Earp, Wyatt

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Friday, 14 February 2014 10:27 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Checking object create dates

James,

For files, you use Record signatures(s) do you mean Member level identifier . . . . . . . . . : 1140213104518
Or is there another field.

Paul

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Wiant
Sent: Thursday, February 13, 2014 4:08 PM
To: Midrange Systems Technical Discussion
Subject: RE: Checking object create dates

Depends on the object, but yes for programs I rely on the source date to determine if two programs are the same. For files, I use the record signature(s). I audit multiple systems to check for discrepancies, and this method has served me well.

James P. Wiant
Test System Administrator
FOODSTUFFS
NORTH ISLAND LIMITED

DD: 09 621 0774 | M: 027 463 4159| P: 09 621 0600 DX Box CX 15021 or PO Box 27480 Mount Roskill, Auckland 1440, New Zealand
Fast is fine. Accuracy is everything
Earp, Wyatt

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Friday, 14 February 2014 10:04 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Checking object create dates

Maybe
Crtdupobj carries the original source date, thus both source dates are equal.
Problem is that my utility uses dspobjd detail(*full) output(*outfile), source dates are not in the outfile.
If I change my utility to use detail(*service), I see the source dates in the outfile.

So, would it be correct to say that if two objects have different create dates, but the source dates are equal, the objects are equal.

Fix library
Creation date/time . . . . . . . . . : 08/15/11 10:41:44
Source file date/time . . . . . . . : 04/01/11 01:52:05
Std library
Creation date/time . . . . . . . . . : 08/28/11 10:49:35
Source file date/time . . . . . . . : 04/01/11 01:52:05

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Briggs, Trevor (TBriggs2)
Sent: Thursday, February 13, 2014 3:44 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Checking object create dates

If you do a DSPOBJD with DETAIL(*SERVICE) it shows the Source file date/time. Will this work for you?

Trevor Briggs
Analyst/Programmer
Lincare, Inc.
(727) 431-1246
TBriggs2@xxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Thursday, February 13, 2014 3:31 PM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: Checking object create dates

I'm working on a utility to find objects that exist in a custom/emergency fix library that would have a create date lt the create date of the object in the standard library, thus sign of an issue.
Utility done, working.
However, I found a scenario where we received a new object (*prtf) for an upgrade. Because we change some print attributes on a few of these, we place a copy of these prtf file objects in the fix library.
The upgrade is done, replacing the objects in the standard library.
Here's the issue.

The prtf object in the fix library was created with crtdupobj, prior to the upgrade being done.
Creation date/time . . . . . . . . . : 08/15/11 10:41:44
The prtf object in the standard library has a create date for the day of the upgrade.
Creation date/time . . . . . . . . . : 08/28/11 10:49:35

The objects are valid, but being flagged because of the create date issue.
I'm looking for some other field on the object, not finding any.

Many of our upgrade processes do this. The upgrade process does a crtdupobj, thus the object loses its original info, (create date, created by user)
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx
http://www.pencor.com/

--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

************************************************************************************************************************************************************************************************************
This message originates from Lincare Holdings Inc. It contains information which may be confidential or privileged and is intended only for the individual or entity named above.
It is prohibited for anyone else to disclose, copy, distribute or use the contents of this message.
All personal messages express views solely of the sender, which are not to be attributed to Lincare Holdings Inc., and may not be copied or distributed without this disclaimer.
If you received this message in error, please notify us immediately at MailAdmin@xxxxxxxxxxx or (800) 284-2006.
************************************************************************************************************************************************************************************************************

--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

######################################################################
This message was scanned for compliance with Foodstuffs North Island Limited email policies ######################################################################
This message has been sent from Foodstuffs North Island Limited (Foodstuffs).

The information contained in this message (including its attachments) is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material.
If you received this message in error, please contact the sender immediately by return email and delete this message and your reply.
You must not use, disclose, distribute, print or copy any part of this message.

The views and opinions expressed in this message may be those of the individual sender and not necessarily those of Foodstuffs, in which case the views are not given or endorsed by Foodstuffs.

Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.
--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

######################################################################
This message was scanned for compliance with Foodstuffs North Island Limited email policies ######################################################################
This message has been sent from Foodstuffs North Island Limited (Foodstuffs).

The information contained in this message (including its attachments) is intended only for the person or entity
to which it is addressed and may contain confidential and/or privileged material.
If you received this message in error, please contact the sender immediately by return email and delete this message and your reply.
You must not use, disclose, distribute, print or copy any part of this message.

The views and opinions expressed in this message may be those of the individual sender and not necessarily those of Foodstuffs,
in which case the views are not given or endorsed by Foodstuffs.

Please note that this communication does not designate an
information system for the purposes of the Electronic
Transactions Act 2002.