On Apr 8, 2008, at 16:46, Schuh, Richard wrote:
Is there any way to coerce either the CMS or COMMAND stage to write
output as it is received rather that waiting for the executed
command to
end before passing any of its output to the next stage?
CMS is not a multiprocessing monitor. Never was. Probably never
will be. Pipelines fakes it by providing a form of multiprocessing
within its own domain. But when it issues a classic CMS command,
it necessarily reverts to single threading. Otherwise, users
would be tempted to run two or more CMS commands concurrently,
and there are too many unserialized shared resources for that
to work.
Consider the effect on any other command if one command does:
LINK
DEFINE
DETACH
ACCESS
RELEASE
FILEDEF
GLOBALV
NUCXDROP
...
to name a few. I suppose two or more Rexx stages could interfere
with each other this way; one must trust the pipeline programmer.
But the programmer is not assumed to know what goes on inside a
CMS command.
Hmmm. What happens if inside a Rexx stage I do ADDRESS COMMAND ...?
-- gil
