Applicable versions and levels
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
Check all applicable actions below to resolve the issue.
Action 1
Points to check
Has an interactive command (such as more, pg) or a shell script that makes an input request been executed?
Cause
The job has fallen into an input wait state, therefore the job may not end.
Action method
If a command or function that makes an input request is contained in the application, investigate if the application can be modified so that these commands or functions do not run.
If there is a possibility that the application stopped because it was in an input wait state when the error occurred, the job will not end, so consider configuring a setting to make the job end after a fixed period has elapsed.
For example, in Specify the time limit of job execution. of the Edit Queue window, consider setting a limit value to execute the job in a particular queue, so that jobs that run for a long time are treated as having ended abnormally.
Action 2
Points to check
Is the application in an infinite loop?
Cause
If the job that was started from Systemwalker Operation Manager is in an infinite loop, or has stopped status because of having to wait for some reason, the job does not end. (Note that Systemwalker Operation Manager does not wait until descendent processes such as child processes and grandchild processes are complete.)
If the target application that was started as a job using the ps command exists, there is a possibility that the application has not ended.
Action method
Debug to find out why the application has not ended. If the application process can be confirmed using the ps command, it may be possible to debug the application by executing the truss command for this process.
