× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Sounds like a good idea.  Do you do the CPYF's right before or after
QUSRSYS is saved?  Is syncronization critical for these files?

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

> -----Original Message-----
> From: Arlene_M_Soderlund/NFCNA.COM@NFCNA.COM
> [SMTP:Arlene_M_Soderlund/NFCNA.COM@NFCNA.COM]
> Sent: Wednesday, August 22, 2001 10:56 AM
> To:   midrange-l@midrange.com
> Subject:      Re: nightly backup: objects not saved error
>
> >> Subject: RE: nightly backup: objects not saved error
> >>
> >> 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.
> >>
> >> These files are used by OV/400 and SNADS. End the QSNADS subsystem
> >> before
> >> doing the backup.
>
>
> We get the same errors, we need to leave SNADS up so I get these
> objects
> via a CPYF into another library called ZUSRSYS since they are just
> PHYSICAL
> files. Knowing this is part of our recovery planning logic.
>
> Arlene


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.