RE: Burned by SAVCHGOBJ

Ted,

        I know where your coming from.  We migrated from a 170 to a 270 2
weeks ago.  We even had an ex-IBMer help us with the migration.  We brought
everything over the 1st weekend using an option 21 save.  We had some issues
to resolve so we decided to iron them out on the new box during the week
that followed. The following weekend we used a SAVCHGOBJ(as refered to by
the  ex-IBMer) to get the weeks worth of changes to complete the migration.
Luckily, the first day up on the new box, we noticed that even though we
thought we were bringing over all source code changes for the week from our
source code library, QCBLSRC and QDDSSRC did not come over although QCLSRC
did. I feel your pain.

Robert D. Perno
Sr. Programmer/Analyst
William S. Hein & Co., Inc.


-----Original Message-----
From: Ted Barry [mailto:TBARRY@xxxxxxxxxxxxxxxxxxxx]
Sent: Tuesday, March 25, 2003 2:38 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Burned by SAVCHGOBJ


That's what we did!  Every day since the 3rd (last full system save) I've
been doing SAVCHGOBJ on the 400, then RSTOBJ on the iSeries.  It seems, some
libraries picked up chgobj's along the way, but some didn't.

>>> Buck.Calabro@xxxxxxxxxxxx 03/25/03 11:09AM >>>
>Thank you IBM.  I did my last SAVLIB *NONSYS on 3/3 and have 
>been doing SAVCHGOBJ's since then.  I just cutover last night 
>and now my NIGHTMARE begins.

I have done disaster recovery (as in dasd destroyed) off of SAVCHGOBJ.  The
typical restore scenario would have you RSTLIB from the SAVLIB tape and
RSTOBJ from the SAVCHGOBJ tapes, each one in turn.  Did you miss some?
Maybe there's daylight after all?  Read the backup & recovery manual; all
may not be lost.

For the future, I wouldn't run a month of SAVCHGOBJs; we used to do a full
SAVLIB once a week, and SAVCHGOBJ daily.  That way, we had to apply at most
6 tape sets: the SAVLIB and 5 SAVCHGOBJ.
  --buck
_______________________________________________
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.