On Wed, Mar 25, 2015 at 7:43 AM, Farley, Peter x23353 <[email protected]> wrote: > It's not just the PDSE bug history. There are still occasional glitches > found and APAR's issued. When was the last time BPAM had an APAR? How can > any business organization that is even moderately concerned with SLA's allow > itself to be forced to use a product that is known to cause production > downtime issues? >
I guess we are: (1) living right; (2) lucky; and/or (3) other, in that we have _never_ had a PDSE problem other than a few times, long ago, with some lock contention. Of course, our z/OS system is scheduled to be euthanized come January and is basically moribund now. I guess if we were doing a lot of concurrent updates we might have more problems. > Mostly I think this advance in technology is making CIO's and their managers > scared. As a programmer I long to get the language and runtime improvements > V5 and up will bring. As level-2 support for production issues, on call > 24x7, I shudder at the potential seriousness of production issues caused by > PDSE problems happening at oh-dark-thirty. > I was going to put in some comments about CIOs and Windows, but I got really bitter, so I'd best not. > After all, this is a bet-the-business-on-it proposition. See elided comments on Windows. > > Peter -- If you sent twitter messages while exploring, are you on a textpedition? He's about as useful as a wax frying pan. 10 to the 12th power microphones = 1 Megaphone Maranatha! <>< John McKown
