Datastage Time Different from Server Time

pjsimon20 · Post by **pjsimon20** » Wed Nov 11, 2009 2:18 pm

Hello All,
The datastage time that shows up in the director is GMT. But the server time is Eastern Time. Does anybody know how to fix this.

I also noticed that if I login as root and issue a date command in AIX, it gives me Eastern Time. If I su to dsadm and issue a date command it gives me GMT.

# whoami
root
# date
Wed Nov 11 15:08:06 EST 2009
# su - dsadm
$ date
Wed Nov 11 20:08:21 America/New_York 2009

It says America/New_York but the time is actually GMT.

Thanks for your help in advance.

chulett · Post by **chulett** » Wed Nov 11, 2009 2:47 pm

Before and after you've switched to dsadm what is the value of $TZ?

pjsimon20 · Post by **pjsimon20** » Wed Nov 11, 2009 2:56 pm

The Time Zone is the same before and after switching.

# whoami
root
# echo $TZ
America/New_York
# su - dsadm
$ echo $TZ
America/New_York

chulett · Post by **chulett** » Wed Nov 11, 2009 3:01 pm

Odd... more of a UNIX than DataStage issue, it seems. Have you pinged your SysAdmin about it?

pjsimon20 · Post by **pjsimon20** » Wed Nov 11, 2009 3:32 pm

We are having this issue on 3 environments. we create other users during installation like db2inst1, db2fenc1 etc.. but they give the right time. Makes me wonder if there is some profile setting for dsadm which was modified during the install.

chulett · Post by **chulett** » Wed Nov 11, 2009 3:42 pm

It's still just a UNIX user and down at the O/S level it's no different from any other user - it's only DataStage in the engine's environment that gives it special privileges. Have you compared dsadm's .profile to some of the others to see if it has anything... 'special' in it that could be affecting this?

jhmckeever · Post by **jhmckeever** » Tue May 24, 2011 10:25 pm

Sorry to bump an old topic, but does anyone know of a resolution to this?

Code: Select all

$> whoami
root
$> date
Wed May 25 11:25:07 GMT+10:00 2011
$> echo $TZ
Australia/Melbourne
$> exit
$> whoami
jmckeever
$> date
Wed May 25 01:25:11 Australia/Melbourne 2011
$> echo $TZ
Australia/Melbourne

ray.wurlod · Post by **ray.wurlod** » Wed May 25, 2011 12:27 am

D'you mean that it's clever enough to recognize that you're English?!!

What's in the startup script (.profile, .bash_profile, etc.) for dsadm? For root? For jmckeever?

roy · Post by **roy** » Wed May 25, 2011 8:45 am

Just since it was bumped...
The director being a client side application, might be getting te settings from the client side, the same as your NLS setting when inporting a DSX file. So my guess would be setting your client with the same time zone as your server or the other way around.
IHTH (I Hope This Helps)...

zhulinqingfeng2 · Post by **zhulinqingfeng2** » Sun Jul 22, 2012 1:15 am

Hi,buddy

Have you got the root cause for this phenom? I came across the same case as you and I just found that when I logging in system without executing the dsenv file, the system time would be correct, but when I logging in system with executing the dsenv file, the time would be different with the root user.
I have checked the dsenv file carefully but didn't get any clue for it.
Expecting your solution for sharing.

Any reply would be appreciated.

Thanks in advance.