10-17-2006
How do you Sum UNIX return codes
Hi,
I know how to read a return code after executing a single command.
"echo $?". But I do not know how to sum the return code for a group of commands.
If I string 3 commands together and I do an echo $? all I get is the retunr code for the last command. Example below:
----------------------------
cat file1 | cut -f1-5 | sort > file2
status=$?
if [ $status -eq 0 ]; then
##continue with rest of my script
else
exit
fi
-----------------
I only get the return code for the last command, the "sort" command.
I want to make sure that the return code for all three commands added togther =0. Can this be done?
The problem is I need to amke sure all 3 commands ran succesful. My status check only tells me the last commadn worked.
Thanks in advance for any assistance.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have the below script I am running on a Solaris system to check the status of a Tivoli Workload Scheduler job and return the status. We need this script to return a '0' if any of the jobs in the stream are in a "EXEC" state and an "1" if in a "HOLD" state. I am not a programmer so I am not sure... (1 Reply)
Discussion started by: leezer1204
1 Replies
2. UNIX for Dummies Questions & Answers
Suppose I have a script which is monitoring a directory
whenever a file drops in that directory,it sends alert
say I want to write a return code for the above script
which on successful execution of script gives a return value
Based on return code , I want to do initiate some jobs in other... (1 Reply)
Discussion started by: abhib45
1 Replies
3. UNIX for Dummies Questions & Answers
Hi,
Can anyone tell me if there are return codes for SFTP? If so how would you capture them? I've tried 'man sftp' but its not particularly helpful.
Many thanks
Helen :confused: (4 Replies)
Discussion started by: Bab00shka
4 Replies
4. UNIX for Advanced & Expert Users
I have a simple script which renames a file.How do i capture the return code of the script if the script fails (3 Replies)
Discussion started by: kris01752
3 Replies
5. Shell Programming and Scripting
Hi
In an unix script I am using an Perl one liner perl -i -ne '-----'
If the perl one liner fails i am not able to catch the return code.
It always give 0 as return code. Can you tell me how can i catch the return code
perl -i -ne '---'
RETCODE=$?
echo $RETCODE
Thanks and Regards
Ammu (2 Replies)
Discussion started by: ammu
2 Replies
6. UNIX for Dummies Questions & Answers
This is a high-level explanation, if more details are needed, please do not hesitate to ask.
I have a set of .ctl files which I want to execute:
AV1.ctl
AV2.ctl
AV3.ctl
I have a script which has a for loop in it:
for filename in AV1 AV2 AV3
do
. execute_another_script.sh
done
... (2 Replies)
Discussion started by: hern14
2 Replies
7. Shell Programming and Scripting
sftp -v b $putlist $SFTP_ID@TARGET_SERVER
How can I get a return code if fails to put the file?
sftp -v b $getlist $SFTP_ID@TARGET_SERVER
How can I get a return code if fails to put the file? (1 Reply)
Discussion started by: TimHortons
1 Replies
8. Shell Programming and Scripting
Hi,
I wanted to know the significance of different return codes when we do echo $?
I know when $? returns 0 the command has worked successfully.
but what does $? = 1, 2, 3 etc. signify.
Thanks in advance for the help !!! (3 Replies)
Discussion started by: aarti.popi
3 Replies
9. UNIX and Linux Applications
Having searched high and low through Oracles documentation, I came to think that they're very scripting-averse, as there's (apparently) no list of possible return/exit codes for their various command line utilities.
Is anyone here in possession of such a list, or knows where to find one? It... (16 Replies)
Discussion started by: pludi
16 Replies
10. UNIX for Dummies Questions & Answers
Not sure if this is of any use but......
I was messing around with getting return codes greater than 255 for special usage...
Of course the code could be made simple but in this code the new stored return code
is generated as exit is progressing...
#!/bin/sh
# Real and imaginary return... (9 Replies)
Discussion started by: wisecracker
9 Replies
exit(1) User Commands exit(1)
NAME
exit, return, goto - shell built-in functions to enable the execution of the shell to advance beyond its sequence of steps
SYNOPSIS
sh
exit [n]
return [n]
csh
exit [ ( expr )]
goto label
ksh
*exit [n]
*return [n]
DESCRIPTION
sh
exit will cause the calling shell or shell script to exit with the exit status specified by n. If n is omitted the exit status is that of
the last command executed (an EOF will also cause the shell to exit.)
return causes a function to exit with the return value specified by n. If n is omitted, the return status is that of the last command exe-
cuted.
csh
exit will cause the calling shell or shell script to exit, either with the value of the status variable or with the value specified by the
expression expr.
The goto built-in uses a specified label as a search string amongst commands. The shell rewinds its input as much as possible and searches
for a line of the form label: possibly preceded by space or tab characters. Execution continues after the indicated line. It is an error to
jump to a label that occurs between a while or for built-in command and its corresponding end.
ksh
exit will cause the calling shell or shell script to exit with the exit status specified by n. The value will be the least significant 8
bits of the specified status. If n is omitted then the exit status is that of the last command executed. When exit occurs when executing
a trap, the last command refers to the command that executed before the trap was invoked. An end-of-file will also cause the shell to exit
except for a shell which has the ignoreeof option (See set below) turned on.
return causes a shell function or '.' script to return to the invoking script with the return status specified by n. The value will be the
least significant 8 bits of the specified status. If n is omitted then the return status is that of the last command executed. If return
is invoked while not in a function or a '.' script, then it is the same as an exit.
On this man page, ksh(1) commands that are preceded by one or two * (asterisks) are treated specially in the following ways:
1. Variable assignment lists preceding the command remain in effect when the command completes.
2. I/O redirections are processed after variable assignments.
3. Errors cause a script that contains them to abort.
4. Words, following a command preceded by ** that are in the format of a variable assignment, are expanded with the same rules as a vari-
able assignment. This means that tilde substitution is performed after the = sign and word splitting and file name generation are not
performed.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
break(1), csh(1), ksh(1), sh(1), attributes(5)
SunOS 5.10 15 Apr 1994 exit(1)