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