× 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: Who pulled the trigger? / Call stack
  • From: Rob Berendt <rob@xxxxxxxxx>
  • Date: Mon, 20 Sep 1999 9:00:22 -0500

And what if that program was a call from MS Query?




jpcarr@tredegar.com on 09/17/99 11:20:29 PM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     MIDRANGE-L@midrange.com@Internet
cc:      
Fax to: 
Subject:        Re: Who pulled the trigger? / Call stack


Here it goes,  This is a low tech solution and can be made into Procedures
using Message API's if you want to make it real fancy.   But as is,  it will

also work for the average Joe/Jane programmer too. 

For trigger's
In your *INZSR subroutine repeatedly call a CLP to retrieve the program
name of the caller.  You can "walk up the Stack" past the programs(OS/400's
that begin with "Q")  to the program you're looking for. 

---
Just call the below program repeatedly(in a loop in your *INZSR),  First
time 
pass your trigger program name(the program who's *inzsr you are
currently in that is)  as the &CALLED, and who ever called your 
trigger will be returned in the &CALLER variable.  This will undoubtedly be
a "Q" 
OS/400 program.  Call the CLP again this time pass what was returned the
first time to find out who called him, and so on.  up the stack till *EXT.

Stop at the first program name(&CALLER) doesn't begin with a "Q". 
That's the application program that kicked off the trigger..

--------------
PGM    &CALLER &CALLED

DCL   &CALLER  *CHAR  10  
DCL   &CALLED  *CHAR  10
DCL   &M1KEY   *CHAR   4
DCL   &M1MDTA  *CHAR  80

SNDPGMMSG  MSG('TEST')  TOPGMQ(*PRV &CALLED) MSGTYPE(*RQS) KEYVAR(&M1KEY)

RCVMSG   PGMQ(*PRV &CALLED)  MSGKEY(&M1KEY)  SENDER(&M1MDTA)

CHGVAR   &CALLER    %SST(&M1MDTA  56 10)

ENDPGM
----------------------------

So,   Just call it with a program name(&CALLED) and it will tell you who
called
that program(&CALLER) ,  next time pass it what was returned the previous
time 
to find out who called him, and so on up the stack.   Look at the name
returned
(&CALLER)  if the first position of the name is a "Q"  it's an OS/400
program.
(Unless you are ,  hmm shall we we say,  Dumb enough to start your program 
names with the letter Q ?)


John Carr
EdgeTech

Visit  www.400school.com  for classroom education information.






+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.