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



Could you please check to see if your batch program is still in queue?

I do a WRKJOBQ *ALL and watch the job get queued up and leave the queue by
hitting F5 repeatedly.  So it appears to be getting that far.

The Debug (Service Entry) approach worked!  Whoo hoo!  So what can I look at
next to see why it doesn't work when I invoke it directly from WDSC?

Thanks for your help Xuan,
Aaron Bartell

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Xuan Chen
Sent: Tuesday, November 21, 2006 1:22 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Debugger, debugger, where art thou?

It looks like the debugger is waiting for your batch program to run so that
it could attach to it.

Could you please check to see if your batch program is still in queue?

One other thing you could try is to use the service entry point.  Right
click on your program in RSE, and choose Debug (Service Entry) -> Set
Service Entry Point to set a service entry point on that program.  And then
just invoke the program you normally do.  For example, submit it to batch,
call it in the 5252 session.  A debug session should come up with your
program under debug.

Thanks,

Xuan Chen,  Problem Determination Tools for iSeries
(905) 413-3769 T/L 969-3769
xuanchen@xxxxxxxxxx



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.