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



If you do a call from PGMA to PGMB (SEP and ILE RPG) and put a
breakpoint in PGMB it will stop the first time.
If in PGMA you call PGMB directly again, what happens is that the debug engine from the previous call is
busy terminating while the new call is trying to
start the debug engine.
As a result the second call is not debugged (It looks a timing issue).
This is surely a bug (WDSCi 7.0.0.1).
They advised to upgrade !!

If you build in a sleep before calling pgmb the problem is gone.

PGMA

h Bnddir('QC2LE') dftactgrp(*no)
*Delay job
DSleep PR 10I 0 Extproc( 'sleep' )
D seconds 10u 0 Value

* Standaard wachttijd tussen check facturen
D Seconds S 10I 0 Inz(1)

c do 30 field

c call 'PGMB'
c parm field 10 0
c
c* callp sleep ( seconds )
c enddo
c

c eval *inlr = *on

PGMB

c *entry plist
c parm field 10 0
c eval *inlr = *on

Best Regards / Met vriendelijke groet,

Willem Kruize
Senior Software Engineer
IBS NEDERLAND B.V.
Postbus 500 3430 AM Nieuwegein, The Netherlands
Nevelgaarde 20 Nieuwegein, The Netherlands
Phone: +31 (0)30 6026666 Direct: + 31 (0)30 - 6026713
Fax:
http://www.ibs.nl



"dnitke" <dnitke@xxxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
26-10-2007 15:26
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To

<wdsci-l@xxxxxxxxxxxx>
cc





Subject
[WDSCI-L] READ: Debugging Issue in WDSCi 7.0






Hey All,

I'm having a strange issue in the WDSCi debugger. Im debugging an RPGIII
program using of course the non SEP (SEP is RPGIV only). This is a Stored
Procedure process where a RPGSQL program calls another RPGIII program
multiple times. I start the debug process add the second program to the
debugger and run the job. The debugger stops the program the first time
but never again, it just lets the job run out. This process can be
debugged normally using STRISDB where the second program hits 3 times as
it should. Anyone else run into this, I seem to remember seeing this on
our list but couldnt find that email. The second program is exiting using
the RETURN command instead of *INLR (just an fyi).

Thanks
Don N.

PS: WDSCi 7.0.0.4


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.