Perhaps a bit clearer: as used in your example the VAR stage creates only one variable, and thus ends with eof propogated back to STACK, preventing subsequent record processing. Not knowing your goal, perhaps in place of VAR, you might consider STEM? Mike Walter Sent from my Verizon, Samsung Galaxy smartphone<div> </div><div> </div><!-- originalMessage --><div>-------- Original message --------</div><div>From: Rob van der Heij <[email protected]> </div><div>Date: 6/24/16 10:38 AM (GMT-05:00) </div><div>To: [email protected] </div><div>Subject: Re: the STACK stage </div><div> </div> > I'm not getting the results I'd expect when STACK is the first in a pipeline.
The "stack" stage will read all from the stack when you let it. When your pipeline decides to read only 1 line from the stack, the rest remains there for next time. The remainder of the pipeline propagates end-of-file backward, so tells the stages earlier in the pipeline to give up when they can. Along the same lines, when you use just the first 10 records of a file, CMS Pipelines will not read the entire file but will stop after the first bit. Indeed, "PIPE stack | hole" will consume all records from the stack. At that point "stack" will report end-of-file and "hole" will terminate as well. Rob
