<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: datasource in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/datasource/m-p/3629713#M817152</link>
    <description>hi,&lt;BR /&gt;&lt;BR /&gt;A data source name (DSN) is a data structure that contains the information about a specific database that an Open Database Connectivity (ODBC) driver needs in order to connect to it. Included in the DSN, which resides either in the registry or as a separate text file, is information such as the name, directory and driver of the database, and, depending on the type of DSN, the ID and password of the user. The developer creates a separate DSN for each database. To connect to a particular database, the developer specifies its DSN within a program. In contrast, DSN-less connections require that all the necessary information be specified within the program. &lt;BR /&gt;&lt;BR /&gt;There are three kinds of DSN: user DSNs (sometimes called machine DSNs); system DSNs; and file DSNs. User and system DSNs are specific to a particular computer, and store DSN information in the registry. A user DSN allows database access for a single user on a single computer, and a system DSN for any user of a particular computer. A file DSN contains the relevant information within a text file with a .DSN file extension, and can be shared by users of different computers who have the same drivers installed. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;regards.</description>
    <pubDate>Tue, 20 Sep 2005 00:06:20 GMT</pubDate>
    <dc:creator>Joseph Loo</dc:creator>
    <dc:date>2005-09-20T00:06:20Z</dc:date>
    <item>
      <title>datasource</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/datasource/m-p/3629710#M817149</link>
      <description>Dear Sirs;&lt;BR /&gt;&lt;BR /&gt;What is datasource name on unix ?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Shiv</description>
      <pubDate>Mon, 19 Sep 2005 23:31:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/datasource/m-p/3629710#M817149</guid>
      <dc:creator>Shivkumar</dc:creator>
      <dc:date>2005-09-19T23:31:52Z</dc:date>
    </item>
    <item>
      <title>Re: datasource</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/datasource/m-p/3629711#M817150</link>
      <description>Hi Shiv, &lt;BR /&gt;&lt;BR /&gt;It is same as DSN on Windows. In unix for MySQL, you will configure it in odbc.ini file. &lt;BR /&gt;&lt;BR /&gt;-Arun &lt;BR /&gt;</description>
      <pubDate>Mon, 19 Sep 2005 23:49:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/datasource/m-p/3629711#M817150</guid>
      <dc:creator>Arunvijai_4</dc:creator>
      <dc:date>2005-09-19T23:49:11Z</dc:date>
    </item>
    <item>
      <title>Re: datasource</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/datasource/m-p/3629712#M817151</link>
      <description>hi,&lt;BR /&gt;see:&lt;BR /&gt;&lt;A href="http://media.datadirect.com/download/docs/odbc/odbcref/unixenviron.html#wp588095" target="_blank"&gt;http://media.datadirect.com/download/docs/odbc/odbcref/unixenviron.html#wp588095&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;also note that, A typical datasource will contain the following:&lt;BR /&gt;Name: OracleDSThin&lt;BR /&gt;Data Source Class: com.evermind.sql.DriverManagerDataSource&lt;BR /&gt;Username: scott&lt;BR /&gt;Password: tiger&lt;BR /&gt;JDBC URL: jdbc:oracle:thin:@hostname:port:sid&lt;BR /&gt;   where: hostname = the hostname where the database is installed &lt;BR /&gt;                     (i.e. ias.acme.com).&lt;BR /&gt;          port = the database port number.&lt;BR /&gt;          sid = the database System Identifier (SID).&lt;BR /&gt;JDBC Driver: oracle.jdbc.driver.OracleDriver&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;yogeeraj</description>
      <pubDate>Tue, 20 Sep 2005 00:01:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/datasource/m-p/3629712#M817151</guid>
      <dc:creator>Yogeeraj_1</dc:creator>
      <dc:date>2005-09-20T00:01:40Z</dc:date>
    </item>
    <item>
      <title>Re: datasource</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/datasource/m-p/3629713#M817152</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;A data source name (DSN) is a data structure that contains the information about a specific database that an Open Database Connectivity (ODBC) driver needs in order to connect to it. Included in the DSN, which resides either in the registry or as a separate text file, is information such as the name, directory and driver of the database, and, depending on the type of DSN, the ID and password of the user. The developer creates a separate DSN for each database. To connect to a particular database, the developer specifies its DSN within a program. In contrast, DSN-less connections require that all the necessary information be specified within the program. &lt;BR /&gt;&lt;BR /&gt;There are three kinds of DSN: user DSNs (sometimes called machine DSNs); system DSNs; and file DSNs. User and system DSNs are specific to a particular computer, and store DSN information in the registry. A user DSN allows database access for a single user on a single computer, and a system DSN for any user of a particular computer. A file DSN contains the relevant information within a text file with a .DSN file extension, and can be shared by users of different computers who have the same drivers installed. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;regards.</description>
      <pubDate>Tue, 20 Sep 2005 00:06:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/datasource/m-p/3629713#M817152</guid>
      <dc:creator>Joseph Loo</dc:creator>
      <dc:date>2005-09-20T00:06:20Z</dc:date>
    </item>
    <item>
      <title>Re: datasource</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/datasource/m-p/3629714#M817153</link>
      <description>In the UNIX environment, there is no ODBC Administrator or Driver Manager. To configure an ODBC data source name (DSN) definition, you must edit the required system information, which is held in a plain text file called .odbc.ini (note that the name of this file starts with a period).&lt;BR /&gt;&lt;BR /&gt;Start of changeSet the ODBCINI environment variable to point to the file, specifying a full path and file name. If you do not set this variable, the path defaults to /var/mqsi/odbc, which is a directory created when WebSphere Business Integration Event Broker is installed. The file must have file permissions of mqm:mqbrkrs. End of change&lt;BR /&gt;&lt;BR /&gt;A sample template is provided as the file &lt;INSTALL_DIR&gt;/mqsi/merant/odbc.ini which contains examples of how to configure a DSN residing in each of the databases supported by WebSphere Business Integration Event Broker. The sample template files for the supported platforms are displayed below. They show the recommended configuration for the supported databases.&lt;BR /&gt;&lt;BR /&gt;The entries in the stanzas that you must configure to match your local requirements are shown in italics (descriptions of these entries are provided in ODBC.ini Parameters). You must retain all the entries shown, but you can remove a complete stanza if you do not require it for your configuration (for example, if you are using an Oracle database, you can remove the stanzas shown for DB2 and Sybase).&lt;BR /&gt;&lt;BR /&gt;Make a copy of the default file, set ODBCINI to point to this copy, and make any changes to the copied file rather than to the default.&lt;BR /&gt;&lt;BR /&gt;Ensure that the appropriate library search path environment variable (LD_LIBRARY_PATH on Solaris and Linux) is set to reflect the database products to be used. Refer to your database product documentation for more details.&lt;BR /&gt;Sample HP-UX:&lt;BR /&gt;&lt;BR /&gt;[ODBC Data Sources]&lt;BR /&gt;WBRKBKDB=IBM DB2 ODBC Driver&lt;BR /&gt;MYDB=IBM DB2 ODBC Driver&lt;BR /&gt;ORACLEDB=DataDirect 410 Oracle Driver&lt;BR /&gt;SYBASEDB=DataDirect 410 Sybase ASE Driver&lt;BR /&gt; &lt;BR /&gt;[WBRKBKDB]&lt;BR /&gt;Driver=/u/db2inst1/sqllib/lib/libdb2.sl&lt;BR /&gt;Description=WBRKBKDB DB2 ODBC Database&lt;BR /&gt;Database=WBRKBKDB&lt;BR /&gt; &lt;BR /&gt;[MYDB]&lt;BR /&gt;Driver=/u/db2inst1/sqllib/lib/libdb2.sl&lt;BR /&gt;Description=MYDB DB2 ODBC Database&lt;BR /&gt;Database=MYDB&lt;BR /&gt; &lt;BR /&gt;[ORACLEDB]&lt;BR /&gt;Driver=/opt/mqsi/merant/lib/UKor818.sl&lt;BR /&gt;Description=Oracle&lt;BR /&gt;ServerName=YourServerName&lt;BR /&gt;EnableDescribeParam=1&lt;BR /&gt;OptimizePrepare=1&lt;BR /&gt;WorkArounds=536870912&lt;BR /&gt;WorkArounds2=2&lt;BR /&gt; &lt;BR /&gt;[SYBASEDB]&lt;BR /&gt;Driver=/opt/mqsi/merant/lib/UKase18.sl&lt;BR /&gt;Description=Sybase12&lt;BR /&gt;Database=sybasedb&lt;BR /&gt;ServerName=YourServerName&lt;BR /&gt;WorkstationID=id&lt;BR /&gt;EnableDescribeParam=1&lt;BR /&gt;OptimizePrepare=1&lt;BR /&gt;SelectMethod=0&lt;BR /&gt;NetworkAddress=10.30.14.72,5000&lt;BR /&gt;SelectUserName=1 &lt;BR /&gt; &lt;BR /&gt;[ODBC]&lt;BR /&gt;Trace=0&lt;BR /&gt;TraceFile=/var/mqsi/odbc/odbctrace.out&lt;BR /&gt;TraceDll=/opt/mqsi/merant/lib/odbctrac.sl&lt;BR /&gt;InstallDir=/opt/mqsi/merant&lt;BR /&gt;&lt;BR /&gt;&lt;/INSTALL_DIR&gt;</description>
      <pubDate>Tue, 20 Sep 2005 01:35:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/datasource/m-p/3629714#M817153</guid>
      <dc:creator>morganelan</dc:creator>
      <dc:date>2005-09-20T01:35:50Z</dc:date>
    </item>
  </channel>
</rss>

