|
Juan Carlos, try the archives at Midrange.com: http://archive.midrange.com/rpg400-l/200112/msg00137.html seems to do what you want (otherwise search the RPG400-L archive for 'trigger caller id') HTH, Peter Colpaert Application Developer Honda Europe NV Langerbruggestraat 104 B-9000 GENT Belgium Peter.Colpaert@honda-eu.com Tel: +32 9 2501 334 Fax: +32 9 2501 231 ---------- Yoda of Borg are we: Futile is resistance. Assimilate you, we will. ---------- -----Original Message----- From: JuanCarlos.Minuesa@es.huhtamaki.com [mailto:JuanCarlos.Minuesa@es.huhtamaki.com] Sent: Tuesday, October 22, 2002 6:28 AM To: midrange-l@midrange.com Subject: Trigger Program : what Program caused the Upd/Del/Ins I am processing? I've writen a trigger program and works OK, The question is: the transaction that caused me (the trigger pgm) execute was originated by some other Application program... I believe the trigger pgm executes under Job/User/JobNo same as the originating job, but where can I find the info about wich PGM (pgmname, libname, ...) originated the transaction? Regards, Juan Carlos ______________________________________________________________________ The information contained in this communication is confidential and may be legally privileged. It is intended solely for the use of the individual or the entity to whom it is addressed and others authorised to receive it. If you have received it by mistake, please let the sender know by e-mail reply and delete it from your system. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance of the contents of this information is strictly prohibited and may be unlawful. Honda Europe NV is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.
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.