Re: OS upgrade and *PRV libraries

[Rob Berendt <robertowenberendt@xxxxxxxxx>]

And, the same goes for QSYS38.  IDK why we have that.  We never had a
S/38.  Went straight from S/36 to the IBM i predecessor.  I think maybe
some software product used that years ago.  I supposed we could audit it
and see if it's used.

On Tue, May 30, 2023 at 3:50 PM Rob Berendt <robertowenberendt@xxxxxxxxx>
wrote:

> Command authorities are commonly altered back to IBM defaults when an
> upgrade happens.
> The commands in QSYSV... call the same programs as the commands in QSYS.
> They are intended for compiles but nothing stops you from using them as a
> way to get around someone locking down the command in QSYS.
>
> On Tue, May 30, 2023 at 1:36 PM <smith5646midrange@xxxxxxxxx> wrote:
>
> > My client did an OS upgrade from V7.3 to V7.4 on their dev machine and it
> > has caused a few problems / questions.  Note that we are currently
> > compiling
> > objects using *PRV because the production box is not yet at V7.4.
> >
> > 1) The authorities on some of the objects on the dev machine in QSYSV7R3M0
> > have been stripped away.  This only appears to have happened to objects
> > that
> > had specific groups and authorities and were not *PUBLIC *USE.  Is this a
> > normal part of the OS upgrade path or do they have some program somewhere
> > doing something that they don't realize is running?
> >
> > 2) Is the QSYSV7R3M0 version of the objects used for anything other than
> > compiles?  Do we need to be worried about the authorities on the
> > production
> > machine for execution purposes?
> >
> > Thanks.
> >
> > --
> > 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.