Implementing Siebel Business Applications on DB2 UDB for z/OS > Preparing for Implementation on the DB2 Host > Setting Up the DB2 Subsystem >

Recommended DSNZPARM Parameter Settings


For optimum operation of Siebel Business Applications, use the recommended settings in Table 7 to configure the parameters within DSNZPARM.

Table 7. Database Manager Configuration Parameters (DSNZPARM)
Parameter
Explanation
Applicable DB2 Version
Recommended Setting

DSN6SPRM

CACHEDYN

Turns on dynamic statement caching.

v7
v8

YES (required)

CDSSRDEF

Turns off parallelism for dynamic statements.

v7
v8

1 (required)

CONTSTOR

Compresses storage on a regular basis. Set this value to YES if DBM1 storage is an issue.

v7
v8

YES

EVALUNC

Allows predicate evaluation on uncommitted data.

v7
v8

YES

IRLMRWT

Time in seconds before a time-out occurs.

v7

300

MAXKEEPD

The total number of prepared, dynamic SQL statements that can be saved past a commit point by applications that run with the KEEPDYNAMIC(YES) bind option.

v7
v8

0

MINSTOR

Compresses storage on a regular basis. Set this value to YES if DBM1 storage is an issue.

v7
v8

YES

MXTBJOIN

Sets the maximum number of tables in a join. The default (15) is not sufficient for Siebel Business Applications.

NOTE:  Unlike other DSNZPARMs that cannot be updated through the installation panels, this parameter must be updated manually.

v7
v8 (default)

128 (required)

 

NPGTHRSH

Allows small tables to use indexes.

v7
v8

10

NUMLKUS

Number of locks per user. The DBA should monitor and set this value.

If you experience persistent locking problems, consider setting the parameter to 0 (unlimited number of locks).

v7
v8

 

100,000

OPTCCOS1

Allows multiple, predicate optimizer enhancements.

v7
v8 (default)

ON (required)

OPTSUBQ1

Allows noncorrelated, subquery optimizer enhancements.

v7
v8

YES

PARTKEYU

Allows update of partitioning keys.

v7
v8

YES (required)

RETVLCFK

Allows index-only access of varying-length characters. This value should be set to NO due to padding.

v7
v8

NO (required)

DSN6SYSP

CHKFREQ

Avoids frequent checkpoints in a high-update environment. DBAs should monitor and set this value for between 10 and 20 minutes.

v7
v8

20

CONDBAT

Maximum number of concurrent remote connections. The DBA should monitor and set this value.

v7
v8 (default)

10,000

EXTSEC

Allows DB2 Connect to receive more complete error messages. Allows you to change passwords from DB2 Connect.

v7
v8 (default)

 

YES (required)

MAXDBAT

Maximum number of database threads (DBAT). The DBA should monitor and set this value.

v7
v8

500

MGEXTSZ

Specifies whether or not the secondary extent allocations for DB2-managed data sets are sized according to a sliding scale that optimizes the likelihood of reaching the maximum data set size before secondary extents are exhausted. If you specify YES, DB2 automatically optimizes the secondary extent allocations.

v8

NO

DSN6FAC

CMTSTAT

Allows a greater number of remote threads without affecting storage. Enables DDF thread pooling.

v7
v8 (default)

 

INACTIVE

IDTHTOIN

Number of seconds before an idle thread is canceled. Prevents long-running threads from holding resources. The DBA should monitor and set this value.

v7
v8

 

600

POOLINAC

Number of seconds an inactive thread remains in the DDF pool. The DBA should monitor and set this value.

v7
v8 (default)

120

PADIX

Determines whether or not new indexes are padded by default. If you specify YES, a new index is padded unless the NOT PADDED option is specified on the CREATE INDEX statement.

v8

YES

NUMLKUS Considerations

If a resource unavailable error occurs because NUMLKUS has been exceeded while performing a Siebel operation, increase the NUMLKUS parameter value.

NOTE:  The NUMLKUS parameter value is important when running large EIM batches and during the use of Siebel Remote for the initial database extract. If this value is too small, EIM runs or the database extract can fail.

If EIM fails because the value specified for the NUMLKUS parameter has been exceeded, take one of the following actions:

  • Reduce the size of the batch.
  • Increase the value of NUMLKUS.

IDTHTOIN Considerations

The IDTHTOIN DSNZPARM recommended setting is 600. (The parameter is specified in seconds.) Monitor this value in your installation to ensure that it is set properly. The IDTHTOIN parameter time- outs active threads that have been idle (no network traffic) for more than 600 seconds. (This time is the recommended value; your value may differ.)

The events that can occur when an active thread times out include:

  • The thread is not returned to the DB2 Connect thread pool for reuse.
  • When the client or component tries to reuse the DB2 Connect thread, the thread is not available. The client or component has to issue a full Connect to continue processing the work.
  • If the component or client cannot issue a full Connect, the client receives a SQL30081N SQLCODE. An example of an error message you may receive if the component or client cannot reconnect is:

    [IBM][CLI Driver][DB2] SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "". Communication function detecting the error: "recv". Protocol specific error code(s): "*", "*", "0". SQLSTATE=08001

Another consideration to bear in mind when specifying a value for the IDTHTOIN parameter is that connection pooling on the ODBC driver must be turned off. Using connection pooling with the driver is not certified with Siebel 7.x.

Implementing Siebel Business Applications on DB2 UDB for z/OS