Error message
No such file or directory bad number |
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
Action
Points to check
Have the following variable strings been defined in the shell script?
Script example
proc1 > ${FILE} 2>&1
CODE=`tail -1 ${FILE}`
exit $CODECause
In the above example, an unintended string is stored in the $CODE variable if an error message is output as the proc1 execution result. In this case, the error message shown below is returned from the shell, however it may be misunderstood that the message was output by Systemwalker Operation Manager, and not by the shell.
Example of the shell error message that is output by the exit statement
$ exit errormessage errormessage: bad number
Action method
In the shell script variable value, check if an unintended string was stored because an error occurred.
Information
Basically, Systemwalker Operation Manager displays the content for the standard output (stdout) and standard error output (stderr) of the job in the previous log for the job without any special processing.
If an error message is output to the previous log for the job, check if the job may have been output first.