× 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 Thursday 14 February 2002 10:19, Mike.Collins@syan.co.uk wrote:
> One thing to bear in mind about using QSS1MRI, is that a few releases back,
> IBM changed the library that it resided in from QSYS to QUSRSYS. However on
> some systems this data area also resided in library QSYS2. Some sites ran
> with a system library list with QSYS2 above QUSRSYS and so encountered
> problems retrieving the data area because the data area in QSYS2 is NOT
> updated at OS/400 upgrade time. (this may be where the original questioners
> recollection of a problem came from). Therefore, you must ensure that you
> retrieve the correct data area.

My understanding was that the dtaaras have always existed in QUSRSYS and QGPL
and reflect the VRM of those libraries only. They were easy to alter
accidentally (eg RSTOBJ from qgpl after upgrading) and some people have
deliberately altered them to keep the LICPGM install option happy.

I guess their existance (and continued use in GO LICPGM) kind of implies
QSZRTVPR wasn't available when they were first created...

Isn't the easiest program method of getting the VRM to RTVOBJD qsys/qcmd and
get the SYSLVL (albeit an optimistic VnnRnnMnn format)...?

Brendan



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.