QSYSWRK - put in own memory pool. -- 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: QSYSWRK - put in own memory pool.
From: Gerald <gmagnuson@xxxxxxxxxxxxx>
Date: Fri, 22 Feb 2008 09:57:35 -0600
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Has anyone here put the QSYSWRK subsystem in its own pool?

The difficult part of this was the pre-start and auto-start jobs have a pool parameter that needs changed.
I was attempting to do this, by creating a duplicate subsystem description in another library, but I am not sure how QSYSWRK gets started. It doesn't appear to get started out of my startup program, since I qualified the library, and it didn't start, the description in QSYS did start.

Thanks,

Gerald

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: QSYSWRK - put in own memory pool. , rob

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.