NXPIPE is back on the CMS/TSO Pipelines home page, as is PIPENEW PDF.
Of the PDF, I'd ask you to review chapters 1 and 3. They describe
the enhancement to add the CALLER scope to the scopes where structures
can be defined. The NXPIPE reflects the documentation and this is
all forward compatible with the current state where there is no
CALLER scope.
My question is, should the defaults change and how?
My original take was to make the default scope CALLER. Regrettbly,
this will break some existing pipelines, certainly a number of test
cases, but more important, the previous level does not support inserting
the default SET scope to prepare for this incompaitble change.
Rob's suggestion is in some ways better, certainly more radical: the
default scope should be the "closest" available to the way the pipeline
specification is issued:
PIPE (and RUNPIPE), thread scope (otherwise the structure
disappears as soon as the PIPE command terminates).
ADDPIPE Set scope; there will be no active caller scope for this.
CALLPIPE Caller scope.
You are free to specify any scope, of course, subject to the condition
that caller scope is available only when the pipeline is a subroutine
pipeline.
Please make your views known and also any comments on the
documentation.
You might consider responding one of:
Don't care
Unaffected
Keep existing defaults
Like the proposed default (which one)
Alternate suggestions.
Thanks,
j.
