RE: Re[2]: V4R5 Frustration

>      Is this situation what caused our devo mechine (170) to show
>      *BACKLEVEL for QGPL and QUSRSYS? We converted a 200 @ V3R2 to the
>      170 @ V4R3. I suspect our former admin restored these library
>      objects (user objects) from tape. The machine seems to be operating
>      ok, but we did notice the exit point problem recently (no exit
>      point registered for delete journal).

You can tell that QUSRSYS/QGPL has been overwritten by this *BACKLEVEL... or
more specifically, the QSS1MRI *DTAARAs.

If you can live with the mistake, you can "fix" it by changing the
dtaaras... do a DSPDTAARA and you'll know what to do.

This fix is useful if you want to selectively install a new licpgm, and it
keeps on insisting you need to upgrade QGPL/QUSRSYS.

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---