MX 2.x)

mploc Property

The property mploc specifies the Guardian location in which SQL tables are created. The format for mploc is:

[\node].$volume.subvolume

Java applications using the JDBC/MX driver can specify mploc by using the system property mploc with the -D option

in the command line.

-Djdbcmx.mploc=mploc

For example with the DriverManager object, in the OSS environment, specify the mploc property in either of the

following forms:

-Djdbcmx.mploc=[\\node.]\$volume.subvolume

-Djdbcmx.mploc='[\node.]$volume.subvolume'

For more information, see the SQL/MX Reference Manual.

maxStatements Property

Sets the total number of PreparedStatement objects that the connection pool should cache. This total includes both

free objects and objects in use. Specify the maxStatements property as:

int

The integer can be 0 through 2147483647. Any negative value is treated like 0. The default is 0, which disables

statement pooling. HP recommends that you enable statement pooling for your JDBC applications, because this

pooling can dramatically help the performance of many applications.

minPoolSize Property

Limits the number of physical connections that can be in the free connection pool. Specify the minPoolSize property

as:

int

The integer can be 0 through 2147483647, but less than maxPoolSize. The default is 0. Any negative value is treated

like 0. Any value greater than maxPoolSize is changed to the maxPoolSize value. This value is ignored when

maxPoolSize is -1. The value determines connection pool use as follows:

When the number of physical connections in the free pool reaches the minPoolSize value, the JDBC/MX driver

closes subsequent connections by physically closing them—not by adding them to the free pool.

0 means the connections are not physically closed; the connections are always added to the free pool when the

connection is closed.

maxPoolSize Property

Sets the maximum number of physical connections that the pool can contain. These connections include both free

connections and connections in use. When the maximum number of physical connections is reached, the JDBC/MX