Re: MAJOR information leaked out in TFM

Alfred,

Since you have first hand experience with it then I must be missing something. My code is identical to what you posted below and I get nothing back from the i5_fetch_assoc() function except the parm I sent in. I don't get a result set. I even changed my code according to a message sent by Sylvain about needing to call the i5_next_result() function once and still no luck.

Glenn

On 4/15/2010 11:48 AM, ADelgado@xxxxxxxxxxxxxxxxxx wrote:

Glenn,

The solution that I provided Tom is based on first hand knowledge, not
simply an interpretation of the manual. The code sample that I provided
using i5_paramdesc( ) was based on code that Tom said was correctly
executing his stored procedure but wasn't returning a result. The number
of parameters described and the specific descriptions would be unique to
that particular stored procedure.

Here is the code once again.

$statuscode='XX';
$qUpdateCustomer = "CALL NEWJCLIB/PROC_JC15_SL( ? )";

$request = i5_prepare( $qUpdateCustomer );
if( !$request ) var_dump( i5_error( ) );
$paramDesc = i5_paramdesc( $request, I5_TYPE_CHAR, 0, 5, 0, I5_INOUT
); // I guessed at 5 for the length
if( !$paramDesc ) var_dump( i5_error( ) );
$paramSet = i5_setparam( $request, 0, $statuscode );
if( !$paramSet ) var_dump( i5_error( ) );
$procExec = i5_execute( $request );
if( !$procExec ) var_dump( i5_error( ) );
$stuff = i5_fetch_assoc( $request );
var_dump( $stuff );

We established earlier in the thread that Tom was making a proper working
connection via i5_connect( ). With the code sample above I'm assuming that
Tom's stored procedure is defined with an input/output parameter of data
type CHAR. I guessed a length of five and commented on my guess in case
the actual length is two, etc.

Regards,
Alfred

--
Alfredo Delgado
6800 Broken Sound Pkwy, Suite 150
Boca Raton, Florida 33487