PEPPLER.ORG
Michael Peppler
Sybase Consulting
Menu
Home
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
Freeware
Sybperl
Sybase::Simple
DBD::Sybase
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
FAQs
Sybase on Linux FAQ
Sybperl FAQ
Personal
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: ldusadev at kestrok dot com (Rich Bailey)
Subject: RE: sybperl nt error
Date: Sep 16 1997 2:43AM

Haider:
You were right! Adding the & (Explicit subroutine call I think) did the trick!!!
Thanks a lot!
Rich
>Rich,
>
>I had the same problem of no output on NT. The problem seems to be in
>the 'ct_sql' code in 'CTlib.pm'. The way to resolve it is to add
>ampersands ('&') to all occurences of 'CS_SUCCEED', 'CS_ROW_COUNT',
>'CS_CMD_DONE' and 'CS_CANCEL_CURRENT' in that function.
>
>I have perl 5.001 with Sybperl 2.03 (DBlib ver 1.26 and CTlib ver 1.18)
>running on Windows NT 3.51.
>
>Regards,
>Haider.
>
>-------------------------------------------------------------------
>Haider Aziz,
>Caspian Securities Limited,
>199 Bishopsgate,
>London EC2M 3TY,
>England.
>http://www.caspinet.com
>
>>----------
>>From: 	ldusadev@kestrok.com[SMTP:ldusadev@kestrok.com]
>>Sent: 	05 September 1997 20:55
>>To: 	SYBPERL-L@trln.lib.unc.edu
>>Subject: 	Re: sybperl nt error
>>
>>*************************************************************************
>>WARNING: This message has been received via the Internet.
>>CAUTION:  No orders may be accepted via the Internet.
>>Any order received must be promptly confirmed verbally with the sender.
>>Any attachments received have been checked for viruses but should be 
>>treated with caution due to their origin over a public network.
>>*************************************************************************
>>
>>>Rich Bailey wrote:
>>>> 
>>>> >Rich Bailey wrote:
>>>> >>
>>>> >> #
>>>> >> #       @(#)ct_sql.pl   1.2     8/7/95
>>>> >> # Using the special one step query routine ct_sql().
>>>> >> use Sybase::CTlib;
>>>> >>
>>>> >> $d = new Sybase::CTlib axis, haleyling, rsdev;
>>>> >>
>>>> >> # ct_sql() returns a 'reference' to an array:
>>>> >> $ref = $d->ct_sql("select * from master..sysprocesses");
>>>> >>
>>>> >> foreach $line (@$ref)  # 'de-reference' the pointer
>>>> >> {
>>>> >>     print "@$line\n";
>>>> >> }
>>>> >>
>>>> >> ERROR MESSAGE:
>>>> >> C:\PROGRAMS\perl5\src>perl ct_sql.pl
>>>> >> Can't locate auto/Sybase/CTlib/ct_sql.al in @INC at ct_sql.pl line 12
>>>> >
>>>> >The AutoLoader may not work in that version of perl.
>>>> >
>>>> >Go to the perl5/Lib/Sybase directory, and edit DBlib.pm and CTlib.pm
>>>> >and move the __END__ token to the very end of the file.
>>>> >
>>>> >Michael
>>>> >--
>>>> >Michael Peppler       -||-  Data Migrations Inc.
>>>> >mpeppler@datamig.com  -||-  http://www.mbay.net/~mpeppler
>>>> >
>>>> >
>>>> Michael:
>>>> Thanks. Your suggestion worked. At least I did not get the previous error
>>>> and the script (above) now runs. HOWEVER, the script does not seem to
>>>> produce any o/p.
>>>> C:\PROGRAMS\perl5\src>perl ct_sql.pl
>>>> C:\PROGRAMS\perl5\src>
>>>> If I run this same script on the UNIX server directly I get lots of o/p.
>>>>So
>>>> it's probably something to do with my PC??
>>>> I have OpenClient 11.1 ( I believe it is 32 bit) for my PC.
>>>> Any ideas?
>>>
>>>My lack of NT experience is showing :-)
>>NO problem. My lack of Sybperl experience is more than showing ;-)
>>>
>>>Can you connect to the Sybase server using other means (maybe via
>>>wisql, for example?)
>>Yep. In fact I use SQLAdvantage. I have no problem with my OpenClient.
>>Though I have never tried an embedded C/SQL program that would use the
>>OpenClient API calls. But I suspect wisql, SQLAdvantage and such do use
>>them. I can ping the server and all other network issues are fine.
>>>
>>>Michael
>>>--
>>Thanks,
>>Rich
>>>Michael Peppler       -||-  Data Migrations Inc.
>>>mpeppler@datamig.com  -||-  http://www.mbay.net/~mpeppler
>>>
>>>
>>
>>
>*********************************************************************
>Caspian is not responsible for any securities related recommendation,
>solicitation, offer or agreement, or any information about any
>transaction contained in this communication.
>*********************************************************************
>
>