Re: SQR 4.3.4 Error - Executing Cursors

["J.-Bernard Favre" <jean-bernard.favre@MOTOROLA.COM>]

I had a similar problem (yesterday), but not exactly the same error message.
I added a 'NULL' column in the begin-select like:

let $col_null='NULL'

begin-select
[$col_null] &colnul=char
xref.voucher_id

  let $vchr_found = 'Y'
  let $voucher_id = &xref.voucher_id

from [$cx_ap_xref] xref
where xref.invoice_id = &ap.invoice_id and
      xref.origin = &ap.origin and
      xref.business_unit = &ap.business_unit and
      xref.batch_type = 'V'
end-select


I cannot guarantee it will work, you can always try.
Jean-Bernard.




Melanie Hershey wrote:

> This is a repost about getting the "problem executing cursor" error. I've
> been through the archives and haven't found anything that sounds like a
> solution to my particular problem.
>
> Here's the message I previously posted:
>
> "In addition to doing a Psoft upgrade, we are also in the process of
> upgrading to SQR version 4.3.4 (from 3.0.7.3) and are encountering the
> following error message intermittently when running an SQR program on our
> unix server:
>
> (SQR 5528) INFORMIX SQL OPEN/EXECUTE error -404 (ISAM: 0) in cursor 11:
>    The cursor or statement is not available.
> Error on line 375:
>    (SQR 3723) Problem executing cursor.
>
> Line 375 starts the following select:
>
> begin-procedure Get-Voucher-Id
>   #Debug display 'Getting Voucher Id'
>
> let $vchr_found = 'N'
>
> begin-select
> xref.voucher_id
>
>   let $vchr_found = 'Y'
>   let $voucher_id = &xref.voucher_id
>
> from [$cx_ap_xref] xref
> where xref.invoice_id = &ap.invoice_id and
>       xref.origin = &ap.origin and
>       xref.business_unit = &ap.business_unit and
>       xref.batch_type = 'V'
> end-select
>
> This procedure is called for each line in another table.  When running this
> select statement and plugging in the bind variables in an outside SQL
> session it runs fine.  Also, the statement generally executes fine for the
> first call to the procedure and errors out on the second call.  Another
> thing to note is that when we run the SQR on the client, there are NO
> problems.  Does this ring any bells? Are there any other environment
> variables or configuration files that I should look at?
>
> Any advice or insights would be greatly appreciated.
> Thanks!
> Melanie Hershey
> Carmax Auto Superstores
> Financial Systems Development
>
> FYI - We are upgrading all of the following at this point:
> Unix OS from HPUX 10.2 to HPUX 11
> Informix from 7.30.UC7 to 7.31.FS7 (64-bit)
> Informix Connectivity from I-Connect to SDK 2.40 HC1
> PeopleTools from 7.03 to 7.07
> PS App from 7.01 to 7.02
> SQR from 3.0.7.3 to 4.3.4
> Tuxedo from 6.3 to 6.5"
> ----------------
> After more research, my I'm thinking that there is a difference between the
> client SQR executable and the UNIX SQR executable in the way SQR is
> translating the code to communicate with an Informix database.  I read on
> an Informix website that this error will occur when you try to reuse a
> cursor that has had a CLOSE or FREE statement issued.  Does anyone know how
> I could determine where this is happening?  Is there an SQR trace that will
> show me the Informix commands being sent to the database? This has me
> completely puzzled, so any assistance would be appreciated....
>
> Thanks!