When we encountered significant performance issues, we investigated JES settings for spool access and gave greater weight to the system on which ControlM was running. You might want to look into what you have specified on MASDEF (I'm assuming, possibly incorrectly, that you are running with a multi-access spool configuration).
-- -- Don Imbriale On Wed, Jan 6, 2010 at 3:44 PM, William Bishop <bill.bis...@tema.toyota.com>wrote: > A sister company of mine is attempting to use Control-M to support a new > application. > > They have defined 25000 jobs into 3000 schedule groups. > > In operation, they have observered that it can take 6 minutes between the > time a job ends and the next job takes off. > > Has anyone running Control-M experienced this kind of issue? > > Is anyone running Control-M with this many jobs and schedules groups? > > We can take this off-list if desired. > > Thanks > > Bill Bishop > > Specialist > Mainframe Support Group > Server Development & Support > Toyota Motor Engineering & Manufacturing North America, Inc. > bill.bis...@tema.toyota.com > (502) 570-6143 > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
