|
Are you getting any errors from RSE? Are you at the latest wdsci version? If your job to be debugged is in a wait state of some kind it won't hit the sep until it cycles... -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Ryan Sent: Thursday, November 02, 2006 9:41 AM To: Websphere Development Studio Client for iSeries Subject: Re: [WDSCI-L] SEP - Server Program Thanks for the info Rick. It's not working for me - I must be doing something wrong. On 11/2/06, Rick DuVall <R_C_DuVall@xxxxxxxxxx> wrote:
Hi List, Actually, I don't think that is true, I am almost certain I have captured a running batch job with the sep debug functions in Lpex. In fact, I just did it.. 1. get a list of program objects in the RSE including the one you want to debug. 2. strdbgsvr on the iSeries command line (there are other ways to do this) 3. right click chosen program object and choose (Debug (Service Entry Point) And Set Sep. 4. if you are not the actual user running the batch job look in the iSeries Service Entry Points list at the bottom and Highlight and modify the sep to have the correct user id. 5. wait for the rse to change to debug mode and display the source...
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.