JDBC Driver for SQL/MP 3.0

jdbcPropfile Property
Sets the name of the Properties file that is used to pass alias names for SQL/MP tables. Specify the jdbcPropfile
property as:
string
The value can be any valid identifier. The default is null.
Troubleshooting
This subsection explains these subjects:
Tracing
No suitable driver error
Data truncation
Dangling statements
Tracing
Through the NonStop Server for Java, the JDBC trace facility enables you to trace the entry point of all the JDBC
methods called from the Java applications. For information on how to use this facility, see the NonStop Server for
Java Programmer's Reference.
No suitable driver Error
The error message No suitable driver means that the Java Virtual Machine (JVM) could not load the JDBC driver
that the program needs. For instructions on loading JDBC drivers, see Loading a Driver.
Data Truncation
Data truncation occurs without warning. To prevent data truncation, use Java data types that are large enough to hold
the SQL data items that are to be stored in them. (See Compatible Java and SQL/MP Data Types.)
Dangling Statements
SQL/MP drivers track all statements within a connection, but when an exception occurs, Java's garbage collection
feature might prevent a driver from immediately closing an open statement. A statement that is left dangling inside a
connection could cause unexpected results.
To avoid dangling statements:
Create statements outside try-catch blocks.
Close statements when they are no longer needed.
In this example, if executeQuery() throws an exception, the statement inside the try-catch block might be left
dangling:
try {
Statement stmt = conn.createStatement();