09-02-2005
catch the errorlevel of the command:
[code]
...
/path/to/somecommand ; RC=$?
if [ $RC -eq 0 ] ; then
print - "everything worked out fine"
else
print - "something screwed up"
fi
[code]
The errorlevel is set anew for every command issued, so be sure to get it as soon as the program in question is finished.
bakunin
Last edited by RTM; 09-02-2005 at 09:50 AM..
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I face some problem with handling of nulls. I declare a variable - say i - and intialise to 0. Later I read it from console, wherein if I dont give any variable and press return key, I get this error:
"0403-004 Specify a parameter with this command"
Is there anyway to handle this error?
... (3 Replies)
Discussion started by: mohanprabu
3 Replies
2. UNIX for Dummies Questions & Answers
I have a shell script, which calls a load script to load a database. How can i handle errors in Unix(similar to 'error level' in Batch scripts)? I am trying to use 'mailx' to send a Success/failure message based on the error level returned by the load script.
I have already used an error log... (2 Replies)
Discussion started by: sarsani
2 Replies
3. Shell Programming and Scripting
Hi All, I am new to this forum as well as to unix scripting.
Can you please help me to create a korn shell script to find out errors in logfiles and get the name of that logfile ( which is having error) in email and email it to me? (2 Replies)
Discussion started by: jithu
2 Replies
4. Shell Programming and Scripting
Hi All
I have a FTP script which FTPs few files into an user folder. I intend to keep track of the folder size before FTP and after FTP and print that once the FTP script is run (a kind of comparison, "Before FTP, "After FTP").
I decided to use kron shells to accomplish this.
#! /bin/ksh
... (2 Replies)
Discussion started by: guruparan18
2 Replies
5. Shell Programming and Scripting
Hello,
I have written a shell script and suppose there is any error in the script. How i can do exception handling in shell script.for example i have below code
sqlplus -s <<uid>>/<<pwd>>@<<$ORACLE_SID>> <<EOF > 1_pid1.log
set pagesize 0
set feedback off
set heading off
set linesize 200... (1 Reply)
Discussion started by: rksingh003
1 Replies
6. Shell Programming and Scripting
Hi all
I've got a question regarding error handling in shell scripts. My background is mainly object oriented programming languages, but for a year or so I've been doing more and more (bash) shell scripting (which I quite enjoy by the way).
To handle errors in my scripts I... (3 Replies)
Discussion started by: script_man
3 Replies
7. Shell Programming and Scripting
Hi, need help, I would like to know what is this IF statement trying to do? When the script is executing and error out with line 9 which is the IF statement line.
if ]
then
TOPDIR=$(pwd)
else
TOPDIR=${0%/*}
fi
TOPDIR=${TOPDIR%/*}
the log file.
Current system time is... (15 Replies)
Discussion started by: beooi
15 Replies
8. Shell Programming and Scripting
I am not able to capture error condition in sftp in Korn Shell
#!/bin/ksh
sftp batch@uat >abc 2>&1 << ENDFILE
cd public
put /data/WELCOME_55
ENDFILE
ret_val=$?
if ]
then
print file "copied successfully"
else
print file "NOT copied successfully"
fi
return 0
Now the... (9 Replies)
Discussion started by: Soham
9 Replies
9. Shell Programming and Scripting
Hi all,
I have a script which should take more than 9 command line inputs while running. Likescript.sh a s d f g h j j k l o p i u y t r e w
Now in the script if I have to access one of the input which is at position after 9, in this case say 'p' then how can I do that?
echo $12 will not work... (15 Replies)
Discussion started by: pat_pramod
15 Replies
10. Shell Programming and Scripting
Hi ,
My Script work as below
1-
On server 1
execute script1.sh ,
through this script one parameter file is generated as file.txt this is to transfer on server 2
2-
After reaching on server2 other shell script script2.sh execute using parameter file file.txt
This generate file... (1 Reply)
Discussion started by: kaushik02018
1 Replies
BEGIN(7) PostgreSQL 9.2.7 Documentation BEGIN(7)
NAME
BEGIN - start a transaction block
SYNOPSIS
BEGIN [ WORK | TRANSACTION ] [ transaction_mode [, ...] ]
where transaction_mode is one of:
ISOLATION LEVEL { SERIALIZABLE | REPEATABLE READ | READ COMMITTED | READ UNCOMMITTED }
READ WRITE | READ ONLY
[ NOT ] DEFERRABLE
DESCRIPTION
BEGIN initiates a transaction block, that is, all statements after a BEGIN command will be executed in a single transaction until an
explicit COMMIT(7) or ROLLBACK(7) is given. By default (without BEGIN), PostgreSQL executes transactions in "autocommit" mode, that is,
each statement is executed in its own transaction and a commit is implicitly performed at the end of the statement (if execution was
successful, otherwise a rollback is done).
Statements are executed more quickly in a transaction block, because transaction start/commit requires significant CPU and disk activity.
Execution of multiple statements inside a transaction is also useful to ensure consistency when making several related changes: other
sessions will be unable to see the intermediate states wherein not all the related updates have been done.
If the isolation level, read/write mode, or deferrable mode is specified, the new transaction has those characteristics, as if SET
TRANSACTION (SET_TRANSACTION(7)) was executed.
PARAMETERS
WORK, TRANSACTION
Optional key words. They have no effect.
Refer to SET TRANSACTION (SET_TRANSACTION(7)) for information on the meaning of the other parameters to this statement.
NOTES
START TRANSACTION (START_TRANSACTION(7)) has the same functionality as BEGIN.
Use COMMIT(7) or ROLLBACK(7) to terminate a transaction block.
Issuing BEGIN when already inside a transaction block will provoke a warning message. The state of the transaction is not affected. To nest
transactions within a transaction block, use savepoints (see SAVEPOINT(7)).
For reasons of backwards compatibility, the commas between successive transaction_modes can be omitted.
EXAMPLES
To begin a transaction block:
BEGIN;
COMPATIBILITY
BEGIN is a PostgreSQL language extension. It is equivalent to the SQL-standard command START TRANSACTION (START_TRANSACTION(7)), whose
reference page contains additional compatibility information.
The DEFERRABLE transaction_mode is a PostgreSQL language extension.
Incidentally, the BEGIN key word is used for a different purpose in embedded SQL. You are advised to be careful about the transaction
semantics when porting database applications.
SEE ALSO
COMMIT(7), ROLLBACK(7), START TRANSACTION (START_TRANSACTION(7)), SAVEPOINT(7)
PostgreSQL 9.2.7 2014-02-17 BEGIN(7)