Kerry,

On the ADSM Scheduler increased the Minimum memory allocation so that it
equaled the Suggested Size (1500).  And I increased the Preferred Size to
2500.  The looping problem I was experienced was actually due to the fact
that my backup window was so small (checking every 10 minutes) that as soon
as the backup was complete it would start all over again.  The ADSM
administrators fixed that problem for me.  So with this fixed and the ADSM
Scheduler's memory adjsuted everything is working fine!!!

I hope this helps you in your troubleshooting.

Tom

P.S.  You may need to allocate more memory than I did if you have extensive
volumes.
>
>Yes yes yes! I am having the exact same problem. I have a call into IBM
>tech support and I'll let you know as soon as I hear something from them.
>
>Kerry Herschel
>kerry.herschel AT jpl.nasa DOT gov
>
>>Hi ADSM gurus!
>>
>>I am beta testing ADSM Scheduler & Backup v. 3.1.0.7 on a G3 (233MHZ) with
>>96 Meg of RAM w/Virtual Memory on running OS 8.5.1 (Extended Format).  As
>>soon as the Scheduler gets a connection with the ADSM server I get an error
>>message to "Memory Allocation Error.  Do you want to Abort the Program?"
>>
>>The default suggested size for the Scheduler is 1500, Minimum is 1000, and
>>Preferred is 1500.
>>The default suggested size for the Backup application is 1500, Minimum is
>>1000 and Preferred is 1500.
>>
>>I changed the Minimum on the Scheduler to 1500 and increased the preferred
>>to 2000.  I also increased the minimum on the Backup to 1500.  It would
>>then generate the" Memory Allocation" error after 5 minutes.  If I then
>>increase preferred on the Scheduler to 2500 I do not get an error message
>>but instead after about 12 minutes the program will start doing the compare
>>all over again and continue doing this loop.  I am going to experiment more
>>on my machine but it appears to me that the memory allocations is not
>>optimal and that the compare function uses a huge amount of memory.
>>
>>Has anyone with also experienced a similar error on Macs?  If so, how did
>>you resolve?
>>
>>Thanks!
>>
>>Tom Klingman
>>tgk5 AT cornell DOT edu
>>