Re: [CMS-PIPELINES] Capturing output from a pipe

2015-07-20 Thread Paul Gilmartin
On 2015-07-20 11:34, Gentry, Steve wrote:
 I'm running the following pipe:
 29 *-* 'pipe',
'sql select TABLETYPE',
...

 And I'm getting the errors below displayed on the console:

 FPLSQL354E Return code -1060 from SQL, detected in module SQLRR003
 ...

 I'd like to be able to capture these messages, and send them to the 
 appropriate person in an email.
 Is it possible to do this?

o SPOOL your console -or-
o Wrap the whole thing in a hyperpipe with a CMS stage and output to a stem.

-- gil


Re: [CMS-PIPELINES] Capturing output from a pipe

2015-07-20 Thread Paul Gilmartin
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


Re: [CMS-PIPELINES] Capturing output from a pipe

2015-07-20 Thread Rob Van der Heij
In general, you would do the pipe under runpipe to capture the messages.
If it's more something ad-hoc, I tend to run the program again through the
command stage, like
 pipe command PIPETEST |  msgs txt a

Rob
---
Rob van der Heij
z/VM Development, CMS Pipelines





From:   Gentry, Steve steve.gen...@westernsouthernlife.com
To: CMS-PIPELINES@VM.MARIST.EDU
Date:   20-07-15 19:35
Subject:[CMS-PIPELINES] Capturing output from a pipe
Sent by:CMSTSO Pipelines Discussion List CMS-PIPELINES@VM.MARIST.EDU



I'm running the following pipe:
29 *-* 'pipe',
   'sql select TABLETYPE',
   'from system.syscatalog',
   where creator='SYSTEM',
   AND TNAME='SYSCATALOG',
   '|not chop 2',
   '|change /V/1/',
   '|change /R/0/',
   '|var db2isLUW'

And I'm getting the errors below displayed on the console:

FPLSQL354E Return code -1060 from SQL, detected in module SQLRR003
FPLMSG003I ... Issued from stage 1 of pipeline 1
FPLMSG001I ... Running sql select TABLETYPE from system.syscatalog where
FPLSQL355I ... RDS: -2145779603 DBSS: 0; 0 rows done; ---
FPLSQL356I ... Message parameter ZWEB01
FPLSQL369I ... SQL statement prepared: select TABLETYPE from
system.syscatalog
FPLSQL354E Return code -1060 from SQL, detected in module SQLRR003
FPLMSG003I ... Issued from stage 1 of pipeline 1
FPLMSG001I ... Running sql select TABLETYPE from system.syscatalog where
FPLSQL355I ... RDS: -2145779603 DBSS: 0; 0 rows done; ---
FPLSQL356I ... Message parameter ZWEB01
FPLSQL369I ... SQL statement prepared: select TABLETYPE from
system.syscatalog

I'd like to be able to capture these messages, and send them to the
appropriate person in an email.
Is it possible to do this?
Thanks,
Steve


[CMS-PIPELINES] Capturing output from a pipe

2015-07-20 Thread Gentry, Steve
I'm running the following pipe:
29 *-* 'pipe',
   'sql select TABLETYPE',
   'from system.syscatalog',
   where creator='SYSTEM',
   AND TNAME='SYSCATALOG',
   '|not chop 2',
   '|change /V/1/',
   '|change /R/0/',
   '|var db2isLUW'

And I'm getting the errors below displayed on the console:

FPLSQL354E Return code -1060 from SQL, detected in module SQLRR003
FPLMSG003I ... Issued from stage 1 of pipeline 1
FPLMSG001I ... Running sql select TABLETYPE from system.syscatalog where
FPLSQL355I ... RDS: -2145779603 DBSS: 0; 0 rows done; ---
FPLSQL356I ... Message parameter ZWEB01
FPLSQL369I ... SQL statement prepared: select TABLETYPE from system.syscatalog
FPLSQL354E Return code -1060 from SQL, detected in module SQLRR003
FPLMSG003I ... Issued from stage 1 of pipeline 1
FPLMSG001I ... Running sql select TABLETYPE from system.syscatalog where
FPLSQL355I ... RDS: -2145779603 DBSS: 0; 0 rows done; ---
FPLSQL356I ... Message parameter ZWEB01
FPLSQL369I ... SQL statement prepared: select TABLETYPE from system.syscatalog

I'd like to be able to capture these messages, and send them to the appropriate 
person in an email.
Is it possible to do this?
Thanks,
Steve


Re: [CMS-PIPELINES] Capturing output from a pipe

2015-07-20 Thread Gentry, Steve
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.
HYPER:  I didn't know you could do this.


-Original Message-
From: CMSTSO Pipelines Discussion List [mailto:CMS-PIPELINES@VM.MARIST.EDU] On 
Behalf Of Paul Gilmartin
Sent: Monday, July 20, 2015 1:42 PM
To: CMS-PIPELINES@VM.MARIST.EDU
Subject: Re: Capturing output from a pipe

On 2015-07-20 11:34, Gentry, Steve wrote:
 I'm running the following pipe:
 29 *-* 'pipe',
'sql select TABLETYPE',
...

 And I'm getting the errors below displayed on the console:

 FPLSQL354E Return code -1060 from SQL, detected in module SQLRR003
 ...

 I'd like to be able to capture these messages, and send them to the 
 appropriate person in an email.
 Is it possible to do this?

o SPOOL your console -or-
o Wrap the whole thing in a hyperpipe with a CMS stage and output to a stem.

-- gil


Re: [CMS-PIPELINES] Capturing output from a pipe

2015-07-20 Thread Michael Harding
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


Re: [CMS-PIPELINES] Capturing output from a pipe

2015-07-20 Thread Gentry, Steve
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