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
  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. DTL__CAPXTIMESTAMP Time Stamps
  15. PowerExchange Glossary

TIMEZONE Statement

TIMEZONE Statement

The TIMEZONE statement enables PowerExchange to read or write Adabas date-time values in the user's local time for bulk data movement sessions. It specifies the local time zone that PowerExchange uses.
This statement applies only to Adabas 8.2.2 data sources or targets that include date-time fields for which the Adabas TZ option is specified in the field definitions.
If you need to maintain consistent date-time values across CDC and bulk data movement sessions that process the same Adabas sources or targets, do not specify this statement.
z/OS
Adabas
No
TIMEZONE=
area
/
location
For the
area
/
location
string, enter the local time zone value from the tz database. This value is case sensitive.
  • For PowerExchange to read or write date-time values in the user's local time, the user's local time zone must be defined in the TZINFO member of the Adabas source library.
  • If you do not use the TIMEZONE statement, PowerExchange reads and writes Adabas date-time values in Coordinated Universal Time (UTC). UTC is the time in which Adabas stores date-time values when the TZ option is specified.
  • For CDC sessions, the TIMEZONE statement is ignored and PowerExchange always reads and writes Adabas date-time values in UTC.
  • IMPORTANT: PowerExchange cannot convert UTC date-time values to the local time for CDC sessions. If you run a CDC session and a bulk data movement session for which you specified a local time zone against the same Adabas sources or targets, these sessions might have inconsistent date-time values.