Preface
Introduction to PowerExchange
- PowerExchange Overview
- PowerExchange Components
DBMOVER Configuration File
Netport Jobs
PowerExchange Message Logs and Destination Overrides
- PowerExchange Message Logs
  - PowerExchange Message Log File
  - PowerExchange Alternative Log Files
    - Determining the Size of the Alternative Log Data Sets on z/OS
    - Allocation Options for Alternative Log Data Sets on z/OS
- PowerExchange Message Destination Overrides
  - DTLMSGO File and Statements
SMF Statistics Logging and Reporting
PowerExchange Security
Secure Sockets Layer Support
PowerExchange Alternative Network Security
PowerExchange Nonrelational SQL
DTLDESCRIBE Metadata
- DTLDESCRIBE Metadata Overview
  - DTLDESCRIBE Metadata Syntax
  - DTLDESCRIBE Qualifiers
PowerExchange Globalization
Using the PowerExchange ODBC Drivers
PowerExchange Datatypes and Conversion Matrix
- PowerExchange Datatype Conversions
- ODBC and PowerExchange Datatype Equivalencies
Appendix A: DTL__CAPXTIMESTAMP Time Stamps
- Time Stamps That Are Reported in the DTL__CAPXTIMESTAMP Field by Data Source
Appendix B: PowerExchange Glossary
- Glossary of Terms

Reference Manual

10.5.4
- 10.5.5
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.1
- 10.4.0 HotFix 1
- 10.4.0

Back Next

Using SQL with User-Defined Fields

You should not use the SQL keyword 'DISTINCT' if the data map includes user-defined fields. Attempting to use DISTINCT with user defined fields causes a message in the logfile 'SELECT DISTINCT not guaranteed with Expressions'.

If DISTINCT is essential to a query then the best approach is to create another table in the data map that contains only the fields that are actually required for that query.

Rename Saved Search

Table of Contents

Reference Manual

Reference Manual

Using SQL with User-Defined Fields

Using SQL with User-Defined Fields