If there is no response from the Jobscheduler function of the Systemwalker Operation Manager client even though the Jobscheduler service is in operation, take the following actions on the server where the Jobscheduler is in operation.
Note
If the server is unable to send replies in response to processing requests from clients, client responses might not come back.
Resolve the problem on the server, and then forcibly terminate the unresponsive client and reconnect the client window.
For Windows system
Log in as a user belonging to the Administrators group.
Execute the jshpkill command.
Use the jshpkil command to restart the Jobscheduler service. Before executing the jshpkill command, wait at least one minute after starting the Jobscheduler service. Otherwise, the Jobscheduler service may terminate without restarting. In this case, the Jobscheduler service must be started manually. To start the Jobscheduler service manually, set the Control subject to Jobscheduler in the Service control section of the Systemwalker Operation Manager Environment Setup window, and then click the Start button.
The above operations also output an error message "7308: tskwnsrv was abnormally terminated" to the event log and close all connections between the Jobscheduler function and Systemwalker Operation Manager client. Reconnect the Jobscheduler function.
For UNIX system
Log in as a superuser.
Submit the following command to request the tskwnsrvb process ID.
ps -le | grep tskwnsrv |
Send SIGUSR1 to the above process ID.
kill -USR1 process-ID |
Use the kill -USR1 command to restart the Jobscheduler daemon. Before executing the kill-USR1 command, wait at least 30 seconds after starting the Jobscheduler daemon. Otherwise, the Jobscheduler daemon may terminate without restarting. In this case, the Jobscheduler daemon must be started manually. To start the Jobscheduler daemon manually, execute the "S99JOBSCH" daemon startup script. Refer to "jobsch_start Command [UNIX]" in the Systemwalker Operation Manager Reference Guide for details on the daemon startup script.
The above operations also close the connection between the Systemwalker Operation Manager client and the Jobscheduler function. Reconnect the Jobscheduler function.
