|
|
sybperl-l Archive
Up Prev Next
From: Michael Peppler <mpeppler at MBAY dot NET>
Subject: problem with custom callback functions
Date: Mar 3 1999 1:52AM
John_Erjavec@cargill.com writes:
> All-
>
> Has anyone run into weird callback problems before? Here is what is going on
> with mine. When I run the program with the callback functions, I get the
> following error message:
>
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Start of ASE 11.9.2 upgrade.
> Step 3 -- Dropping LynxSP.
> Use of uninitialized value at ./rssd_1192_upgrade.spl line 163, chunk
> 1 (#1)
>
> (W) An undefined value was used as if it were already defined. It was
> interpreted as a "" or a 0, but maybe it was a mistake. To suppress this
> warning assign an initial value to your variables.
That's a benign message (usually).
>
> ct_cmd_alloc failed at ./rssd_1192_upgrade.spl line 163, chunk 1.
>
This one's the real problem. Why does ct_cmd_alloc() fail? What does
line 163 look like?
> Open Client Message: (In msg_cb)
> Message number: LAYER = (1) ORIGIN = (1) SEVERITY = (1) NUMBER = (60)
> Message String: ct_con_drop(): user api layer: external error: There is a usage
> error. This routine has been called at an illegal time.
This is probably because of the error above - it tries to drop the
context, but the internal state of CTlib is somehow inconsistent.
The real problem is the ct_cmd_alloc() failure.
Michael
--
Michael Peppler -||- Data Migrations Inc.
mpeppler@mbay.net -||- http://www.mbay.net/~mpeppler
Int. Sybase User Group -||- http://www.isug.com
Sybase on Linux mailing list: ase-linux-list@isug.com
|
