×
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.
The 'command length error' will occur when the data type of the
second parameter was not cast to the expected P(15, 5) that CL wants.
Rob presumably has an [external] SQL PROCEDURE definition to handle 95
typed as packed (15, 5). Replacing ",95);" with ", 0000000095.00000);"
will expose the noted errors, due to the length being insufficient to
describe the total string length being passed.
IMO the best solution is to create a SQL procedure that takes only a
single parameter, a VARCHAR command string, and pass that to QCMDEXC,
instead of coding directly to the QCMDEXC. Let the SQL procedure pass
LENGTH(CmdString) as the second parameter to QCMDEXC.
I think how to do that was covered here recently; past couple months.
Regards, Chuck
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
