Synopsis
mjsdaemon [-sys subsystem-number](*1)[-sys subsystem-number] is an option of Systemwalker Operation Manager EE.
Description
The Job Execution Control starts when the following two processes are completed in sequence.
Startup of the Job Execution Control daemon
Startup of the Job Execution Control operations
The process (a) is automatically activated when the Systemwalker Operation Manager server starts, and then the process (b) is automatically activated.
The mjsdaemon command starts the Job Execution Control daemon and the operation of the Job Execution Control. Use this command from the following job execution demon startup scripts:
Solaris | /etc/opt/FJSVMJS/etc/rc3.d/S99MJS |
HP-UX | /opt/FHPMJS/usr/lib/mjes/S99MJS |
AIX | /opt/FAIXMJS/usr/lib/mjes/S99MJS |
Option
-sys subsystem-number
In the system with multiple subsystems, this option is used to specify the subsystem that you want to operate. Specify the target subsystem number using a range of 0 to 9. If omitted, the default is subsystem 0.
Return Values
Return Value | Meaning |
|---|---|
0 | The command processing has terminated normally. |
Other than 0 | The command processing has failed. An error message is output. |
Command Location
Solaris | /usr/lib/mjes |
Privilege Required
System administrator (superuser) privileges are required.
Cautions
Be sure to use this command from the job execution control daemon startup script. If you execute the command directly, the settings such as environment variable configured within the job execution control daemon startup script are not set, which causes the problem of inconsistent character codes.
In Red Hat Enterprise Linux 7, the operating system may need to be stopped or restarted even if the daemons are configured to stop automatically when the operating system is stopped.
In this case, manually execute the poperationmgr service/daemon termination command in advance to stop the Systemwalker Operation Manager daemons. [Linux]