Re: CRTDUPOBJ: how to retain the create date and usage info -- MIDRANGE-L

And to clarify further, the /verb/ [action] mnemonic that defines the command is the word "Create" [i.e. the CRT of CRTDUPOBJ], for which *intuitively* a _new_ object is the effect, as duplicated from the _old_ object, and thus the new object will have its own "create date". As well, a new object intuitively has no indication of a "last used date".

Unlike some other Operating Systems which lack integrity with regard to maintaining the equivalent attributes of their representation of an /object/ , the IBM i architecturally implements /objects/ and ensures those attributes are established and maintained accordingly. So the complaint against that integrity being maintained by the OS is misplaced. A more appropriately directed complaint is that the IBM i OS does not provide very much, arguably insufficient user-defined attribute-storage, to enable storing user-controlled [variants of those] attributes aside from those attributes being properly\logically maintained by the OS. A CMS has, outside of the compiler and PTF\APAR information, little more than the "Object control level" portion of the Service OIR.

I would have suggested to use Move Object (MOVOBJ), but even that is, architecturally, considered a /change/ to the object.... because the owning context has been "changed" with that request.

But considering the requirement apparently is merely "to retain the
last-used date" of the old\existing objects, as others have suggested, extract that information from those and store it for later reference [e.g. DSPOBJD to an output file]. Or just retain those objects in the old library, from which a later reference can be made to extract\retrieve those details when required; e.g. RTVOBJD.

p.s. I have never seen any ruddy libraries ;-)

Regards, Chuck

On 19 Jul 2013 07:58, TheBorg wrote:

<<SNIP>>

When you use CRTDUPOBJ to duplicate an object, it creates a NEW
object based on an existing object. What is it about NEW OBJECT
that you do not understand?

Please read the help text:

>>> New <<< object (>>> NEWOBJ <<<) - Help

<<SNIP>>

On 19 Jul 2013 07:27, Stone, Joel wrote:

Not "last changed" date, rather "last used date" and "create date"
intuitively should be identical when savobj/rstobj or crtdupobj
is used to dup an object.

I believe that on all other OS's that survived, creating a
duplicate means just that; an identical instance of that object.
It is frustrating that this is not possible on the "i"
without MI or API programming.

I am trying to merge a rouge library into our change mgmt system.
There are 700 objects in there. It is important to retain the
last-used date so I can figure out which objects to import into our
production system and which ones to retire.

Ditto for create-date (and also for change date).

If these date stamps weren't important then why does every OS treat
them with importance - except os/400 ?

Please suggest some alternatives but the data is too important to
drop.