Re: PTF dependencies

Nathan,

My (current) view of applying IBM i updates is it isn't ignorant-user(me)
friendly. It appears they've developed a robust system that is very
modularized which is great for automating from a CL/shell-script but causes
a new user to get lost. I reserve final opinion until after I've become
accomplished at installing updates.

I am guessing they have something in IBM Systems Director Navigator that
maybe ties the loose ends together**, but that isn't currently working for
me... because I need to apply PTFs to fix it :-)

​**Would be great to have notifications declaring available updates,
downloaded updates, updates waiting to be applied, updates applied and
when, etc.

I meant to comment on your thread about install approach but got side
tracked. We(KrengelTech) do our own install processes and don't use the
IBM APIs. I am sure the IBM APIs could provide all the flexibility you
could need, but I believe you could spend a great deal of time learning how
to use them.

Aaron Bartell
litmis.com - Services for open source on IBM i


On Tue, Jan 5, 2016 at 10:52 AM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

Am I supposed to always manually read through the PTF cover letters and
find related PTF groups and manually type them into the INSPTF command?

Or

is there a better way?

I've recently been exploring whether to use IBM's infrastructure for
packaging and distributing software releases and modifications vs. coming
up with a homegrown alternative. I initiated a discussion on this list
about the topic just days ago. As my exploration proceeded, the more
concerned I became about how IBM handles PTFs. The process seems too prone
to errors. And rather than accept responsibility, IBM pushes it off on
customers in the form of "cover letters", and disclaimers.

Customers deserve better.