sybperl-l Archive

From: Vlad Markov <vlad dot dvoichenko-markov at bellatlantic dot com>
Subject: Re: Open Client Errors When executing statements
Date: Apr 17 1998 11:56AM

I used to get these errors when I did not have the processing loop for
processing returned results correct. In the examples shipped with
sybperl is an excellent example loop which can be used as a basis for
your own.

The first message is telling you that you haven't fetched all the
results back from your database call before issuing another one.

The second message is telling you the that you are trying to drop an
unfinished database call before you finished processing it.

I am pretty new at this myself. I suspect that someone has written a
production quality processing loop and each one of us are reinventing
the same wheel every time we write our own. Is it possible to write a
generic one?

Rashmi Anand wrote:
> 
> Hello,
> When I send a Select statement to Sybase using CTLib, I am getting the
> following errors:
> 
> If anyone has any insights...please reply (I am using sybperl on win95
> and I am getting some rows back)
> ERRORS are:
> 
> Open Client Message: Message number: LAYER = (1) ORIGIN = (1) SEVERITY
> = (1)
> NUMBER = (163) Message String: ct_results(): user api layer: external
> error: This routine
> cannot be called until all fetchable results have been completely
> processed.
> Open Client Message: Message number: LAYER = (1) ORIGIN = (1) SEVERITY
> = (1)
> NUMBER = (159) Message String: ct_cmd_drop(): user api layer: external
> error: This
> routine can be called only if the command structure is idle.
> 
> _________________________________________________________
> DO YOU YAHOO!?
> Get your free @yahoo.com address at http://mail.yahoo.com