Re: MONMSG CLP Question -- MIDRANGE-L

Subject: Re: MONMSG CLP Question
From: CRPence <CRPbottle@xxxxxxxxx>
Date: Mon, 18 Mar 2013 11:29:46 -0700
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>

On 18 Mar 2013 11:11, rob@xxxxxxxxx wrote:

I started thinking ALCOBJ.

Of course using ALCOBJ introduces its own issue that I had not mentioend. That issue is the requirement to request the corresponding DLCOBJ not only in mainline processing after the lock is no longer required, but also from\in any termination handler for which the application [that requests and obtains the lock] is ending. Obviously not a concern for terminations whereby the process\thread that obtained the lock is ending, as the origin for the application ending, because the locks go away with the thread\process that obtained them.

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.