Yes, it's the "CP DETach" portion of the "CMS RELease" command that is not being suppressed via your methods.
If you don't know all of the disk addresses and just the modes, a non-pipe solution is to set IMSG OFF, which will suppress the "DASD nnnn DETACHED" portion of the CP command. Of course it's always nice to CP QUERY SET and save the IMSG setting before setting it off, and restoring IMSG to original setting once done... J -----Original Message----- From: CMSTSO Pipelines Discussion List [mailto:[email protected]] On Behalf Of Rob Van der Heij Sent: Monday, December 28, 2015 1:28 PM To: [email protected] Subject: Re: CMS PIPE output > Example 2: I remove the HOLE stage and use SET CMSTYPE HT RelList='C E > F G H I J K L M N O P Q R T U' > 'SET CMSTYPE HT' > 'pipe var RelList' , > '| split ' , > '| spec /RELEASE/ 1 W1 nw /(detach/ nw' , > '| CMS' > 'SET CMSTYPE RT' > > Neither method suppresses the output. Am I doing something wrong? > Can someone suggest a method to suppress output? > Thanks, > Steve Neither CMS Pipelines nor CMSTYPE HT are aware that the RELEASE will under the covers issue a CP command that produces output. If you do the DETACH yourself through "cp" you can have CMS Pipelines intercept (and discard) the output. I would do something like this, but that may be throwing you in the deep... Untested (and you'd have to do the quotes in REXX) PIPE (end \) \ var RelList | split | o: fanout | spec /RELEASE/ 1 w1 nw | command \ o: | spec /QUERY DISK/ 1 w1 nw | command | nlocate w4 ,STAT, | nlocate w2 ,DIR, | spec ,DETACH, 1 w2 nw | cp Or I would probably issue a QUERY DISK once and use "lookup" to find the ones to release, and then build CMS and CP commands... :-) Rob Tenzij hierboven anders aangegeven: / Unless stated otherwise above: IBM Nederland B.V. Gevestigd te Amsterdam Inschrijving Handelsregister Amsterdam Nr. 33054214
