Re: User-defined subsystems -- MIDRANGE-L

Subject: Re: User-defined subsystems
From: rob@xxxxxxxxx
Date: Tue, 24 Mar 2009 16:44:05 -0400
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>

Other things to consider with a user written subsystem.
1. Operational attributes
Make sure that the maximum jobs in the subsystem fits your needs.

2. Pool definitions
Match those up with WRKSHRPOOL. Normally people put two entries. *BASE
and another. You control the other by the routing entries (discussed
below).

6. Job queue entries

7. Routing entries
Pay attention to the pool entries.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 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.