In Systemwalker Operation Manager, the power schedule is integrated with power control software and the server power is automatically switched on or off, or rebooted, based on the defined schedule.
Determine a server power schedule if power is to be controlled.
Items to be considered
Determine the power control pattern. There are three types of patterns, as described below.
Create a non-standard pattern or an individual pattern, as required.
Note that standard patterns must be created and applied in advance even when using a non-standard pattern or an individual pattern.
Standard pattern
This is a general-purpose pattern that defines the power-on/off schedule and the reboot opportunities for a week. If the server operates using a standard pattern alone, the server will be powered on and off, and rebooted using the same repeated pattern every week.
This standard pattern is automatically applied to all days other than those configured as holidays in the SYSTEM_CALENDAR, and the power is switched on or off, or rebooted, accordingly.
Non-standard patterns (patterns other than standard patterns)
This is a general-purpose pattern that defines the power-on/off schedule and the reboot opportunities for a day. Consider creating a non-standard pattern for days when you need to power on or off, or reboot, according to a pattern that differs from the standard pattern.
This pattern can be applied to multiple days other than those configured as holidays in the SYSTEM_CALENDAR.
Individual patterns
This pattern defines the power-on/off schedule and the reboot opportunities for a particular day. An individual pattern can also be created for days set as holidays in the SYSTEM_CALENDAR, but for which the user wants to switch power on or off, or reboot.
If you want to perform completion monitoring when shutting down the server, consider the completion conditions, such as those listed below, for shutting down or rebooting the server.
Monitor the presence of users connected via the network
Notify users connected via the network that the server will shutdown
Shut down the server waiting for jobs to be completed
Other completion monitoring options include the execution of commands when the work end time is reached, and issuing operator notifications if the completion conditions have not been satisfied after a certain period of time has elapsed following the work end time.
Note that shutdown will take place immediately if completion monitoring options have not been specified.
If multiple completion conditions have been specified, shutdown will occur after all the specified conditions have been satisfied.
