Re: Problem in Result Set with No Error

Marvin,

I don't understand why you're manually adding x'00' to your string. This is not a call to a C routine, so that doesn't make a lot of sense. (Java does not use null-terminated strings like C does -- unless your application specifically requires this?) Even if it did use null-terminated strings, coding x'00' manually is generally a bad practice unless you're coding for V3r2... you should use options(*string) instead.

With regards to your question: Errors are printed to the standard error/stdout data streams, not logged somewhere. If you're running this interactively, you'll see them flash on the screen quickly.

You can override them to go to a printer file with commands like these:

OVRPRTF FILE(STDOUT) TOFILE(QSYSPRT) HOLD(*YES)
OVRPRTF FILE(STDERR) TOFILE(QSYSPRT) HOLD(*YES)

This would be run before the JVM is started (so start a fresh job if you already loaded Java) and the files won't be closed until the JVM ends, so that'd be at the end of the job.

Having said that... it's also possible that there simply isn't an error. You say that you're not getting a result set... but many, many, many stored procedures simply don't return result sets, so not having one wouldn't be considered an error.

-SK


On 1/30/2018 10:36 AM, Marvin Radding wrote:

I am trying to execute a stored procedure on a remote system. The request goes through and no error is reported but I have no result set. Where on the AS/400 are the java logs stored or where can I look to see where they are.

Here is the code:

String = 'SP_get_Membership ' + %trim(manager) + x'00';

stmt = JDBC_PrepCall(conn: String);

IsResultSet = jdbc_execCall(stmt);

if not IsResultSet;
return *on;
endif;
return *off;

The connection is good and the stmt has a value but the IsResultSet is zero, which I take to be null and no result set to be retrieve.

I got it to the point there the is no error reported but I get no result set.

Anybody have any ideas where to go now that it seems to work but doesn't?

Thanks,

Marvin

---
This email has been checked for viruses by AVG.
http://www.avg.com