Re: Moving to QSECURITY 40

It may not be that the vendor was just being sloppy. The vendor needs to
get on new releases and they actually need to test.
7.6 did a lot of restricting on commands, APIs, etc. Much that was open
now either requires *IOSYSCFG or the new 7.6 function to give 'read' part
of *IOSYSCFG

WRKFCNUSG
Function ID Function Name
QIBM_IOSYSCFG_VIEW View Input/Output System Configuration

Like, you cannot even view SOME of the system values anymore if you do not
either have *IOSYSCFG or are in the list of QIBM_IOSYSCFG_VIEW. There are
a lot of other things controlled by these.
https://www.ibm.com/docs/en/i/7.6.0?topic=values-whats-new-i-76
https://www.ibm.com/docs/en/i/7.6.0?topic=changes-command-api-authority
https://www.ibm.com/docs/en/i/7.6.0?topic=arc-sql-services-changes-require-iosyscfg-qibm-iosyscfg-view
https://www.ibm.com/docs/en/i/7.6.0?topic=commands-relational-database
https://www.ibm.com/docs/en/i/7.6.0?topic=ssw_ibm_i_76/cl/cfgtcp.html
https://www.ibm.com/docs/en/i/7.6.0?topic=changes-authority-change-tape-commands-apis
...
...
...
Now, I supposed that many vendors will just require the user profile
running them to have *IOSYSCFG without even an explanation why.

Suppose you have an operator with very limited authority. This operator
has to unload the tape, load a new tape and ensure that the device/library
is ready for tonight's run. Checking that device status? Well, WRKCFGSTS
and WRKMLBSTS were affected by this change. Sure there are simple enough
work arounds, like a custom program with adopting authority for one
example. But it's something to prepare for and be aware of.
There are still a shipload of vendors who rely upon their customers to do
new release testing.


On Wed, Nov 5, 2025 at 4:54 PM James H. H. Lampert via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

On 11/5/25 12:42 PM, Rob Berendt wrote:

So far the earliest is V3R6M0. Since that is after "Version 1 Release

3" I

should be ok, right?

What is interesting is finding vendor supplied programs with V4R1M0 and a
TEXT_DESCRIPTION of "(C) 2024...". Bet you can't guess it's a vendor

we're

knocking upside the head to get tested for 7.6, eh? I suppose they could
be generating on ancient stuff and restoring on newer to test.

We've been on Sec40 for over a decade, basically as soon as I managed to
work the Sec40-unfriendly hacks out of QuestView (and that was probably
before V3R2 was out).

And I think we've had at least one box up to Sec50.

There's nothing in QuestView that crashes under V4R4 (the worst-case
scenario is that it degrades gracefully), and nothing that (if you have
the current release, in the V5R2-and-up compatible version) isn't fully
compatible with OS versions up to at least V7R5 (and probably R6 as well).

So if there's a vendor-supplied program on your system that *doesn't*
like your OS release, or doesn't like Sec40 at your OS release, then the
vendor was just being sloppy.

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