Our application development team are currently trying out node.js (v6)
as a proof of concept on our IBM i, but have hit a number of problems
already with accessing local DB2 tables using the (new) DB2 toolkit functions.
Is anybody else trying it out and encountering the the sort of
problems we have been, which are such things as...
1. Intermittent memory fault/core dump errors on repeated fetches.
2. Truncation occurring when retrieving the contents of text columns
3. Intermittent failure and error 'SQLSTATE=22504 SQLCODE=-191 Mixed
data or UTF-8 data not properly formed.' when inserting a row into a
table with an empty string ('') value for a text column.
The developer has had to do workarounds for the issues he's found, but
they aren't ideal. Some involve having to use blocking functions
instead of non-blocking.
I've opened PMRs for all of these which are being looked at but was
wondering what others experiences have been and whether we are just
unlucky, possibly doing something wrong, or others have found the same.
I'm trying to advocate IBM i as being the right platform to use for
these sort of projects since 5733OPS was made available, but it's
getting harder to justify with each issue that's found.
This is the IBMi Open Source Roundtable (OpenSource) mailing list To
post a message email: OpenSource@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
or email: OpenSource-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.