|
|
sybperl-l Archive
Up Prev Next
From: "Ashish Gupta" <ashish dot gupta at mizuho-sc dot com>
Subject: RE: sybperl ct_config CS_RETRY_COUNT
Date: Aug 26 2005 12:57AM
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
The files in that directory are as follows:
/export/home/guptaash/perl/lib/site_perl/5.8.6/sun4-solaris-thread-multi
/auto/Sybase/CTlib> ls -l
total 738
-r--r--r-- 1 guptaash staff 0 Jul 5 17:27 CTlib.bs
-r-xr-xr-x 1 guptaash staff 363228 Jul 5 17:27 CTlib.so
-r--r--r-- 1 guptaash staff 94 May 16 13:39 autosplit.ix
Thanks again for all your help.
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 1:00 AM
To: ashish.gupta@mizuho-sc.com
Cc: sybperl-l@peppler.org
Subject: Re: sybperl ct_config CS_RETRY_COUNT
On Thu, 2005-08-25 at 16:53 +0900, Ashish Gupta wrote:
>
> If I want to restrict the number of retries, using the following
> command :
>
> ct_config(CS_SET, CS_RETRY_COUNT, 2, CS_INT_TYPE);
>
> I get the following errors :
>
>
> Argument "CS_RETRY_COUNT" isn't numeric in subroutine entry at b.pl
> line 12.
I guess CS_RETRY_COUNT isn't exported.
Try:
ct_config(CS_SET, &Sybase::CTlib::CS_RETRY_COUNT, 2, CS_INT_TYPE);
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.
|