Siebel Analytics Platform Installation and Configuration Guide > Configuring the Siebel Analytics Data Sources >

Configuring DB2 Connect Under UNIX

Analytics License: All licenses.

Operating System: z/OS or s/390 only.

Databases: IBM DB2 only.

This topic is part of the Roadmap for Configuring Siebel Analytics Platform.

IBM DB2 Connect does not support the option of automatically disconnecting when an application using it receives an interrupt request. If you are running a relational database that uses DB2 Connect workstation, then you must change the setting of the parameter INTERRUPT_ENABLED. This parameter must be changed on any Siebel Analytics Server machine if the database or any data source resides on IBM DB2 on a mainframe running z/OS or s/390 platforms.

NOTE:  If IBM DB2 is used, DB2 Connect must be installed on the Siebel Analytics Server machine. The version of DB2 Connect used must match the most recent DB2 instance, configured as a data source.

To configure the INTERRUPT_ENABLED parameter

1. Configure a database alias to be used as the native CLI Data Source Name. For example, create a new database entry using DB2 Configuration Assistant.
2. Using the database alias created and the name of the actual target DB2 database, set the INTERRUPT_ENABLED parameter using the following syntax:

   uncatalog dcs db local_dcsname
   catalog dcs db local_dcsname as target_dbname parms \",,INTERRUPT_ENABLED\"

   where:

   • local_dcsname represents the local name of the host or database (database alias name).
   • target_dbname represents the name of database on the host or database system.

     NOTE:  Be sure to use backslashes to pass the quote marks as part of the string.

     The following example uses an OS390 DB2 instance:

     uncatalog dcs db DB2_390
     catalog dcs db DB2_390 as Q10B parms \",,INTERRUPT_ENABLED,,,,,\"
     catalog database DB2_390 as DB2_390 at node NDE1EF20 authentication dcs