|
View previous topic :: View next topic
|
| Author |
Message |
cser_oxygen
New User
Joined: 25 Oct 2006
Posts: 33
|
|
|
|
Guys,
How can I know the CPU execution time for a JOB from the JES2 log?
Thanks,
Galen |
|
| Back to top |
|
 |
Escapa
Senior Member
Joined: 16 Feb 2007
Posts: 1399
Location: IL, USA
|
|
|
|
Have you had look at JESMSGLG
It should have everything you needed...
You will find below in JESMSGLG
| Code: |
TOTAL TCB CPU TIME= .00 TOTAL ELAPSED TIME= .0
|
|
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
| Back to top |
|
|
cser_oxygen
New User
Joined: 25 Oct 2006
Posts: 33
|
|
|
|
| Sambhaji wrote: |
Have you had look at JESMSGLG
It should have everything you needed...
You will find below in JESMSGLG
| Code: |
TOTAL TCB CPU TIME= .00 TOTAL ELAPSED TIME= .0
|
|
Thx.
What does TCB stands for? I also can find
| Code: |
| CPU SRB TIME 00.00.00.01 |
Galen |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
google is your friend:
web.utk.edu/~mnewman/ibmguide10.html
then do a find on TCB a couple of times.
The explanation includes definition of the two ACRONYMs as well as what purpose they serve. |
|
| Back to top |
|
|
Escapa
Senior Member
Joined: 16 Feb 2007
Posts: 1399
Location: IL, USA
|
|
|
|
Thanks Dick Brenholtz.
Link mentioned is very informative.
Below is part of infomation form link explaining various terms..
| Quote: |
PROCLIB substitution messages (IEF653I messages)
RACF messages repeated from the job log
Messages concerning each job step including
Allocation messages for this step (IEF237I messages)
Condition code for this step (IEF142I)
Deallocation messages for this step (IEF285I messages)
EXCPs by DDNAME (UNT531I messages)
Step Statistics (UNT501I-UNT510I messages)
Starting and ending wallclock time (hh:mm:ss)
Elapsed time (hh:mm:ss)
Region requested (in Kilobytes)
Region used -- not billed to user
Region limit -- region requested + 64K
System area used -- not billed to user
TCB time in seconds -- CPU time billed to user
SRB time in seconds -- CPU time not billed to user
CPU time -- TCB time multiplied by rate
VF time -- vector facility time used
Kilobyte-hours -- computed according to formula in UTCC Schedule of Charges
KBHOURS -- not billed to user
DCT -- device connect time by device type and total
EXCPs by device type and total
EXCP cost by device type and total
Job statistics (UNT521I-UNT530I messages) -- totals for all steps
|
|
|
| Back to top |
|
|
cser_oxygen
New User
Joined: 25 Oct 2006
Posts: 33
|
|
|
|
| Thanks all! |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
Hello,
SRB stands for Service Request Block: A system control block used for dispatching tasks. It is not owned by any application, but is used when work is done by the operating system on behalf of an application.
It should be norted that CPU time is the time for which the CPU was busy executing the task. It does not take into account the time spent in waiting for I/O (disk IO or network IO). Since I/O operations, such as reading files from disk, are performed by the OS, these operations may involve noticeable amount of time in waiting for I/O subsystems to complete their operations. This waiting time will be included in the elapsed time, but not CPU time. So, CPU time is usually less than the elapsed time. |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
| And for that matter, TCB, Task Control Block, is the consolidation of control information related to a task, so this is the CPU time billed to user. |
|
| Back to top |
|
|
Bill Dennis
Active Member
Joined: 17 Aug 2007
Posts: 562
Location: Iowa, USA
|
|
|
|
While your SRB time is not a function of the task, it is certainly task-related and many shops do charge total TCB+SRB to the user.
For example, if a user writes 10 times as many blocks because they chose a small blocksize then SRB will be higher. |
|
| Back to top |
|
|
|
|
