|
Implementing Siebel eBusiness Applications on DB2 UDB for z/OS and OS/390 > Preparing for Implementation on the DB2 Host > Setting Up the Subsystem >
DSNZPARM Parameters for Setting Up the Subsystem
For optimum operation of Siebel eBusiness Applications, use the recommended settings in Table 7 to configure the parameters within DSNZPARM. The following parameter values are required by Siebel eBusiness Applications: CACHEDYN=YES
CDSSRDEF=1
EXTSEC=YES
MXTBJOIN=128
PARTKEYU=YES
RETVLCFK=NO
OPTCCOS1=ON
OPTSUBQ1=YES
NOTE: PARTKEYU is only required if partitioning is used with the Siebel Schema.
From the Siebel Systems standpoint, there are three categories of DSNZPARMs: required, recommended, and the remaining DSNZPARMs. Generally it is recommended that the default values for the DSNZPARMs, which are not explicitly listed here, could be modified by your DBA if it benefits your environment. Modifications of such DSNZPARM values should be closely monitored by your DBA to assess the impact on your DB2 subsystem. You can configure some parameters online, but other parameters require you to shut down DB2 to configure them. For information on which parameters can be updated online, refer to the vendor documentation on the IBM Web site.
Table 7. Database Manager Configuration Parameters (DSNZPARM)
|
|
|
DSN6SPRM |
CACHEDYN
|
Turns on dynamic statement caching. This is a required value for Siebel eBusiness Applications. |
YES (required)
|
CDSSRDEF
|
Turns off parallelism for dynamic statements. This is a required value for Siebel eBusiness Applications. |
1 (required)
|
CONTSTOR
|
Compresses storage on a regular basis. Set this value to YES if DBM1 storage is an issue. |
YES
|
EVALUNC
|
Allows predicate evaluation on uncommitted data. This is a recommended Siebel eBusiness Applications value. |
YES
|
IRLMRWT
|
Time in seconds before a time-out occurs. This is a recommended Siebel eBusiness Applications value. |
300
|
MINSTOR
|
Compresses storage on a regular basis. Set this value to YES if DBM1 storage is an issue. |
YES
|
MXTBJOIN
|
Sets the maximum number of tables in a join. The default (15) is not sufficient for Siebel eBusiness Applications. NOTE: Unlike other DSNZPARMs that cannot be updated through the installation panels, this parameter must be updated manually.
|
128 (required)
|
NPGTHRSH
|
Allows small tables to use indexes. This is a recommended Siebel eBusiness Applications value. |
10
|
NUMLKUS
|
Number of locks per user. This value should be monitored and set by the DBA. If you experience persistent locking problems, consider setting the parameter to 0 (unlimited number of locks). |
100,000
|
OPTCCOS1
|
Allows multiple predicate optimizer enhancements. |
ON (required)
|
OPTSUBQ1
|
Allows non-correlated subquery optimizer enhancements. |
YES (required)
|
PARTKEYU
|
Allows update of partitioning keys. This is a required Siebel eBusiness Applications value. |
YES (required)
|
RETVLCFK
|
Allows index-only access of varying-length characters. This value should be set to NO due to padding. This is a recommended Siebel eBusiness Applications value. |
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. |
500,000 (or 15 when FREQUENCY TYPE = MINUTES)
|
CONDBAT
|
Maximum number of concurrent remote connections. The DBA should monitor and set this value. |
10,000
|
EXTSEC
|
Allows DB2 Connect to receive more complete error messages. Allows the changing of passwords from DB2 Connect. This is a required Siebel eBusiness Applications value. |
YES (required)
|
MAXDBAT
|
Maximum number of database threads (DBAT). The DBA should monitor and set this value. |
500
|
DSN6FAC |
CMTSTAT
|
Allows a greater number of remote threads without affecting storage. Enables DDF thread pooling. This is a recommended Siebel eBusiness Applications value. |
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. |
600
|
POOLINAC
|
Number of seconds an inactive thread remains in the DDF pool. The DBA should monitor and set this value. |
120
|
NUMLKUS Considerations
If a resource unavailable error occurs, because NUMLKUS has been exceeded while performing a Siebel operation, do one of the following:
- Increase the
NUMLKLUS parameter value.
- Issue COMMIT statements more frequently, and reduce the number of update and insert operations while using Siebel eBusiness Applications.
NOTE: The NUMLKLUS 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.
Should EIM fail due to NUMLKUS being exceeded, do one of the following:
- 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.) This value must be monitored in your installation to be sure that it is set properly. The IDTHTOIN will time out active threads that have been idle (no network traffic) for more than 600 seconds. (This is the recommended value; your value may differ.) The events that may occur when an active thread is timed out include:
- The thread is not returned to the DB2 Connect thread pool for re-use.
- When the client or component tries to re-use that DB2 Connect thread, the thread will not be available. The client or component must be able to issue a full connect in order to continue processing the work.
- If the component or client is not capable of issuing a full connect, the client will receive a SQL30081N SQLCODE. An example of an error message you may receive if the component or client cannot reconnect are:
[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 for specifying the IDTHTOIN is that connection pooling on the ODBC driver must be turned off. Using connection pooling with the driver is not certified with Siebel 7.
| 
