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