In October 2011 Russia ceased using of Daylight Savings Time (DST) and kept Summer time forever. Nine time zones around the territory were implemented in a range from UTC 3 to UTC 12. Moscow local time became UTC 4. Those changes are described in my previous post: https://www.novell.com/communities/coolsolutions/how-implement-lastest-time-zone-changes-russia-netware/
In 2014, the latest time zone changes in Russia are established by a Federal Law #248-FZ that was published in July 2014 (see http://www.rg.ru/2014/07/25/vremiya-dok.html). The law declares shifting of local time in most regions 1 hour behind, closer to UTC. Number of time zones increases from nine to eleven. The offset range is from UTC 2 to UTC 12. Moscow local time will be UTC 3 all year round. Time zone changes are active since the 26th Oct 2014 2:00 local time.
Since Novell NetWare lifecycle is in Extended Support phase, it is not likely the Time Zone updates will be issued for NetWare.
As for Java, Oracle has issued JRE Time Zone patch "tzupdater-1_4_6-2014f" that contains Time Zone changes for Russia. Actually, any TZUpdater of that version or later is suitable.
As you know, erroneous setting of UTC time to the past causes eDirectory Synthetic Time error. That is why you should keep UTC time on NetWare continuous while implementing time zone settings. This is crucial for eDirectory health.
Please keep in mind that UTC time in NetWare is calculated based on the local time and time zone information (zone offset and DST offset):
UTC = local time time zone offset - daylight savings time offset
For example, at 10:00am of Moscow local time (Time Zone = MSK-4) the equation would look like the following:
Before the 26th Oct 2014, TZ = MSK-4: UTC = 10:00 (-4) - 0 = 6:00
After the 26th Oct 2014, TZ = MSK-3: UTC = 9:00 (-3) - 0 = 6:00
Because on the 26th Oct 2014 you would have to change two items in the right-hand side of the equation (Local Time and Time Zone Offset), there is no way to make manual re-configuration of Time Zone "on-the-fly" and keep UTC time continuous while the NetWare OS is running.
The safe way to tackle this, is to make changes in offline mode.
An approach described below provides a safe way to change TZ settings on NetWare. It involves server reboot and is suitable for physical or fully virtualized NetWare. A minor drawback is that the time zone changes are implemented not momentary and not at the exact moment (26th Oct 2:00am). Therefore some servers will be running incorrect local time for a while. That is why it should be done during off-work hours on weekend.
At this step, Time Zone configuration for NetWare has complete.
The procedure is described in details in my previous post https://www.novell.com/communities/coolsolutions/how-implement-lastest-time-zone-changes-russia-netware/.
Also, you can find there a brief explanation of how JRE works with Time Zone.
You need TZupdater version 1.4.6 (2014f) or later.
You might use appropriate values from the following list:
CNA6, CNE6, MCNE, NCA, NCE, CLA, CLP