The down size of using a file device is that it requires mount points unlike 
diskpools.

Have you checked that your client has enough mount points set? Each backup 
session from the client will require its own mountpoint. This value is set on 
the client node definition on your tsm server.

Regards

Daniel Sparrman

Sent from my Sony Ericsson XPERIA™ X1.

----- Ursprungligt meddelande -----
Från: Nick Laflamme <dplaflamme AT GMAIL DOT COM>
Skickat: den 12 mars 2009 19:22
Till: ADSM-L AT VM.MARIST DOT EDU <ADSM-L AT VM.MARIST DOT EDU>
Ämne: ANR0539W node has exceeded its maximum number of mount points.


Setting up a new TSM server (5.5.1.1 on an AIX server) to replace an
existing server (5.4.3.0 on z/OS), I'm trying to implement DIRMC support for
the first time. I'm also using FILE storage pools, not DISK storage pools,
as the initial landing spots for the clients' backup data. DIRMC is being
implemented through a client option set from the server. I know it's in use
because when I hadn't set up the DISK storage pool for directory data
correctly, I didn't even get this far.

When my test Windows client connects to the new server, the system console
shows an ANR0539W message, that the client is exceeding its allowable mount
points.

Occam's Razor would tell me to stop trying to do DIRMC support and to use
DISK, not FILE, spaces as the initial storage pools so my new server is as
much like the old server and then change one thing at a time to see where
the problem comes in.

While I get ready to do that, does anyone recognize this as a situation that
sounds like something they've been through? If so, is there a short-cut to
guide me to happier times and better configurations?

Thanks,
Nick