I know it was pipeline error 30 because I remember doing "pipe ahelp 30" to get the explanation (and I wouldn't have done that unless I had specific evidence), but sadly I don't have a console trace anymore so I can't paste that evidence here (sigh). It was a bit of a hectic situation and I was scrambling to put things back together as a deluge of new data was arriving and I just wasn't careful enough to preserve the record of what was happening.
The pipeline in question is quite complex (aren't they all? :-) so there's likely no point in pursuing it further (at the moment anyway, but if it recurs perhaps I will be back). -- bc On Tue, Oct 5, 2010 at 3:30 PM, John P. Hartmann <[email protected]>wrote: > Bob, > > Message is 30 is issued for each active stage after message 29, which > is the real message to say the pipeline is stalled. Are you sure it > was a pipeline message 30 you saw? Without msg 29, that is unlikely. > Seeing just one msg 30 is also rather unlikely (though pipe f:fanin|:f > will produce just the one). > > Which module issued msg 30? > > (Audit sounds like some local bolt-on.) > > Cheers, > > j. > > On 5 October 2010 21:00, Bob Cronin <[email protected]> wrote: > > The only reason I said it stalled was because the pipeline returned rc=30 > > which is doc'd as: > > > > 30I Stage is in state <state> > > > > Explanation: The pipeline is stalled. The state of each stage is > > listed. > > The following states are defined: > > > > So you tell me, did it stall or not? > > > > Further investigation showed the SFS filepool server had abended due to a > > corrupted AUDIT disk (whatever that is). > > > > Thanks for the feedback. > > -- > > bc > > > > On Tue, Oct 5, 2010 at 2:57 PM, Kris Buelens <[email protected]> > wrote: > > > >> Most of the time such errors mean you have to get in touch with SW > support. > >> To get the message number, you could > >> - ACCESS 19D as Z > >> - use a tool to scan all DMS* HELPMSG Z files for string "Detecting > module" > >> > >> 2010/10/5 Bob Cronin <[email protected]> > >> > >> > I had a pipe stall (return code 30) in the middle of writing a file to > an > >> > SFS directory using ">". The only clue as to what might have been > wrong > >> was > >> > this cryptic error message I found on the console log: > >> > > >> > Error 76000 for file pool XAGSFS; error codes -1 and -115; Detecting > >> module > >> > DMS3WM > >> > > >> > Sadly, I don't have the actual message number. > >> > > >> > All subsequent attempts to write to the filepool failed (with rc 30 or > >> 31) > >> > for about the next 45 minutes, after which the problem mysteriously > went > >> > away by itself (i.e. without any help from me, anyway). > >> > > >> > Anyone ever seen this or have any suggestions what might be going on? > >> > -- > >> > bc > >> > > >> > >> > >> > >> -- > >> Kris Buelens, > >> IBM Belgium, VM customer support > >> > > >
