Canada's 2026 Time Zone Changes: What Your JD Edwards Team Needs to Fix

On November 1, 2026, Alberta, the Northwest Territories and Manitoba stop changing their clocks. British Columbia made the same move on March 8. All four kept their summer (daylight) time and made it permanent.

For JD Edwards EnterpriseOne customers, this touches more than the clock on the wall. Scheduled jobs, application servers, Orchestrator, user profiles and custom code each store their own time zone setting. If one of them stays on the old rule, jobs launch an hour off, or JDE skips them without an error.

Work through the layers below in order. Each fix depends on the one before it.

What's Changing

• Alberta: permanent Mountain Daylight Time (UTC-6), effective November 1, 2026
• British Columbia: permanent Pacific Daylight Time (UTC-7), in effect since March 8, 2026
• Northwest Territories: permanent UTC-6, effective November 1, 2026
• Manitoba: permanent Central Daylight Time (UTC-5), effective November 1, 2026 (proclaimed September 25, 2026)

The "Uncheck DST" Trap

The obvious fix is to open the existing time zone and turn off Daylight Savings Observed. That gives you the wrong hour. Turning off DST on a seasonal zone freezes the clock at the old standard offset, so Alberta would sit at UTC-7 instead of UTC-6.

The correct fix points the Time Zone Rule at a zone whose base (non-DST) offset already matches the new permanent offset, with the DST flag off:

• Alberta and NWT (UTC-6): Saskatchewan, fixed Mountain with no DST
• British Columbia (UTC-7): Yukon, fixed Pacific with no DST
• Manitoba (UTC-5): no native Canadian match yet, so use a fixed UTC-5 stand-in until Oracle and Microsoft ship a Manitoba zone

Step 1: Patch the Operating System on Every Server

Every JDE setting sits on top of the operating system's time zone data. Patch the Enterprise, HTML/JAS, AIS and Citrix servers before you touch anything in JDE. Those servers don't always run the same OS, so check each one.

Windows. Microsoft's October 13, 2026 updates include the new rules. KB5126655 (Windows Server 2022) and KB5126646 (Windows Server 2025) confirm permanent DST for Alberta and BC plus a new Manitoba zone. Microsoft released updates for Windows 11, Windows 10 ESU and Server 2016 the same day; confirm the time zone content for your build in Microsoft's release notes. Microsoft doesn't ship a separate NWT zone. Its guidance has Yellowknife and Inuvik use the Alberta zone (Mountain Time (Alberta), UTC-6).

Linux (RHEL / Oracle Linux). Set ZONE in /etc/sysconfig/clock, replace /etc/localtime with a symlink into /usr/share/zoneinfo/<zone>, and reboot. Linux has no native fixed-offset Canadian zone yet either, so point ZONE at the same proxy you use for the JVM (America/Regina or America/Dawson_Creek) until one ships.

IBM i. The QTIMZON system value points to a time zone object. IBM's built-in objects start with Q, and you can't edit them. IBM doesn't ship a Canada-specific object, so clone the nearest fixed-offset Q zone into a new non-Q object that carries the corrected rule.

Step 2: Fix the Scheduler (P91300)

Each P91300 version stores its own Time Zone, Daylight Savings flag and Daylight Savings Rule (P00085) in its processing options. When you schedule a job, JDE stamps those values onto F91300 and pre-calculates the launch time into F91320. JDE doesn't re-check them later.

• Single-region environments: update ZJDE0001 (or your existing version) directly.
• Multi-region environments: create a version for each region. Separate versions let several time zones run on one scheduler.

Then reset your existing jobs. F91320 won't recalculate on its own, and editing the version only affects jobs you schedule afterward. On each recurring job, use Form Exit → Reset Schedule so JDE regenerates the stored launch time under the corrected rule.

Step 3: Check the JVM and AIS Server

Each application server JVM can carry a hardcoded time zone that overrides the OS. A hardcoded value stays wrong after you patch the OS, so update or remove it.

• WebLogic: Server Start tab → Java Arguments → -Duser.timezone=<zone>
• WebSphere 6/7/8.5: JVM Custom Properties (user.timezone) or Environment Entries (TZ)
• OC4J 10.1.3.x: add -Duser.timezone=<zone> to the java-options in opmn.xml

The JVM also bundles its own tzdata, separate from the OS. Oracle documents a case where Java 1.7_55 shipped older tzdata and set Moscow an hour off after Russia's 2014 change. Check yours with Oracle's tzupdater utility, or move to a certified JDK (MOS Doc ID 1260014.1).

Orchestrator. The Orchestrator Scheduler has no JDE Time Zone or DST Rule of its own. The AIS server's JVM argument controls when jobs run, for both the standard scheduler and the Resilience (Quartz) scheduler. Each user's Universal Time field in P0092 only controls what Orchestrator Studio displays.

If you use the Quartz scheduler, each CRON trigger stores its own zone in QRTZ_CRON_TRIGGERS.TIME_ZONE_ID, and existing triggers won't pick up a JVM change. After you make the change, restart AIS, clear the WebLogic container and Server Manager Agent logs, then start a CRON job and check TIME_ZONE_ID (MOS Doc IDs 2800801.1, 2778902.1 and 11479496.1).

Step 4: Audit User Profiles

Each user profile (P0092) carries its own Daylight Savings Rule, separate from the scheduler version and from the Universal Time display field. If a user's rule falls out of sync with the version's corrected rule, JDE skips the job and throws no error.

Fixing the scheduler and AIS won't catch this. Audit the DST Rule and the Universal Time setting on each user profile as a separate pass.

Step 5: Review Custom Code and Integrations

A correct fix inside E1 doesn't guarantee correct values in custom code, audit trails or the systems on the other end of an interface.

• Event Rules and BSFNs: E1 ships a UTC-aware data type (JDEUTIME) and Expression Manager functions (utc_get_hour, utc_add_days and others) that take an explicit time zone. Raw date math against the server clock carries no time zone. Route custom logic through the utc_* functions instead of patching the arithmetic (MOS Doc ID 626609.1).
• EDI and external interfaces: an outbound timestamp reflects the offset in effect when JDE wrote it. Confirm your trading partners and downstream systems read each region's new offset correctly.
• 21 CFR Part 11 auditing: a database trigger writes the audit timestamp using the database server's sysdate, so it follows the database host's time zone, not the application server's (MOS Doc ID 2561752.1).

To find custom code that already uses JDEUTIME, open the Cross Reference Facility (W980011K) and search the JDEUTIME data item. Run Rebuild Relationships first, from a fat client, or recent changes won't appear. Custom date math that never touched JDEUTIME won't show up in that search. Your team will need to search the custom source on the Enterprise Server and review the hits by hand.

Settings Reference

• UTC-6 (Alberta, NWT): JVM argument -Duser.timezone=America/Regina; JDE time zone Saskatchewan
• UTC-7 (British Columbia): JVM argument -Duser.timezone=America/Dawson_Creek; JDE time zone Yukon
• UTC-5 (Manitoba): JVM argument -Duser.timezone=America/Atikokan (interim); closest fixed Eastern stand-in until a native Manitoba zone ships

Apply the JVM argument and the user profile time zone together so the two don't drift apart. Switch to America/Edmonton, America/Vancouver or America/Winnipeg only after you update the JVM's tzdata to the new rules.

Before You Cut Over

• Confirm the OS time zone update landed on each Enterprise, HTML and AIS server
• Confirm JVM tzdata is current on each managed server
• Check My Oracle Support for a region-specific patch before you rely on a configuration-only fix
• Spot-check next-run times on a few jobs after each reset

Give each region its own validation window. Alberta, NWT and Manitoba all switch on November 1, and the week of the change leaves you no room to troubleshoot.

ERP-One's CNC team has supported JD Edwards environments for more than 20 years. If you want a second set of eyes on your scheduler, servers or custom code before November 1, book a conversation with us today.