Basic System Problem Analysis - August 2003

Case Study: SA663

A system abort 663 occurs when a problem is encountered in a file system structure but

the Subsystem Dump facility has not been enabled by running SDUTIL. Had it been

enabled the file system and storage management would have been able to quarantine the

file preventing it from being accessed until it could be checked and, if necessary restored

with a good copy.

Since the failure is the result of a problem with a file the first thing to do would be to find

out what file that is.

We already know that FCLOSE would not have saved the file number in the stack so

there is no point looking there. The routine fclose_nm may have.

Note! The “level” (lev) command is used to move to a particular stack frame in a trace.

You always move to the “level” one past the code you want to look at. We want to look

at “fclose_nm” so we must set the level to 5 not 4.