Offer, et al: If some of your users can tolerate some changes, and the CP command of CMS is already used in many of the other places, consider something like the following:
CP EXEC: /* REXX- Trap CP output for CMS stage. */ "pipe cp" arg(1) "| cons" return RC In addition to simplicity, this allow users to control which commands should be trapped, and in which environments the output should be trapped. On Tue, Nov 29, 2016 at 8:49 AM, Offer Baruch <offerbar...@gmail.com> wrote: > Thank you all for your help. > > At the end STARMSG *MSGALL did the trick without the CPCONIO or VMCONIO > parameters... > Everything works perfectly now. > > Thanks again! > Offer Baruch > > On Tue, Nov 29, 2016 at 2:48 PM, Rod Furey <bent...@gmail.com> wrote: > > > ---- > > But you would be better off to modify your tools to make it more suitable > > for usage in a pipe (and not prompt for input or things like that). > > > > Rob > > ---- > > > > To emphasise what Rob says: we discovered long ago that a rewrite paid > > dividends and very quickly paid back the development investment. > > > > I have fond memories of the time the Pipelines forum contributors helped > > someone out and we got an exec's running time down from hours to > > sub-minute. > > > > I realise it may not be possible for you to get a rewrite organised but > > it's something to think about for the future. > > > > Rod > > > -- OREXXMan
