Re: Initiating debug takes 20 seconds

From: albartell

Today I timed how long it takes to initiate a debug on a small RPG ILE
program and determined it took 20 seconds. By initiated I mean the time
it
took from pushing the debug button to when the first line of the program
was
highlighted in that aqua color. I think it takes way to long considering
I
am the only one on the box today. Note that this isn't the first debug of
this program I have executed with this startup of WDSC. All subsequent
debug
initiations take the same amount of time.

PC config: 2 core duo Xeon procs (4 processors) and 4GB Ram and mirrored
400GB 7200RPM SATA HD's.

iSeries config: http://mowyourlawn.com/blog/linkto/systemiconfig.pdf

Is there some priority tweaking I can do on the iSeries (i.e. give a
subsystem more throughput or something)?

WDSC 7 takes seven seconds to load a program here. Since this includes
submitting the job, holding it, attaching to it via remote debug, setting
the initial breakpoint, releasing the job, servicing the initial event and
displaying the results graphically in WDSC, I think seven seconds is pretty
good.

And this is a little model 520, accessed from my game machine (since WDSC 7
won't run on my 64-bit workstation) - a 2.4GHz P4 with 1GB of RAM. My
initial guess is that your network latency really sucks, but that's just a
guess. Have you looked at the joblog for the job to see if there's anything
there?

Joe