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 >
