× 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.



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.



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark S Waterbury
Sent: Thursday, July 18, 2013 4:45 PM
To: Midrange Systems Technical Discussion
Subject: Re: CRTDUPOBJ: how to retain the create date and usage info

Hi, again, Joel:

Correction to my earlier reply -- the QLICOBJD API "last changed" key
only lets you change the object's last changed date and time stamp to
the current date-time stamp, or not change it at all. So, this may not
help you.

If you can explain why you think you need this "last changted" date to
be set the same as the original object, and what exactly you are doing
with that information, perhaps we can suggest some alternatives.

All the best,

Mark S. Waterbury

On 7/18/2013 5:31 PM, Stone, Joel wrote:
Thanks for the tip.

So I tried SAVOBJ/RSTOBJ.

Now I lose the "Last used date" info, which is critical to retain for this project.

Is it possible to create a copy of an object and retain both the CREATE-DATE and the LAST-USED-DATE?

I tried SAVOBJ UPDHST(*NO) but this still stepped on the last-used date when restored.



Thanks



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark S Waterbury
Sent: Wednesday, July 17, 2013 2:36 PM
To: Midrange Systems Technical Discussion
Subject: Re: CRTDUPOBJ: how to retain the create date and usage info

Joel:

By definition, CRTDUPOBJ creates a new object based on an existing
object as a "template". The new object will have today's date and time
as the "Create Date" and the current user profile as the object owner.

If you want to "clone" a objects from one library to another, preserving
all of the attributes, you could do something like this:

CRTSAVF QTEMP/SAVF
SAVOBJ OBJ(objectname) LIB(libraryone) DEV(*SAVF)
SAVF(QTEMP/SAVF) OBJTYPE(*PAGSEG) UPDHST(*NO)
RSTOBJ OBJ(objectname) SAVLIB(librarytwo) DEV(*SAVF)
SAVF(QTEMP/SAVF) OBJTYPE(*PAGSEG)

Hope that helps,

Mark S. Waterbury

> On 7/17/2013 3:24 PM, Stone, Joel wrote:
I need to copy objects from one lib to another and retain the create date and last date used info.

How can this be accomplished?

Object type = *pagseg and *ovl, maybe others

Thanks!



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.