None. Allocation has enqueued on the dataset(s), which is handled by GRS, and sits there waiting for the ENQ to be completed. Allocation does nothing explicitly (polling or so), but is signalled when the datasets are available. So this will not cost any CPU. The fact that the job is in the system, occupies an address space, has allocated storage, etc. etc. will cost something, but I think this is neglectable.
Kees. "Kent Ramsay" <[email protected]> wrote in message news:<962689126.288418.1331838701488.javamail.r...@sz0149a.emeryville.ca .mail.comcast.net>... > 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 information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ******************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
