Start of change

DRDA enhancements for migration from DB2 Version 8

Enhancements to DRDA in DB2® 10 improve performance and security.

Some of the DRDA enhancements in DB2 10 include:

  • DB2 10 can use IPv6 only with DRDA.
  • DDF supports running the address space in AMODE 64, which relieves the storage constraints that exist in DB2 Version 8. The performance of TCP/IP has improved because the communications buffer is in 64-bit shared memory. This change means that you do not have to copy the buffer into your own address space or into the DBM1 address space. Reply communications are built and defined in 64-bit shared memory and can be pointed to instead of copied into your own address space or into the DBM1 address space.
  • DB2 10 can use trusted application servers with DRDA.
  • The performance of LOB retrieval is improved.
  • VTAM® independence allows you to set up a DB2 10 DDF to support TCP/IP and DRDA access.
  • DB2 10 has a new DRDA secure port, which allows use of SSL authentication methods. SSL authentication methods support secure communications between a client and DB2 10.
  • DB2 10 uses new DRDA capabilities to encode DRDA metadata in Unicode instead of EBCDIC, thereby eliminating the need for character conversion from EBCDIC to Unicode.
  • New monitoring capabilities in DRDA enable monitoring tools to track the execution of statements and to track the sequence of transactions in the distributed environment.
  • DB2 10 supports the following new DRDA user data type capabilities:
    • TIMESTAMP data (SQLTYPE 392/393) with extended timestamp precisions
    • TIMESTAMP WITH TIME ZONE data type (SQLTYPE 2448/2449)
  • DB2 10 implements new DRDA capabilities that support various new DB2 10 SQL functions. If new DRDA capabilities are required to support the new DB2 10 SQL functionality, then the requester system must be at the correct DRDA level to use the new SQL function. These new capabilities include support for the PREPARE ATTRIBUTES clause CONCENTRATE STATEMENTS WITH LITERALS.
  • DRDA always resolves aliases during a PREPARE of a dynamic SQL statement or binding of a static statement into a package at a remote location.
End of change