Dave,
Whoops, I meant *BEFORE* you start your job...
I use the method "Debug Configuration" to debug jobs that alreadying running on the system. Here are abbreviate instructions:
Simple Method using GUI:
1.) Open Remote Systems
2.) expand out jobs:
3.) right-click my job and select Debug as"IBM i Job"
Method-2 manual, which I use more often: (And save for Re-Use in Debugging)
1.) Create Debug Configuration
> Run > Debug configurations or drop down on Debug ICON and select debug configurations
2.) Enter in information:
o Name: I name it after the batch-job
O Connection: xxxxxxxxx --> your IBM i connection
O Job name: xxxxxxxx --> Job to debug
O Job user: For re-use, I might use "*" or enter in the specific User
O Job Number: for re-sue, I might use "*", assuming there is only one job running with that name.
otherwise, enter in the specific job-number.
Note: You can click the button "Browse" to select the job on the system. I usually enter in the Name first! <Hint Hint>
So, that is my second favorite way to debug... There are actually 3-ways to debug with RDI...
Hope that helps a little bit.
PS. Since I am normally debugging my program fixes/Updates. I normally use the S.E.P. about 95% of the time.
If the job is already running on the system, then I use this "second-method" of the "Debug configurations".
Very handy if the job blew up, and you want to see what is going on the programming that is already RUNNING!
RDI debugging is the AWESOME!!! <Joy Joy> I use it all the time!!!
-Ken Killian-
-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of dlclark@xxxxxxxxxxxxxxxx
Sent: Thursday, January 10, 2019 12:58 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] 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
--
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 Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/wdsci-l.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com
midrange.com
