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



You're my golden child for today Joe!!!!!

This is a silly question, I know, Aaron, but how many breakpoints do you
have set up?
I probably had 100 or so and I removed them all. Many were left over from
other debugging sessions from weeks ago. I am now down to about 7 seconds!!
Whoo hoo!

Thanks 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 9:12 AM
To: 'Websphere Development Studio Client for iSeries'
Subject: Re: [WDSCI-L] Initiating debug takes 20 seconds

From: albartell

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)

Yeah, this is your bad boy. The delay on my machine is only three seconds.
So what is happening at this point? What is causing the lag between the job
entering the system and being started?

This is the time between when the job is submitted and when it is released.
Maybe someone from IBM can tell us what's actually happening during this
time period.

This is a silly question, I know, Aaron, but how many breakpoints do you
have set up?

Joe


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.