JR20763: SLOW CONNECT TIME FROM A DB2 UDB V8.1 FP7A CLIENT TO A Z/OS

DB2 UDB Version 8.1 FixPak 16 (also known as Version 8.2 FixPak 9 )

APAR status

• Closed as program error.

Error description

• Slow connect times might be experienced when connecting from a
  DB2 UDB Version 8.1 FixPak 7a Windows client in a Windows Domain
  environment to either a DB2 UDB Version 8 server or a z/OS
  server. This problem is caused by a call to the Windows API
  LookupAccountName on the client, which is done to determine the
  user ID on the connect statement. In certain circumstances, this
  call can take a long time to complete, because an entire domain
  might be searched. In FixPaks 7a and 8, this is done even if
  authentication is set to SERVER. In previous FixPaks, this API
  would only be called if authentication was set to CLIENT or not
  specified. Starting in FixPak 9, the Windows API will again only
  be called when authentication is set to CLIENT or not specified.
  

Local fix

Problem summary

• Users Affected: Windows clients running DB2 UDB Version 8.1 FP7
  and FP8
  
  Problem Description: Slow connections from V8 fp7a client to
   z/OS or LUW servers due to call to Windows API on client even
   if authentication is set to server.
  
  Problem Summary: Slow connections from V8 fp7a client to z/OS or
   LUW servers due to call to Windows API on client even if
   authentication is set to server.
  

Problem conclusion

• The complete fix (JR20763) for this problem first appears in DB2
  UDB Version 8.1 FixPak 9.
  The fix needs to be applied to the DB2 Client machine.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• ENG_SQEX
  

Fix information

• Fixed component name

  DB2 CPE WINDOWS

• Fixed component ID

  5724B5601

Applicable component levels

• R820 PSN

     UP