Re: [CMS-PIPELINES] optional secondary stream in a REXX stage

2016-01-05 Thread John P. Hartmann
You can determine the number of streams and use SELECT and all the other stuff, but if you refer to a stream that isn't there, retribution will be swift. In short, you can do whatever you like. addstream input or addstream output creates a single stream. I'm not sure that was smart on my part.

Re: [CMS-PIPELINES] Funny finding

2016-01-05 Thread Amphitryon
In my opinion there is no need neither for an option nor a configuration variable. Who has the hours to fine-adjust processing with options may use a STRLIT IFEMPTY to achieve the same. Fiddling with my OCT2>HEX rexx I found VERIFY does pass null records too. So I use LOCATE to filter them out.

[CMS-PIPELINES] optional secondary stream in a REXX stage

2016-01-05 Thread Amphitryon
I flipped through The Book but did not find an example. When I want an optional secondary stream in a REXX, do I have to query for it and optional use '*..1:' or 'take 0' in my callpipe? Or is there a canonical way to make the secondary connector act smart? And, what do I have to do that

Re: [CMS-PIPELINES] optional secondary stream in a REXX stage

2016-01-05 Thread Glenn Knickerbocker
On 1/5/2016 12:03 PM, amphitr...@ok.de wrote: > I flipped through The Book but did not find an example. When I > want an optional secondary stream in a REXX, do I have to query > for it and optional use '*..1:' or 'take 0' in my callpipe? Or is > there a canonical way to make the secondary