MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » January 2013

RE: JDE QZDASOINIT restarts



fixed

That's the application opening and closing the connections; ie not using connection pooling. When the connection is closed, the QZDASOINIT job ends. In fact, it could be a bunch of applications. I've seen that situation with Microsoft Query being run within Microsoft Excel. User opens up a spreadsheet, Query connects and pulls down a little data, user closes the spreadsheet, and QZDASOINIT job ends having five or six uses. If you have a hundred users doing that all day, you burn through a lot of QZDASOINIT jobs.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Thursday, January 03, 2013 6:34 PM
To: Midrange Systems Technical Discussion
Subject: Re: JDE QZDASOINIT restarts

Dan,

The QZDASOINIT jobs were getting somewhere in the neighborhood of 4 -6 uses before they are restarted, so clearly IBM i is not dong the restarts. Even changing the prestart job to a much higher number of uses did not cure the problem, so clearly it's an application somewhere that's causing the problem. There are significant number of QZDASOINIT jobs running and with that number of jobs at 200 uses each this system would go a week without a restart. Again clearly there is a setting somewhere that is causing the problem.

I know the work management portion of it extremely well, it's the JDE processes I don't know.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 1/3/2013 6:21 PM, Dan Kimmel wrote:
The prestart job entry for QZDASOINIT jobs has them ending after 200 uses by default. That has nothing to do with JDE, just the way the subsystem (QUSRWRK) comes preconfigured from IBM. You can change it. (Well, delete the prestart entry and make a new one). The F1-help behind that in ADDPJE has some comments about keeping the number of uses relatively small to keep from running out of log space or user storage max usage. 200 uses might be roughly equivalent to two hours. There's roughly one QZDASOINIT job for each JDBC/ODBC connection. We use connection pools extensivily in our code and QZDASOINIT jobs will stay up for a long time, depending on how the connection pool and the prestart job entries are configured.

-----Original Message-----
From:midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Thursday, January 03, 2013 1:20 PM
To: Midrange Systems Technical Discussion
Subject: JDE QZDASOINIT restarts

Does anyone know if the JDE (Older version running V5R4) automatically restarts the QZDASOINIT jobs every two hours, or if there is a function inside JDE to accomplish this? If so, any clues on how to turn it off would be greatly appreciated.

Regards;

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

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








Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact