Thank you
Lionel B. Dyck <>< Website: https://www.lbdsoftware.com Github: https://github.com/lbdyck “Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are.” - - - John Wooden -----Original Message----- From: CMSTSO Pipelines Discussion List <CMS-PIPELINES@VM.MARIST.EDU> On Behalf Of Rob van der Heij Sent: Saturday, June 25, 2022 04:05 PM To: CMS-PIPELINES@VM.MARIST.EDU Subject: Re: [CMS-PIPELINES] Trapping or preventing pipes error messages? While you know that you should be talking to your BatchPipes support folks ;-) You can wrap it in a pipeline to run though PIPCMD, but you'd have to tell from the output whether it's an error message or valid content. pipe literal callpipe listcat ntpx || *: |pipcmd | cons On Sat, 25 Jun 2022 at 22:18, Lionel B. Dyck <lbd...@gmail.com> wrote: > Is there a way to trap the error/warning messages when using pipes > (specifically pipes under TSO REXX) > > I'm starting with something trivial: > > 'pipes listcat' hlq '| stem hlq.' > > If there is nothing found for the value of hlq I get these messages: > > BPW00730E No data sets found matching xxx BPW00003I ... Issued from > stage 1 of pipeline 1 BPW00001I ... Running "listcat xxx" > > I don't really need these error messages as the stem (hlq.) will have > either a hlq.0 = 0 or nothing. > > Please advise > > Thank you > > > Lionel B. Dyck <>< > Website: https://www.lbdsoftware.com > Github: https://github.com/lbdyck > > "Worry more about your character than your reputation. Character is > what you > are, reputation merely what others think you are." - - - John Wooden >
