On Thu, May 27, 2010 at 7:28 AM, Glenn Knickerbocker <[email protected]> wrote:
> On Wed, 26 May 2010 20:25:50 -0500, you wrote: >>I have rexx stage that has suddenly started giving looping alerts. A trace >>reveals that a PEEKTO is not returning. Any thoughts? > > If PEEKTO hasn't returned and the pipeline hasn't stalled, then your REXX > stage can't be involved in the problem at all. Control is somewhere else > in the pipeline. Maybe something that was supposed to be feeding the > primary input of your REXX stage is accidentally connected to the wrong > place. Got any |DUP *| stages in your pipeline that might have gotten > hooked up to a HOLE somehow? If the 'peekto' was the last thing you saw in the REXX program, it's normally because whatever is on the input stream is not producing a record. So the REXX program is suspended until we have the next record. The LISTRC option may be helpful to see what stages terminate and may don't propagate eof. Rob
