IPlanet Calendar Server 5.0 WCAP commands fetchcomponents_by_range,fetchevents_by_id,fetchtodos_by_id returns the event dtstart & dtend in GMT and not in the timezone (tzid) specified in the command

Question

hi,
i am vinod from knowledge systems pvt ltd. we are the partners with the iplanet india for customer support.
problem description :
m fetchcomponents_by_range,m fetchevents_by_id,m fetchtodos_by_id returns the event dtstart & dtend in GMT and not the timezone (tzid) requested
i have an development issue with the iplanet calendar server 5.x.if i execute WCAP command storeevents.wcap as follows for storing an event
http://localhost:portnumber/storeevents.wcap?id=n38tew98wbhhv95s&calid=userA&tzid=America/Indianapolis&rid=0&dtstart=20020419T050000Z&duration=PT1H0M&summary=eventtest&fmt-out=text/xml
in the calendar server the dtstart and the dtend for this event is as follows
dtStart = 1019210400 (20020419T100000Z) [19-Apr-02 10:00AM GMT] (isDate = 0)
dtEnd = 1019214000 (20020419T110000Z) [19-Apr-02 11:00AM GMT] (isDate = 0)
NOTE : in the WCAP command i had specified the time in America/Indianapolis i,e 0500 hrs behind GMT(-0500) hence the server stores the dtstart & dtend in the GMT which is perfect as explained in the docs.
Now for retreving the same event i execute the following command
http://localhost:portnumber/fetchcomponents_by_range.wcap?id=n38tew98wbhhv95s&rid=0&calid=vt&tzid=America/Indianapolis&fmt-out=text/xml
the result has the event details but the dtstart & dtend are in GMT and not in the America/Indianapolis timezone requested.
<START>20020419T100000Z</START>
<END>20020419T110000Z</END>
NOTE : the Mime type requested in the WCAP is text/xml. the expected dtstart is 20020419T050000Z and dtend is 20020419T060000Z applied to the timezone specified in the tzid parameter(America/Indianapolis)
issue :
m fetchcomponents_by_range,m fetchevents_by_id,m fetchtodos_by_id returns the event dtstart & dtend in GMT and not the timezone (tzid) requested
docs says the following which is not true for retrieving the events.....
For example, if a command such as storeevents or fetchcomponents_by_range
specifies a tzid parameter, the parameter value must be a tzid that is defined in the list of 91 time zones. The server will return data in that time zone and all data will have dates applied to that time zone.If the command specifies an unrecognized tzid, the server will return a GMT timezone by default. All data returned on that command will have its dates applied in GMT.
release notes has the following. i could not understand the point no. 1 could u please suggest me how to retrieve the event with dtstart & dtend values applied to the timezone supplied in the parameter tzid.
1. The following seven commands now take an additional parameter, tzid:
m deleteevents_by_id
m deletetodos_by_id
m fetchcomponents_by_alarmrange
m fetchcomponents_by_lastmod
m fetchcomponents_by_range
m fetchevents_by_id
m fetchtodos_by_id
The value of tzid must be a time zone ID string, such as &#8220;America/Los_Angeles&#8221;. Note that these are not localized. If other ISO 8601 DateTime string parameters, such as rid, dtstart and dtend, do not have a &#8220;Z&#8221; on the end, this parameter determines the time zone to use.
2. The following two commands, which already have the tzid parameter, have been modified:
m storeevents
m storetodos
The value is no longer a quoted string, but is now a time zone ID string to match the acceptable values for tzid in the seven commands listed above.The default value of the tzid parameter in all commands is the server's default time zone. This is a change for storeevents and storetodos.
thanks
vinod

Answer 1

I have found the solution! I post how I managed in case someone else has the same issue.
You have to go to "Settings" -> "Settings Editor".
There, there is a "display" entry.
When you open the tree, you can see both of your displays (in my case, LVDS1 and VGA1).
Under VGA1 (the "extra" monitor), there is a "Position" entry. There, you need to set the "X" variable to the last pixel of the other display resolution.
E.g.: if you principal display is a "1366x768", then the "X" value will be 1366.
You can also play on the "Y" if your screens are not horizontally aligned, but 0 should be fine.
I hope this helps :-)