Objects defined to CSM that do not specify a schedule are given a default schedule of UP 24 hours a day, 7 days a week.
Most objects fall into this category.
Some objects, usually online inquiry tasks, require periods of inactivity for system maintenance and batch file processing. CSM can control the schedule for these objects and stop the object (change its actual state to DOWN) and then restart the object after a specified period of time.
You need to determine the DOWN time and the DOWN duration for all the objects and then input these times to CSM as part of the object’s definition.
| Hint |
|---|
| The best place to gather object scheduling information is from the Operations staff or systems programming group. |
If the object you are defining a schedule for is the child of an object other than MVS, you must take the scheduling of the parent into consideration to avoid conflicts. A child object can be UP only when its parent is UP.
Remember, an object that does not have a schedule always has a desired state of UP unless it is altered by a schedule, a Global Calendar Override, or a CSMACT EXEC. Any object that has a schedule, at some point in time, will have desired states that are not UP.
