Applicable versions and levels
Windows versions: V5.0L10 or later
Solaris versions: 5.0 or later
Linux versions: 5.2, V10.0L10 or later
Linux for Itanium versions: V12.0L10 or later
HP-UX versions: 5.1 or later
AIX versions: 5.1 or later
DS versions: V20L10
Action
Points to check
Has the application that was started as the job ended?
Cause
If the job does not end, the cause may be that the application (*1) that was started as the job has not ended.
*1: If a child process and grandchild processes are started from the application, these processes are also included.
Action method
In Windows versions, use Task Manager (in UNIX versions, use other ways such as using the ps -ef command) to check if the application (including the child or grandchild processes) has ended. If the application has not ended, there may be a problem in the application, so perform a review.
If this problem is reproduced in Windows versions, use the procedure shown below to check the application status.
Note
The function described in "Confirmation procedure" below is not provided for use in normal operations. It is used temporarily to investigate a problem where a job does not end.
For this reason, do not use it for purposes other than problem investigation.
[Confirmation procedure]
Perform the steps shown below on the server on which the job that caused the problem is executed (the server on which the Systemwalker Operation Manager server function is installed).
Start the command prompt and execute the command shown below.
By executing this command, the job window will be displayed.
All jobs started after the command is executed will run in the background (that is, the window is minimized or iconized).
mjstool -option jobwindow=unhide
Start the job on which the problem occurred from Systemwalker Operation Manager, and reproduce the problem.
After the job is started, if it can be confirmed that the problem has occurred, check if an event that can confirm the cause of the problem (for example, a message box will be displayed) has occurred in the window.
Additionally, if an application assumed to have hung exists in an icon or on the task bar, restore the window for that application to its original size, and check if that resolves the problem.
If the cause of the problem can be confirmed, take the appropriate action, and then repeat steps 2 and 3.
After the problem investigation steps are complete, start the command prompt and execute the command shown below.
By executing this command, the status is restored to the original status from the status in step 1 in which the job window can be displayed.
mjstool -option jobwindow=hide
