I am writing a series of blogs on prestart jobs. Two articles on PJE configuration and tuning were recently published. These articles review the key parameters and considerations for how to set them.

http://ibmsystemsmag.com/blogs/i-can/july-2018/prestart-job-configuration-settings/
http://ibmsystemsmag.com/blogs/i-can/july-2018/display-active-prestart-jobs/

I will have several more articles on managing prestart jobs in the upcoming weeks.


Changes to prestart job entries happen over time. Active prestart jobs are not affected. Prestart jobs that are started after the PJ entry is changed do pick up the new values. If you are using a MAXUSE value of 200, it will take time for those jobs to reach their maximum use count and be ended.


Dawn

Dawn May Consulting, LLC

________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> on behalf of Christopher Bipes <chris.bipes@xxxxxxxxxxxxxxx>
Sent: Tuesday, July 24, 2018 12:26 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: V7R1 SQL performance

Thank you for the response. I went through all the cover letters and the only fixes applied were JAVA. What I did find is:
1. QZDASOINIT prestart job was not configured for our rapid connections. Initial number of jobs=1, threshold of 1, additional of 2, max use of 2. - Change to init=10, threshold=5, additional left at 2 and max use of 200 - the normal.

2. Asked our programming staff to review how they connect from WebSphere running on Windows as the connections are not being reused and left idle until the keep alive probe closes the connection. (currently 60 minutes.)

Hopefully the Band-Aid I put in place keeps us from having internal users screaming at us again.





Chris Bipes
Director of Information Services
CrossCheck, Inc.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Tuesday, July 24, 2018 5:50 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: V7R1 SQL performance

I would have thought that, if you upgraded to 7.1 only a month ago,
and you put on the 7.1 PTFs just last weekend
you would have gotten few if any new PTF's, unless,
- you didn't apply any PTFs when you upgraded to 7.1 (a huge no-no unless
you're one of those gods who generate their own distribution media with
the latest PTFs on a frequent basis)
- you used an ancient copy of PTF's shipped to you a decade or so ago with
7.1

This late in the game I would suspect there would be few dramatic 7.1 PTFs
which would change SQL function like that. But, what the hey, you're
paying through the nose for extended support, open a ticket.

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD

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.