In my copies of the reference it seems that the term "pipeline" is ambiguous. It refers to (in various places) either to 1 - the subsets of a specification separated by endchars. or to 2- everything defined by a specification
Examples of (1): - under Operands (of PIPE, ADDPIPE and CALLPIPE) endchar "Use endchar to separate multiple pipelines on a single PIPE command." BTW this is followed by a reference to "multistream pipelines", which does not necessitate endchar. - under Commit Level "A pipeline specification can consist of one or more pipelines." - under ADDPIPE "Use the ADDPIPE pipeline subcommand to add one or more pipelines to the set of running pipelines. The stage that issues ADDPIPE continues to execute in parallel with any newly added pipelines." OK so far, but then I find meaning (2): "When the ADDPIPE pipeline subcommand is invoked to add a new pipeline..." should not this say "add one or more new pipelines"? and then follows "the pipeline specified on ADDPIPE" same question. Please let me know whether you agree that there is ambiguity in the use of "pipeline" or I'm just not understanding it. And if there is ambiguity how can we improve the documentation to remove the ambiguity. (I will be glad to help with this). It seems we need two terms (for the 2 meanings given at the top). -- Bob Gailer 510-978-4454
