Re: [CMS-PIPELINES] saving the last section I skipped

2014-07-02 Thread Michael Harding
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

Re: [CMS-PIPELINES] saving the last section I skipped

2014-07-01 Thread Michael Harding
CMSTSO Pipelines Discussion List CMS-PIPELINES@vm.marist.edu wrote on 07/01/2014 09:47:49 AM: From: Glenn Knickerbocker n...@bestweb.net To: CMS-PIPELINES@vm.marist.edu Date: 07/01/2014 09:48 AM Subject: Re: saving the last section I skipped Sent by: CMSTSO Pipelines Discussion List

Re: [CMS-PIPELINES] saving the last section I skipped

2014-07-01 Thread John P. Hartmann
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

[CMS-PIPELINES] saving the last section I skipped

2014-06-30 Thread Glenn Knickerbocker
I have a file of transactions with the timestamps at the end of each. I want the transactions after a particular time. If the time matches a timestamp in the file, fine, I can start with the next record. If it doesn't, though, once I find the next timestamp, I need the whole transaction that