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
