Specify continuous execution mode by executing the jmmode command on all schedule servers and execution servers.
The following figure shows an overview of this definition.
Execute this command with all the Systemwalker Operation Manager daemons stopped. After the command is executed, these daemons will need to be restarted in order for continuous execution mode to take effect.
Refer to the Systemwalker Operation Manager Reference Guide for details on the jmmode command.
Example of command execution for a 1:1 active/standby configuration (without subsystems), N:1 active/standby configuration, or cascading configuration
Perform the following procedure on all the nodes:
Stop the Systemwalker Operation Manager daemons.
# /opt/systemwalker/bin/poperationmgr
Execute the jmmode command with the "continue -func JOB" option specified.
# jmmode continue -func JOB
Execute the jmmode command with the "check" option specified, and check that "JOB" has been set to "on".
# jmmode check
[Display example]
SYS 0 JOB on WRT off
Example of command execution for a 1:1 active/standby configuration (with subsystems)
Perform the following procedure on all nodes. In this example, Subsystem 0 and Subsystem 1 are operating.
Stop the Systemwalker Operation Manager daemons.
# /opt/systemwalker/bin/poperationmgr
Execute the jmmode command with the "continue -func JOB" option specified
# jmmode continue -func JOB -sys 0 # jmmode continue -func JOB -sys 1
Execute the jmmode command with the "check" option specified, and check that "JOB" has been set to "on".
# jmmode check
[Display example]
SYS 0 JOB on WRT off SYS 1 JOB on WRT off
Example of command execution for a 1:1 active/standby configuration (with subsystems and partial cluster operation)
Perform the following procedure on all nodes. The following example shows a configuration in which both Subsystem 0 and Subsystem 1 are operating but only Subsystem 1 is registered with a cluster system and Subsystem 0 is using a network job. In the case of a 1:1 active/standby configuration (with subsystems and partial cluster operation) in which Subsystem 0 cannot be used in cluster operation but a network job is used, use the jmmode command with Subsystem 0, just as in the example of a 1:1 active/standby configuration (with subsystems).
Stop the Systemwalker Operation Manager daemons.
# /opt/systemwalker/bin/poperationmgr
Execute the jmmode command with the "continue -func JOB" option specified
# jmmode continue -func JOB -sys 0 # jmmode continue -func JOB -sys 1
Execute the jmmode command with the "check" option specified, and check that "JOB" has been set to "on".
# jmmode check
[Display example]
SYS 0 JOB on WRT off SYS 1 JOB on WRT off
Example of command execution for a dual node mutual standby configuration
Perform the following procedure on all the nodes:
Stop the Systemwalker Operation Manager daemons.
# /opt/systemwalker/bin/poperationmgr
Execute the jmmode command with the "continue -func JOB" option specified.
# jmmode continue -func JOB -sys 1 # jmmode continue -func JOB -sys 2
Execute the jmmode command with the "check" option specified, and check that "JOB" has been set to "on".
# jmmode check
[Display example]
SYS 0 JOB off WRT off SYS 1 JOB on WRT off SYS 2 JOB on WRT off
Continuous execution mode has not been specified for Subsystem 0, and so "JOB off" is set for this subsystem.
Note
When executing the jmmode command after transferring resources to the shared disk in "2.6 Moving Resources to the Shared Disk," be sure to run this command on the active node where the shared disk is mounted.