Rob van der Heij wrote:
On 5/29/07, Bob Gailer <[EMAIL PROTECTED]> wrote:
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
I believe the Author's Edition uses the term "pipeline" as a loose
term to refer to some plumbing. The term "pipeline segment" is
typically used for a "straight pipeline" (between pipeline end
characters). The syntactic definition is that a "pipeline
specification" consists of "pipelines" separated by end characters.
The phrases you mention sound vague to me and I cannot find them in my
book. Could it be you refer to the CMS Pipelines User Guide or CMS
Pipelines Reference?
I was using z/VM V5R2.0 CMS Pipelines Reference: 4.4
If so, then put those in corner and pick up a copy of CMS/TSO
Pipelines - Author's Edition (there's a 1.1.11 level of earlier this
year).
I just copied it as vm.marist.edu/~pipeline/pipeline.pdf. Thanks.
Referring to chapter 17 Syntax of a Pipeline Specification:
"The pipeline specification is one pipeline unless an end character is
declared and used to separate pipelines." Good so far.
But then we find, under ENDCHAR: "The character or hex value is the end
character for the pipeline specification." This is really confusing!
But I think I can wade thru it anyway. I certainly like the Author's
Edition.
--
Bob Gailer
510-978-4454
