Home > Archive > Cobol > December 2007 > High CPU consumption in VSAM Record Management due to COBPACK-OS ESMS
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
High CPU consumption in VSAM Record Management due to COBPACK-OS ESMS
|
|
|
| Hi all,
While trying to tune Batch Jobs / Cobol Programs using Strobe , I
came across this . Strobe Profile / Report shows Most CPU consuming
Procedure as VSAM RECORD MANAGEMENT. While the Attribution Table for
VSAM RECORD MANAGEMENT shows COBPACK-OS ESMS as the function which
causes much of the CPU consumption.This function alone consumes as
high as 50% of CPU utilization. I would like to more about this
function. Can anyone help me ?
Regards,
saravanan
| |
| William M. Klein 2007-12-17, 6:56 pm |
| VSAM tuning is a "big deal" in the IBM mainframe world. There are lots of
papers on it and you may want to use the IBM-MAIN list for "hints and tips" -
but without more information, I doubt they will be able to help you.
--
Bill Klein
wmklein <at> ix.netcom.com
"GM" <gm.saravanan@gmail.com> wrote in message
news:ebabacd8-b97a-477f-b4da-92bd59164161@a35g2000prf.googlegroups.com...
> Hi all,
>
> While trying to tune Batch Jobs / Cobol Programs using Strobe , I
> came across this . Strobe Profile / Report shows Most CPU consuming
> Procedure as VSAM RECORD MANAGEMENT. While the Attribution Table for
> VSAM RECORD MANAGEMENT shows COBPACK-OS ESMS as the function which
> causes much of the CPU consumption.This function alone consumes as
> high as 50% of CPU utilization. I would like to more about this
> function. Can anyone help me ?
>
> Regards,
> saravanan
|
|
|
|
|