On 2013-05-22 10:27, Frank M. Ramaekers wrote: > > Don't really want to do that. I want to take an existing EXEC that > doesn't create a log file and run it through this to produce a log file. > It's conceivable that if you invoked your existing EXEC via the API and provided a RXSIO exit, you could redirect output from SAY to a Pipeline connector. Lotsa work; 'way beyond my skill set. And I suspect it still wouldn't capture terminal output from host commands called from the EXEC.
If you were to run your EXEC under CMS OpenExtensions, could you use the ">" and "<" operators to redirect REXX I/O to descriptors? I know that's how REXX works under z/OS UNIX System Services. And do Pipelines connectors interface nicely to OpenExtensions descriptors? -- gil
