Re: Quick question on triggers -- determining pgm that tripped the trigger? -- 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: Quick question on triggers -- determining pgm that tripped the trigger?
From: "Mark S. Waterbury" <mark.s.waterbury@xxxxxxxxxxxxx>
Date: Wed, 09 Mar 2011 13:50:00 -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>

Hi, James:

Issue the MATINVS MI instruction, or call the QWVRCSTK API ... (available since V5R1).

HTH,
Mark

> On 3/9/2011 1:28 PM, James Lampert wrote:

I'm pretty sure I've done this before myself, but I can't recall what,
or where:

In a trigger program, what's the easiest way to determine what program
tripped the trigger?

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

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.