Table of Contents


  1. Preface
  2. Introduction to PowerExchange
  3. DBMOVER Configuration File
  4. Netport Jobs
  5. PowerExchange Message Logs and Destination Overrides
  6. SMF Statistics Logging and Reporting
  7. PowerExchange Security
  8. Secure Sockets Layer Support
  9. PowerExchange Alternative Network Security
  10. PowerExchange Nonrelational SQL
  11. DTLDESCRIBE Metadata
  12. PowerExchange Globalization
  13. Using the PowerExchange ODBC Drivers
  14. PowerExchange Datatypes and Conversion Matrix
  15. Appendix A: DTL__CAPXTIMESTAMP Time Stamps
  16. Appendix B: PowerExchange Glossary

HOSTNAME Statement

HOSTNAME Statement

The HOSTNAME statement specifies an i5/OS host name that overrides the host name that PowerExchange retrieves from the TCP/IP Host table for communications with the PowerExchange Listener on i5/OS.
This statement pertains to an ethernet-type of environment in which an i5/OS server is configured to use multiple i5/OS host names and IP addresses. You might use this type of environment to improve performance when a high volume of transactions exists or to use different host names for different business functions. In this situation, the HOSTNAME statement is required.
For the
variable, enter a valid TCP/IP host name up to 64 characters in length. No default value is provided.
You can enter one HOSTNAME statement in the DBMOVER member in the CFG file on the i5/OS system. This statement can specify only one host name override.
Use the HOSTNAME statement when you want to start or connect to a PowerExchange Listener on i5/OS under a host name other than the one PowerExchange retrieves by means of a TCP/IP gethostname() call to the TCP/IP Host table and other than the one that the HOSTENT utility reports. PowerExchange tasks and utilities can then use the override host name to connect to the PowerExchange Listener on i5/OS to perform tasks such as fetching data or pinging the Listener. The specified host name is used in conjunction with the IP address in the LISTENER statement, provided that the IP address is not associated with the host name returned by the TCP/IP getshostname() call.


We’d like to hear from you!