> treating it as a defect to be fixed would break apps such as those posted here.
?! ... How would an ADDED option supported by IBM break *existing* apps? Old commands would continue to work. Use of a new option (for sake of this thread's consistency: "QUIET") would work on those systems that support it, but yes, it would fail on older systems without support. Upward compatibility is IBM's strong suite, I don't think any rational customer expects IBM to provide PTFs to add support for new command options to out-of-support systems. 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. But IMHO there are more important matters for VM development to address first. If Tom really, REALLY wants a "QUIET" option, he could always spend some time getting up close and personal with DMSARE ASSEMBLE to build and implement a local modification. He'd get what he'd like, and have a chance to learn a lot about VMSES/E in the process. Respectfully, Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not those of my employer. "Alan Altmark" <[EMAIL PROTECTED]> Sent by: "The IBM z/VM Operating System" <[email protected]> 07/12/2006 08:40 AM Please respond to "The IBM z/VM Operating System" <[email protected]> To [email protected] cc Subject Re: a really little pipe question Tom Heugel said: > Too much .. thanks to everyone that had something to add. > I think I'll just write up a requirement for IBM to add a QUIET option to > all commands.. ie REL Z (DET QUIET While it doesn't address this particular issue (the fact that RELEASE doesn't trap the CP response to a CP command it issued), I should also point out the CP SILENTLY command. If you add the SILENTLY option to the ATTACH, DETACH, or GIVE commands via the CP MODIFY COMMAND command, then you can use CP SILENTLY DETACH to get CP to surpress all output related to the command. While SILENTLY was really intended to stop the messages related to tape drive management, there's no reason I know of you can't use it for vdevs. If you're serious about writing a requirement, I would have to say that a requirement to add a QUIET option to all commands would be rejected. It's too broad. We'd consider a QUIET-like option only if there's no alternative. SILENTLY was created to shut off asynchronous messages that can't be trapped by diag 08, and those occuring in *another* virtual machine. As far as the RELEASE command goes, this is one of those Working as Coded things. It has worked this way since before rocks were invented, and treating it as a defect to be fixed would break apps such as those posted here. CMS is a 40-year-old operating system and has its warts. Some are lovable and some aren't. :-) Regards, Alan Alan Altmark Sr. Software Engineer IBM z/VM Development The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
