Correct, sort of. I want to programmatically capture those messages. I just did a cut-n-paste from the console log to the email to show as an example.
-----Original Message----- From: CMSTSO Pipelines Discussion List [mailto:CMS-PIPELINES@VM.MARIST.EDU] On Behalf Of Michael Harding Sent: Monday, July 20, 2015 2:21 PM To: CMS-PIPELINES@VM.MARIST.EDU Subject: Re: Capturing output from a pipe CMSTSO Pipelines Discussion List <CMS-PIPELINES@VM.MARIST.EDU> wrote on 07/20/2015 11:14:32 AM: > From: Paul Gilmartin <paulgboul...@aim.com> > To: CMS-PIPELINES@VM.MARIST.EDU > Date: 07/20/2015 11:14 AM > Subject: Re: Capturing output from a pipe Sent by: CMSTSO Pipelines > Discussion List <CMS-PIPELINES@VM.MARIST.EDU> > > On 2015-07-20 12:04, Gentry, Steve wrote: > > I thought of both of these: > > SPOOL, couldn't figure out how to do this dynamically. I'd only > want to do this before this pipe starts and return it to normal after > the pipe is done. > > > If the SQL pipe is embedded in an EXEC, you should be able to SPOOL > START before the PIPE SQL command and SPOOL STOP CLOSE after. > But this may interfere with existing spooling for other purposes. > > > HYPER: I didn't know you could do this. > > > Sorry; I was inventing jargon. If the SQL pipe is embedded in an EXEC > (as above), you should be able to PIPE CMD EXEC SQLPIPE | stem. > > (I am not a master plumber.) > > -- gil > Okay, I'm missing something but the original post said you wanted to capture the messages and include in an email, which you'd already accomplished in the act of posting the question. -- Mike Harding z/VM System Support /sp
