Ah, I see, you checked the documentation starting from today and going back to the past. Yes, that is a valid approach.
But wouldn't it be better if IBM could add something like:
Available since:
* V7R3
* V7R2, TRx
* V7R1, TRy
That would make it a lot easier to decide whether or not it is possible to use a new feature.
Thomas.
-----Ursprüngliche Nachricht-----
Von: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> Im Auftrag von Daniel Gross
Gesendet: Samstag, 30. März 2024 18:27
An: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Betreff: Re: How to get the program library name of a program that sent a message
   
   First - the IC page is available for 7.2:
   - [1]
https://www.ibm.com/docs/en/i/7.2?topic=services-joblog-info-table-function
   And Simon has written something in 2015:
   - [2]
https://www.rpgpgm.com/2015/06/using-sql-to-get-information-from-job.html
   That's what I could find quickly. 
   D. 
   Von meinem iPhone gesendet
     Am 30.03.2024 um 18:19 schrieb Thomas Raddatz <thomas.raddatz@xxxxxx>:
     May you please share the URL with me? I did not see anything like that
     on page:
     
https://www.ibm.com/docs/en/i/7.3?topic=services-joblog-info-table-function
     The above link was the first match of a Google search. The 7.5 page does
     not provide the release information either:
     
https://www.ibm.com/docs/en/i/7.5?topic=services-joblog-info-table-function
     The release when a function was first introduced is quite important for
     open source developers and hence I would like to know where to find
     that.
     Thomas.
     -----Ursprüngliche Nachricht-----
     Von: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> Im Auftrag von
     Daniel Gross
     Gesendet: Samstag, 30. März 2024 18:07
     An: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
     Betreff: Re: How to get the program library name of a program that sent
     a message
     Hi Thomas,
     according to Info Center its available since 7.2 - but Simon writes it
     was introduced with 7.1 TR9.
     Regards,
     Daniel
     Von meinem iPad gesendet
       Am 30.03.2024 um 17:56 schrieb Thomas Raddatz <thomas.raddatz@xxxxxx>:
       Hi Daniel,
       meanwhile I discussed the problem with Mark Waterbury and I noticed
       that the QGYOLJBL API returns the program libraries (sender and
       receiver).
       I did not yet pay attention to the JOBLOG_INFO table function. Thank
       you for pointing me to that. For now I assume that I will go with the
       API, because I already have it in place and I can specify a message
       key for identifying the first (and in this case only) message to read.
       But good point. Thank you for that. By the way, do you know since when
       the JOBLOG_INFO table function is available? Is it available on 7.3? I
       am just curious. 7.3 is the minimum release for the iRPGUnit plug-in.
       Have a nice Easter weekend,
       Thomas.
       -----Ursprüngliche Nachricht-----
       Von: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> Im Auftrag von
       Daniel Gross
       Gesendet: Freitag, 29. März 2024 21:51
       An: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
       Betreff: Re: How to get the program library name of a program that
       sent a message
       True - that call stack entry isn't available anymore.
       What about the JOBLOG_INFO table function? If the message is in the
       job log, you should be able to retrieve it from there - and there is a
       column FROM_LIBRARY.
       Maybe that should work.
       HTH
       Daniel
         Am 29.03.2024 um 18:55 schrieb Thomas Raddatz
         <thomas.raddatz@xxxxxx>:
         Hi Daniel,
         Good point, but does not work in this case. The RPGUnit service
         program calls the test procedure inside a monitor block and in case
         of an unexpected error receives the escape message that caused the
         exception. At this time the call stack entry of the procedure that
         sent the escape message has already been removed from the call
         stack.
         Compressed example code:
         monitor;
         callProcByPtr( proc );
         on-error;
         result.error = rcvExcpMsgInfo(); // ==> QMHRCVPM endmon;
         Thomas.
         -----Ursprüngliche Nachricht-----
         Von: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> Im Auftrag von
         Daniel Gross
         Gesendet: Freitag, 29. März 2024 18:34
         An: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
         Betreff: Re: How to get the program library name of a program that
         sent a message
         Hi Thomas,
         if no other format of the API is containing the library, I would go
         over the call stack - and simply try to select the correct row from
         the STACK_INFO table function.
         HTH
         Daniel
             Am 29.03.2024 um 18:08 schrieb Thomas Raddatz
             <thomas.raddatz@xxxxxx>:
           I already use the QMHRCVPM message to receive a message send by a
           program. The sender information of format RCVM0300 contains the
           program, module and procedure name as well as the statement number
           of the program that sent the message. But it does not contain the
           program library name.
           However the program library name is displayed, e.g. if you do a
           DSPJOBLOG, prompt a message with F1 and switch to the message
           details with F9, e.g.:
           From program . . . . . . . . . :   RUCALLTST
           From library . . . . . . . . :     RPGUNITDVP
           From module  . . . . . . . . :     PGMMSG
           From procedure . . . . . . . :     PGMMSG_sndEscapeMsgAboveCtlBdy
           From statement . . . . . . . :     35600
           Hence the information must be available somewhere. Hopefully not
           only for the operating system.
           So does somebody know how to get the above information of a
           message send by a program?
           Thomas.
           --
           This is the RPG programming on IBM i (RPG400-L) mailing list To
           post
           a message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe,
           unsubscribe, or change list options,
           visit: 
https://lists.midrange.com/mailman/listinfo/rpg400-l
           or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
           Before posting, please take a moment to review the archives at
           
https://archive.midrange.com/rpg400-l.
           Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
           related questions.
         --
         This is the RPG programming on IBM i (RPG400-L) mailing list To post
         a message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe,
         unsubscribe, or change list options,
         visit: 
https://lists.midrange.com/mailman/listinfo/rpg400-l
         or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
         Before posting, please take a moment to review the archives at
         
https://archive.midrange.com/rpg400-l.
         Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
         related questions.
         --
         This is the RPG programming on IBM i (RPG400-L) mailing list To post
         a message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe,
         unsubscribe, or change list options,
         visit: 
https://lists.midrange.com/mailman/listinfo/rpg400-l
         or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
         Before posting, please take a moment to review the archives at
         
https://archive.midrange.com/rpg400-l.
         Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
         related questions.
       --
       This is the RPG programming on IBM i (RPG400-L) mailing list To post a
       message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe,
       or change list options,
       visit: 
https://lists.midrange.com/mailman/listinfo/rpg400-l
       or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
       Before posting, please take a moment to review the archives at
       
https://archive.midrange.com/rpg400-l.
       Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
       related questions.
       --
       This is the RPG programming on IBM i (RPG400-L) mailing list To post a
       message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe,
       or change list options,
       visit: 
https://lists.midrange.com/mailman/listinfo/rpg400-l
       or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
       Before posting, please take a moment to review the archives at
       
https://archive.midrange.com/rpg400-l.
       Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
       related questions.
     --
     This is the RPG programming on IBM i (RPG400-L) mailing list To post a
     message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or
     change list options,
     visit: 
https://lists.midrange.com/mailman/listinfo/rpg400-l
     or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
     Before posting, please take a moment to review the archives at
     
https://archive.midrange.com/rpg400-l.
     Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
     questions.
     --
     This is the RPG programming on IBM i (RPG400-L) mailing list
     To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
     To subscribe, unsubscribe, or change list options,
     visit: 
https://lists.midrange.com/mailman/listinfo/rpg400-l
     or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
     Before posting, please take a moment to review the archives
     at 
https://archive.midrange.com/rpg400-l.
     Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
     questions.
References
   Visible links
   1. 
https://www.ibm.com/docs/en/i/7.2?topic=services-joblog-info-table-function
   2. 
https://www.rpgpgm.com/2015/06/using-sql-to-get-information-from-job.html?m=1
--
This is the RPG programming on IBM i (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: 
https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at 
https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
As an Amazon Associate we earn from qualifying purchases.