Shell Programming and Scripting

Of course, all the child scripts must know how to exit not zero on any sort of error, a recursive search for unexpected exits and unchecked conditions.

I tried with the pre-script error processing, with "sed -e". Looks like its working fine, but for what ever case (0 ,2, 4), it should send the e-mail to the user, stating the result.
But as per the script, its not sending e-mail for any failure, but the user is receiving the e-mail for any success.

Can you please look at the sub-script attached to this e-mail and let me know as to where i am going wrong.

No, shell command set -e, nothing to do with sed, the stream editor.

I got rid of set -e command.

Now i am facing a new issue.
When i execute the shell script, it just shows me blank with no progress.

-bash-3.00$ ./sqlldrclaims_backup_new.sh
Password:
SQL*Loader: Release 11.2.0.1.0 - Production on Tue Jan 18 10:26:39 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.

When i do "ps -ef" i see this

Code:

zx01324 25166 25150   0 10:12:25 pts/1       0:00 sqlldr zx01182 control=/space/dbexport/PHR/control/claims.ctl log=/space/dbexpo

Can anyone explain to me as to what's going on, as it used to load the data, but now,, its runs at the background.

https://www.unix.com/shell-programmin...e-files-5.html
In you previous threads on this script from a couple of months ago I don't think we found out what Shell you were using.

Anyway, one of your problems may be the "set -e".

Code:

         -e   Execute the ERR trap, if set, and exit if a command has a
                nonzero exit status, and is not part of the compound list
                following a if, until, or while keyword, and is not part of
                an AND or OR list, and is not a pipeline preceded by the !
                reserved word.  This mode is disabled while reading
                profiles.

Good idea to put a line in after saving $rc to display the value. This will tell you if the line is ever executed when the preceding command returns a non-zero exist status.

Code:

rc=$?
echo "The value of rc = $rc"

You can set -ex and get a progress report as child processes are started. However, if there is information to catch in the return code, you need to capture $? in another variable, IMMMEDIATELY, before it is overwritten by your error handling code.

But that is your choice, in terms of error handling architecture. The child script could log everything and just return 0 or 1, so when testing a child, you do not need the parent or a hand coded echo $? to see the result (and you might overlook that in a quick test). Logging should be clear, so it is good to have the parent log just say 'parent started at this time, started child at this time with these arguments, child can write log location, child ended good or bad at this time, parent ended at this time. This way, clutter can be logged down at the leaf level, and in some case rejects or errors are potentially large enough to go in a specific separate file, not the main log, but with the side log path and its stats in the main log. If you reuse the same log path, there should be internal start/end headers and code to prevent two runs at once.

You, too, deserve good error checking, handling, logging. Think of it as a real product, just like processed data. When x runs, it owes me an output file and a log of happy ending or a log of why not, all the time, 100%, unity, 1.0 probability!

Methyl,

I am sorry for not replying back to you as to what Shell i am using.

The answer is :

Its "bash"

Code:

-bash-3.00$ echo $0
-bash