If you are like me, you probably have copies of ConsoleOne, DNSDHCP,
etc. scattered on a number of different workstations, as well as the
copies on the actual servers. To make updating the JVMs under Windows
for each of these programs (as well as any other JVM on the Windows PCs,
and the Windows JVMs on the servers), I wrote a little DOS batch file that:

1. searches the entire drive for Windows JVMs (looks for "java.exe")
2. creates a text file (jupdate.txt) containing the paths to each of
these JVMs
3. uses that text file (jupdate.txt) to create a new batch file
(jupdate.bat) to run each JVM with the daylight savings time update
(the "tzupdater.jar" from Sun)
4. allows you to then run that new batch file, updating all JVMs while
logging the results (jupdate.log)

Drop this batch file (tzu.bat), along with the "tzupdater.jar" into a
temporary directory on a Windows PC (or even right on the desktop).
Then run "tzu.bat", and the files mentioned above will be automatically
created (jupdate.txt, jupdate.bat). You can then allow "tzu.bat" to run
"jupdate.bat" for you (you will be prompted to "press any key to
continue"), or you can kill the DOS box at that point and manually run

The jupdate.bat creates the jupdate.log file, with the results from the
JVM updates. The jupdate.* files are all unique for each PC, so don't
copy those from one PC to the next, you only need the tzu.bat and
tzupdater.jar files copied to the PC to do the update.

The versions of ConsoleOne, DNSDHCP, etc. on the NetWare servers can be
updated the same way. From a Windows PC with admin rights (to allow
updating the JVM files), just create a temporary directory on the server
volume that you want to have searched and updated (i.e. - SYS), and
drop the tzu.bat and tzupdater.jar files in. Run tzu.bat, and the
versions of ConsoleOne, etc., will be updated as the ones on the local
Windows drives are.

The tzupdater.jar can be found on suns web site. Go to:


I've inserted the batch file body below, so create your own "new" batch
file, and cut-n-paste.

As usual, use all of this at your own risk - I'm not responsible for any
bad stuff that happens. I will take credit for any good stuff that
happens, though. ;-)

NOTE: For those that may be confused: you cannot update the NetWare JVM
with this batch file (as it is currently), only the Windows JVMs. (I
have a batch file for that, too, but since there is only one JVM to
update on the server, not counting SP backups, it really doesn't save
too much time.)


REM ------------- TZU.BAT START -------------

@echo off & setlocal enabledelayedexpansion

set batpath=.

REM ***************************************
REM ***************************************
echo Creating list of JVMs to update...
echo .

dir \java.exe /b /x /s > %batpath%\jupdate.txt

REM ***************************************
REM ***************************************

echo done...
echo .
echo Creating list of JVM commands to run...
echo .

FOR /F "tokens=*" %%I in (%batpath%\jupdate.txt) DO (
set cpath=%%~pI
echo "%%I" -jar tzupdater.jar -u -v >> %batpath%\jupdate.bat

echo done!
echo .
echo Hit any key when ready to run JUPDATE.BAT!
echo .


REM ***************************************
REM ***************************************

jupdate.bat >> jupdate.log

REM -------------- TZU.BAT END -------------