× 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: Debugging a trigger to tap the calling program,
  • From: Peter Connell <peterc@xxxxxxxxxxxxx>
  • Date: Fri, 13 Jul 2001 12:35:12 +1200

Cory,
Once you've done a STRSRVJOB on the active batch job then a STRDBG for the
trigger pgm (sometimes it pays it explictly qualify it) and added the break
point, you should press F12 to exit. This should mean that the next time the
batch job runs the trigger it should debug at your screen. It's sometimes
easy to mess things up if you've done and endsrvjob job in which case you're
debugging your interactive session or vicea versa when you forget to do an
endsrvjob and you can't figure why your interactive session won't debug.

Peter

-----Original Message-----
From: Contractor2@Parkdalemills.com
[mailto:Contractor2@Parkdalemills.com]
Sent: Friday, July 13, 2001 12:55 AM
To: RPG400-L@midrange.com
Subject: Debugging a trigger to tap the calling program,


I need to find the name of a batch program that is writing to the file that
has a trigger.  I researched the solution in the archives and found a
solution from Peter Connell dated 06/13/00 08:57 titled "Who pulled the
trigger?".  The solution said to debug the trigger program to look at the
program stack to find the program to send and receive a message so I could
acquire the program name.  I did a STRSRVJOB and then STRDBG on the trigger
program.  I set break a point and pressed F10, the step key.  The program
updating the file ran fine but the debugged trigger program never broke.
Why did it not break?  Was it because the debug program was not running in
the same job as the updating program.

Thank you,

Cory King
704-874-5035
1-800-331-1844 Ext: 5035


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

This communication is confidential and may be legally privileged. 
If it is not addressed to you, you are on notice of its status. 
Please immediately contact us at our cost and destroy it.  
Please do not use, disclose, copy, distribute or retain any of it 
without our authority - to do so could be a breach of confidence. 
Thank you for your co-operation.  
Please contact us on (09) 356 5800 if you need assistance.
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-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.