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

{DTLDSN= } Escape Sequence

{DTLDSN= } Escape Sequence

Enables SQL to override the physical file name coded in the data map. This enables users to use ODBC to read NRDB and NRDB2 data from various files through one ODBC data Source. For ODBC, this is coded anywhere in the SQL as {DTLDSN=
TABLE="{DTLDSN=filename}NRDBSchema.NRDBMapName.NRDBTableName" TABLE="{DTLDSN=filename}DB2Schema.DB2Table"
  • Filename is any valid filename for the system on which it resides. For NRDB and NRDB2 the filename will override the file name specified in the PowerExchange data map NRDBSchema.NRDBMapName.NRDBTableName.
  • For the DB2 bulk load, filename will override the value FName specified in the ODBC setup (ODBC.INI).
  • For i5/OS, the fully-qualified library and table name to be used instead of that specified in the PowerExchange change data capture registration. For example:
    If tables exist in multiple libraries you can define this by using an asterisk (*) instead of the library name. Matching tables in all libraries will be used.
    For example:


We’d like to hear from you!