If you go through the overhead of firing up a COMMAND stage, you might
as well reap the benefit from using it. Make the pipeline:
PIPE command LISTFILE PROFILE EXEC A ( NOH | ...
and forget all about the stack. Looks a lot more inviting, no?
Now, if you want to process the data from LISTFILE, but also its error
messages in different ways, the contorted pipeline quoted below might
have some merit.
Finally, if you are looking for a single file, STATE is what you want:
PIPE STATE some file x | stem info.
The period at the completion of the previous line is part of the command.
On 02/27/2015 02:53 PM, Rob van der Heij wrote:
On 27 February 2015 at 13:48, Gentry, Steve <
[email protected]> wrote:
Rob, that's it, thanks.
BTW, is STACK considered a stage?
PIPE command LISTFILE PROFILE EXEC A ( STACK | hole | append stack | ...
As Bruce says, but I see the confusion. The "STACK" (in uppercase) is an
option on the LISTFILE command (the first one that came to mind - I gave up
smoking EXECIO a long time ago). The "stack" (lowercase) is a pipeline
stage. And indeed, "append" is like a short-hand notation for a
multi-stream pipeline that concatenates two streams, but this case is
common enough that it's worth to have in your plumber's toolbox without
completely understanding what's inside.
Rob
