search

IBM / nodejs-idb-connector

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
37 stars 23 forks source link

db2ia.node symbol resolution failed #51

Closed abmusse closed 5 years ago

abmusse commented 5 years ago

Original report by Gary Patterson (Bitbucket: gpatterson317, GitHub: Unknown).

IBM i V7R3, Node V6.11.5 Just installed idb-connector and itoolkit via npm.

Testing data queue:

var xt = require("itoolkit");
var dq = require("itoolkit/lib/idataq");

var conn = new xt.iConn("*LOCAL", "validuser", "validpw"); var dtq = new dq.iDataQueue(conn);

dtq.sendToDataQueue("TESTQ", "MYLIB", "Hello World!"); console.log(dtq.receiveFromDataQueue("TESTQ", "MYLIB", 12));
dtq.clearDataQueue("TESTQ", "MYLIB");

-bash-4.4$ node dtaq.js module.js:597 return process.dlopen(module, path._makeLong(filename)); ^

Error: Symbol resolution failed for /home/garyp/qhc080/node_modules/idb-connector/lib/binding/Release/node-v48-ibmi-ppc/db2ia.node because: Symbol napi_call_function (number 90) is not exported from dependent module node. Symbol napi_close_escapable_handle_scope (number 91) is not exported from dependent module node. Symbol napi_close_handle_scope (number 92) is not exported from dependent module node. Symbol napi_coerce_to_bool (number 93) is not exported from dependent module node. Symbol napi_coerce_to_number (number 94) is not exported from dependent module node. Symbol napi_coerce_to_string (number 95) is not exported from dependent module node. Additional errors occurred but are not reported.

abmusse commented 5 years ago

Original comment by Gary Patterson (Bitbucket: gpatterson317, GitHub: Unknown).

PTF SI68770 resolved issue. Thanks Jesse G.

abmusse commented 5 years ago

Original comment by Jesse G (Bitbucket: ThePrez, GitHub: ThePrez).

Greetings. The itoolkit package has been reworked to use the newer N-API interface for native add-ons. You will need version 6.14.2 or newer, per https://nodejs.org/api/n-api.html#n_api_n_api_version_matrix

This should be resolved if you load the latest PTF's. SI68770 Is the latest, but it might not have hit distribution yet. SI68287 should be good enough.