This is a known problem with 3.1.0.7 (ref: APAR IC24268). It doesn't affect
the functionality of the client but does put bogus messages in dsmerror.log
every time the client contacts the server.

At 12:32 8/26/99 , you wrote:
>>From: Dustin Cavanaugh <dcavanaugh AT UCSD DOT EDU>
>>Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>>To: ADSM-L AT VM.MARIST DOT EDU
>>Subject: Re: TCP window size not supported
>>Date: Thu, 26 Aug 1999 09:10:00 -0700
>>
>>No size is recommended. Please see my other response this day.
>>
>>At 08:38 8/26/99 , you wrote:
>> >Question....what is the recommended TCP window size?
>> >
>> >=======================================
>> >
>> >-----Original Message-----
>> >From: Ray Schafer [mailto:schafer AT TKG DOT COM]
>> >Sent: Thursday, August 26, 1999 7:14 AM
>> >To: ADSM-L AT VM.MARIST DOT EDU
>> >Subject: Re: TCP window size not supported
>> >
>> >
>> >Richard Sims wrote:
>> >
>> >> >Docs call for 1-2048.
>> >>
>> >> Hmmm.  The latest online manual for Unix B/A Clients says
>> >> "For Solaris the maximum value is 1024.", otherwise the
>> >> maximum is 2048.  Well, that's one way to move people to
>> >> RS/6000 boxes.
>> >
>> >I beleive that it's purley an operating system limitation. Solaris can't
>> >do a TCP window size as large as AIX can.  I find it surprising,
>> >actually, that Sun hasn't been more aggresive in handling  fast
>> >networks. (Full Duplex 100 MB Ethernet is lame, TCP Receive space is
>> >small).
>> >
>> >
>> >--
>> >Ray Schafer                   | schafer AT tkg DOT com
>> >The Kernel Group              | Distributed Systems Management
>> >http://www.tkg.com
>
>Its really a system limitation. Try to allocate such a big communications
>buffer from the OS, and you will get an error message. But only on Solaris
>not on the other client platforms.
>Thats why we limited the solaris client.
>
>
>______________________________________________________
>Get Your Private, Free Email at http://www.hotmail.com