(Just picked off the last note in the thread.) I hate to leave this intriguing
discussion without a stab at lessons learned. Given that the problem was
finally solved and remediated through a PE APAR, there are a couple of actions
that might have led to faster resolution.
1. Rigorously pull the latest and greatest HOLDDATA early and often. We just
installed a V2R1 maintenance bundle that would otherwise have included the same
PE PTF except that it was blocked by an ERROR hold. OP redid his entire
maintenance cycle. I would have expected that effort to have succeeded if the
latest HOLDDATA had been swished into the mix.
2. Even after the fact, there can be great value in an error sysmod report:
SET BDY(GLOBAL ) .
REPORT ERRSYSMODS ZONES(MVST100) .
Again, with the latest HOLDDATA tow, this report might have uncovered the
bad boy with less agony than OP experienced.
On the other hand, we Listers would have missed out on a great adventure. ;-)
.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
[email protected]
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Tony Harminc
Sent: Thursday, March 26, 2015 8:10 AM
To: [email protected]
Subject: Re: Intermittent, not consistently reproducible problems with PDSEs on
z/OS V2R1 (incl. infrequent S0F4-20 RSN 1C0752EE ABENDs)
On 26 March 2015 at 08:06, Don Poitras <[email protected]> wrote:
> The special thanks should really go to Bob Rutledge. He's the one that
> pointed out the APAR. Tony just gave you a "public" url.
I was about to point that out. Thanks for doing it for me. :-)
Tony H.
basking in undeserved glory...
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
