Thanks for enlightening me. I guess I know the mechanism of how exit code is constructed. Just like you said, shell scripting is somewhat different. I believe certain exit codes should be avoided. For example,
It worked until someone accidently changed the owner of a.file. Suddenly, it returns "1". But "1" is does not come from the if statement. It actually comes from the shell after chgrp fails.
My thinking is maybe there is a range of exit code that we should avoid. Just a guess.
In one of my programs another process is called using the system command e.g.
lv_error = system("myproc");
where lv_error is declared as an int.
myproc would be returning 0 for success and 1 for failure. e.g.
if (success)
{
return(0);
}else{
return(1);
}
When the return code... (3 Replies)
I'm receiving an exit code 64 in our batch scheduler (BMC product control-m) executing a PERL script on UX-HP. Can you tell me where I can find a list of exit codes and their meaning. I'm assuming the exit code is from the Unix operating system not PERL. (3 Replies)
I'm investigating strange behaviour on two boxes (Sun OS 5.10 and AIX 5.1) in ksh
have used $? to get exit codes returned:-
137 and 34
where can I find what these mean?
thank you (1 Reply)
i am writing a script to perform some mysqldumps and gzip them. The problem I am running into is that if the user specifies a database that doesn't exist, the error the mysql engine produces is still piped into gzip, and the exit code returned is 0. If I don't pipe into gzip, an exit code... (4 Replies)
Can some one tell me what it means to get a exit code od 137 from a cron scheduled backup on HP-UX. Also if you know of a book that has the HP-UX codes that would be great.
Thanks (4 Replies)
We have a batch Unix process that runs during the day and it is getting an exit code 11 from Unix. It finishes a sqlplus step and gets the exit code 11 before it starts the next step. This used to happen once a year and now is happening more often (but not every time the process runs). We have... (2 Replies)
I have a file with size as 120,371 bytes in local machine and trying to FTP it to a remote server using put command. say that it transferred exactly the same size of 120,371 bytes and hence it returns a 226 code.
I have a doubt on how the rule is made for 226 - if both size on local and remote... (7 Replies)
Discussion started by: penqueen
7 Replies
LEARN ABOUT OSF1
intro
intro(1) General Commands Manual intro(1)NAME
intro - Introduction to commands
DESCRIPTION
Section 1 describes the commands available for all Tru64 UNIX users.
Some reference pages in this section may contain suffixes to allow their files to exist with those of other reference pages having the same
base name and section number. When used, suffixes are made up of one to four letters. See the man(1) reference page for more information
on suffixes.
Commands related to system maintenance appear in Section 8.
ERRORS
On termination, each command returns two bytes of status, one supplied by the system giving the cause for termination and, in the case of
normal termination, one supplied by the program. For more information, see exit(2). The first byte is 0 for normal termination; the sec-
ond byte is customarily 0 for successful execution. A nonzero status indicates a problem, such as erroneous parameters, or bad or inacces-
sible data. The status value is called variously exit code, exit status, or return code, and is described explicitly on reference pages
only when special conventions apply.
SEE ALSO
Commands: man(1)
Functions: exit(2)intro(1)