27.2.2 DF/UX environment setup

Executor: Superuser and DF/UX system administrator
Organization of this subsection
(1) DF/UX installation
(2) DF/UX environment definition
(3) DF/UX distribution definition
(4) Creating a server facility executable file (for distributed server facility only)
(5) Environment variable setup (for distributed server facility only)

(1) DF/UX installation

(2) DF/UX environment definition

HiRDB-related operands in the DF/UX environment definition are explained below. For details on DF/UX environment definition, see the manual Distributed Database System DF/UX.

(a) Related operands (for distributed client facility only)

The following table shows the operands that are related to use of the distributed client facility:

OperandSpecification
sql_environment_nameSpecifies the RD node name of the distributed server. Specify the name specified in the rd_node_name operand of the SQL environment definition in DF/UX.
context_nameSpecifies RDA#SQL#BASIC#OSAS.
block_fetch_countBecomes the default value of the PDRDABLKF operand.
(b) Invalid operands (for distributed client facility only)

When the distributed client facility is being used, the following operands are ignored even if specified:

(c) Specification of maximum_client_users and maximum_server_users operands

The maximum_client_users and maximum_server_users operands must be specified so that the following condition is satisfied:

Formula

Value of pd_process_count (in single server definition*)
[Figure]value of maximum_client_users + value of maximum_server_users

* In the case of a HiRDB/Parallel Server, use the value in the front-end server definition.

(3) DF/UX distribution definition

The operand shown below must be specified in the DF/UX distribution definition. For details on the DF/UX distribution definition, see the manual Distributed Database System DF/UX.

OperandSpecification
context_nameSpecifies RDA#SQL#BASIC#OSAS.

(4) Creating a server facility executable file (for distributed server facility only)

Use the dfsvplink command of DF/UX to create a server facility executable file. Specify the options listed below in this command. For details on the dfsvplink command, see the manual Distributed Database System DF/UX.

dfsvplink command optionSpecification
-xSpecifies p_rdb_df_xa_switch as the name of the xa_switch_t structure.
-lSpecifies the following as the libraries of the distributed server's DBMS:
  • $PDDIR/lib/libdfc.sl*
  • $PDDIR/client/lib/libzcltx.sl*

* The library suffix depends on the platform; for AIX 5L, it is .a.

(5) Environment variable setup (for distributed server facility only)

As in the case of a local-access UAP, communication between DF/UX and HiRDB uses the HiRDB client's library. Therefore, client environment definitions must be specified in environment variables of the startup command (dfstart command) of DF/UX. To start DF/UX automatically, specify the client environment definitions before the dfstart command in localrc in the /etc/rc file. For details on automatic startup of DF/UX (details of specifying localrc in the /etc/rc file), see the manual Distributed Database System DF/UX.

The following are the client environment definitions that must be specified (for details, see the manual HiRDB Version 8 UAP Development Guide):

1 Specifies $PDDIR/spool/dfc as the error log output destination. The HiRDB administrator must create $PDDIR/spool/dfc. Because error logs are output under the ID of the DF/UX system manager, the privilege to write into the directory must be granted to the DF/UX system manager.

2 Specifies a value that is greater than the value of the limit_access_interval operand of DF/UX. To safeguard against errors in distributed clients, access time is monitored based on the value specified in the limit_access_interval operand. If an error occurs in DF/UX, access time is monitored based on the value specified in the PDSWAITTIME operand.