DB2 graphic  QMF Version 8

Multiple schedules for one resource limits group

When a user accesses a database server, QMF for Windows identifies the one or more resource limits groups to which the user has been assigned and verifies the schedules of the groups to determine which resource limits are currently in effect. Because users can be assigned to multiple resource limits groups, each will multiple schedules, there can easily be overlapping spans of time when technically multiple sets of resource limits could be in effect.

In the cases of overlapping schedules, QMF for Windows uses a unique schedule number to determine which schedule is in effect. The schedule with the lowest number takes precedence.

For example; if a resource group has the following four schedules:

Table 16. Resource Limits Group Schedules
Schedule # 1 2 3 4
From Day Wednesday Monday Monday Sunday
To Day Wednesday Friday Friday Saturday
From Time 10:30 9:00 17:00 00:00
To Time 11:30 17:00 9:00 24:00

You will notice that schedule #1 is embedded in schedule #2 and schedules #1, #2, and #3 are embedded in schedule #4. If a user accessed this database server on Wednesday at 11:00, schedules #1, #2, and #4 could be in effect. QMF for Windows will use the schedule with the lowest number.

When you create your resource limits group schedules, it is recommended that you stagger your numbering so additional schedules can be inserted where appropriate or deleted without impact. Keep in mind that schedules do not have to be numbered sequentially but once a schedule is assigned a number it cannot be changed.

All time and day ranges of the schedules are inclusive. That means if the From time is 08:00, the schedule is in effect exactly at 08:00. If the To time is 17:00 the schedule is in effect until 16:59:59. The from and to times can wrap around midnight, and the from and to days can wrap around weekends.

When users are accessing servers in different time zones, the clock used to determine time resides on the database server being accessed. For example, an end user in New York is accessing a database server in California and it is 9:00am Monday in New York. Based on the example schedules, schedule 3 is in effect because according to the database server it is 6:00 California time.


Go to the previous page Go to the next page

Downloads | Library | Support | Support Policy | Terms of use | Feedback
Copyright IBM Corporation 1982,2004 Copyright IBM Corporation 1982, 2004
timestamp Last updated: March, 2004