sybperl-l Archive

From: "Ashish Gupta" <ashish dot gupta at mizuho-sc dot com>
Subject: RE: sybperl ct_config CS_RETRY_COUNT
Date: Aug 26 2005 6:33AM

Hi Michael,

I still get an error.

I tried the command :

	ct_config(CS_SET, 9173,   2, CS_INT_TYPE);


And the following error was reported :

Open Client Message:
Message number: LAYER = (1) ORIGIN = (1) SEVERITY = (1) NUMBER = (5)
Message String: ct_config(): user api layer: external error: An illegal
value of 9173 given for parameter property.


Thanks for your kind help.
Best regards,
Ashish


-----Original Message-----
From: owner-sybperl-l@peppler.org [mailto:owner-sybperl-l@peppler.org]
On Behalf Of Michael Peppler
Sent: Friday, August 26, 2005 3:24 PM
To: ashish.gupta@mizuho-sc.com
Cc: sybperl-l@peppler.org
Subject: RE: sybperl ct_config CS_RETRY_COUNT


On Fri, 2005-08-26 at 09:57 +0900, Ashish Gupta wrote:
> Thanks Michael.
> 
> I tried it, but get the following error:
> 
> Can't locate auto/Sybase/CTlib/CS_RETRY_CO.al in @INC (@INC contains:
> /export/home/guptaash/perl/lib/5.8.6
>
/export/home/guptaash/perl/lib/site_perl/5.8.6/sun4-solaris-thread-multi
> /export/home/guptaash/perl/lib/site_perl/5.8.6
> /export/home/guptaash/perl/lib/site_perl .) at b.pl line 13

Ah - I guess it's a new(ish) symbol that isn't mapped in Sybase::CTlib.

You can use the actual value of the #define for now - checking in
cspublic.h I see:

#define CS_RETRY_COUNT		(CS_INT)9173

So if you pass 9173 you should be OK.

Michael
-- 
Michael Peppler  -  mpeppler@peppler.org  -  http://www.peppler.org/
Sybase DBA/Developer
Sybase on Linux FAQ: http://www.peppler.org/FAQ/linux.html


Note: This e-mail contains privileged and confidential information and is for the sole use of the intended recipient(s).  If you are not an intended recipient, you are hereby kindly requested to refrain from printing, copying, or distributing the information contained herein.  Furthermore, any other use of the information contained herein is strictly prohibited.  If you have received this transmission in error, please kindly notify the sender immediately and destroy all copies of the original message.