perl localtime and gmtime inconsistent on cluster nodes

Hi,

I'm sure this must be a FAQ, but I have not yet
found the answer.

Running on OpenVMS (AlphaServer) VMS8.3 with 
patches through July; and perl 5.8.6.

On 2 nodes, gmtime and localtime is an hour 
behind, but correct on the 3rd node.  All of 
the vms time logicals look like this:

  "SYS$TIMEZONE_DAYLIGHT_SAVING" = "0"
  "SYS$TIMEZONE_DIFFERENTIAL" = "-18000"
  "SYS$TIMEZONE_NAME" = "EST"
  "SYS$TIMEZONE_RULE" = "EST5EDT4,M3.2.0/02,M11.1.0/02"

6.0:friedb$ sysman
SYSMAN> set e/c
%SYSMAN-I-ENV, current command environment:
        Clusterwide on local cluster
        Username FRIEDBERG    will be used on nonlocal nodes
---> vms show time is the same on each node:
SYSMAN> do show time
%SYSMAN-I-OUTPUT, command execution on node VMS6
  25-JAN-2010 19:43:14
%SYSMAN-I-OUTPUT, command execution on node K
  25-JAN-2010 19:43:14
%SYSMAN-I-OUTPUT, command execution on node J
  25-JAN-2010 19:43:14

--> gmtime is off on VMS6 and K:

SYSMAN> do perl -e "print scalar(gmtime)"
%SYSMAN-I-OUTPUT, command execution on node VMS6
Mon Jan 25 23:43:22 2010
%SYSMAN-I-OUTPUT, command execution on node K
Mon Jan 25 23:43:22 2010
%SYSMAN-I-OUTPUT, command execution on node J
Tue Jan 26 00:43:22 2010

--> localtime is off on VMS6 and K:

SYSMAN> do perl -e "print scalar(localtime)"
%SYSMAN-I-OUTPUT, command execution on node VMS6
Mon Jan 25 18:43:27 2010
%SYSMAN-I-OUTPUT, command execution on node K
Mon Jan 25 18:43:27 2010
%SYSMAN-I-OUTPUT, command execution on node J
Mon Jan 25 19:43:27 2010
SYSMAN>  Exit
6.0:friedb$ perl -v

This is perl, v5.8.6 built for VMS_AXP

Copyright 1987-2004, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using `man perl' or `perldoc perl'.  If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.

Any help appreciated. I don't know when this started; I'm betting
there is something funky with a bad file located in the local sys
root for K and VMS6, but I don't know what file I am looking for.


Carl Friedberg