Re: OS upgrade 7.1 to 7.3 and Enforcive

Jack,

I certainly would do the initial restricted state save before making any changes.

I’m glad the vendor has a process, it’s rare I run into it, the exception being those vendors that sell exits, such as the security ones.

Still, I would document it anyway, at some point it might become important information to have

Remember to do the *SAVSYS and *IBM saves after the upgrade. Between the two saves you now have an anchor point for a DR just before, and immediately after the upgrade. You could do the data too, but it’s on the first tape.

Jim Oberholtzer
Agile Technology Architects

On Jul 18, 2020, at 5:00 AM, Jack Kingsley <iseriesflorida@xxxxxxxxx> wrote:

The vendor does support it with removing them before the upgrade and then
adding them back. I was sent a document by tech support. I would imagine
you would do the full save with them present, remove them, perform upgrade,
then put them back. The documentation was so-so to explaining it overall.

On Fri, Jul 17, 2020 at 9:27 AM <midrangel@xxxxxxxxxxxxxxxxx> wrote:

The vendor would not have a method because the vendor does not have a good
way to deal with exits they don't support. I believe Rich suggested
restricted state, remove the exits, upgrade, finish configuration changes
etc., the while still in a restricted state reapply the exits. A good
plan,
just use a CL to do it for you so it's documented and repeatable.

There are however, a couple of exits you would not want to remove. If you
use BRMS, (or any other tape/recovery management system) do not remove the
exits for Media and Storage Extensions. There are three of them:
QIBM_QTA_STOR_EX400
QIBM_QTA_STOR_EX400
QIBM_QTA_TAPE_TMS
If you remove these that will fubar BRMS until they are put back. IBM
deals with their own programs during the upgrade process.

--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Bryan
Dietz
Sent: Friday, July 17, 2020 7:39 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: OS upgrade 7.1 to 7.3 and Enforcive

i agree with the notion of removing them. what "bothers" me is the vendor
does not have their own automated method for doing so.
they most likely have their own process for adding them during the software
install.
not many have an automatic "uninstall process".


Bryan

midrangel@xxxxxxxxxxxxxxxxx wrote on 7/17/2020 7:12 AM:

Depending on which exit points, that might be a valid suggestion, I
have not however had any problem with 90% of the exits during upgrades.

The ones that could cause issues are ones that deal with object
creation or changes, User Profiles, etc. Those activities happen in
great quantities during an upgrade.

So the answer is IBM's favorite: "it depends". To be safe, you could
build a list of the exits on the system, document the library/program
name, and build a CL to remove, then replace them as two separate
actions. That has two benefits. First it documents all your exits
quite thoroughly, and second it's repeatable.

--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Jack Kingsley
Sent: Friday, July 17, 2020 4:56 AM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: OS upgrade 7.1 to 7.3 and Enforcive

Going from 7.1 to 7.3. The vendor advises to remove all the exit
point programs before starting the upgrade. Can someone confirm this
is a requirement.
--
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.

Help support midrange.com by shopping at amazon.com with our affiliate

link:

https://amazon.midrange.com

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

Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com

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

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

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

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com