On 2016-02-14, at 02:05, Rob van der Heij wrote: > On 14 February 2016 at 06:55, Paul Gilmartin <[email protected]> wrote: > >> >> At least I think that's what's happening. If I set the loop limit smaller >> the problem does not occur. Is there a way to flush the buffers and >> recover >> the storage without exiting my Rexx stage? >> >> Do I need to nest another Rexx stage? >> >> pipe query >> PIPINX086I CMS/TSO Pipelines, 5654-030/5655-A17 1.0112 >> (Version.Release/Mod) - Generated 30 Jul 2015 at 16:26:54. >> >> > At first glance I would assume the added pipeline to wrap up when you sever > the output. It will notice end-of-file on its primary input and wrap up > business. Unless your schematic display excludes things in the pipeline > that keep him alive. Maybe the dispatcher does not get to running those > pipes to termination because your REXX stage keeps running - try a SUSPEND > after you SEVER the output. You might run one of the addpipes list LISTRC > to see when it terminates. > Thanks. I see why I should have been maming all my pipelines. (BTW, what's the syntax of a "name"? I don't easily find it in the manuals. Can I use 100 characters?)
Is there a command that will list all active stages? Thanks again, gil
