RE: Use of QGPL library for custom objects -- MIDRANGE-L

Subject: RE: Use of QGPL library for custom objects
From: "Musselman, Paul" <pmusselman@xxxxxxxxxxxxxxxx>
Date: Fri, 9 Aug 2019 17:53:07 +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>

I think the big issue with QGPL is that early on some users were placing application programs, files, &c in QGPL, instead of in their own application libraries. Hence, the recommendations.

We've always used application libraries, including a set of 'utility' libraries with things like the backup programs &c.

We've stopped adding (most) things to QGPL, and really ought to look at the date of last use for everything in there, as well as QUSRSYS. We have individual job queues for each user, and if the 'remove user' process hiccoughs, they sometimes get left behind.

Paul E Musselman
PaulMmn@xxxxxxxxxxxxx

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Use of QGPL library for custom objects , Jerry Draper

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.