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. Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com ITIL v3 Foundation Certified Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://search390.techtarget.com/ateExperts/ On Fri, 20 Sep 2013 17:28:58 +0000, Jousma, David <david.jou...@53.com> wrote: >Nice timing. We are in the midst of a maintenance cycle. > >_________________________________________________________________ >Dave Jousma >Assistant Vice President, Mainframe Engineering >david.jou...@53.com >1830 East Paris, Grand Rapids, MI� 49546 MD RSCB2H >p 616.653.8429 >f 616.653.2717 > >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >Behalf Of Thomas Conley >Sent: Friday, September 20, 2013 1:08 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: OA42799 - loop in initiator caused by PDSE > >FYI, > >Just wanted to give a heads up to be on the lookout for OA42799. >Initiator may loop due to PDSE job end code, and cannot be cancelled or >forced. You can get a slip from PDSE L2 to abend the looping task. >APAR is not marked HIPER, so stay frosty. > > > > >This e-mail transmission contains information that is confidential and may be >privileged. It is intended only for the addressee(s) named above. If you >receive this e-mail in error, please do not read, copy or disseminate it in >any manner. If you are not the intended recipient, any disclosure, copying, >distribution or use of the contents of this information is prohibited. Please >reply to the message immediately by informing the sender that the message was >misdirected. After replying, please erase it from your computer system. Your >assistance in correcting this error is appreciated. > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
