On Wednesday, 07/12/2006 at 09:05 EST, Mike Walter <[EMAIL PROTECTED]> wrote:
> ?! ... How would an ADDED option supported by IBM break *existing* apps? Sorry to confuse. I thought I was saying that considering RELEASE to be "broken" and that it needs "fixing" is a non-starter. Changing RELEASE to trap and display the CP response so that PIPE CMS RELEASE would trap everything wouldn't be wise, and would cause apps to break. Adding a new option wouldn't be in the context of a fix - that's new function. > That having been said, were I to be asked to vote on this at SHARE, I'd > have to place it in the "Kind'a nice to have" category. We can code > around it without too much tedious awkwardness. And that's kind of where it lays. It's a bit of extra code to get around the feechur. :-) And we supplied VMLINK years ago to assist exec writers in the access and release of disks and directories. Alan Altmark z/VM Development IBM Endicott
