Eric -

As Andy indicates, overlapping filespace naming can result in
perplexing query results.  Doing 'dsmc query filespace' will help
uncover such.

Some other possibilities I can think of...

Check that the system clock on the client is current.  One should
never expect that a system clock should be like a month out of date,
but...

Check for unexpected characters in the filename.  There's nothing like
blanks at the end of a filename to bewilder us humans, especially
where the filename is reported at the end of the report line.  Or,
where something whacky has happened, there may be binary chars in the
filename, where backspace is one of the most misleading.  To check for
such, do like
    echo "'`ls -b /oracle/T02/sapdata2/el31hd_2/el31*`'"
which will reveal binary as octal and put touching single quotes
around the output string to reveal any trailing blanks.
You might also do 'istat oracle/T02/sapdata2/el31hd_2/el31hd.data2'
and check the "updated" value (the ctime) to see if anyone has been
monkeying with file name or attributes more recently than the file's
modified (mtime - when last written) timestamp.

   Richard Sims