Re: Are there any V7R6 "Gotchas" that I would need to worry about?

James,
We had one vendor product which broke simply upon it's startup when it
tried to check it's license. One of the things it retrieved now requires
access to that WRKFCNUSG QIBM_IOSYSCFG_VIEW
I have to give them kudos for just using that function vs having the user
get *IOSYSCFG. Granted, you have to add it after the upgrade to 7.6 since
that function did not exist before then. The alternative would have been
to have the user profile their software runs under have *IOSYSCFG and be
7.6 ready prior to 7.5. Big security hole. So, again, I give them kudos.
GoAnywhere by Fortra.

On Wed, Jun 24, 2026 at 11:33 AM James H. H. Lampert via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

On 6/24/26 4:32 AM, Rob Berendt wrote:

You're doing the right thing by upgrading instead of waiting years down

the

road when everyone forgot their pain points.

Uh, I don't think you understand the question: we have a few products on
the market. And while the Memo to Users gives me no reason why those
products would break under V7R6 (we got rid of the undocumented system
calls and deprecated MI instructions over a quarter century ago; the
closest thing we have to a "hack" is the ability to open files with LOB
fields in QuestView, a pure RLA application), I'd like a second opinion.

--
JHHL

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.