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

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

On 7/19/2013 10:27 AM, 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.

DSPOBJD the rogue library's objects into a PF and save the last used
date. You can then delete / merge the rogue into your CMS and still
keep the last use date in this archival / historical file.
--buck

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.