Scalable Database Server, HiRDB Version 8 UAP Development Guide

[Contents][Index][Back][Next]

6.7.2 Registering an environment variable group in a Windows environment (registry registration)

Use the tool for registering HiRDB client environment variables to register environment variables in the registry.

To use the tool for registering HiRDB client environment variables, execute xxxx\UTL\pdcltadm.exe (xxxx is %PDDIR%\client in the HiRDB server and the HiRDB client installation directory in the HiRDB client).

The rest of this section describes procedures for registering environment variables in the registry with the tool for registering HiRDB client environment variables.

In an OLE DB connection, the environment variables registered with the tool for registering HiRDB client environment variables have priority over the user environment variables and the specifications in HIRDB.INI.

Client environment definitions set using this method become invalid when the Type4 JDBC driver is used. Client environment definitions that begin with PDJDB become invalid if this method is used.

Organization of this subsection
(1) Starting the tool for registering HiRDB client environment variables
(2) Registering an environment variable group
(3) Changing the settings of an environment variable group
(4) Checking the HiRDB connection with a registered environment variable group
(5) Deleting an environment variable group
(6) Setting an OLE DB provider trace

(1) Starting the tool for registering HiRDB client environment variables

Execute xxxx\UTL\pdcltadm.exe. The Tool for Registering HiRDB Client Variables dialog box is displayed.

[Figure]

Explanation

User Group
Select this item to add, delete, or modify an environment variable group for a user. This information is registered in HKEY_CURRENT_USER.

System Group
Select this item to add, delete, or modify an environment variable group for a computer. This information is registered in HKEY_LOCAL_MACHINE.

Select either User Group or System Group, and click the Add button.

Note
When a UAP that uses an X/Open-compliant API under OLTP is used as a client, select System Group so that you can use the tool for registering HiRDB client environment variables to register the environment variables group whose name is specified in the open character string. For details about open character strings, see the HiRDB Version 8 Installation and Design Guide.

(2) Registering an environment variable group

The HiRDB Client Environment Variable Setup dialog box is displayed.

[Figure]

Explanation

Group Name
Specify the group name with up to 30 characters.

Environment variable fields
Specify a setting for each environment variable. For details about each environment variable, see 6.6.4 Environment definition information.

After completing the setup, click the OK button. When the OK button is clicked, the client environment variable settings are registered in the registry, and the Tool for Registering HiRDB Client Variables dialog box is displayed again.

Click the Cancel button to cancel the client environment variable settings and return to the Tool for Registering HiRDB Client Variables dialog box.

(3) Changing the settings of an environment variable group

After one or more environment variable groups are registered, a list of the registered environment variable group names is displayed, as shown in the next dialog box.

[Figure]

When an environment variable group name in the list is selected, the Delete, Configure, and Test buttons become enabled and can be clicked. Click the Configure button or double-click an environment variable group name in the list. The following dialog box is displayed:

[Figure]

Change the environment variable settings, and click the OK button. When the OK button is clicked, the new client environment variable settings are registered in the registry, and the Tool for Registering HiRDB Client Variables dialog box is displayed again.

Click the Cancel button to cancel the client environment variable settings and return to the Tool for Registering HiRDB Client Variables dialog box.

(4) Checking the HiRDB connection with a registered environment variable group

You can use a registered environment variable group to check whether a connection to HiRDB can be established for that group.

From the environment variable group name list in the Tool for Registering HiRDB Client Variables dialog box, select the environment variable group name for which connection to HiRDB is to be checked, and click the Connect button. The following dialog box is displayed:

[Figure]

Click Yes.

If connection to HiRDB is successful, the following dialog box is displayed:

[Figure]

If connection to HiRDB fails, the following dialog box is displayed. If the error is due to the contents of an environment variable, change the settings of the environment variable group.

[Figure]

(5) Deleting an environment variable group

From the environment variable group name list in the Tool for Registering HiRDB Client Variables dialog box, select the environment variable group name to be deleted, and click the Delete button.

The following dialog box is displayed:

[Figure]

(6) Setting an OLE DB provider trace

The OLE DB provider trace is for troubleshooting only. Do not set this trace for any other investigation. Note that when a trace is performed, the performance of other operations may drop dramatically.

To set an OLE DB provider trace when the HiRDB client is connected to an OLE DB, open the Tool for Registering HiRDB Client Variables dialog box, and click the OLE DB Trace button. The following dialog box is displayed:

[Figure]

To perform a trace, select TRACE ON and then click the OK button. Note that the trace continues until you select TRACE OFF and click the OK button.

For the log file name, always specify the absolute path name of the file.

For the data size, specify the output size, in bytes, of the void*-type data dump.

(a) Environment variables that become invalid when the multi-connection facility is used

When the multi-connection facility is used, the following environment variables cannot be set for each connection destination. These environment variables become invalid even if they are registered to a normal file or registry and specified in each connection destination.