<Set Learn On> What is this PIPE and CALLPIPE attempting to do? I am unable to follow the ins and outs and would like to understand.
Thanks. ____________________ Jim Hughes 603-271-5586 "It is fun to do the impossible." -----Original Message----- From: CMSTSO Pipelines Discussion List [mailto:[email protected]] On Behalf Of Glenn Knickerbocker Sent: Monday, October 18, 2010 12:09 PM To: [email protected] Subject: Re: LOOKUP eats unused input record! "John P. Hartmann" wrote: > Glen, am I correct in infering that the frtarget test case (the first > one) works with the pipeline at Marist, but the second one fails? Right. Trying the older versions I have saved, I see the first one works on 110B0009 but not 110A0026. Here's a similar test of the CALLPIPE LOOKUP|GATE case: pipe query level CMS/TSO Pipelines, 5654-030/5655-A17 level 110C0006. pipe (end /) literal 1 2 3 4 5|split|a:lookbad|cons /literal 3|a: 6 *-* 'callpipe (end /) *..0: | exact: lookup detail | end: gate' , '/ *..1: | exact: | end: | *..0:' >>> "callpipe (end /) *..0: | exact: lookup detail | end: gate / *..1: | exact: | end: | *..0:" 1 2 +++ Interactive trace. TRACE OFF to end debug, ENTER to continue. +++ 9 *-* 'peekto line' >>> "peekto line" 10 *-* Say line >>> "4" 4 Looks like this happens only when the alternate output of GATE is connected. Leave off the CONS stage, and the 3 is left in the pipeline. ¬R
