× 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.



On 10-Apr-2015 12:38 -0500, Adam Driver wrote:
On 09-Apr-2015 14:03 -0500, Jim Oberholtzer wrote:
QUSRSYS is where all of that is stored and it's very likely it's
hosed up. You performed a "downgrade" of QUSRSYS/QGPL when you
restored the older version over the top of the new one. The
proper procedure would have been, load V5R4 LIC and OS. Restore
QUSRSYS/QGPL then upgrade them to V5R4 with the V5R4 save.

<<SNIP>>

I suggest you rebuild the V5R3 partition from its save, and then
upgrade it.


Unfortunately that is not an option, the hardware won't run V5R3.
Also, the customer will not allow us to restore again.

What I did do was:

1) Load OS from a V5R4 tape
2) Restore QUSRSYS *NEW objects from the V5R3 tape
3) Update the QUSRSYS LICPGM from DVD to V5R4

Now I'm considering:

1) Restore QUSRSYS with option *ALL from the V5R3 tape (And
ALWOBJDIF(*YES).
Presumably this will put QUSRSYS in back level, so then,
2) Update QUSRSYS from the V5R4 DVD.

What are your thoughts on that approach?


I can not claim to fully understand from the OP exactly what is the situation, but based on the implication of the followup reply:

Seem more likely that the process being considered [i.e. RSTLIB QUSRSYS OPTION(*ALL) ALWOBJDIF(*ALL)], and presumed to be helpful, instead could easily lead from SNAFU to FUBAR.

A better option might be to:

1> effect CLRLIB of the three "user libraries" QUSRSYS, QSYS2, and QGPL; the Clear Library requests alone might fail, but what is necessary to effect the result would be done, until CLRLIB succeeds.
2> RSTLIB (QSYS2 QUSRSYS QGPL) OPTION(*ALL) ALWOBJDIF(*ALL) from the v5r3 tape.
3> reinstall QUSRSYS, QGPL, and the OS OPTION(1)
4> reinstall the cumulative and groups


If that would qualify as "restore again" and thus be prohibited, then the situation likely would require someone to /correct/ the SNAFU across those pseudo-user libraries [system libraries that contain user data, typically in system-files]. The biggest problem with manual corrections is ensuring everything is caught and corrected, and there is a good chance that if something is missed; the effects of what is left incorrect may be subtle such that the resulting errors might not be seen until long into the future and the problematic effects may be quite confusing per lack of a conspicuous origin.


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.