Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide

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.

The Local Power Control job or Remote Power Control job must be executed by a superuser or a member of the Administrators group.

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

(2) Example of a jobnet that uses the Remote Power Control job

(3) Handling a jobnet for which a start condition is satisfied more than once

(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.

For details about the functionality that can be executed by the Local Power Control job, see the Job Management Partner 1/Power Monitor Description, User's Guide and Reference.

Supplementary note

To execute a Local Power Control job, you must be a member of the Administrators group (on a Windows host) or have superuser permission (on a UNIX host). 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.

For details about the functionality that can be executed by the Remote Power Control job, see the Job Management Partner 1/Power Monitor Description, User's Guide and Reference.

Cautionary note

To execute a Remote Power Control job, you must be a member of the Administrators group (on a Windows host) or have superuser permission (on a UNIX host). 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) Handling a jobnet for which a start condition is satisfied more than once

When a jobnet's start condition is satisfied more than once within the valid range of the start condition, some subordinate jobnets might be placed in the Skipped so not executed status. Execution of the jobnets placed in this status is skipped. This occurs when the following conditions coexist:

A jobnet with a start condition for which Disable is set for Concurrent exe. is registered for execution.

During execution of a generation with a satisfied start condition, the start condition is satisfied again. The latter generation (in the Wait for start cond. status) is waiting for the previous generation to terminate.

The timeout period set for the root jobnet has expired.

When the above three conditions are met, the message KAVS0277-I is output, and the generation waiting for the end of the previous generation is placed in the Skipped so not executed status and not executed.

To avoid this situation, take one of the following measures:

Enable concurrent execution of jobnets.
To perform this setting from JP1/AJS3 - View, open the Define Details - [Jobnet] dialog box. On the Definition page, set Concurrent exec. to Enable.
To perform this setting by command, in the unit definition file, set the mp jobnet definition parameter to y.

Set an unlimited timeout period for the jobnet.
To perform this setting from JP1/AJS3 - View, open the Define Details - [Jobnet] dialog box. On the Definition page, set Time-out period to Unlimited.
To perform this setting by command, in the unit definition file, set the cd jobnet definition parameter to un.

[Contents][Back][Next]

[Trademarks]