×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
When the "use block insert" property is set to true, it fails with a
message:
"Error occurred in SQL Call Level Interface - HY009 "
There's a job log created which has the following:
SQ99999 Diagnostic 30 12/16/08 08:53:35.935112
QSQCLI QSYS *STMT QJVAJDBC QS
From module . . . . . . . . :
SQLPO
From procedure . . . . . . :
SQLParamOptions
Statement . . . . . . . . . :
4742
To module . . . . . . . . . :
QJVACLII
To procedure . . . . . . . :
JDBCParamOptions
Statement . . . . . . . . . :
4
Message . . . . : Error occurred in
SQL Call Level Interface
Cause . . . . . : A procedure call
encountered an error. The error code is
9. Error codes are: 3 -- Program type
out of range. 4 -- SQL data type out
of range. 9 -- Argument value not
valid. 10 -- Function sequence error. 12
If I change "use block insert" to FALSE, it works fine.
Also, I can leave "use block insert" to TRUE and have it work if instead of
batching the inserts, I do them one at a time:
try {
Statement stmt = sqlConn.createStatement();
ResultSet rs = stmt.executeQuery("select varchar05, intfld,
varchar02 " +
" from
CINTAS.cadmin.sometable");
PreparedStatement ps = i5Conn.prepareStatement("INSERT INTO
CINTASDTA.INACTCAB VALUES(?,?,?)");
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.