Re: problem with QSYSARB holding a lock on a library object -- MIDRANGE-L

Subject: Re: problem with QSYSARB holding a lock on a library object
From: rob@xxxxxxxxx
Date: Mon, 2 Nov 2009 11:06:11 -0500
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>

If it's not a pmr issue then it's always a DCR issue. Just a general
philosophy. Others may argue against your request though.

Were any of these jobs active before the change?
A change to this system value takes effect for all jobs that become
active after the change. The shipped value is 1.

Rob Berendt

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