Error message
MpJobsch: ERROR: 0027: The jobscheduler failed to retrieve day change time. |
Applicable versions and levels
Solaris versions: 11.0 or later
Linux versions: V11.0L10 or later
Linux for Itanium versions: V12.0L10 or later
HP-UX versions: 11.0 or later
Action 1
Points to check
Was the calendar daemon (f3crhcs2) stopped?
Check whether the process is started by using the following command.
# ps -ef |grep f3crhcs2
Action method
If you stopped Systemwalker Operation Manager by using the poperationmgr command, start Systemwalker Operation Manager (calendar daemon) by using the soperationmgr command, and then start the job scheduler daemon from the cluster system.
Action 2
Points to check
Was the symbolic link of the script that starts the calendar daemon set correctly?
The following method can be used to check if the symbolic link was set correctly:
[Solaris versions]
# ls -l /etc/rc3.d/S28JMCAL # ls -l /etc/rc2.d/S28JMCAL
[Linux versions]
V 13.8.0 or earlier, or Red Hat Enterprise Linux 6 or earlier
# ls -l /etc/rc3.d/S28JMCAL # ls -l /etc/rc2.d/S28JMCAL # ls -l /etc/rc5.d/S28JMCAL
Sample Output from the ls Command
#ls -l lrwxrwxrwx 1 XXXXX XXXXX XX mm:dd hh:mm S79JMCAL -> /opt/FJSVjmcal/bin/S99JMCAL
Cause
The Jobscheduler daemon started when the calendar daemon is not running or while the startup is in progress.
For the Jobscheduler daemon to start, the calendar daemon must already have been started.
If the environment is not a cluster environment, the calendar daemon and the Jobscheduler daemon will be started by the Systemwalker Operation Manager startup script when the system starts up, and the startup order is guaranteed. However, in a cluster environment, the Jobscheduler daemon is started from the cluster daemon, not from the Operation Manager startup script.
For this reason, the cluster daemon may start before Systemwalker Operation Manager, and the Jobscheduler daemon may start before the calendar daemon startup completes.
Action method
Execute the calsetcluster commnd.
For the details of the calsetcluster command, refer to the "Settings for Automatic Reflection" in the "Systemwalker Operation Manager Cluster Setup Guide for UNIX" or the "Systemwalker Operation Manager Reference Guide".
Execute the following command to create a symbolic link.
[Solaris version]
# ln -s /opt/FJSVjmcal/bin/S99JMCAL /etc/rc3.d/S28JMCAL # ln -s /opt/FJSVjmcal/bin/S99JMCAL /etc/rc2.d/S28JMCAL
[Linux versions]
For Red Hat Enterprise Linux 6 and earlier
# ln -s /opt/FJSVjmcal/bin/S99JMCAL /etc/rc3.d/S28JMCAL # ln -s /opt/FJSVjmcal/bin/S99JMCAL /etc/rc2.d/S28JMCAL # ln -s /opt/FJSVjmcal/bin/S99JMCAL /etc/rc5.d/S28JMCAL
For Red Hat Enterprise Linux 7 (V13.8.0 and earlier)
# cd /etc/rc3.d # ln -s ../init.d/JMCAL /etc/rc3.d/S28JMCAL # cd /etc/rc2.d # ln -s ../init.d/JMCAL /etc/rc2.d/S28JMCAL # cd /etc/rc5.d # ln -s ../init.d/JMCAL /etc/rc5.d/S28JMCAL
Refer to your operating system documentation for details on how to configure rc3.d.
Action 3
Points to check
Is the unit file that starts the calendar service set up?
How to check
You can check the setting status of the unit file in the following ways.
[Linux versions]
For V 17.0.0 or later and Red Hat Enterprise Linux 7 or later
# systemctl list-unit-files --type=service | grep JMCAL.service |
Sample Output from the systemctl Command
JMCAL.service enabled |
Cause
The Jobscheduler daemon started when the calendar daemon is not running or while the startup is in progress.
For the Jobscheduler daemon to start, the calendar daemon must already have been started.
Action method
Execute the calsetcluster commnd.
For the details of the calsetcluster command, refer to the "Settings for Automatic Reflection" in the "Systemwalker Operation Manager Cluster Setup Guide for UNIX" or the "Systemwalker Operation Manager Reference Guide".
Set the unit file that starts the calendar service.
[Linux versions]
For V 17.0.0 or later and Red Hat Enterprise Linux 7 or later
# cp -p /opt/FJSVjmcal/etc/unit/JMCAL.service /usr/lib/systemd/system/JMCAL.service # chmod 644 /usr/lib/systemd/system/JMCAL.service # chown root:sys /usr/lib/systemd/system/JMCAL.service # systemctl daemon-reload # systemctl enable /usr/lib/systemd/system/JMCAL.service
