RE: Question on QZDASOINIT jobs in QUSRWRK

I think for this situation, I'd probably set the Initial number to some
optimal value greater than the max of jobs, i.e. 40. Then to handle the
peak times of the year, I would set the Additional number of jobs to
something really high (100, 200, something like that).

Elvis

Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400
www.centerfieldtechnology.com


-----Original Message-----
Subject: RE: Question on QZDASOINIT jobs in QUSRWRK

Thanks for the responses on this one. We have made the changes as outlined
on the pdf you reference.

I do have a follow up question. We are a college and for most days of the
year workload is fairly random but 10-15 days a year when classes first open
up to be scheduled and just before a semester starts when we do Late
Registration, we can have 300-400 students who all want to do something at
the same time. We usually know when these hits will occur. Every student is
going through a web logon that is a java app that will need to make a
connection thought a QZDASOINIT job before moving on to use the RPG CGI app
that we use for class scheduling. Would we be better off to bump these
numbers up really high for these peak days or set the values high enough to
deal with a peak day and leave them that way all year?