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



I think your understanding is correct, however:

If the queries that run in QZDASOINIT and just moved to the QSQSRVR jobs all
you're doing is moving the workload from one point to another causing your
administrator different pain. QZDASOINIT and QSQSRVR do not really operate
all that differently. They are both prestart jobs and both deal with SQL.
First off I would check to be sure the SQL statements are correctly written
and all the appropriate indexes are built.

If that's true then the administrators has to understand that is real work
and they have to run it. Balance out the system by tuning it properly and
if that's not enough make a case for more horsepower.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Kelly
Cookson
Sent: Sunday, February 15, 2015 9:27 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Does Node.JS create QZDASOINIT jobs?

When the Node.JS event loop passes something off to be processed (using a
callback), does that create a QZDASOINIT job?

By on my limited understanding, I wouldn't think so. I think QZDASOINIT jobs
are for apps using JDBC and ODBC/OLD DB connections. But I could be wrong. I
don't have Node.JS yet, so I can't check it myself yet.

I'm want to know because our system administrator is already complaining
about the resources used by QZDASOINIT jobs by apps using the .NET Data
Provider. I would like to know if I can leverage this as a selling point for
using Node.JS instead of the .NET Data Provider.

Thanks,

Kelly Cookson
IT Project Leader
Dot Foods, Inc.
1.217.773.4486 ext. 12676
kcookson@xxxxxxxxxxxx<mailto:kcookson@xxxxxxxxxxxx>


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