You can define custom AWT resource limits for utilities, and TASM will either reject or delay utilities that exceed these limits. To create custom limits, in the Throttles view, use the Resource Limits tab.
- You want to enforce a lower percentage of AWTs for utility jobs than the system default.
- You want to create separate AWT resource limits for utility jobs from different users or applications.
- Rule 1: A limit of 45 percent of AWTs for all DSA restore jobs in the system, with delay
- Rule 2: A limit of 15 percent of AWTs for DSA restore jobs from user Lee, with delay
- Scenario #1: Only DSA restore jobs from user Lee are running. These jobs together cannot use more than 15 percent of AWTs.
- Scenario #2: User Lee is not running any DSA restore jobs. Other users are running DSA restore jobs and consuming the limit of 45 percent of AWTs. When user Lee submits a DSA restore job, TASM delays it because it would exceed the AWT limit of Rule 1 (45 percent of AWTs for all DSA restore jobs).
You can see all the AWT Resource Limit rules in the Resource Limits by State tab in the Throttles view.
The following illustrates custom AWT resource limits for different groups of users.
|Utility Protocol||AWTs Required To Start|
|FastExport No Spool||2|
|MLOADX||MIN(2, number of target tables)|
* TASM initially assumes a DSA restore job needs 3 AWTs. Actual AWT usage, which can be up to 55 AWTs, will be dynamically updated later in the job and will affect the next utility job.