I got bit by this one pretty good, and couldn't find anything about it, so I
figured I'd share:

Apparently, the AIX client 3.1.0.6, which has seemed to be quite stable, has a
weird bug where it can decide to stop seeing filesystems that start out "/u".

Yep, /usr, /usr/sap/trans, /usr/sap/SID, all of them, act like they aren't in
the domain statement any longer.

I was trying to restore a system to a test box (gotta love this Y2K testing).
And I couldn't get back any of the filesystems starting with "/u".  QUERY BACKUP
didn't show them, Q FILESPACE on the server didn't show them.  Checked my DOMAIN
statement, it's fine.  Looked everywhere, nothing.  Searched the archives here,
and didn't see it (hence my posting here) (didn't see doesn't mean it's not
there, just I couldn't find it in the mental state I was in at that point).
ADSM acted like the filesystem didn't exist.  Even doing a selective backup
didn't see the filesystem.  And no errors in the ActLog, just no entries at all
about these filesystems.

When I called ADSM support, they knew about it right off - the fix is 3.1.0.7.

When I ran an incremental after the upgrade, I expired a whole lot of files in
/usr/sap/trans, so, at some point, it did work.  3.1.0.6 is the only client
version that's ever been on this system, so I didn't get it with an old version.
So, my conclusion is that it just broke on day.  Weird.

Nick Cassimatis
nickpc AT us.ibm DOT com

If you don't have the time to do it right the first time, where will you find
the time to do it again?