On Thursday, 07/06/2006 at 01:23 AST, "Hughes, Jim - OIT" <[EMAIL PROTECTED]> wrote: > Interesting. > > PIPE literal RELEASE X | append literal CP DETACH 120 | command | hole > > I still see the cp dasd detach message. If I run the CP DEATCH command > by itself, I do not see the dasd detach message. > > I am going to learn from this one. > > <Set lurk mode on>
'cuz the RELEASE command issues a diagnose 8 with "DETACH 120", but doesn't trap the response, so it goes to the console (or *MSG or ....). Now that the requirement has become clear (get rid of pesky messages), I say: Try VMLINK instead. "EXEC VMLINK CHUCKIE 123 (PUSH .FM" if rc = 0 then pull . . filemode . "EXEC VMLINK CHUCKIE 123 (POP" There are a ton of options for the exec writer. Alan Altmark z/VM Development IBM Endicott
