Re: Cannot connect using JDBC

Job . . : QZDASOINIT User . . : QUSER Number . . . :
139403


Job 139403/QUSER/QZDASOINIT started on 03/20/26 at 11:41:56 in
subsystem
QSERVER in QSYS. Job entered system on 03/20/26 at 11:41:56.

Tried to refer to all or part of an object that no longer exists.

Value for call stack counter parameter not valid.

Application error. MCH3402 unmonitored by QZDASRV at statement

0000031317, instruction X'0000'.

This job ended abnormally.

Job 139403/QUSER/QZDASOINIT ended on 03/20/26 at 11:41:56; .003 seconds

used; end code 30 .


And the individual messages:



Message ID . . . . . . : MCH3402 Severity . . . . . . . : 40

Message type . . . . . : Escape

Date sent . . . . . . : 03/20/26 Time sent . . . . . . :
11:41:56


Message . . . . : Tried to refer to all or part of an object that no
longer
exists.

Cause . . . . . : The most common cause is that a stored address to an

object is no longer correct because that object was deleted or part of
the
object was deleted.






Message ID . . . . . . : CPF24A3 Severity . . . . . . . : 40

Message type . . . . . : Escape

Date sent . . . . . . : 03/20/26 Time sent . . . . . . :
11:41:56


Message . . . . : Value for call stack counter parameter not valid.

Cause . . . . . : The value 5, specified for call stack counter
parameter,
is not valid. The value was specified in parameter number 7 on the API.

Recovery . . . : Correct the value for call stack counter parameter and
try
the request again. This value must be greater than or equal to 0 but
cannot
be larger than the number of entries on the call stack.




Message ID . . . . . . : CEE9901 Severity . . . . . . . : 30

Message type . . . . . : Diagnostic

Date sent . . . . . . : 03/20/26 Time sent . . . . . . :
11:41:56


Message . . . . : Application error. MCH3402 unmonitored by QZDASRV at

statement 0000031317, instruction X'0000'.

Cause . . . . . : The application ended abnormally because an exception

occurred and was not handled. The name of the program to which the

unhandled exception is sent is QZDASRV QZDACMDP PRE_START_SETUP. The
program
was stopped at the high-level language statement number(s) 0000031317 at
the
time the message was sent. If more than one statement number is shown,
the
program is an optimized ILE program. Optimization does not allow a
single
statement number to be determined. If *N is shown as a value, it means
the
real value was not available.

Recovery . . . : See the low level messages previously listed to locate
the
cause of the exception. Correct any errors, and then try the request
again.













On Fri, Mar 20, 2026 at 1:31 PM Jim Franz <franz9000@xxxxxxxxx> wrote:

if you are not getting a joblog - check the job description values for
logging - wrkjobd qdftsvr

Job description . . . . . . . . . . . . . . . . . : QDFTSVR
...
Severity . . . . . . . . . . . . . . . . . . . : 0
Text . . . . . . . . . . . . . . . . . . . . . : *SECLVL
Log CL program commands . . . . . . . . . . . . . : *YES


if not finding the joblogs - could be pending - look at WRKJOB QZDASOINIT
- also make sure user profile quser not disabled

Jim Franz

On Fri, Mar 20, 2026 at 1:04 PM Rob Berendt <robertowenberendt@xxxxxxxxx>
wrote:

What is in the QZDASOINIT joblog?

On Fri, Mar 20, 2026 at 12:20 PM Mark Murphy <jmarkmurphy@xxxxxxxxx>
wrote:

I am having trouble with JDBC connectivity. QZDASOINIT will not stay
running. The tech group has replaced an IO card twice in an attempt to
correct the issue, but the same issue remains. I was just wondering if

any

of the wizards here have any troubleshooting advice. I can connect

using

Access Client Solutions, but RDi and SQL clients like DBeaver fail to
connect. I can ping, and JPing from the toolbox works as well.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related

questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.