|
You could get it by calling the QMHRCVPM API. However, the RNX0301
puts some significant limits on the size of the exception string which,
in my experience, makes it very difficult to tell what the error
actually is.
Also, some of the code in JDBCR4 bypasses IBM's Java support for RPG and
calls the JNI APIs directly. This won't have the string limitation, but
also won't send an RNX0301... so that case would have to be handled
separately.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.