In z/OS 1.12, the original CPITCBTM and CPISRBTM "Initiator" TOTAL
CPU times were (finally!) separated into the Init-to-Load "INIT" CPU
times (CPITCITM/CPISRITM) for the CPU times prior to LOADTIME,
and into "TERM" CPU times (CPITCTTM/CPISRTTM) from the end of your
program execution until the last SMF record is written
(steps with MANY DD's write MANY SMF 30 subtype 4 records for a
single step, and more records at job termination for the last step).
This schematic maps the where the CP Engine CPU times in SMF 30-4
Step Termination Records are recorded:
FIRST SMF LAST SMF
INITTIME ALOCTIME LOADTIME TERMTIME TERMTIME
1->--------2----------3----------------4----w----w----w----5
| | | | |
|<-DSENQ-->|<-ALOCTM->|<----EXECTM---->| |
| | | | |
| | | | |
|IIIIIIIIIIIIIIIIIIIII|PPPPPPPPPPPPPPPP|TTTTTTTTTTTTTTTTTTT|
| CPITCITM | CPUTCBTM | CPITCTTM |
| CPISRITM CPUSRBTM | CPISRTTM |
CPUHPTTM
CPUIIPTM
CPURCTTM
Barry
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
Charles Mills
Sent: Tuesday, August 6, 2019 2:02 PM
To: [email protected]
Subject: Re: CPU time cost of dynamic allocation
Can you please clarify? Your first sentence seems to say that SVC 99 (or do you
mean Initiator) CPU time is in the SMF 30? Can you be more specific?
Your last sentence seems to say the opposite? Or ... ?
Charles
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Allan Staller
Sent: Tuesday, August 6, 2019 12:54 PM
To: [email protected]
Subject: Re: CPU time cost of dynamic allocation
This allocation time can be calculated from SMF type 30.
I am sure time is tracked. I am not sure the associated CPU is tracked.
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
Paul Gilmartin
Sent: Tuesday, August 6, 2019 11:45 AM
To: [email protected]
Subject: Re: CPU time cost of dynamic allocation
On Tue, 6 Aug 2019 12:25:05 -0400, Charles Mills wrote:
>
>OTOH I have an IEFBR14 batch job on the same machine that allocates 15
>temporary datasets in JCL. The entire job lock, stock and barrel uses
>(according to IEF032I) .00 CPU seconds. Can anyone explain why JCL
>allocation is apparently much more CPU efficient than SVC 99 allocation?
----------------------------------------------------------------------
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
