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?
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. After all, this is a bet-the-business-on-it proposition. Peter -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of John McKown Sent: Wednesday, March 25, 2015 8:32 AM To: [email protected] Subject: Re: (Regular Expressions followup) On Wed, Mar 25, 2015 at 7:17 AM, John Gilmore <[email protected]> wrote: > Program objects and PDSEs are in no way new features. Why all the pother? Cross sysplex sharing is one _good_ reason. It just ain't possible to do reliably in the general case. The main _bad_ reason is that some people still have scars from the early days and have an aversion due to that. I had the same problem back when VSAM first came out. The need for "suballocation" made the DASD person go nuts because hiss VTOC listings didn't show the suballocated DSNs. So he wanted to stay ISAM. -- 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 This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
