Comitting means for example that a PIPE containing a stage that reads files, this stage will not even start reading the file when some other stage finds an invalid syntax in its parameters. Similar, a stage might ERASE a file: it should no do this when some other stage has an invalid syntax.
2007/9/6, Bob Cronin <[EMAIL PROTECTED]>: > > Can anyone give a good reference to material that explains what the heck > this committing to levels business is all about? My head spins whenever I > read posts like these. A high level introduction will do for now (as I > suspect it is complex enough that if you hit me with the full load all at > once I'd run away screaming ;-). > > bc > > On 9/6/07, Glenn Knickerbocker <[EMAIL PROTECTED]> wrote: > > > > James Johnson wrote: > > > The CallPipe can commit to whatever it wants. The userstage is > suspended > > > waiting for the CallPipe to complete. > > > > Aha, looks like the official documentation is misleading here. > > The author's help (PIPE AHELP CALLPIPE) says: > > > > > The stage that issues CALLPIPE > > > commits to the highest commit level of the subroutine pipeline while > it > > waits > > > for it to complete. > > > > So once the subroutine pipeline commits to 0, the issuing stage also > > commits to 0, and the calling pipeline can run. > > > > ¬R > > > -- Kris Buelens, IBM Belgium, VM customer support
