10.2.8 Operands related to communication processing

26) PDIPC MEMORY | DEFAULT
Specifies the inter-process communication method to be used when the back-end server for connecting to the foreign server and the foreign HiRDB (a single server or the unit containing a front-end server) are located on the same server machine.
MEMORY:
Uses memory for the inter-process communication. This is called the inter-process memory communication facility. This facility increases the speed of communication with the foreign HiRDB.
DEFAULT:
Uses the default communication method (TCP/IP or PIPE) of each OS for inter-process communication.
The function and specification method of this operand are the same as those of the PDIPC operand of the client environment definition. For details on the PDIPC operand, see the HiRDB Version 8 UAP Development Guide. If the HiRDB version number of the foreign server is different, see the manual for the correct version.
27) PDSENDMEMSIZE memory-size-for-sending-data
[Figure]<unsigned integer>((4-2097152)) <<16>> (KB)
Specify this operand if you use the inter-process memory communication facility (MEMORY is specified for the PDIPC operand).
Specify the size of the data storage area (units: KB) to be used for sending data to the foreign server. Specify a multiple of 4.
The function and specification method of this operand are the same as those of the PDSENDMEMSIZE operand of the client environment definition. For details on the PDSENDMEMSIZE operand, see the HiRDB Version 8 UAP Development Guide. If the HiRDB version number of the foreign server is different, see the manual for the correct version.
28) PDRECVMEMSIZE memory-size-for-receiving-data
[Figure]<unsigned integer>((4-2097152)) <<32>> (KB)
Specify this operand if you use the inter-process memory communication facility (MEMORY is specified for the PDIPC operand).
Specify the size of the data storage area (units: KB) to be used for receiving data from the foreign server. Specify a multiple of 4.
The function and specification method of this operand are the same as those of the PDRECVMEMSIZE operand of the client environment definition. For details on the PDRECVMEMSIZE operand, see the HiRDB Version 8 UAP Development Guide. If the HiRDB version number of the foreign server is different, see the manual for the correct version.
29) PDTCPCONOPT 0 | 1
Specifies whether the number of TCP ports to be used by HiRDB External Data Access Adapter for communication between a HiRDB client and a foreign HiRDB (Version 06-02 or newer) be reduced. Depending on the TCP protocol specifications, TCP ports may not be usable for new TCP connection (by going into the TIME_WAIT state) for a certain amount of time (1-4 minutes) after TCP connection is terminated. Ports in the TIME_WAIT state are used by the TCP connection that has been terminated.
0: Does not reduce the number of TCP ports in the TIME_WAIT state.
1: Reduces the number of TCP ports in the TIME_WAIT state.
The function and specification method of this operand are the same as those of the PDTCPCONOPT operand of the client environment definition. For details on the PDTCPCONOPT operand, see the HiRDB Version 8 UAP Development Guide. If the HiRDB version number of the foreign server is different, see the manual for the correct version.
30) PDKALVL 0 | 1 | 2
Specifies whether to send packets from the HiRDB client used by HiRDB External Data Access Adapter to a foreign HiRDB.
0: Does not send packets to the foreign HiRDB.
1: Regularly sends packets to the connection route with the foreign HiRDB.
2: Regularly sends packets to the connection route with the foreign HiRDB and receives return packets from the foreign HiRDB.
If 1 or 2 is specified for this operand, a packet send thread is generated for each connection with the foreign HiRDB. The packet send interval is specified by the PDKATIME operand of the foreign server information definition.
Specification guidelines
  • Some network management applications, such as routers and firewalls, terminate connection if packets are not received within a specified amount of time. Consequently, web applications that wait for service requests while being connected to a foreign HiRDB are disconnected from the foreign HiRDB when the wait state exceeds the predetermined time limit. To avoid this kind of problem, specify 1 or 2.
  • When maximum wait time is not specified for a foreign HiRDB (the first argument of the PDSWAITTIME operand of the foreign server information definition is omitted and 0 is specified for the second argument), a server process may remain in the foreign HiRDB, if the server machine on which the HiRDB client used by HiRDB External Data Access Adapter is located is abnormally terminated, or if a network error occurs. Specifying 2 for this operand can prevent these server processes from remaining.
The function and specification method of this operand are the same as those of the PDKALVL operand of the client environment definition. For details on the PDKALVL operand, see the HiRDB Version 87 UAP Development Guide.
31) PDKATIME interval-for-sending-packets-to-foreign-HiRDB
[Figure]<unsigned integer>((60-65535)) <<3000>> (seconds)
Specifies the interval (units: seconds) at which to send packets from the HiRDB client used by HiRDB External Data Access Adapter to a foreign HiRDB.
Condition
The PDKALVL operand of the foreign server information definition must be set to 1 or 2.
The function and specification method of this operand are the same as those of the PDKATIME operand of the client environment definition. For details on the PDKATIME operand, see the HiRDB Version 8 UAP Development Guide.
32) PDNODELAYACK YES | NO
This operand is specified when an external HiRDB being used is the AIX 5L version.
The operand specifies whether or not immediate acknowledgment is to be used when data is received during communication between the HiRDB server machine and the HiRDB client machine.
The function of and specification method for this operand are the same as for the PDNODELAYACK operand in the client environment definition. For details about the PDNODELAYACK operand, see the HiRDB Version 8 UAP Development Guide. For an external server with a different HiRDB version, see the applicable manual.
YES: Use immediate acknowledgment.
NO: Do not use immediate acknowledgment.