Well, your doc says when dam senses a trigger it shorts ALL streams, and indeed supplying a hole stage as primary output worked. And with this topology it can receive at most one primary stream record.
-- Mike Harding z/VM System Support /sp CMSTSO Pipelines Discussion List <CMS-PIPELINES@vm.marist.edu> wrote on 07/01/2014 09:02:23 PM: > From: "John P. Hartmann" <jphartm...@gmail.com> > To: CMS-PIPELINES@vm.marist.edu > Date: 07/01/2014 09:04 PM > Subject: Re: saving the last section I skipped > Sent by: CMSTSO Pipelines Discussion List <CMS-PIPELINES@vm.marist.edu> > > You need to stick a buffer or an elastic before DAM. > > On 07/01/2014 09:37 PM, Michael Harding wrote: > > Duh! Need more sleep I reckon. Should have seen the first, misunderstood > > DAM's behavior (and a trailing hole stage took care of that). > > Thanks again > > -- > > Mike Harding > > z/VM System Support > > /sp > > > > > > CMSTSO Pipelines Discussion List <CMS-PIPELINES@vm.marist.edu> wrote on > > 07/01/2014 10:48:09 AM: > > > >> From: Glenn Knickerbocker <n...@bestweb.net> > >> To: CMS-PIPELINES@vm.marist.edu > >> Date: 07/01/2014 10:48 AM > >> Subject: Re: saving the last section I skipped > >> Sent by: CMSTSO Pipelines Discussion List <CMS-PIPELINES@vm.marist.edu> > >> > >> On 7/1/2014 1:29 PM, Michael Harding wrote: > >>> First, the second pick, matching against the cutoff time works for the > >> > >>> case but doesn't seem to for the = case. > >> > >>> '|Pick w2 >>= /'cutoff'/', > >> > >> Looks like the value of CUTOFF in your test case has a trailing blank, > >> so it will never match a word. > >> > >>> Second, even though a record is obviously flowing to the Dam, the line > >>> count (var gotem) is always zero, which you can see inserting a cons > > stage > >>> in front of the var stage. > >> > >>> '|ga:Count lines', > >>> '|dd:Dam', > >> > >> It flows *to* but not *into* the DAM. It's left in the pipeline, so > >> COUNT doesn't count it as having gone through. > >> > >> ¬R > >> > > >
