RE: triggers and clrpfm and such -- 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: RE: triggers and clrpfm and such
From: Rob Berendt <rob@xxxxxxxxx>
Date: Tue, 29 Oct 2019 20:04:39 +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>

<snip>
If you qualify it, the QIBM_CA_CHG_COMMAND exit point doesn't fire
</snip>
If this is true then one man's trash is another man's treasure.
Let's assume that the application code doesn't qualify it. So it calls the exit point. The exit point would qualify it with QSYS. Therefore it would not call itself recursively. No need to dup the command.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: triggers and clrpfm and such , Jay Vaughn

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.