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

[John Yeung <gallium.arsenide@xxxxxxxxx>]

On Fri, Jul 19, 2013 at 10:27 AM, Stone, Joel <Joel.Stone@xxxxxxxxxx> wrote:
> 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.

Well, putting aside the issue of whether it's a good idea for the
operating system to make it easy to duplicate and/or futz with these
timestamps, if all you need is the information, then the most
straightforward is probably just to retrieve it and save it to a file.

Sure, you would then have to do some programming/querying to retrieve
these timestamps from the file rather than from the object metadata,
but at least you could write something to isolate the products of
interest.  If you're concerned that the dates will look "wrong" in the
change management system... well, I think for most purposes, it's
understandable and perfectly OK for the initial merge that you see
this kind of thing.  Once they're in the system, then going forward
things will work out.

John