Basic Work Management Was: Check your ancient performance settings -- MIDRANGE-L

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

Subject: Basic Work Management Was: Check your ancient performance settings
From: Rob Berendt <rob@xxxxxxxxx>
Date: Wed, 9 Oct 2019 12:44:02 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Patrik,
I understand where you are coming from. I have some lpars where system value QCTLSBSD is still set to the default of QBASE and not QCTL. However those lpars run no traditional interactive or batch processes. They are primarily Domino lpars.

While memory is a big factor it isn't the only consideration in using different subsystems and memory pools. Things like time slices and other factors come into play. However I just don't have time to delve into this. I took a cursory glance at wiki.midrange.com to see if they discuss some of the rudimentary aspects of work management, memory pools and that like but, not yet.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Basic Work Management Was: Check your ancient performance settings , Patrik Schindler

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.