Did you do this from a newly signed on job? Because that's in effect what
you do when you debug in batch.
Yes. Signed on, added two libs to library list and then started the debug
process.
Timestamps from job in QBASE. I did an F1 on each line and placed the time
displayed at the end of each line. Note the third line down where it says
"Job entered system on 04/09/07 at 07:44:02".
Job 030690/AARON/AARONJOBD released by user AARON. (7:44:21)
Job 030690/AARON/AARONJOBD started on 04/09/07 at 07:44:21 in subsystem
(7:44:21)
QBASE in QSYS. Job entered system on 04/09/07 at 07:44:02. (7:44:21)
Job 030690/AARON/AARONJOBD submitted. (7:44:21)
Job 030690/AARON/AARONJOBD held by user AARON with option SPLFILE(*NO).
(7:44:21)
Job 030690/AARON/AARONJOBD released by user AARON. (7:44:21)
> CALL PGM(QDEVTOOLS/QRSEEXEC)
PARM('/home/AARON/.eclipse/RSE/SBM00056.log' (7:44:21)
'CALL PGM(AARONLIB/PGM1)') (7:44:21)
Library QDEVTOOLS added to library list. (7:44:22)
2>> CALL PGM(AARONLIB/PGM1) (7:44:22)
I have not used WireShark before, but it sounds like fun! :-)
Thanks for the tip Joe,
Aaron Bartell
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [
mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Joe Pluta
Sent: Monday, April 09, 2007 8:40 AM
To: 'Websphere Development Studio Client for iSeries'
Subject: Re: [WDSCI-L] Initiating debug takes 20 seconds
From: albartell
Executing STRDBG PGM1 from command line took less than 1 sec.
Pressing F6 to add break point to PGM1 took even less than STRDBG.
Calling the debugged program and having it stop on the first
executable line of code took less than 1 second. At this point I
would consider I am at the same point as WDSC.
Did you do this from a newly signed on job? Because that's in effect what
you do when you debug in batch.
So to tally the numbers I would say that I am safely under 3 seconds
on the green screen side and still at 20 seconds on the WDSC side.
Again, I highly suggest you check your joblog, and see what the timestamps
are. In a normal scenario, all the lines in your joblog will be pretty
close together (within milliseconds, IIRC). I'm particularly interested to
see if the 20 seconds is BEFORE the first statement of the job is executed,
or AFTER the job hits the breakpoint, so you're going to need another job
that you can display the System i system time on at the exact time you
submit the job from WDSC.
If that doesn't help, the next step is Ethereal (now called WireShark).
Watch the traffic on the network to try and identify when the various events
occur.
Joe
--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
midrange.com
