pddbadset (Set up HiRDB External Data Access Adapter)

Function

The pddbadset command sets up HiRDB External Data Access Adapter in the HiRDB environment in order to use the HiRDB External Data Access facility. If the external DBMS is HiRDB Version 5.0, HiRDB Version 7, or XDM/RD E2, HiRDB External Data Access Adapter is included in HiRDB External Data Access.

When you execute the pddbadset command, files are copied from the installation directory to the HiRDB environment ($PDDIR/adapter). One execution of the pddbadset command sets up a single HiRDB External Data Access Adapter.

This command also enables you to cancel the setup of an existing HiRDB External Data Access Adapter.

You can use the pddbadset command only if HiRDB External Data Access has been installed.

Executor

HiRDB administrator

Format

pddbadset {HiRDB-External-Data-Access-Adapter-name installation-directory-name

            |-d HiRDB-External-Data-Access-Adapter-name}

Options

Specifies the name of the HiRDB External Data Access Adapter whose setup is to be cancelled. When you cancel the setup of the existing HiRDB External Data Access Adapter, the shared library for the HiRDB External Data Access Adapter is deleted from the HiRDB environment.

Command arguments

Specifies the name of the HiRDB External Data Access Adapter to be set up. Note that an attempt to set up again at a server machine an existing HiRDB External Data Access Adapter results in abnormal termination.

hiv6:
Specifies that the DBMS is HiRDB or XDM/RD E2. With XDM/RD E2, the XDM/RD E2 connection facility is used to establish connection from the HiRDB client to XDM/RD E2 via a DB connection server.
orav8:
Specifies that the DBMS is Oracle 8i.
orav9:
Specifies that the DBMS is Oracle 9i.
orav10:
Specifies that the DBMS is Oracle 10g.
db2udbv6:
Specifies that the DBMS is DB2. Note that this argument is not applicable in the Solaris or Linux version.

Specifies the name of the directory that contains the files of the HiRDB External Data Access Adapter installed on the server machine.

Rules

  1. The pddbadset command can be executed only while HiRDB is inactive.
  2. The pddbadset command must be executed at each server machine.

Notes

  1. The result of the pddbadset command can be checked on the basis of the return code from execution of the command. A return value of 0 indicates normal termination, and 8 indicates abnormal termination.
  2. Do not execute multiple pddbadset commands concurrently on the same server machine.
  3. If there is no $PDDIR/adapter directory during execution of the pddbadset command, the $PDDIR/adapter directory is created automatically.