The DBSERVERALIASES parameter lets you assign additional dbservernames to the same database server. The maximum number of aliases is 32. Figure 8 shows entries in an ONCONFIG configuration file that assign three dbservernames to the same database server instance.
DBSERVERNAME sockets_srvr DBSERVERALIASES ipx_srvr,shm_srvr
The sqlhosts entries associated with the dbservernames from Figure 8 could include those shown in Figure 9. Because each dbservername has a corresponding entry in the sqlhosts file or SQLHOSTS registry key, you can associate multiple connection types with one database server.
shm_srvr onipcshm my_host my_shm sockets_srvr onsoctcp my_host port1 ipx_srvr ontlispx nw_file_server ipx_srvr
Using the sqlhosts file shown in Figure 9, a client application uses the following statement to connect to the database server using shared-memory communication:
CONNECT TO '@shm_srvr'
A client application can initiate a TCP/IP sockets connection to the same database server using the following statement:
CONNECT TO '@sockets_srvr'
DBSERVERALIASES must begin with a lowercase letter and can contain other lowercase letters, digits, and underscores. DBSERVERALIASES should not include uppercase characters, a field delimiter (space or tab), or a new line character. Other characters from the basic ASCII code set are not necessarily reliable. For example, a hyphen or minus sign can create problems and a colon might not work reliably. The @ character is reserved to separate the database from the server (as in dbase@server).
In the examples above, the @shm_srvr statement connects to an unidentified database at that server; alternatively, you could connect to dbase1@shm_srvr.
Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]