This content has been marked as final. Show 2 replies
I guess the two databases are on different machines?
The VMS logicals to set (in SYS$STARTUP:FORTE_STARTUP_V*.COM) are
FORTE_TIMEZONE and FORTE_TIMEZONEDST. We currently have ours set to
"-12" and "TRUE" respectively. It probably doesn't matter as long as
they're all the same on every machine (assuming all your machines
really are in the same time zone).
This sort of thing has turned out to be a real nuisance for us,
because it's the sort of thing we forget when we're setting up a
new machine (esp. client machines). I reckon it'd be kinda nice if
you could set up an environment with a "everything is guaranteed to
be in the same time zone" option so that everything using that
environment grabbed its timezone from there.
We have recently discovered that Forte(version 2F0) thinks our database- Ed
server(Oracle v7) is in a different time zone. For example if we issue a
SYSDATE command from SQLPLUS the date and time are correct. However, if we
execute the same statement through forte the time is three hours early. We
are in a VMS environment for both Forte and Oracle. Where is time-zone info
kept/changed in forte(at the server level)? Is there a system variable that
needs to be set? Any help would be appreciated.
Eduard E Havelaar, Information Services Section, University of Canterbury
phone: +64-3-366 7001 extn 8910
fax: +64-3-364 2999
snailmail: Private Bag 4800, Christchurch, New Zealand
I'm running Forte 3.0.M.2 and Windows 2003 server 32bit. Here is a quick breakdown of the environement and the problem. I have remote machine on the west coast(Fullerton,CA) running Windows Server 2003 32 bit version along with the Forte Client 3.0.M.2. My backend is AIX 5.3 with DB2v8 and the Forte Client and App which located in Chicago.
When I communicate from the client which is on the west coast to my backend server in Chicago, I get errors that related to a date and time stamp issue. The date appears to be coming in the following format DD-M-YYYY. The forte application running on the backend expects to see the date in the following format YYYY-MM-DD. In troubleshooting, this problem I have found that when I set the timezone to Central Standard time on my remote machine I don't get the error. I would like to know is there something that could be done on the Windows Server 2003, Forte, or DB2 to correct this issue.
Any info is appreciated.