AW: Re: How comes SDSF HOLD panel shows one line per OutputGroup instead of per job?

2015-07-27 Thread Peter Hunkeler
>The multiple output groups are caused when you do a SET BOUNDARY within a >step. If you use a different step for each SET BOUNDARY, then a single output >entry appears for the job. Yep, this is what I did: multiple lists each for a different zone. I added DD statements to this job for the

AW: Re: How comes SDSF HOLD panel shows one line per OutputGroup instead of per job?

2015-07-27 Thread Peter Hunkeler
Solved! It was SMP/E who fooled me. I'm sorry to not have recognized this before posting. I had an SMP/E job doing some LIST processing for one zone. All DDs except from the CSI were dynamically allocated. I repeated the LIST statement in the same step to list from some more zones. SMP/E allocat

AW: Re: How comes SDSF HOLD panel shows one line per OutputGroup instead of per job?

2015-07-27 Thread Peter Hunkeler
>Any chance of a screen print/trap to show this phenomena? Yes, I could, but further investigation revealed that somehow the sysout dds for the jobs in question were somehow split into separate JES2 output groups. So it is obvious now, why each SYSOUT is display on a line of its own: They're