Recently I came across a job in production the job CPU and elapsed time makes me some doubtfull.
This job runs during batch update and I see the driver file it reads which is a falt file
of around 2,185 allocated megabytes with 55 alocated extents and jumbo dataclas as defined.This file basically gets created from other place.
The lrecl of this file is 900.
I see that the COU time for this job is around 1.6 whereas the elapsed time around 64 minutes which makes me to beleive that this
is probably more I/O bound job.This file is read first in the cobol program before further readin around 10 vsam file(there could be a possibility that these vsam file tuning could be done).
Our shop had strobe earlier but now they have take this off so I can not get any conclusion blind.
But as I mentioned about the driver flat file I see it has got following on jcl
DCB=BUFNO=2,I am just thinking on what basis we select the BUFNO should be of what value if we really want to get the work finished as quickly as possible.
This job is running in critical path so I am trying to find out any imporvemnt if can be done
to get its elapsed time reduced as of now job takes around 1 hour to complete.Please advise I know that this is very little information for this job for you but
still experienced eyes can catch something ...Please let me know if
I can provide some other details.
Joined: 06 Jun 2008 Posts: 8214 Location: Dubuque, Iowa, USA
My experience has been that sequential files benefit from having about 30 to 50 buffers allocated as long as memory is available. VSAM file buffering is more complicated as it depends upon whether the file is being accessed randomly or sequentially. However, the default 2 data and 1 index buffer for KSDS is usually provides much worse performance than can be achieved.