Re: *Backlevel

Do not confuse the described solution given by Pete [for removing the condition of a *BACKLEVEL indication] with a full correction of the side effects of an improper migration which could have seriously impacted the QGPL, [typically and more importantly] QUSRSYS & QSYS2 libraries. Sometimes that error arises for not having followed the migration instructions, and would result from having restored using a RSTLIB or RSTOBJ with ALWOBJDIF(*ALL) into QUSRSYS. Such a restore can effect much more severe consequences than just the indication of its having been back-leveled. Presumably such a restore was origin for the noted prior situation, for which a scratch install to recover the migration would have been suggested as recovery action by SupportLine; i.e. given that the re-install is often the quickest safe resolution, rather than trying to [figure out what to] /clean up/ whatever is wrong with the objects in the QUSRSYS library.

Any customized objects, objects which are part of the [actually any] LPP, should be re-customized as part of proper system change-management, rather than restored. Restore of an object would lose updates that were made to that object for the new release of the LPP, thus /back-leveling/ that object [just as the *BACKLEVEL intends to indicate is an issue for the LPP]. Since those libraries are quasi-system libraries, identified as /user libraries/ for B&R [as is QSYS2 since V5R?], any new objects [as part of customization] that are not part of the newest version of the LPP would be user-objects that could be restored [and OPTION(*NEW) MBROPT(*ALL) on the RSTxxx request would ensure conflicts of any such objects would not replace a same-named object that originated as part of the newest version of the LPP].

Regards, Chuck

tkreimer wrote:

Wish I ran into you a long long time ago Pete. I went under the
guidance of the support line for this case. What about any custom
objects in this library? Will they have to restore those objects?

Pete Massiello wrote:

You can just reinstall those options. The only issue is that you
will have to be in a restricted state for these 3 options. This is
a piece of cake to fix, and will take about 20 minutes. Then, I
would reapply the current cumulative PTF package they have
installed to make sure everything is in sync for PTFs.

tkreimer wrote:

I ran into this a long long time ago. With QGPL and QUSRYS anyway,
the only way out was a backup and then a scratch restore of the
LIC, then restore the libraries, then continue loading the licensed
programs etc. Very long downtime. Check into it carefully.

Jacktucky wrote:

These are backlevel. I'll read up on the links. I bet they did
a save from their old system and restored QGPL and Qusrsys.

5722SS1 V5R2M0 L00 Library QGPL
5722SS1 V5R2M0 L00 Library QUSRSYS
5722SS1 V5R2M0 Extended Base Support

Rob Berendt wrote:

Traditionally what happens in that case is that they got a new
box at a release higher than their old box and restored a few
libraries and stuff (screw the Backup and Recovery Guide) and
got themselves into that situation.

*BACKLEVEL ... To correct this problem, install a current
release of this product. ... <<SNIP>>