I'm not understanding something. Why does this work: GLOBALV SELECT SQL/DS LIST
And this doesn't: GLOBALV SELECT SQL/DS GET DBNAME (DBNAME IS valid.) -----Original Message----- From: CMSTSO Pipelines Discussion List [mailto:[email protected]] On Behalf Of Michael Harding Sent: Thursday, December 21, 2017 10:47 AM To: [email protected] Subject: Re: GLOBALV Or... 'PIPE command GLOBALV SELECT $$RDRLIS LIST | ... ' and locate or pick the item(s) of interest. -- Mike Harding /sp CMSTSO Pipelines Discussion List <[email protected]> wrote on 12/21/2017 07:31:37 AM: > From: Rob van der Heij <[email protected]> > To: [email protected] > Date: 12/21/2017 07:31 AM > Subject: Re: GLOBALV > Sent by: CMSTSO Pipelines Discussion List > <[email protected]> > > Steve, > > Not really. CMS does not provide a native interface for CMS Pipelines > to exploit. > > You can do things with "command" like this: > 'PIPE command GLOBALV SELECT $$RDRLIS STACK RDATETYP | append stack | ...' > > If you write a REXX filter, the value() function may be useful to do > what you need. > > Rob > > > On 21 December 2017 at 16:24, Gentry, Steve < > [email protected]> wrote: > > > Hi. Is it possible to issue the GLOBALV command from pipes? Or is > > there a STAGE to retrieve the info? > > I've tried a number of combination of commands with no luck. Those > > include "| CMS GLOBALV . . . ." , "| CP GLOBALV . . . ." , "| COMMAND > > GLOBALV . . . . " and a couple of things with SPEC. > > I could just read the file in a pipe and get what I want but prefer > > not to. > > Thanks, > > Steve > > >
