RE: Preserving last change date on a restored object

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Well, phooey! Thanks for the correction, Mark.

There probably is a way, but it would likely need to use MI.

Vern

At 02:27 PM 7/14/2004, you wrote:
> I do not recall that API being able to set the change date.  All I
> remember is that it has a setting to set it to the current date/time, it
> could not set it to any arbitrary value.
>
> It can set the source member change date/time in the service attributes
> but not the object change date.
>
> Mark
>
> midrange-l-bounces@xxxxxxxxxxxx wrote on 07/14/2004 02:29:58 PM:
>
> > You can set it back, if you know the values you want. The QLICOBJD API
> can
> > do that for you. You'd need to have saved that info before the save. The
>
> > output from a SAVxxx operation does not have it, so a DSPOBJD
> LIBNAME/*ALL
> > would be needed. The API is not too weird - can use it in CL, probably.
> Run
> > a RCVF loop, plug in the object info and old date/time, call the API,
> voila!
> >
> > HTH
> > Vern
> >
> > At 01:06 PM 7/14/2004, you wrote:
> >
> > >I was afraid of that
> > >
> > >-----Original Message-----
> > >Don't think so.
> > >
> > >Charles
> > >
> > > > -----Original Message-----
> > > > From: rick.baird@xxxxxxxxxxxxxxx [mailto:rick.baird@xxxxxxxxxxxxxxx]
> > > > Sent: Wednesday, July 14, 2004 9:59 AM
> > > > To: midrange-l@xxxxxxxxxxxx
> > > > Subject: Preserving last change date on a restored object
> > > >
> > > >
> > > > Hey all,
> > > >
> > > > We're migrating to a new box, and in a dry run, did a side-by-side
> > > > save/load.
> > > >
> > > > All is good, except that all user objects now have a new
> > > > 'changed date' -
> > > > that of the restore date.
> > > >
> > > > Is there anyway to save / restore objects, preserving the last date
> > > > changed?
> > > >
> > > > Thanks,
> > > >
> > > > Rick
> > >
> > >
> > >--
> > >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > >To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > >To subscribe, unsubscribe, or change list options,
> > >visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > >or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > >Before posting, please take a moment to review the archives
> > >at http://archive.midrange.com/midrange-l.
> >
> >
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.