ADSM-L

Re: apar's where are they located

1998-04-01 11:11:45
Subject: Re: apar's where are they located
From: Larry Sanders <sanders AT SHOWME.MISSOURI DOT EDU>
Date: Wed, 1 Apr 1998 10:11:45 -0600
On Tue, 31 Mar 1998, Doug Thorneycroft wrote:

> The following is part of the readme for ptf 3 (Windows) ip21295
>
> Important: Set LARGECOMMBuffers=no in the options file.  See apar
> IC20486
>            for more information.
>
> Does anyone know where the apar's are listed?

You can search for APARs if you have an IBMLINK account.  Here is the text
for APAR IC20486:

------------------------------------------------------------------------
Item IC20486
Item IC20486

  APAR Identifier ...... IC20486       Last Changed..98/03/26
  ADSM CLIENT LARGECOMMBUFFER OPTION CAN CAUSE BACKUP PERFORMANCE
  DEGRADATION ON SOME V3 CLIENTS, SUCH AS WINDOWS NT AND SOLARIS

  Symptom ...... IN INFO              Status ........... OPEN
  Severity ................... 2      Date Closed .........
  Component .......... 565511902      Duplicate of ........
  Reported Release ......... 31D      Fixed Release ............
  Component Name ADSM CLIENTS         Special Notice
  Current Target Date ..98/07/26      Flags
  SCP ................... PC/DOS
  Platform ............ DOS

  Status Detail: Not Available

  PE PTF List:

  PTF List:


  Parent APAR:
  Child APAR list:


  ERROR DESCRIPTION:
  While the LARGECOMMBUFFER option improves backup performance
  on certain operating systems that can take advantage of the
  larger buffers, certain other operating systems such as Solaris,
  Windows NT, and OS/2 do not have large enough read-ahead buffers
  or tunable parameters to take advantage of the large buffers.
  In fact, because of the operating system restrictions, backup
  performance can actually decrease when LARGECOMMBUFFER is YES.

  On Windows NT, LARGECOMMBUFFER default is YES. Set it to NO.
  On AIX, LARGECOMMBUFFER default is YES, and as long as VMTUNE
     is used to tune performance, the value can remain YES.
  On NetWare, LARGECOMMBUFFER default is YES and should remain YES
  On OS/2 and Solaris, LARGECOMMBUFFER default is NO and should
     remain NO.
  On the other Version 3 PTF 3 clients, the default is NO.
  The value can be changed to YES if the operating system takes
  advantage of the larger buffers.

  ADSM should tune the LARGECOMMBUFFER value more closely to what
  the client's operating system can take advantage of, where that
  is known.


  LOCAL FIX:
  Set LARGECOMMBUFFER to NO.

Set LARGECOMMBUFFER to NO.



----------------------------------------------------------------------------
Larry Sanders                         Email:  cclrs AT showme.missouri DOT edu
Larry Sanders                         Email:  cclrs AT showme.missouri DOT edu
Information and Access                Phone:  573 882-6002
     Technology Services
University of Missouri - Columbia
----------------------------------------------------------------------------
=========================================================================
<Prev in Thread] Current Thread [Next in Thread>
  • Re: apar's where are they located, Larry Sanders <=