Client requirements for execution
m
option
to 1
. The following dbservername parameter
specifies a multiplexed connection to the personnel database
server: Servername | nettype | hostname | servicename | options |
---|---|---|---|---|
personnel | onsoctcp | corp | prsnl_ol | m=1 |
Setting the multiplexing option to zero (m
= 0
), which is the default, disables multiplexing for the
specified database server.
To use multiplexed connections for any application that was compiled before version 9.13 of HCL OneDB™ ESQL/C for UNIX™ or version 9.21 of HCL OneDB ESQL/C for Windows™, you must relink it. Applications that you compiled before these versions of HCL OneDB ESQL/C can connect to a multiplexing database server, however. The database server establishes a non-multiplexed connection in this case.
- Use different sqlhosts information.
- Use a dbserver alias in the sqlhosts file
that does not specify the multiplexing option. For example, you could
use the following configuration:
Servername Nettype Host name Servicename Options personnel onsoctcp corp prsnl_01 m=1 personnel_nomux onsoctcp corp prsnl_02
Any multithreaded application connecting to the personnel server uses the servername personnel_nomux while single-threaded applications can continue to use the servername personnel.