× 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.



Rob,

The errors from JDBCR4 are written to the STDERR data stream. By default, these would appear on the display if you're in an interactive job, but a common issue is that they scroll off the display faster than they can be read.

I would suggest doing something like this:

OVRPRTF FILE(STDOUT) TOFILE(QSYSPRT) HOLD(*YES)
OVRPRTF FILE(STDERR) TOFILE(QSYSPRT) HOLD(*YES)
call your jdbcr4 program
SIGNOFF (or end job)

This should result in error information being sent to spooled files that you can look at after the job has ended.

The error messages will be much more helpful than debugging the code.


On 5/3/17 6:38 PM, Robert Rogerson wrote:
Our network folks can't see any reason why TELNET can access the server
but JDBCR4 can not.

Does anyone know if there's a log file (or can one be turned on) that
might shed some light on the issue?

Thanks,

Rob


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.