Re: Debugging

The problem should have nothing to do with WDSC.  If you launch debug 
configuration, it just sends the command on to the AS/400 / iSeries / 
System i.  Have you checked to make sure there isn't another copy of the 
program in the library list?

Also, if you're looking for a good resource to help understand the 
transition from PDM/SEU to LPEX, try the following:

ftp://ftp.software.ibm.com/as400/products/ad/wdt400/v60/manuals/SEUtoLPEX.pdf 


This link can be found in the help text under 'Developing iSeries server 
applications' and 'SEU - LPEX transition guide'.

wdsci-l-bounces@xxxxxxxxxxxx wrote on 11/03/2006 01:00:07 PM:

date: Fri, 3 Nov 2006 12:51:16 -0500
from: "Bill Barnes" <bbarnes@xxxxxxxxxxxxx>
subject: [WDSCI-L] Debugging

OK, this thing is bugging me.  I bring up the Program in the program
library (source in different library).  I right click on the program
name and then click on Debug(Prompt)(K) and choose batch.  I check to
make sure that the program cal ed in the SBMJOB command is correct and
click on Apply then Debug.  A window pops up telling me I do not have
write access to a different source member than the one I clicked on.  In
our shop programmers do not have write access to the production source
files.  The problem is that I debugged (or tried to) the program that
keeps coming back about 2 weeks ago.  Why doesn't it go away and let me
debug the program I want to now?



Thanks

Bill Barnes

Sr Analyst/Programmer

The Pantry, Inc

919-774-6700

ext 5211