Speaking as one of those journeyman plumbers who have written fairly complex pipelines without ever having the need to address commit levels (wonderful default designs permit that!)... > some task a stage might want to do before reading records that it needs
Perhaps checking that a downstream connection exists, perhaps even that a TCPIP connection is complete and ready to accept messages, before reading any records. Why bother to read them if no one's listening? Or, perform syntax checking of the stage syntax. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. "Bob Cronin" <[EMAIL PROTECTED]> Sent by: "CMSTSO Pipelines Discussion List" <[email protected]> 09/10/2007 08:27 AM Please respond to "CMSTSO Pipelines Discussion List" <[email protected]> To [email protected] cc Subject Re: Should this pipe run Nice, thanks for that. Could you give a simple example? That is, some task a stage might want to do before reading records that it needs to use a pipeline to do? I promise to read the paper someday soon ;-) On 9/10/07, Rob van der Heij <[EMAIL PROTECTED]> wrote: > Normally a REXX stage only needs to bother with commit levels > explicitly if it wants to use a pipeline to do the initialization (so > before touching the records in the real pipeline). > > Rob > The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
