I am writing a script in which I am using an IF-Else statement.
Code sample:
Code:
# Check for the product.
If (test "$3" = "Pet") Then
Product_Code="PI"
elif (test "$3" = "Breakdown") Then
Product_Code="RI"
elif (test "$3" = "Travel") Then
Product_Code="TI"
elif (test "$3" = "Dental & Health") Then
Product_Code="DI"
elif (test "$3" = "FRIENDS PROVIDENT LIFE") Then
Product_Code="LI"
elif (test "$3" = "LIFE 2") Then
Product_Code="OF"
elif (test "$3" = "Aviva Life") Then
Product_Code="LI"
elif (test "$3" = "Direct Line Life") Then
Product_Code="LI"
echo 'Not a valid Product'
exit 1;
fi
Please correct me if anything is wrong. Now I want to exit out if I don't have any matching condition and print the message 'Not a valid Product'
on the prompt.
I have more statements to follow if any of the condition matches.
Hi Friends,
Is it possible to exit nicely(ie, to echo a message with the error occurred) from a shell script(quiet a big one :)) once it encounter an error in between the lines?
For example, in my script I am calling the command mkdir and sometimes (when the directory already exists) it... (4 Replies)
Hello again all. I have a user editable script that I'd like to have point out the user error to. Problem is I'm having troubles getting an echoed error message to give me the line. Here's what I'm trying to do. grep -n $loc /this/script.sh where '$loc' is the argument passed to the script.... (9 Replies)
Hi,
I have a shell script which is residing on AIX which is triggered by Mainframe through Connect Direct. The shell script creates several files and sends those files to mainframe using Connect Direct. The shell script is working fine, still it is returning exit code 2 to mainframe.
What... (0 Replies)
Hi,
I have initailized a varaible EBID as typeset Long EBID=0
i am calculating value of EBID using certian formula as below:
(( CURR_EBID= ($BANDINDEX << 27) | ($CURR_FREQ << 16) | ($CURR_CELLID << 4) | $CURR_SECTOR_VALUE ))
return $CURR_EBID
The output is as below:
+ (( CURR_EBID=... (6 Replies)
I am having a parent scripts which reads a file with child scripts name.
I need to read one by one child script , execute it and
1. If child script fails send mail to the team with the log file
2. If the child script executes fine then proceed with the next child script execution.
#!... (3 Replies)
We are having issues with our Postfix. The POP and IMAP services randomly stops working an sent e-mails return a "Command time limit exceeded".
We've found out that running these command fix the problem:
service cyrus-imapd stop
rm /var/lib/imap/tls_sessions.db*
rm... (2 Replies)
Script name is test.ksh
I know that that the ssh command is working properly, this can be verified by the value returned in respond variable. It is unique to the remote server
_____________________________________________________
respond=$(ssh $remoteHost find... (3 Replies)
hi all,
I created a sh script to import some tables from mysql to hive.
No problem launching it manually, but if I schedule via crontab it returns me an error in the following part:
#create an array containing all the tables for $dbname
query="SELECT table_name FROM information_schema.tables'... (10 Replies)
Greeting!!
I wrote the below script to e-mail me only file names in a specific directory when a file is delayed for some time in a that directory. I am getting unexpected eof error message.
I don't want any email if the folder is blank.(if the condition is not met) I am not getting the email at... (4 Replies)
I have this UNIX script code with a query to export sql table in Oracle and export to csv file. The code gets the data correctly. However, when I run the script second time, I got the error message "not spooling currently" and shows the older data in csv file. When I delete the csv file and run... (5 Replies)
Discussion started by: Hope
5 Replies
LEARN ABOUT REDHAT
xmlif
XMLIF(1)XMLIF(1)NAME
xmlif - conditional processing instructions for XML
SYNOPSIS
xmlif [attrib=value...]
DESCRIPTION
xmlif filters XML according to conditionalizing markup. This can be useful for formatting one of several versions of an XML document
depending on conditions passed to the command.
Attribute/value pairs from the command line are matched against the attributes associated with certain processing instructions in the docu-
ment. The instructions are <?if> and its inverse <?if not>, <?elif> and its inverse <?elif not>, <?else>, and <?fi>.
Argument/value pairs given on the command line are checked against the value of corresponding attributes in the conditional processing
instructions. An `attribute match' happens if an attribute occurs in both the command-line arguments and the tag, and the values match. An
`attribute mismatch' happens if an attribute occurs in both the command-line arguments and the tag, but the values do not match.
Spans between <?if> or <?elif> and the next conditional processing instruction at the same nesting level are passed through unaltered if
there is at least one attribute match and no attribute mismatch; spans between <?if not> and <?elif not> and the next conditional process-
ing instruction are passed otherwise. Spans between <?else> and the next conditional-processing tag are passed through only if no previous
span at the same level has been passed through. <?if> and <?fi> (and their `not' variants) change the current nesting level; <?else> and
<?elif> do not.
All these processing instructions will be removed from the output produced. Aside from the conditionalization, all other input is passed
through untouched; in particular, entity references are not resolved.
Value matching is by string equality, except that "|" in an attribute value is interpreted as an alternation character. Thus, saying
foo='red|blue' on the command line enables conditions red and blue. Saying color='black|white' in a tag matches command-line conditions
color='black' and color='white'.
Here is an example:
Always issue this text.
<?if condition='html'>
Issue this text if 'condition=html' is given on the command line.
<?elif condition='pdf|ps'>
Issue this text if 'condition=pdf' or 'condition=ps'
is given on the command line.
<?else>
Otherwise issue this text.
<?fi>
Always issue this text.
FUTURE DIRECTIONS
The mark-up used by this tool is not set in stone, and may change in the near future.
AUTHOR
Eric S. Raymond.
Sep 26 2002 XMLIF(1)
11-15-2011
Script returning an error message on exiting
