|
Implementing Siebel Business Applications on DB2 UDB for z/OS > Preparing for Implementation on the DB2 Host > About Setting Up the DB2 Subsystem >
DSNZPARM Parameter Settings for Siebel Applications
To run your Siebel Business applications, you must set the values of some of the DSNZPARM parameters to required settings; other DSNZPARM parameter values are recommended to improve the performance of your Siebel Business applications. This topic describes both the recommended and the required DSNZPARM parameter settings. NOTE: Use the IBM default values for any DSNZPARMs for which recommended or required values are not listed in this topic. The IBM default values for any DSNZPARMs not listed in this topic are the most appropriate values for running Siebel 8.0.
You can configure some DSNZPARM parameters online, but to configure other parameters, you must shut down DB2. For information on the parameters that can be updated online, refer to the vendor documentation on the IBM Web site. Required DSNZPARM Parameter Settings
The DSNZPARM values that are required by Siebel Business Applications are listed as follows:
For a description of the required DSNZPARM parameters, see Table 6. Recommended DSNZPARM Parameter Settings
For optimum operation of Siebel Business Applications, use the recommended settings for the DSNZPARM parameters in Table 6. This table also lists the required DSNZPARM parameter settings.
Table 6. Database Manager Configuration Parameters (DSNZPARM)
|
|
|
|
DSN6SPRM |
CACHEDYN
|
Turns on dynamic statement caching. |
YES
|
Required |
CDSSRDEF
|
Turns off parallelism for dynamic statements. |
1
|
Required |
CONTSTOR
|
Compresses storage on a regular basis. Set this value to YES if DBM1 storage is an issue. |
YES
|
Recommended |
EVALUNC
|
Allows predicate evaluation on uncommitted data. |
YES
|
Recommended |
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. |
0 |
Recommended |
MINSTOR
|
Compresses storage on a regular basis. Set this value to YES if DBM1 storage is an issue. |
YES
|
Recommended |
NPGTHRSH
|
Allows small tables to use indexes. |
10
|
Recommended |
NUMLKUS
|
Number of locks for each user. It is recommended that the DBA monitors and sets this value. If you experience persistent locking problems, consider setting the parameter to 0 (unlimited number of locks). |
100,000
|
Recommended |
PARTKEYU
|
Allows update of partitioning keys. |
YES
|
Required if using partitioning |
RETVLCFK
|
Allows index-only access of varying-length characters. Set this value to NO due to padding. |
NO
|
Required |
DSN6SYSP |
CHKFREQ
|
Avoids frequent checkpoints in a high-update environment. It is recommended that DBAs monitor and set this value for between 10 and 20 minutes. |
500,000 |
Recommended |
CONDBAT
|
Maximum number of concurrent remote connections. It is recommended that the DBA monitors and set this value. |
10,000
|
Recommended |
EXTSEC
|
Allows DB2 Connect to receive more complete error messages. Allows you to change passwords from DB2 Connect. |
YES
|
Required |
MAXDBAT
|
Maximum number of database threads (DBAT). It is recommended that the DBA monitors and set this value. |
500
|
Recommended |
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. |
YES |
Recommended |
DSN6FAC |
CMTSTAT
|
Allows a greater number of remote threads without affecting storage. Enables DDF thread pooling. |
INACTIVE
|
Recommended |
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. |
120
|
Recommended |
POOLINAC
|
Number of seconds an inactive thread remains in the DDF pool. The DBA should monitor and set this value. |
120
|
Recommended |
PADIX Considerations
The PADIX parameter 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. The IBM default value for this parameter is YES. If you do not want new indexes to be padded by default, you must specify NO for this parameter. In some Siebel implementations, setting the PADIX parameter to NO has been found to lead to performance improvements and savings in disk space; it also allows for index-only access to data. If you do set PADIX to NO, ensure that you carefully monitor the impact of doing so in your environment. 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 might 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 might 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 8.0.
| 
