|
Typically compiles are only done on the dev box and installed on the prod
box. However, when the defecation hits the wind movement device, all bets
are off.
Also, there would be no reason to compile *PRV on the prod machine because
it is always the last one to be upgraded. All of the other machines are
already at V7.4 except the prod machine.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob
Berendt
Sent: Tuesday, May 30, 2023 3:54 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: OS upgrade and *PRV libraries
BTW, do you compile on Production? Do you compile to previous release on
the Production box? Or do you only compile on Development and move that
over to Production?
We do not install the following on Production: 5770SS1 9 5050
*PRV CL Compiler Support
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.
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.
--
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.