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



I'm not a performance or tuning expert.
My thoughts:
1 - review the tweak
2 - from your job log what steps used the most cpu ?
3 - can you compare to a job log made before the tweak ?
4 - maybe a more verbose job log could help ?
5 - use System I Navigator to look for recommended indexes (good general practice)
6 - run a job in debug mode to get access path recommendations

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John R. Smith, Jr.
Sent: Friday, June 19, 2015 1:52 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Seconds used question

I agree that it is CPU seconds but what miscellaneous CPU seconds are being charged to my job.

The question came from a job that ran the 403 seconds. A minor tweak was make to one of the programs and it used 10 times as many CPU seconds. The first run was on a light day and the second run was on a heavily abused day so before I totally blame the tweak, I want to make sure there wasn't a bunch of misc system functions such as swapping that got added to my CPU seconds and skewed the numbers.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Thompson
Sent: Friday, June 19, 2015 2:57 PM
To: Midrange Systems Technical Discussion
Subject: RE: Seconds used question

I don't know, but if you have a job log print file for that job, look at start and end times - a little math should answer your question and, if memory serves, the job log shows net cpu seconds.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John R. Smith, Jr.
Sent: Friday, June 19, 2015 12:54 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Seconds used question

The line in the joblog states



Job 999999/UUUUUUUUUU/JJJJJJJJJJ ended on 06/12/15 at02:36:42; 430.362 seconds used; end code 0



I have always thought this was CPU seconds used to execute the job but some questions have come up to make me wonder if it is more than that.



For example,

1) If the system is really bogged down and doing a lot of swapping,
does the CPU time spent swapping get added to this?

2) If the DASD is really bogged down, does that have any effect on this
number?

3) If there is a lock of a record and the program is in a LCKW state,
does that add any CPU overhead to my job (not sure if my program goes to sleep and the OS wakes it up when the lock frees or if my program is checking the lock status behind the scenes)?



Can someone provide a good explanation of this number and what else if anything other than my program instructions are included in it?







--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.