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



Very true

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Evan Harris
Sent: Tuesday, April 01, 2014 9:25 PM
To: Midrange Systems Technical Discussion
Subject: Re: QZDASOINIT prestart job tuning

Agreed. I was just making the point that having a pre-start job there waiting would be even more important if you did this - I wasn't recommending it one way or the other.


On Wed, Apr 2, 2014 at 2:12 PM, Mike Cunningham <mike.cunningham@xxxxxxx>wrote:

I think setting the uses to 1 is going ti have an impact on overall
system CPU use. I think initial job startup is one of the more
resource intensive tasks.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Evan Harris
Sent: Tuesday, April 01, 2014 6:29 PM
To: Midrange Systems Technical Discussion
Subject: Re: QZDASOINIT prestart job tuning

Hi Chris

I've changed the initial number of jobs in the past, and seen other
customers do this as well, in order to get the preferred number of
jobs activated as part of starting the subsystem. At one customer it
was set to
3,000 but I bet there are others out there with significantly higher
settings.

I'd set the number of jobs at around 750-800 maybe even a little
higher in your case (say 850), particularly if you are going to change
the maximum number of uses to 1. In that case you would want a job
available for new connections as they connect rather than having them
delayed while a job starts up.


On Wed, Apr 2, 2014 at 11:20 AM, Chris Bipes
<chris.bipes@xxxxxxxxxxxxxxx
wrote:

Has anyone made changes to the QUSRWRK subsystem for the QZDASOINIT
prestart job?

I am looking at the ramification of changes the maximum number of
uses to
1 so they recycle after every connection. Also changing the initial
number of jobs and threshold. Even the additional number of jobs.

We have what I assume is the default:
Job . . . . . . . . . . . . . . . . . . . . . . : QZDASOINIT
Job description . . . . . . . . . . . . . . . . : *USRPRF
Library . . . . . . . . . . . . . . . . . . . :
Start jobs . . . . . . . . . . . . . . . . . . . : *YES
Initial number of jobs . . . . . . . . . . . . . : 1
Threshold . . . . . . . . . . . . . . . . . . . : 1
Additional number of jobs . . . . . . . . . . . : 2
Maximum number of jobs . . . . . . . . . . . . . : *NOMAX
Maximum number of uses . . . . . . . . . . . . . : 200
Wait for job . . . . . . . . . . . . . . . . . . : *YES

We currently have 747 running with a peak of 806 and 746 in use.
Peak usage is 805. Any suggestions on what I should set the values at?

--
Chris Bipes
Director of Information Services
CrossCheck, Inc.

707.665.2100, ext. 1102 - 707.793.5700 FAX
chris.bipes@xxxxxxxxxxxxxxx<mailto:chris.bipes@xxxxxxxxxxxxxxx>
www.cross-check.com
<../../../../jj/Application%20Data/Microsoft/Signatures/
www.cross-check.com>

Notice of Confidentiality: This e-mail, and any attachments thereto,
is intended only for use by the addressee(s) named herein and may
contain legally privileged and/or confidential information. If you
are not the intended recipient of this e-mail, you are hereby
notified that any dissemination, distribution or copying of this
e-mail, and any attachments thereto, is strictly prohibited. If you
have received this e-mail in error, please immediately notify me by
e-mail (by replying to this message) or telephone (noted above) and
permanently delete the original and any copy of any e-mail and any
printout thereof. Thank you for your cooperation with respect to this matter.

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




--

Regards
Evan Harris
--
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.

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