Quote:
|
Originally Posted by kirfan
Our city zone is Pacific standard time(PST). and our unix server time zone is GMT.
I am calling informatica job in unix script. Below is the steps in script.
1. Before starting the informatica job i get the datetime in startdate variable.
2. Calling the informatica configuration file which has the timezone as GMT.
3. Now the informatica job is called and upon the completion of Informatica job, I get the datetime in enddate variable.
This works fine in development environment. ie startdate and enddate variable values are in GMT timezone.
In Production the above unix script is called in Control M scheduler application which has the PST. The starttime variable is set to PST and enddate variable is set to GMT. so we were not able to get exact time difference. Is this due to the Control M scheduler timezone.
Control M and our login account are same. I checked in the production unix box time zone using TZ variable shows GMT timezone.
Pl help me to solve this issue.
|
It would be nice if our city zone is Pacific standard timePST.It would be nice if our unix server time zone is GMT.What is the phone number?Tell me more about steps in script.
Only one?What happened after starting the informatica job he or she get the datetime in startdate variable ?Two what?I never call the informatica configuration file which has the timezone as GMT, that would be impolite.Three what?Why now? Thanks for the info.What does "this" refer to?All of them?What is in Production the above unix script is called in Control M scheduler application which has the PST like in there? What is your real name?Uh. Was this something you planned?Yes I think this is due to the Control M scheduler timezone, but I'm not completely sure.I think there might be a few exception.Do you mind if I tell other people:
said checked in the production unix box time zone using TZ variable shows GMT timezone.
Tell me a story.
