I second the opinion on using ODBC perhaps so you can code in Windows and quickly deploy in the IFS.
One other thought that could be contributing: If you are using CALL QP2TERM there are potential issues with multi-threading that could be at work. In other words not available.
Potentially better to use SSH and bash if you can to run the node commands from an SSH shell. Then multi-threading should not be an issue.
I was a die-hard QSH/QP2TERM user until I discovered using SSH, bash and my good buddy Midnight Commander.
Regards,
Richard Schoen
Web:
http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
----------------------------------------------------------------------
message: 1
date: Wed, 3 Jun 2020 10:26:46 -0500
from: Steve M via OpenSource <opensource@xxxxxxxxxxxxxxxxxx>
subject: [IBMiOSS] Node/Express/DB2
Okay, I surrender. The divot on my desk, matching my forehead, is getting quite deep from repeated pounding.
I am sure I am missing something very simple here, but for the life of me I can't figure out what.
Developed a project, on my PC, using Node and using NPM installed Express, Path, JDBC and it works fine being locally hosted and accessing data on DB2.
Created a new folder on my IFS, then went to Call QP2Term and navigated to the folder. NPM INIT worked fine. NPM install of Express and Path, no issues.
Tried to NPM install JDBC and received a failure, as near as I can tell, from this: as400 Error: java@0.12.1 <mailto:java@0.12.1> install:
`node-gyp rebuild`
It seems to be related to a child-process rebuild during the install. After being unable to resolve this issue, I then found an example which was using
this:
"var db = require('/QOpenSys/QIBM/ProdData/Node/os400/db2i/lib/db2');
I looked in my IFS and have nothing like that. My Node installation appears to be here: /QOpenSys/pkgs/lib/nodejs8
I am sure I have gotten myself all twisted up somewhere.
midrange.com
