Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

pb nvo on Jag returns wrong date

2 posts in General Discussion (old) Last posting was on 2000-02-23 03:11:05.0Z
Anne Pruitt Posted on 2000-02-23 01:45:44.0Z
Newsgroups: sybase.public.easerver
From: "Anne Pruitt" <annepruitt@mediaone.net>
Subject: pb nvo on Jag returns wrong date
Date: Tue, 22 Feb 2000 20:45:44 -0500
Lines: 21
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
NNTP-Posting-Host: hsd0a94c2.ne.mediaone.net 24.218.214.30
Message-ID: <347_rkTK#$Zf$GA.201@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:28114
Article PK: 160002

NT 4, PB 7, Jag 3, Sybase EAS 11.x

I sure hope someone can help on this. We have a PB object deployed to Jaguar
that calls a transaction object's method. The transaction object's method
calls a stored procedure that places today's date in a reference argument
(datetime). The trans obj's method returns the datetime.

When the value gets to the client, the date is wrong - by a year. In debug
on the server, you can see that the trans obj's method has a local variable:
after the call to the stored procedure, the variable has the correct value
of 02/22/00. This value is returned to the client, and at the client, the
value magically turns into 2/22/1999!

What's worse, this only happens on our production server. A localhost Jaguar
server does not misbehave in this fashion. In debug on the server, however,
the local variable is formatted as 02/22/2000.

We have checked and rechecked the Windows shortdate setting on the
production server. Any other ideas?


Dave Wolf [Sybase] Posted on 2000-02-23 03:11:05.0Z
Newsgroups: sybase.public.easerver
From: "Dave Wolf [Sybase]" <dwolf@sybase.com>
Subject: Re: pb nvo on Jag returns wrong date
Date: Tue, 22 Feb 2000 22:11:05 -0500
Lines: 34
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
NNTP-Posting-Host: PPPa49-ResaleAnnapolis1-1R7308.saturn.bbn.com 4.48.176.110
Message-ID: <347_POY$iwaf$GA.251@forums.sybase.com>
References: <347_rkTK#$Zf$GA.201@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:28110
Article PK: 159999

This is a known bug with Jag3 GA. Please contact support for the EBF.

Dave Wolf
Internet Applications Division

"Anne Pruitt" <annepruitt@mediaone.net> wrote in message
news:rkTK#$Zf$GA.201@forums.sybase.com...
> NT 4, PB 7, Jag 3, Sybase EAS 11.x
>
> I sure hope someone can help on this. We have a PB object deployed to
Jaguar
> that calls a transaction object's method. The transaction object's method
> calls a stored procedure that places today's date in a reference argument
> (datetime). The trans obj's method returns the datetime.
>
> When the value gets to the client, the date is wrong - by a year. In debug
> on the server, you can see that the trans obj's method has a local
variable:
> after the call to the stored procedure, the variable has the correct value
> of 02/22/00. This value is returned to the client, and at the client, the
> value magically turns into 2/22/1999!
>
> What's worse, this only happens on our production server. A localhost
Jaguar
> server does not misbehave in this fashion. In debug on the server,
however,
> the local variable is formatted as 02/22/2000.
>
> We have checked and rechecked the Windows shortdate setting on the
> production server. Any other ideas?
>
>