Introduction to CSM
The following list important CSM terms:
- objects
- relationships between objects
- states of objects
- schedules
Term | Definition |
---|---|
Objects and objects relationships | With the ISPF dialogs provided by Continuous State Manager, you define objects (for example, CICS, JES, or NetView) and establish relationships and dependencies between them, thereby enabling the application to automatically manage your system in an ordered way. |
States | To refer to an object’s accessibility is to describe the state of the object. An object that is available is in an UP state and when it is not available, it is in a DOWN state. |
Schedules | By default, Continuous State Manager assumes that any object you define is UP 24 hours a day, 7 days a week. The object’s schedule is what the application uses to determine when to make objects UP (available) or DOWN (unavailable). The schedule consists of all the times an object should be down. For example, an object might need to be brought down every Thursday from 1:00 A.M. to 3:00 A.M. for maintenance. If you do not define a schedule for an object to be DOWN, Continuous State Manager defines a default schedule where the object is UP 24 hours a day, 7 days a week. Ideally, by using CSM, you are enabling important processes such as IPL and orderly shutdowns to be managed and controlled automatically. However, if you do encounter situations where you must change the state of an object manually, CSM also provides a facility that enables you to do this modification. |