On 23-Jan-2012 06:12 , Victor Hunt wrote:
Thanks for the link. While it does discuss the duplicate file names,
I'm not getting CPI9A9C errors. I also do not have a backup tape that
does not have the duplicate files on it. This issue goes back to at
least 2005, in some cases longer.
On Mon, Jan 23, 2012 at 7:34 AM,<rob@xxxxxxxxx> wrote:
http://www-912.ibm.com/s_dir/slkbase.NSF/1ac66549a21402188625680b0002037e/9f9b16faf978756f86256714005b516d?OpenDocument&ExpandSection=-1
While the noted KB document number 14995701 may be somewhat specific
for its origin, probably noting a specific symptom from an original
failing scenario that prompted its creation, the text can be read more
generically to get an understanding for the more general situation of
the renamed files in QUSRSYS. The document is not so specific as to
justify being easily dismissed.
As to a backup, there are two things of note. Unless someone has
deleted some files, then all of the files and members still exist, just
improperly named\related.... so on the problematic system, the use of
just save, rename, and restore can enable recovery. However that is a
very tedious method, so restore from the IBM media for the current
release is much more practical. Restore from that media can be effected
by either an install of the QUSRSYS [requires restricted state] or by a
standard restore from the "label" where those files are stored; locating
the files to enable the restore is, IIRC, not so fun nor easy, so best
to find an example restore request to mimic. For a standard restore as
recovery, the original objects should be "moved" rather than deleted, to
enable authority recovery using GRTOBJAUT REFOBJ().
Regards, Chuck
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.