On 9/20/2013 2:29 PM, Mark Zelden wrote:
No disrespect here to Tom and his "head's up", you, his problem etc.
It's nice to have a head's up on a problem. This is just something
to ponder on a Friday afternoon (and not OT either!).
I am always curious why people "jump" after a post like this and think to
themselves "I have to get this PTF on "because someone they know ran
into the problem". As Tom noted, the APAR is not marked HIPER and hasn't
even hit RSU (at least as of a couple of days ago when I received
"CONTENT(RECOMMENDED)".
If your maintenance philosophy is to put on PTFs for a problem "some shop"
ran into, that would include all PUT maintenance and it wouldn't matter that
Tom or anyone else you know in person or from IBM-MAIN ran into the
problem or not. The fact is - "someone" ran into the problem and IBM opened
an APAR then a ++APAR fix followed by a ++PTF will be made available
(which BTW, could go PE!).
I am registered for ASAP for most of the z/OS FMIDs and I get
notifications pretty much every day and review them every few days. It's a bit
scary to see all the PE notification and read about all the potential problems
but I resist the temptation to apply outside of RSU unless I read the
description
and think there is good chance I would run into the problem in my environment.
One exception for me is that I usually apply SMSVSAM PTFs as soon as I can
as my client has a history of big impact issues with VSAM RLS when they hit.
I have some other exceptions too, like I see PTFs via ASAP for problems
like spin loops that lead to IPLs - but it depends on the cause / environment
described in the APAR text.
My good friend the gentleman from Illinois has a hot button for SMSVSAM,
mine is PDSE. In this case the fixing PTF has been available for 3-4
weeks, so it looks like a good one to put on. I can't wait to see
what's coming with PDSE V2 (shudder).
Regards,
Tom Conley
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
