On 02/15/2011 07:08 PM, Paul Gilmartin wrote: > But another question: my pipeline writes the data body to *.OUTPUT.0: > and messages I generate to *.OUTPUT.2:. The caller may connect > either or both of these to CONSOLE. If both, I'd like the summary > to appear after the body. This seems to be unpredictable.
Connect them to CONSOLE--through what else? If the data body isn't typed to the console before your stage has a chance to write anything else, then there must be something in between delaying the record. Severing your stage's output might or might not trigger that something to write its output. Your stage doesn't have any control of what stages downstream do with its output. In the caller, if you want to make sure the order is enforced, instead of two separate CONSOLE stages, use FANIN to combine the outputs: 'PIPE (end /) a: mystage | b: fanin | cons / a: / a: | b:' ¬R
