A JavaScript (Node.js) library for communicating with Db2 for IBM i, with support for queries, procedures, and much more. Uses traditional callback-style syntax
MIT License
38
stars
23
forks
source link
Error SQLSTATE=38501 SQLCODE=-443 does not return the true message #140
Hi,
When executing from Node a system command like dbstmt.exec( "CALL QCMDEXC('ENDSBS xxxxx OPTION(*IMMED)' )" ) , where "xxxx" doesn't exists :
with the idb-connector, i obtain a generic error message Trigger program or external routine detected an error. SQLSTATE=38501 SQLCODE=-443
with a OLEDB connector, I obtain a more concise error message CPF1054: No subsystem xxxxx active
In my code, I found an old test on this "CPF1054" string, and I'm pretty sure I got this kind of information in a previous version of the idb-connector.
Is it a design choice? Is it possible to find these details in the error messages?
Hi, When executing from Node a system command like
dbstmt.exec( "CALL QCMDEXC('ENDSBS xxxxx OPTION(*IMMED)' )" )
, where "xxxx" doesn't exists :with the idb-connector, i obtain a generic error message Trigger program or external routine detected an error. SQLSTATE=38501 SQLCODE=-443
with a OLEDB connector, I obtain a more concise error message CPF1054: No subsystem xxxxx active
In my code, I found an old test on this "CPF1054" string, and I'm pretty sure I got this kind of information in a previous version of the idb-connector.
Is it a design choice? Is it possible to find these details in the error messages?
Thanks