
	Version 8.2.5	SEARCH INDEX CONTENTS \| PDF PAGE PDF BOOKS \| HOME UP PREV NEXT

Supported Time Zones

Adabas uses the time zone data taken from the tz database, which is also called the zoneinfo or Olson database. The specific list of time zone names that Adabas supports in any given release can be found in the TZINFO member of the Adabas source library.

Notes:

Time zone names are case-sensitive and must be specified inside single quotation marks.
The default number of time zones that can be used in a nucleus session is limited to 8 and the time zone pool size default to 32K. However, Software AG allows you to increase these numbers (refer to the appropriate zap in member ZAPOPT of the distributed source library) so that all time zones can be loaded.
The nucleus session startup procedure or the ADACMP utility job must include the TZINFO data definition statement (DD, LINK, or DLBL statement) identifying the TZ library or sublibrary if you are using time zone support. For more information, review the nucleus startup procedure examples provided in Adabas Session Execution or the ADACMP utility job examples in ADACMP Utility: Compress-Decompress Data.

The following is a sample of the information in the TZINFO member:

# Timezone, Timezone Member name, Old Timezone Names
Africa/Abidjan, AFRABIDJ,
Africa/Accra, AFRACCRA,
Africa/Addis_Ababa, AFRADDIS,
Africa/Algiers, AFRALGIE,
Africa/Asmara, AFRASMAR, Africa/Asmera
Africa/Bamako, AFRBAMAK, Africa/Timbuktu
Africa/Bangui, AFRBANGU,
...
America/Denver, AMEDENVE, Navajo US/Mountain
...

TZINFO is a comma-delimited file:

The time zone name is given before the first comma. This is the name that you should use in the record buffer of an OP command (when setting the time zone of a user session).
The Adabas time zone library member name associated with the time zone name is given between the first and second comma. This is the name of the time zone library member containing the code required to convert date-time fields in that time zone.
Older names for the time zone are given after the second comma. Older names cannot be specified in the record buffer of an OP command (when setting the time zone of a user session).

Consider the following examples:

Example	Description
Africa/Accra, AFRACCRA,,	The current time zone name is "Africa/Accra"; the member name in which the code associated with this time zone resides is "AFRACCRA". There are no older names for this time zone.
Africa/Asmara, AFRASMAR,, Africa/Asmera	The current time zone name is "Africa/Asmara"; the member name in which the code associated with this time zone resides is "AFRASMAR". "Africa/Asmera" is an older name for the time zone.
America/Denver, AMEDENVE, Navajo US/Mountain	The current time zone name is "America/Denver"; the member name in which the code associated with this time zone resides is "AMEDENVE"; "Navajo" and "US/Mountain" are older names for the time zone.

For information on the conversions between date-time fields defined with the TZ option, read Conversions Between Date-Time Representations for Fields with the TZ option.

SEARCH INDEX CONTENTS | PDF PAGE PDF BOOKS | HOME UP PREV NEXT