× 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.



Hi Dave,

Thank you for your reply. Do you think this will work if I call your procedure from my trigger program? This issue I'm having is I need to know within a specific trigger program what program is causing the trigger program to fire or in essence which program is updating my database table. I will check out your midrange wiki in the meantime.

Thank you,
Mike

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of dlclark@xxxxxxxxxxxxxxxx
Sent: Thursday, August 02, 2018 10:38 AM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: caller-id program

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 08/01/2018 04:36:04
PM:
I seem to recall not too long ago someone posted a question regarding
the program called "caller-id" written by Lloyd Deviney from NEWS/400.
It was stated that there is an issue with this program working on
V7R3. I forgot to print off the solution to the problem. I've tried
searching the archives, but I can't find the answer. Is the issue
related to the APIs that are being called in this program? When I
Google "caller-id" I came across a question I had posted on the RPG
Café. One of the replies references a link to the original article
which doesn't seem to exist any more. Can someone please post a link
to the solution to fixing this?


FWIW, I created a service procedure (utilizing the QWVRCSTK API) return the "previous" call stack entry from a particular program or to simply "find" and return the call stack entry for a particular program.
This allows, for example, retrieving the name of the calling program (and module name and procedure name) or finding out if a particular program is already in the call stack (e.g., to prevent recursion). I posted this service procedure on the midrange wiki for free use. However, we aren't at 7.3 yet (at 7.2 still) but I see no reason why this service procedure won't work just as well at that release level since IBM's API should maintain reverse compatibility.

https://wiki.midrange.com/index.php/QWVRCSTK_%E2%80%94_Retrieve_Call_Stack


Sincerely,

Dave Clark
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300

Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331




*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary information. If you have received this message in error, please immediately notify the sender and delete and destroy the message and all copies. All unauthorized direct or indirect use or disclosure of this message is strictly prohibited. No right to confidentiality or privilege is waived or lost by any error in transmission.
*********************************************************************************************
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.