James (and other ADSM Exchange Agent customers),

Yes, APAR IX77929 is fixed and included in
ADSM Server PTF 3.1.1.3 (a.k.a. PTF #4).

Thanks,

Del Hoobler
ADSM Agent Development

===============================================================

>> I've upgraded to NT ADSM PTF4 (3.1.1.3) but did not see a list of fixes in
>> the reademes.  Has this been fixed in PTF4?
>>
>> Thanks,
>> James Louie
>> Nabisco

> On Monday, May 18, 1998 7:50 AM, Del Hoobler
> [mailto:hoobler AT US.IBM DOT COM]
> wrote:
>
> Hello,
>
> The workaround is documented in APAR IX77929.
> Here it is:
> -----------------------------------------------------------------
> ADSM Development has recently discovered an incompatibility
> between an ADSM V3 Server and an ADSMConnect Agent for
> Microsoft Exchange Server product and try-and-buy.
> When attempting to store multiple files whose total size
> exceeds 4 Gbytes within a single transaction the server
> will fail the transaction.  As a temporary work around
> perform the following command either from the server console
> command line or from an Administrative Command Line client:
>
>  update node node_name fileag=no
>
> IMPORTANT! The above command should ONLY be used for
>            MS Exchange Agent nodes.
>
> This incompatibility will be fixed in ADSM Server PTF 3.1.1.3.
> This PTF will be available for download from our
> ADSM Web site at
>
>  http://www.ibm.com/storage/adsm/adsercli.htm
>
> When the PTF becomes available, please install it and then
> perform the following command either from the server console
> command line or from an Administrative Command Line client:
>
>  update node node_name fileag=yes
>
> IMPORTANT!!  The above command MUST be performed in order
>              to ensure optimal storing of objects onto
>              the ADSM server.
> -----------------------------------------------------------------
>
> Del Hoobler
> ADSM Agent Development
> email: hoobler AT us.ibm DOT com