×
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 marked as "damaged"
Object . . . . . . . : LDAP_ENTRY
Library . . . . . : QUSRDIRDB
Library ASP device . : *SYSBAS
Type . . . . . . . . : *FILE
I discovered this during our full system save. We only do this every
other month. IBM wants me to restore the whole library QUSRDIRDB.
Save/Restore information:
Save date/time . . . . . . . . . . . : 07/27/08 19:31:55
Restore date/time . . . . . . . . . :
Save command . . . . . . . . . . . . : SAVLIB
Device type . . . . . . . . . . . . : Tape
Sequence number . . . . . . . . . . : 116
Volumes . . . . . . . . . . . . . . : M2V1S4
File label ID . . . . . . . . . . . : QUSRDIRDB
Save format . . . . . . . . . . . . : Serial
DSPFD shows 9 records and 1 deleted records. And IBM set the attributes
so that it cannot be read or written - even by QSECOFR. (Must be some
really special APIs they use.)
So, if I simply restore the library from July, what kind of negative
ramifications do you see? Or not enough to stress about?
Now to go on to deal with the plethora of other damaged objects on various
other partitions running a mix of V5 and V6. Is Windows any more stable
than this?
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
