12-11-2008
This isn't really a scripting question so much as a DB2 question, because the return codes for different error or warning conditions while executing DB2 are entirely defined by DB2.
Perhaps if you check the DB2 documentation it will describe what codes are returned under what conditions, and thereby allow you modify your shell script to handle them appropriately. Maybe it would be safe for you to ignore error code 1, and only report other error codes.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a file "dbshot.xml" that contains lines that need replacing in a batch format but the parameters are based on two lines.
Ex.
<role roletype="01">
<status>1
needs to be changed to
<role roletype="01">
<status>0
I can't use simply "<status>1" replace since the... (2 Replies)
Discussion started by: E Orgill
2 Replies
2. UNIX Desktop Questions & Answers
Issue resolved:
The 'culprit file' was .bash_aliases. It had the naughty (ASCII for the octal string Bash was detecting and returning an error about). I cleaned it up in Pico (see my post to the thread on favorite editors if you want background on why I use Pico/Nano), re-sourced it via... (0 Replies)
Discussion started by: SilversleevesX
0 Replies
3. Shell Programming and Scripting
Hi All,
Does anyone has script to align java/c/c++ code? or pls advice
I need it very badly...... :-(
Thanks in advance (4 Replies)
Discussion started by: askumarece
4 Replies
4. Shell Programming and Scripting
I have another Question:
I tried to run the following script: (I actually wanted to print out the second field in the text field.)
#!/usr/bin/ksh
set -x
readfile=/dir1/data.txt
cat $readfile | while read line
do
x = `echo $line|awk '{print $2}'`
echo $x
done
But, it shows the... (3 Replies)
Discussion started by: ss3944
3 Replies
5. Shell Programming and Scripting
I am writing a wrapper to one of the .ksh script. The wrapper script should capture the error/fatal(if any) and exit out of the script. Here is the script:
#!/bin/sh
. main_script.ksh <arg1> <arg2> > mainscript.log 2>&1
cnt=`grep 'ERROR' -c mainscript.log`
if ; then
echo "Error"
... (6 Replies)
Discussion started by: stunnerz_84
6 Replies
6. Red Hat
I am running a script that runs a loop and executes a command on ${i} until the end of the for loop.
From time to time the command generates an error ( which is good) for example ERROR0005:
How can I trap the error and send an email echoing the ${i} variable in the loop and the error ?
... (2 Replies)
Discussion started by: pcpinkerton
2 Replies
7. Shell Programming and Scripting
Hi
i need code to get sql queries through a shell script for a text file input which contain the service ids
iputfile
I-H-2048-10GB-M
I-H-4096-12GB-M
I-H-2048-p1000-M
the code should contain below queries among which service_id is replacable with value from input file.
... (4 Replies)
Discussion started by: surender reddy
4 Replies
8. Shell Programming and Scripting
Hey Friends, its me again! :o
I was asked to create a script that would go into our backup directories and delete/purge anything in the directory after a certain amount of days, normally I would be able to write something up that goes to the directory finds it and deletes it.
cd... (12 Replies)
Discussion started by: gkelly1117
12 Replies
9. Red Hat
I have an application rpm which when installed is failing to get installed with error
error: Failed dependencies:
libc.so.6 is needed by testSam-4.7.x86_64
libc.so.6(GLIBC_2.0) is needed by testSam-4.7.x86_64
libc.so.6(GLIBC_2.1) is needed by testSam-4.7.x86_64
... (1 Reply)
Discussion started by: rupeshkp728
1 Replies
DDB(8) BSD System Manager's Manual DDB(8)
NAME
ddb -- configure DDB kernel debugger properties
SYNOPSIS
ddb capture [-M -core] [-N -system] print
ddb capture [-M -core] [-N -system] status
ddb script scriptname
ddb script scriptname=script
ddb scripts
ddb unscript scriptname
ddb pathname
DESCRIPTION
The ddb utility configures certain aspects of the ddb(4) kernel debugger from user space that are not configured at compile-time or easily
via sysctl(8) MIB entries.
To ease configuration, commands can be put in a file which is processed using ddb as shown in the last synopsis line. An absolute pathname
must be used. The file will be read line by line and applied as arguments to the ddb utility. Whitespace at the beginning of lines will be
ignored as will lines where the first non-whitespace character is '#'.
OUTPUT CAPTURE
The ddb utility can be used to extract the contents of the ddb(4) output capture buffer of the current live kernel, or from the crash dump of
a kernel on disk. The following debugger commands are available from the command line:
capture [-M core] [-N system] print
Print the current contents of the ddb(4) output capture buffer.
capture [-M core] [-N system] status
Print the current status of the ddb(4) output capture buffer.
SCRIPTING
The ddb utility can be used to configure aspects of ddb(4) scripting from user space; scripting support is described in more detail in
ddb(4). Each of the debugger commands is available from the command line:
script scriptname
Print the script named scriptname.
script scriptname=script
Define a script named scriptname. As many scripts contain characters interpreted in special ways by the shell, it is advisable to
enclose script in quotes.
scripts
List currently defined scripts.
unscript scriptname
Delete the script named scriptname.
EXIT STATUS
The ddb utility exits 0 on success, and >0 if an error occurs.
EXAMPLES
The following example defines a script that will execute when the kernel debugger is entered as a result of a break signal:
ddb script kdb.enter.break="show pcpu; bt"
The following example will delete the script:
ddb unscript kdb.enter.break
For further examples, see the ddb(4) and textdump(4) manual pages.
SEE ALSO
ddb(4), textdump(4), sysctl(8)
HISTORY
The ddb utility first appeared in FreeBSD 7.1.
AUTHORS
Robert N M Watson
BUGS
Ideally, ddb would not exist, as all pertinent aspects of ddb(4) could be configured directly via sysctl(8).
BSD
December 24, 2008 BSD