On HP I would tune the maxdsize to allow the ADSM process to obtain more
memory.  Run the process and what how much memory it uses.   Also, count the
files per directory on the client and see if any directory has a huge
amount.

Jeff Bach
Home Office Open Systems Engineering
Wal-Mart Stores, Inc.

WAL-MART CONFIDENTIAL


        -----Original Message-----
        From:   Cook, Dwight E [SMTP:cookde AT BP DOT COM]
        Sent:   Tuesday, June 12, 2001 9:02 AM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Solaris 3.7.2.0 tsm client file system limit ?

        I added additional file systems to blah, the TSM incremental died
and the
        process terminated. The logged error was "Program memory exhausted".
        Experimented with unmounting some file systems. In the range of 487
through
        489 file systems mounted, the TSM client fails similarly. Below
that, the
        incremental works. The total mounted now, with all new file systems
in
        place, is 495.

        Wasn't a shortage of memory (that we could see... this is a hugh
E10K)

        I checked the web site but couldn't find any hits on this...

        Is there a limit for the number of file systems this can process ? ?
?

        memoryeff yes
        didn't help

        one thing that did help was to use a domain statement to exclude
file
        systems we didn't want to deal with
        (normally we use exclude statements)

        Just wondering if anyone else has run into this

        Dwight


**********************************************************************
This email and any files transmitted with it are confidential
and intended solely for the individual or entity to
whom they are addressed.  If you have received this email
in error destroy it immediately.
**********************************************************************