7.7.4 Notes on the Local Power Control job and Remote Power Control job
The following provides precautions (items you should know in advance) for using the Local Power Control job and Remote Power Control job.
-
The Local Power Control job links with JP1/Power Monitor and shuts down the manager host or agent host.
-
The Remote Power Control job links with JP1/Power Monitor and starts and shuts down the agent host of JP1/Power Monitor on the network. This job can control hosts in the manager/agent configuration of JP1/Power Monitor. It does not depend on the manager/agent configuration of JP1/AJS3.
-
When the Remote Power Control job is executed, the job sends a request to JP1/Power Monitor on the agent (job-executing host) to perform remote power control. JP1/Power Monitor then starts remote power control. The agent's next power-on time is determined by the time zone setting of the agent.
-
The host that executes the Remote Power Control job must be set as the manager host for the remote power linkage function of JP1/Power Monitor.
- Supplementary note
-
If you use the option to continue execution of active event jobs, the event job will remain in Now running status on the manager host if JP1/AJS3 terminates on the agent host. This rules out planned termination and other modes of operation that depend on waiting for jobs to terminate on the manager host. If you must use a Local Power Control job or Remote Power Control job in an environment where this option is enabled, you can work around this problem by waiting for active event jobs to end or forcibly terminating them, or waiting for the scheduling function to end the event jobs before performing power control.
- Organization of this subsection
(1) Example of a jobnet that uses the Local Power Control job
Example jobnets defined with the Local Power Control job are as follows:
-
When the preceding job ends, the jobnet shuts down the manager host or agent host specified as the execution host.
Note that executing a Local Power Control job from JP1/AJS3 is the same as using the JP1/Power Monitor calendar to perform a planned stop.
- Supplementary note
-
For details about the OS users who can execute a Local Power Control job, see (3) Notes on OS users capable of executing power control jobs. Because you cannot specify a User name in an action job, to execute a Local Power Control job, log in as a JP1 user that mapped to the root user as the primary OS user, and then register the job for execution.
(2) Example of a jobnet that uses the Remote Power Control job
The following shows examples of jobnets that use the Remote Power Control job:
-
The jobnet starts the agent host (agent host of JP1/Power Monitor) before executing a job on the host. When the job ends, the host is shut down.
-
If the preceding job ends abnormally, the jobnet restarts the host (agent host of JP1/Power Monitor) that executed the job, and executes the job again.
- Cautionary note
-
For details about the OS users who can execute a Remote Power Control job, see (3) Notes on OS users capable of executing power control jobs. Because you cannot specify a User name in an action job, to execute a Remote Power Control job, log in as a JP1 user that mapped to the root user as the primary OS user, and then register the job for execution.
(3) Notes on OS users capable of executing power control jobs
A power control job (Local Power Control job or Remote Power Control job) that links with JP1/Power Monitor can only be executed by the OS users listed in the following table.
|
OS |
OS user |
|
|---|---|---|
|
Windows |
With UAC enabled |
Administrator user (built-in Administrator account)# |
|
With UAC disabled |
Administrator user (built-in Administrator account) or user in Administrators group |
|
|
UNIX |
Superuser |
|
- #
-
You can have an OS user with administrator permissions execute power control jobs by enabling the setting that gives OS users with administrator permissions to execute power control jobs. For details, see 6.2.22 Settings for executing jobs as a user with administrator permissions when the UAC is enabled in the JP1/Automatic Job Management System 3 Configuration Guide.