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



QZDASOINIT jobs are worker jobs autostarted by the QUSRWRK subsystem
when the subsystem is started. If you want to end them and restart them,
end the subsystem and then start it again. Look in the subsystem
description for QUSRWRK and then under autostart jobs and you'll see
QZDASOINIT. In that declaration, you'll see what job description is used
to start the job. It is NOT the user profile jobd. These jobs are
configured to NOT produce job logs. You can change the job description
logging level, end and restart the subsystem, and then check QEZJOBLOG
for logs.

These are the jobs that handle ODBC and JDBC requests. They don't listen
on the IP port, another job does that. These jobs perform the
interaction with the SQL database engine and return the results, then
wait for something else to do.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Dixon
Sent: Thursday, September 18, 2008 2:13 PM
To: Midrange Systems Technical Discussion
Subject: Re: Prestart jobs QDASSINIT, QZAINIT, QZDASOINIT failing

Scott

There doesn't seem to be a previous command. The job is submitted e.g.
003520/QUSER/QZDASONIT in subsystem QUSRWRK in QSYS (CPF1124) and then a
few seconds later MCH3601 is issued with nothing in between.

I don't know which command or program to check for logging level.

Any ideas?

Rob

2008/9/17 Ingvaldson, Scott <scott.ingvaldson@xxxxxxxxxx>

OK, also make sure that the message logging has LOGCLPGM(*YES) and
tell us what command is receiving the MCH3601. It should be one or
two lines before the MCH3601 message.

Regards,

Scott Ingvaldson
Senior IBM Support Specialist
Fiserv Midwest


-----Original Message-----
From: Rob Dixon [mailto:robertsdixon@xxxxxxxxx]
Sent: Wednesday, September 17, 2008 9:11 AM
To: Midrange Systems Technical Discussion
Subject: Re: Prestart jobs QDASSINIT, QZAINIT, QZDASOINIT failing

Thanks Scott,

I had already seen Richard Belles advice and tried it but it had no
effect.
I found the MCH3601 code from checking the log as he advised.

best wishes

Rob


2008/9/17 Ingvaldson, Scott <scott.ingvaldson@xxxxxxxxxx>

Generally MCH3601 would indicate a library list or authority issue.

Please see:
http://search400.techtarget.com/expert/KnowledgebaseAnswer/0,289625,
si
d3
_cid594816,00.html<http://search400.techtarget.com/expert/Knowledgeb
as eAnswer/0,289625,sid3_cid594816,00.html>

for advice from Richard Belles.

Regards,

Scott Ingvaldson
Senior IBM Support Specialist
Fiserv Midwest


-----Original Message-----
From: Rob Dixon [mailto:robertsdixon@xxxxxxxxx]
Sent: Wednesday, September 17, 2008 8:06 AM
To: Midrange Systems Technical Discussion
Subject: Re: Prestart jobs QDASSINIT, QZAINIT, QZDASOINIT failing

Thanks Simon,

The joblog for QZDASOINIT shows

MCH37601 From module QZDACRTP to module QZDACRTP

Message .. pointer not set for location referenced

I have checked QUSER profile, etc. and that seems OK.

Generally MCH37601 relates to incorrect parameters being passed but
in

this instance it is an OS/400 problem. I believe that I have
installed all the correct PTFs but of course I may have missed
something. Any ideas?

Thanks for your help again.

Best wishes

Rob Dixon

www.erros.co.uk
www.boarstall.com

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

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




--
Rob Dixon

www.erros.co.uk
www.boarstall.com

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

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




--
Rob Dixon

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




As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.