Re: Is an IPL adequate to end servers/subsystems for applying PTFs?

Hence my comment about it not being a totally benign process in another post.
--
Jim Oberholtzer
Agile Technology Architects

On Oct 9, 2025, at 11:50 AM, Rob Berendt <robertowenberendt@xxxxxxxxx> wrote:

*DLYALL doesn't necessary wait to apply some PTFs. I've used this and
still had some prereqs or coreqs or some such thing get loaded on and
applied immediately. Some disruption did happen.

On Thu, Oct 9, 2025 at 11:04 AM Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
wrote:

As Rob points out, there are some functions that a restricted state will
not necessarily stop, notably TCP.

In order to accomplish what the OP wants, use an image catalog with all
the needed PTFs and pre-requisites and co-requisites in it with the IPL
yes.

An application of an FTP package from an Image Catalog, along with the IPL
attributes set to yes will almost always apply PTFs properly and as quickly
as the process can run. Notable exceptions are TRs and other major groups
where the LIC level might change. There some proper prior planning is in
order.


--
Jim Oberholtzer
Agile Technology Architects

On Oct 9, 2025, at 9:44 AM, Raul Alberto Jager Weiler <

raul.jager@xxxxxxxxx> wrote:

IPL will end all, and restart it after.
It is not what you need.

On Wed, Oct 8, 2025 at 1:40 PM Charles Wilt <charles.wilt@xxxxxxxxx>

wrote:

On Wed, Oct 8, 2025 at 10:25 AM x y <xy6581@xxxxxxxxx> wrote:

However, an IPL is not required--IIRC the PTF cover letter will notate

such

a requirement. In this case, it sounds like ending the subsystem,

applying

the PTF, and restarting the subsystem is all that's required.

An IPL can be inconvenient for many users and IT professionals alike.

While true, I assume Michael knows if he can IPL or not..

Personally, I've always preferred to install all PTFs delayed and have

them

applied at IPL.

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

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