Yes the iSql class is deprecated and will be removed in v2.x. We are releasing v1.0.0 soon so I expect iSql to still be supported for some time.

We recommend users to migrate to the odbc, idb-connector, or idb-pconnector npm packages. These are much better SQL interfaces for IBM i and should be used instead. In your case, use odbc to connect to Db2 from your linux server. Refer to the odbc setup guide for instructions.

I do agree with if one wants to query tables outside of the job's QTEMP. What I have been doing is calling a program, it dumps into QTEMP and then I select * from qtemp/table in the same XMLSERVICE call which is fronted by a CL to manage and it also cleans up the QTEMP files. I will have to refactor to return a DS array. This is not a problem to make it is just that it was an easy pattern when working with the senior RPG programmers.

Thank you all for all of the great work with this package!

As @abmusse said, we plan to support iSql for some time and the SQL capabilities of XMLSERVICE aren't going away so I suppose one could always generate the XML themselves and pass it to the toolkit (or fork the iSql classes/functions if/when needed).

Additionally, you can use the node-odbc transort in the upcoming v1.0 instead of REST. By using the default *here control option for XMLSERVICE, the program should be called in the SQL job so then you could query with odbc instead of iSql.

@kadler, you bring up a good point. I was too fixed on rest I have forgotten about the odbc option of the connection. Thank you for the hint! I'll do that instead.

Will you all consider the ability to set an existing opened odbc connection to the odbc transport?
This should should allow me to open a connection, which establishes a job, then I can use the toolkit to make the program call, and finally I can use the same odbc connection to query the QTEMP files.

Ahh, right. I forgot that the Node version of this package opens its own connection and closes it every time you call it. I've definitely had that idea, perhaps we can target it for v1.1 or beyond.

👋 Hi! This issue has been marked stale due to inactivity. If no further activity occurs, it will automatically be closed.

I think we can close this one out as the original question is answered and we are tracking the ability to use an existing connection in the open PR.