Archives of the TeradataForum

Message Posted: Wed, 18 Apr 2001 @ 20:03:01 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Frank,

From the MVS persepctive, you can implement some controls on your MVS side to address this problem.

What you can do is assign your production workload to a certain set of job classes. You could then assign your users to use different job classes in order to do work against Teradata. Each job class can be assigned one to many job initiators (i.e. concurrent threads), allowing concurrent activity for work within the job class. The number of initiators assigned to a job class can dynamically change based on a time schedule (or possibly by an event). Therefore, you could limit (or eliminate) the number of initiators available while your batch processes are running. The jobs submitted by your users will simply sit in the job class queue until an initiator becomes available.

I have implemented this used successfully in the past with a mainframe customer. This would eliminate mainframe contention for the number of load utilities and also gives you a good deal of control on the mainframe workload. However, it sometimes only takes one badly written query to cause problems for a batch cycle. For that, you really need to start to look at other workload management techniques like Priority Scheduler.

Hope this helps!

Regards,

Thomas F. Stanek
TFS Consulting

	<Prev	Next>		<<First	<Prev	Next>	Last>>