Table of Contents

Search

  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. PowerExchange Globalization
  12. Using the PowerExchange ODBC Drivers
  13. PowerExchange Datatypes and Conversion Matrix
  14. Appendix A: DTL__CAPXTIMESTAMP Time Stamps
  15. Appendix B: PowerExchange Glossary

Syntax Rules and Guidelines for DBMOVER Statements

Syntax Rules and Guidelines for DBMOVER Statements

You must follow syntax rules and guidelines when you include statements in the DBMOVER configuration file.
Use the following rules and guidelines for statements in the DBMOVER configuration file:
  • Start every statement on a new line.
  • If a statement or parameter has more than one option, include them in parentheses and separate them by a comma (,) or a space. For example:
    NODE=(
    node_name
    ,TCPIP,
    host_name
    ,2480)
  • You can span statements across lines but specify only one parameter on each line. For example:
    DB2CODEPAGE=(DSN9, EBCDIC_CCSID=(037,037,037), MIXED=Y)
  • If you need to include a space in a value such as a Windows path, enclose the complete parameter value in double quotation marks. For example:
    "aaa bbbb\cccc"
    Use straight quotes ("). Do not use curly quotes (“).
  • Begin comment statements with /*. PowerExchange does not parse comment statements. For example:
    /* this is a comment
    You can include comment statements between DBMOVER statements but not between parameters of a single, multiline DBMOVER statement.
  • If you need to specify a Windows network path, use three leading backslashes (\\\) so that PowerExchange can parse the network path correctly.

0 COMMENTS

We’d like to hear from you!