SRE: nightly backup: objects not saved error

[Ian Scotson <IanS@xxxxxxxxxxxx>]

Dan,

Not these objects, but i had some others (4) from QUSRSYS not saved
and tracked them down to object locks based on QSERVER SBS.

Once that ended, all ran OK.

Not documented though..

Ian.


-----Original Message-----
From: Bale, Dan [mailto:D.Bale@handleman.com]
Sent: Wednesday, 22 August 2001 8:19
To: MIDRANGE-L@midrange.com
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.

On one of our V3R7 systems, I've got 6 objects in library QUSRSYS which
are almost never saved:
   Cannot allocate object for file QAOKP01A in QUSRSYS.
   Cannot allocate object for file QAOKP09A in QUSRSYS.
   Cannot allocate object for file QAOKP08A in QUSRSYS.
   Cannot allocate object for file QAOKP04A in QUSRSYS.
   Cannot allocate object for file QASNADSQ in QUSRSYS.
   Cannot allocate object for file QAZCADIR in QUSRSYS.

Can anyone tell me what processes are running on these systems that
preclude them from being saved?  And how to end them short of ending all
of the subsystems?  And where this is documented, if you know this?

TIA.

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952
D.Bale@Handleman.com
  Quiquid latine dictum sit altum viditur.
  (Whatever is said in Latin seems profound.)

_______________________________________________
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