Non-DB2 UDB for iSeries to DB2 UDB for iSeries blocking

 

Non-DB2^® UDB for iSeries™ to DB2 UDB for iSeries blocking will not occur under these conditions.

• The cursor is updatable (see note 1).

• The cursor is potentially updatable (see note 2).

• A precompile or bind option is used that caused the package default value to be force-single-row protocol.

  • For DB2 Universal Database™ for iSeries, there is no option to do this.

  • For DB2 Universal Database for VM, this is the NOBLOCK keyword on SQLPREP (the default).

  • For DB2 for OS/2^® (DB2/2), this is /K=NO on SQLPREP or SQLBIND.

• The row size is greater than approximately 0.5 multiplied by QRYBLKSIZ. The default and maximum QRYBLKSIZ values are as follows:

  Table 1. QRYBLKSIZ

  DB2 product	Default QRYBLKSIZ	Maximum QRYBLKSIZ in Version 8
  DB2 Universal Driver for SQLJ and JDBC	32 KB	32 KB
  DB2 Universal Database for z/OS®	32 KB	64 KB
  DB2 Universal Database for VM	8 KB	32 KB
  DB2 for Linux®, UNIX®, and Windows®	32 KB	64 KB

  In the latest level of Distributed Relational Database Architecture™ (DRDA^®), the system can choose to operate in a mode in which it is not limited to a fixed query block size in returning result sets.

• The cursor is defined as scrollable and a block cursor is not used in the application.

 

Parent topic:

Factors that affect blocking for DRDA