Hi
(As it is Friday)
We have customers complaining (and they have right) about a CPU usage
for an idle STC about 0.04 CPU second/hour.
On 3/15/2012 8:24 PM, Gibney, Dave wrote:
Between little and none :) IMHO
Dave Gibney
Information Technology Services
Washington State University
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf Of Kent Ramsay
Sent: Thursday, March 15, 2012 12:12 PM
To: [email protected]
Subject: Hypothetical Performance Question
Hi,
A hypothetical question but first the setting: A customer has two jobs auto-
submitted within five minutes of each other. Job 1 grabs the dozen or so data
sets and executes, leaving Job 2 with a formal "waiting for data sets"
situation. Obviously, when Job 1 finishes, Job 2 actually starts. Now the
question: While Job 2 is queued up waiting for the data sets, is there any
appreciable use of CPU by z/OS or JESx services to continually check to see if
the data sets are free, yet? In this case, Job 1 runs for almost 4 hours so
Allocation services is checked at least occasionally. I'm not interested in
doing
a charge-back, just wondering if there's any real cpu usage.
Since this cropped up, the customer has changed the job schedule to submit
Job 2 after Job 1 completes but the mind wonders. Thanks.
Kent
Kent Ramsay
425.681.2278
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
