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


  1.  Home
  2. WDSCI-L
  3. January 2019

Re: Debugging Inflight Jobs

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 01/10/2019
12:41:06 PM:
Absolutely, and simpler! It is called "S.E.P" (Service Entry Points)

Open view: IBM I Service Entry Points
Right-click to "Set Service Entry Point"

Enter the following information in the modal dialog box:
1.) IBM I Box
2.) Library/Program
3.) User
I usually default to module '*ALL"

It will catch your program no matter how it is started!
* Interactive
* batch
* web-service
* stored Procedure
* etc...

It is the only way I debug! <Joy Joy>

PS. Using RDI of course!


Then I must be doing something wrong. I have been debugging from
RDi for the last 8 years or so (using service entry points, of course).
But I can never get RDi to intercept an inflight job. I always have to
set the service entry point, first, and then submit the job I want to
debug.


Sincerely,

Dave Clark

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.