The REXX variable pool addressed by ADDPIPE is different from CALLPIPE. - with CALLPIPE, the REXX instance issuing it is surely available as long as the called PIPE runs. - with ADDPIPE, this REXX instance can long be gone when the added PIPE still runs. The online help explains this.
2011/1/7 Paul Gilmartin <paulgboul...@aim.com> > Naively, I'd expect the following: > > 5 *-* 'addstream output FOO' > >>> "addstream output FOO" > 7 *-* 'addpipe *.output.FOO: | stem BAR.' > >>> "addpipe *.output.FOO: | stem BAR." > 8 *-* 'select output FOO' > >>> "select output FOO" > 9 *-* 'output Wombat' > >>> "output Wombat" > 10 *-* 'sever output' > >>> "sever output" > 11 *-* say symbol( 'BAR.0' ) value( 'BAR.0' ) > >>> "LIT BAR.0" > LIT BAR.0 > > ... to do the same as: > > 13 *-* 'callpipe literal Wombat | stem BAR.' > >>> "callpipe literal Wombat | stem BAR." > 14 *-* say symbol( 'BAR.0' ) value( 'BAR.0' ) > >>> "VAR 1" > > It doesn't. What's the paradigm for adding to a stem piecemeal? > > Thanks, > gil > -- Kris Buelens, IBM Belgium, VM customer support
