RE: V7R3 upgrade preparation - DLTLICPGM no longer supported - any way of identifying if LPP still being used

We generally do not remove LPPs unless the upgrade process will do it
anyway, IE: Java levels, WAS, etc. Then after the upgrade we can
save/remove LPPs as needed. One of the beauties/curses of IBM i not
breaking old stuff. Old stuff tends to hang around too long. It's always
that one job stream that runs only so often that needs that old LPP and goes
casters up when it's removed, usually a month or two after the LPP has been
removed and no one remembers it.


--
Jim Oberholtzer
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob
Berendt
Sent: Friday, January 05, 2018 10:57 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: V7R3 upgrade preparation - DLTLICPGM no longer supported - any
way of identifying if LPP still being used

In general I agree that I would hesitate to remove any LPPs being
automatically replaced as part of the upgrade. Unless you weren't using
them to begin with.

I have done some SAVLICPGM to save files and then a DLTLICPGM to see what
would blow up. Especially while testing java stuff. Quite easy to do a
RSTLICPGM to get them back.

Maybe you could journal objects shown in the LPP libraries as an
alternative?

They problem I run into is when you're concerned more about IFS stuff, for
example, what a bunch of Java consumes to execute.


Rob Berendt