Restriction: This topic applies to Windows environments only.
You can use the Gateway Profile Utility to:
- Define remote locations to XDB Link so that XDB client applications can access data in those locations.
- Configure the settings XDB Link needs to translate data correctly and control client conversations.
If you have installed XDB Link on an XDB Server as part of a gateway configuration, you must:
- Have super-user privileges on the XDB Server where XDB Link is installed.
- Run the Gateway Profile Utility on the machine where XDB Link is installed.
If you need additional information about the Gateway Profile Utility while doing this procedure, see the topic Gateway Profile Utility.
To configure XDB Link using the Gateway Profile Utility
- If you are using XDB Link in a gateway configuration, start the XDB Server on the machine where XDB Link is installed.
- Start the Options utility. (If you are using the gateway configuration, do this at the machine where XDB Link is installed).
- When the Options window opens, set the following values on the Connect page:
| If you are using ... |
Make these selections... |
| Gateway configuration |
In the Server Name field, select the name of the XDB Server on which XDB Link is installed. In the Location field, select the SYSTEM location.
In the Protocol field, select the Local protocol.
|
| Direct-connect configuration |
In the Protocol field, select DRDA. |
- Click OK to save your settings and close Options.
- Start the Gateway Profile Utility by selecting its icon in the XDB program group or folder. (If you are using the gateway configuration, do this at the machine where XDB Link is installed.) If prompted for a user ID, enter an ID that has super-user or SYSADM privileges.
- When the Gateway Profile Utility window opens, click Register to display the Location Configuration dialog box. You use this dialog box to add the remote database to XDB Link.
- In the Location Name field, type the name of the remote database from row B9 in your DB2 worksheet. This is the DB2 location name used by the DDF facility.
Note:
A common mistake is to specify theDB2 APPLID in VTAM or the 4-character SUBSYSTEM name for DB2. These names are usually NOT the same name as the DB2 location name (although your DB2 systems programmer may have decided that all three of these names should be the same.) See your DB2 systems programmer to determine the DB2 location name.
- Complete the configuration process using the appropriate steps for your connection type:
