What about an app accessing an allowed resource, and the dev creates a new connection for every request, without closing any? Those jobs may eventually time-out, but in the short term that means a lot of extra jobs.
-----Original Message-----
From: Jim Oberholtzer [mailto:midrangel@xxxxxxxxxxxxxxxxx]
Sent: Saturday, June 30, 2018 2:45 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Lots of QZDASOINIT jobs
Not true. You can control prestart jobs, how many, how often they restart, memory, class etc.
You can also use the exit points to limit who, and when they can connect.
We've discussed this before.
It's standard work management and security controls. The system manager controls that, not the developers.
Jim Oberholtzer
Agile Technology Architects
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
