I would argue, as have others, that our operating system does it *correctly*
in the sense that the duplicate object truly has no usage. If, for example,
I wanted to see if select objects were actually in use, I might duplicate
them to a library higher in the library list. Then, if *those* objects get
used, I'd see them updated as appropriate.
From an auditing standpoint, the actual behavior keeps the system integrity
intact.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Stone, Joel
Sent: Friday, July 19, 2013 9:10 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: CRTDUPOBJ: how to retain the create date and usage info
I would agree with you if the command was named CRTNEWOBJ. But it is not,
it is CRTDUPOBJ. It should create a duplicate of the original.
Why does MOVOBJ retain the important last-used date stamps but not
CRTDUPOBJ?
Can you imagine copying photos on your PC from one folder to another and
have all the snapshot dates change to the current day?
Its just sloppy and other OS vendors figured out the correct way to do this
decades ago.
Im not saying its right or wrong - it just seems very sloppy - like everyone
else figured out how to handle these things but OS/400 is behind and not
interested in catching up.
Just my opinion.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of TheBorg
Sent: Friday, July 19, 2013 9:58 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: CRTDUPOBJ: how to retain the create date and usage info
Joel -
Nice try, but you are /totally/ wrong.
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
Specifies name of the >>> new <<< object. A name must be
specified here if *SAME or *FROMLIB is specified for the
To library (TOLIB) parameter and the same auxiliary
storage pool device is specified for both the From ASP
device (ASPDEV) parameter and the To ASP device (TOASPDEV)
parameter. The names of members in a database file to be duplicated
remain the same in the new file.
*OBJ
The new object has the same name as the original
object. If this is specified, the new object and
original object must reside in different libraries.
*SAME
See *OBJ above. *SAME and *OBJ have the same meaning.
name
Specify the name of the >>> new <<< object.
-sjl
"Stone, Joel" wrote in message
news:mailman.3236.1374244056.9013.midrange-l@xxxxxxxxxxxx...
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!
midrange.com
