Thanks Richard! When doing further investigation, the TSM server's client, which backs up to our other TSM server, was backing up it's storage pool volumes which I had just created. I have since excluded those filesystems from it's backup and the memory has freed up.
******************************** Joni Moyer Highmark Storage Systems, Senior Systems Programmer Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] ******************************** "Richard Sims" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[email protected]> 12/14/2006 08:10 AM Please respond to "ADSM: Dist Stor Manager" <[email protected]> To [email protected] cc Subject Re: ANR999D shmcomm.c(1826) error Sounds like a client that is co-resident in the TSM server system, using the Shared Memory Communications method, as though the client is at a very different level than the server, so the server doesn't understand what the client is saying; else there may be problems in the shared memory area. I would start by looking for system changes which may have been effected, which precipitated the problem condition, as possibly the TSM client being boosted to a high 5.3 level relative to the 5.2 server. Richard Sims
