...
>ANR9999D IMFS(3570): ThreadId<6027> Lock conflict error in obtaining sLock for 
>node 39, filespace 7
...

Joe - I regret that I haven't the knowledge to advise on getting the nodename
      from the number; but you may see nearby messages about a client session
failing as a result, or the like.

You may be able to compensate for this problem by reducing the simultaneity of
sessions and processes, or by increasing server option RESOURCETimeout if
it is rather small (the default in v5 is 60 minutes, boosted from its
introductory value of 10 due to too many customer db contention problems).
But this may be a product problem that you need to refer to TSM Support.

  Richard Sims, BU