RE: nightly backup: objects not saved error

This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Ah, new information.  So after an upgrade or PTFs are applied, I should
do both a SAVSYS *and* a SAVLIB *IBM?  I thought it was just SAVSYS.

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952
D.Bale@Handleman.com

> -----Original Message-----
> From: R. Bruce Hoffman, Jr. [SMTP:rbruceh@attglobal.net]
> Sent: Wednesday, August 22, 2001 10:50 AM
> To:   midrange-l@midrange.com
> Subject:      Re: nightly backup: objects not saved error
>
> -----Original Message-----
> From: Bale, Dan <D.Bale@handleman.com>
> To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
> Date: Tuesday, August 21, 2001 6:21 PM
> Subject: nightly backup: objects not saved error
>
>
> >In my nightly backups for our seven AS/400s, five of which are
> remote, I
> >am getting consistent occurences of objects not being saved.
> >
> >On our V4R4 system, I've got 7 objects in library QIWS which are
> never
> >saved:
> >   Cannot use PGM QNPSERVD in QIWS.
> >   Cannot use PGM QZDASRVSD in QIWS.
> >   Cannot use PGM QZHQSRVD in QIWS.
> >   Cannot use PGM QZRCSRVSD in QIWS.
> >   Cannot use PGM QZSCSRVSD in QIWS.
> >   Cannot use PGM QZSOSGND in QIWS.
> >   Cannot use PGM QZSOSMAPD in QIWS.
> >
>
>
> These are IBM objects. Don't save IBM every night. Just after PTFs and
> software upgrades.
>
> ===========================================================
> R. Bruce Hoffman, Jr.
>  -- IBM Certified Specialist - AS/400 Administrator
>  -- IBM Certified Specialist - RPG IV Developer
>
> "America is the land that fought for freedom and then
>   began passing laws to get rid of it."
>
>      - Alfred E. Neuman
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
>