RE: Burned by SAVCHGOBJ

> From: Ted Barry
>
> I have INDEED confirmed there were several objects that changed
> since my last *NONSYS and no other SAVxxxxx have been run other
> than SAVCHGOBJ.  My nonsys was run on 3/3 and several objects
> from our payroll library were changed on 3/10, 3/13, 3/18, 3/21
> and these objects were NEVER picked up by SAVCHGOBJ.  Might want
> to sanity check your procedures.  I will NEVER use it again.

Has anybody been checking the joblogs on the SAVCHGOBJ commands?  Locked
objects may not get saved, and you'll get a CPF3702 error.  Occasionally,
there is a good reason for an object to not get saved, and rather than deal
with the CPF3702 error, an enterprising programmer puts in a MONMSGH.
However, this can mask REAL problems in the save process.  I'd suggest
careful review of your SAVCHGOBJ joblogs.  A simple MONMSG has been the
source of many SAVxxx problems in my past.


> I've heard the horror stories for the past 25+ years and always
> thought it was somebody else and it would never happen to me.  OOPS!

Never had a problem in 20+ years, but I have to say that I currently use
SAVLIB and FTP (eventually burning things to CD-ROM), so I don't worry about
it anymore.

Joe