Frederic,

We had the same problem here with Solaris.  Support suggested just using TCP/IP 
for the comm method, that's what we did, and it hasn't been a problem since.  
I'd be interested if anyone on this list knows a reason why that might have 
been a bad idea.  ( Support also suggested that the problem would be repaired 
in the 4.2.X series of TSM Server.

Ed Anderson - Unix / Backup Admin



>>> Frederic.Jager AT DEXIA-BIL DOT COM 10/09/01 04:09PM >>>
We have just experienced a shared memory problem on our TSM v4.1.4.0 server.
It consists of a 4 way RS6000 high node with 1GB RAM attached to a 3494
library with six 3590 drives. The error is as follows :

10/09/01   19:15:00  ANR0402I Session 70361 started for administrator ADMIN

                      (AIX) (ShMem).

10/09/01   19:15:00  ANR9999D shmcomm.c(1900): No memory available in shared

                      memory block

10/09/01   19:15:00  ANR9999D shmcomm.c(1618): Error obtaining storage for
data
                      buffers

10/09/01   19:15:00  ANR8294W Shared Memory session unable to initialize.

Any idea or comment on that problem ?

Thanks,
----------------------------------------------------------------------------
-
---------------------------------
---------------------------------
JAGER Frederic - Unix Systems / Storage
JAGER Frederic - Unix Systems / Storage



---------------------
An electronic message is not binding on its sender.
An electronic message is not binding on its sender.
Any message referring to a binding engagement must be confirmed in writing and 
duly signed.
---------------------
=======================================================================