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



Buck,

Buck,

Sure!

I have this job running 990196/QUSER/MSGPGMDQ in a sub-system

1.) Open Debug perspective
2.) Menu: "RUN"
a.) Option: "Debug Configurations"
3.) Inside the "tree-view" on the left, click on "IBM i:Debug job"
4.) Click on the icon that looks like a piece of paper with a "+" (a.k.a. New button)
5.) I populate my debug this way:
a.) Name: "MSGPGMDQ" the Job name
b.) connections: "TEST" (Name of your power-system running IBM i)
c.) Name: "MSGPGMDQ" the job name
d.) User: "*" for current user. Since I only have ONE run, I leave this as "*"
Or you could use the "QUSER" from above
e.) Number: "*" for the current job Number. I only have one job running.
6.) Check-box: Step into CHECKED
7.) Check-Box: Update production files CHECKED
8.) Click the "Debug Button"

Now, your job could be 123456/KKILIAN/QPADEV0001 (Your interactive session)

I normally only use this for our NEVER-ENDING Data-Queue processing jobs. Once in a while we encounter bad data from our vendors... Which make this option EXCELLENT for examining variables in Debug Mode.

It had been working flawless form WDSC 6.0 to RDP 8.0.3. And on RDP 8.5.1. It broke...

I just flip the "system", and then I can debug a different system job, with the exact same name and different job number! If the job is unique, only one running actively. Because I use "*" for both JOB-USER & JOB-NUMBER.



-Ken Killian-
(423) 510-3129


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck Calabro
Sent: Wednesday, January 16, 2013 12:29 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] RDP 8.5.1 debug problem: "Source not found."

On 1/16/2013 11:31 AM, Ken Killian wrote:

Is there a way to get "SEP" to work on currently running batch program? Like the Debug Job?

I am afraid I was not clear. I only know how to do SEP debugging with RDP - I don't know what 'Debug Job' is. Can you show the steps for that?
--buck
--
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@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.