× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Title: JDBC Native Driver

Hi,

We have a very strange problem since we have installed Websphere 3 Advanced version on our as400 (v4r4).

We had some Java program using the native drive. Everything worked correctly.

We tested servlets with Websphere3. We then had a problem when getting a connexion.
The exception we received is:

 Getting the connection: jdbc:db2://gva4004/CHDATAR;                         
 com.ibm.db2.jdbc.app.DB2SQLException2: SQL system error.                    
       com/ibm/db2/jdbc/app/DB2ConnectionRuntimeImpl.connect(Ljava/lang/String
 ;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;III)I+80 (DB2Connectio
 nRuntimeImpl.java:100)                                                      
 

Since we have this problem nothing runs. It is not possible to get a connexion. We always receive
the same exception.

We used the following code:

                // Create a properties object for JDBC connection
                Properties jdbcProperties = new Properties();
       
                // Set the properties for the JDBC connection
                jdbcProperties.put("user", "HERVE");
                jdbcProperties.put("password","HERVE");
                jdbcProperties.put("naming", "system");
                jdbcProperties.put("errors", "full");
                jdbcProperties.put("date format", "iso");
                jdbcProperties.put("libraries", "CHOBJ1R,CHDATAR,CHOBJ1");

       
                // Load the AS400 Native JDBC driver into the JVM
                // This method automatically verifies the existence of the driver
                // and loads it into the JVM -- should not use DriverManager.registerDriver()
                System.out.println("Instanciating the native driver");
                Class.forName ("com.ibm.db2.jdbc.app.DB2Driver");

                // Connect using the properties object
                System.out.println("Getting the connection: jdbc:db2://gva4004/CHDATAR;");
                dbConnection = DriverManager.getConnection("jdbc:db2://gva4004/CHDATAR;" , jdbcProperties);


Is there something wrong in the properties?

It's like if the driver suddenly become unavailable.

Any idea?

Gilles



**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept for
the presence of computer viruses.
**********************************************************************

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.