Way cool! Thanks Mike. -----Original Message----- From: CMSTSO Pipelines Discussion List [mailto:cms-pipeli...@vm.marist.edu] On Behalf Of Michael Harding Sent: Tuesday, April 06, 2010 4:37 PM To: CMS-PIPELINES@VM.MARIST.EDU Subject: Re: Looking for a nifty solution
Sure! Use Specs to construct the same callpipe command as a record and feed it to pipcmd. -- Mike Harding z/VM System Support mhard...@us.ibm.com mike.b.hard...@kp.org mikehard...@mindless.com (925) 926-3179 (w) (925) 323-2070 (c) IM: VMBearDad (AIM), mbhcpcvt (Y!) CMSTSO Pipelines Discussion List <CMS-PIPELINES@vm.marist.edu> wrote on 04/06/2010 01:23:34 PM: > From: "Hughes, Jim" <jim.hug...@doit.nh.gov> > To: CMS-PIPELINES@vm.marist.edu > Date: 04/06/2010 01:24 PM > Subject: Looking for a nifty solution > Sent by: CMSTSO Pipelines Discussion List <CMS-PIPELINES@vm.marist.edu> > > Here is a sample of what I have working: > > > > /* */ > > Signal on novalue > > "peekto $data" > > Do while rc = 0 > > Parse var $data $x1 $x2 $x3 . > > "callpipe < backup jcl a ", > > "| change /$var1/"$x1"/" , > > "| change /$var2/"$x2"/" , > > "| change /$var3/"$x3"/" , > > "| *: " > > "peekto $data" > > End > > > > Return rc*(rc<>12) > > > > Is there a way to connect the input stage(peekto) directly to the > callpipe reading the input file and do the variable substitution? > > > > Just curious.... > > > > > > ____________________ > > Jim Hughes > > 603-271-5586 > > "It is fun to do the impossible." > >
