Sponsored Content
Full Discussion: Validating Input parameters
Top Forums Shell Programming and Scripting Validating Input parameters Post 302305238 by Amit.Sagpariya on Wednesday 8th of April 2009 10:11:39 AM
Old 04-08-2009
Hi all,

This is the solution...

Quote:
date=$( echo $1 |ckdate -f "%Y%m%d" )

if [[ $? == 0 ]]
then
print " success"
else
print "no success"
fi
This utility will help to reduce the code, while validating the input parameters.
 

10 More Discussions You Might Find Interesting

1. Programming

validating input

how do i validate y script so that it only accepts values between 1 and 3 and against any character input, cause at the moment i can only validate against numbers outside 1 and 3 but not characters cheers (4 Replies)
Discussion started by: ruffenator
4 Replies

2. Shell Programming and Scripting

validating input using regular expressions

I am trying to validate input from the user in a script. I thought is was easy to do using regular expressions but I can't figure out how to use REs in a conditional. I have tried using grep from a temp file, sed from a temp file, sed from command line, comparison in an if condition and I cannot... (1 Reply)
Discussion started by: nrodolfich
1 Replies

3. Shell Programming and Scripting

Input parameters

I have a script which take 3 input parameters 1st - a date (i.e. current date) 2nd - type (i.e. A) 3rd - limit (i.e. 40) normally the date parameter would be current date, so I thought I could do this calculate.sh $(date +%Y-%m-%d) A 40 however, it seems like it can't be done,... (3 Replies)
Discussion started by: mpang_
3 Replies

4. Shell Programming and Scripting

Validating the input date format

I have one script.for that the inputs are fromdate(dd/mon/yyyy) and todate(dd/mon/yyyy). How i can validate the input format?for eg.27/08/2008 is not valid.27/aug/2008 or 27/Aug/2008 are valid. and the todate is optional.so if the todate is not present in the input then i need to assign the... (6 Replies)
Discussion started by: Sharmila_P
6 Replies

5. Shell Programming and Scripting

Validating user input is not blank

Trying to create a script in BASH that would ask the user to enter another user name making sure the input is not blank before they hit enter then to check the home directory of that user does exist, I have the check folder sorted it's just the loop to make sure the user has entered chars (5 Replies)
Discussion started by: MBN
5 Replies

6. Shell Programming and Scripting

validating a input file for numeric and character

i have a input file like this 001|rahim|bajaj|20090102 while reading the file i need to check whether the first column is a number second column is a name is there any methodology to check for the same thanks in advance (2 Replies)
Discussion started by: trichyselva
2 Replies

7. UNIX for Dummies Questions & Answers

Validating input based on fixed number of fields

Yes, i did... let me state my problem in more detail Inputs: I have one input CSV file And, i have stored no. of comma each line should in a variable. e.g. $ cat cmt.csv this, is a ,comma ,count test1 ,,this, is a ,comma ,count test2 this, is a ,comma ,count test3... (6 Replies)
Discussion started by: Dipali
6 Replies

8. UNIX for Dummies Questions & Answers

Validating user input

I'm trying to set up a script that takes user input and validates that the user input was entered correctly. So far I have this: while : do echo "Please enter your name." read NAME if then echo "You have not entered a name." echo... (13 Replies)
Discussion started by: fufaso
13 Replies

9. Shell Programming and Scripting

Validating uppercase/lowercase of user input with perl compared to unix folders

Hi, I need to copy files from a source directory to a destination directory in unix. I'm using the file::copy for the actual copy. The problem is that the source and dest directories are supplied by different users, who might type the name of the directories in various combinations of lower... (6 Replies)
Discussion started by: Furou
6 Replies

10. Shell Programming and Scripting

How can I take input parameters after the first one?

Hi, Is there a simple way to take input of parameters after the first one? As following example, if I assign others=$2, it only takes the second one, if I assign others=$@, it will include the first one. I may try to assign others="$2 $3 $4 $5 $6 $7 $8 $9", it looks very ugly and could missing... (1 Reply)
Discussion started by: hce
1 Replies
SH(1)							      General Commands Manual							     SH(1)

NAME
sh, ., break, case, cd, continue, eval, exec, exit, export, for, if, read, readonly, set, shift, trap, umask, wait, while - shell SYNOPSIS
sh [-eiknqstvxu] [-c str] [file] OPTIONS
-c Execute the commands in str -e Quit on error -i Interactive mode; ignore QUIT, TERMINATE, INTERRUPT -k Look for name=value everywhere on command line -n Do not execute commands -q Change qflag from sig_ign to sig_del -s Read commands from standard input -t Exit after reading and executing one command -v Echo input lines as they are read -x Trace -u Unset variables EXAMPLES
sh script # Run a shell script DESCRIPTION
Sh is the shell, which forms the user's main interface with the system. On startup, the shell reads /etc/profile and $HOME/.profile, if they exist, and executes any commands they contain. The Minix shell has most of the features of the V7 (Bourne) shell, including redirect- ion of input and output, pipes, magic characters, background processes, and shell scripts. A brief summary follows, but whole books have been written on shell programming alone. Some of the more common notations are: date # Regular command sort <file # Redirect stdin (standard input) sort <file1 >file2 # Redirect stdin and stdout cc file.c 2>error # Redirect stderr a.out >f 2>&1 # Combine standard output and standard error sort <file1 >>file2 #Append output to file2 sort <file1 >file2 & #Background job (ls -l; a.out) & # Run two background commands sequentially sort <file | wc # Two-process pipeline sort <f | uniq | wc # Three-process pipeline ls -l *.c # List all files ending in .c ls -l [a-c]* # List all files beginning with a, b, or c ls -l ? # List all one-character file names ls ? # List the file whose name is question mark ls '???' # List the file whose name is three question marks v=/usr/ast # Set shell variable v ls -l $v # Use shell variable v PS1='Hi! ' # Change the primary prompt to Hi! PS2='More: ' # Change the secondary prompt to More: ls -l $HOME # List the home directory echo $PATH # Echo the search path echo $? # Echo exit status of previous command in decimal echo $$ # Echo shell's pid in decimal echo $! # Echo PID of last background process echo $# # Echo number of parameters (shell script) echo $2 # Echo second parameter (shell script) echo "$2" # Echo second parameter without expanding spaces echo $* # Echo all parameters (shell script) echo $@ # Echo all parameters (shell script) echo "$@" # Echo all parameters without expanding spaces The shell uses the following variables for specific purposes: SHELL the path of the current shell HOME the default value for the cd(1) command PATH the directories to be searched to find commands IFS the internal field separators for command strings PS1 the primary shell prompt PS2 the secondary shell prompt There are various forms of substitution on the shell command line: `...` Command string between back-quotes is replaced by its output "..." Permits variable substitution between quotes '...' Inhibits variable substitution between quotes $VAR Replaced by contents of variable VAR ${VAR} Delimits variable VAR from any following string The expressions below depend on whether or not VAR has ever been set. If VAR has been set, they give: ${VAR-str} Replace expression by VAR, else by str ${VAR=str} Replace expression by VAR, else by str and set VAR to str ${VAR?str} Replace expression by VAR, else print str and exit shell ${VAR+str} Replace expression by str, else by null string If a colon is placed after VAR, the expressions depend on whether or not VAR is currently set and non-null. The shell has a number of built-in commands: : return true status . fn execute shell script fn on current path break [n] break from a for, until or while loop; exit n levels continue [n] continue a for, until or while loop; resume nth loop cd [dir] change current working directory; move to $HOME eval cmd rescan cmd, performing substitutions eval rescan the current command line exec cmd execute cmd without creating a new process exec <|> with no command name, modify shell I/O exit [n] exit a shell program, with exit value n export [var] export var to shell's children; list exported variables pwd print the name of the current working directory read var read a line from stdin and assign to var readonly [var] make var readonly; list readonly variables set -f set shell flag (+f unsets flag) set str set positional parameter to str set show the current shell variables shift reassign positional parameters (except ${0}) one left times print accumulated user and system times for processes trap arg sigs trap signals sigs and run arg on receipt trap list trapped signals umask [n] set the user file creation mask; show the current umask wait [n] wait for process pid n; wait for all processes The shell also contains a programming language, which has the following operators and flow control statements: # Comment The rest of the line is ignored = Assignment Set a shell variable && Logical AND Execute second command only if first succeeds || Logical OR Execute second command only if first fails (...) Group Execute enclosed commands before continuing for For loop (for ... in ... do ... done) case Case statement ((case ... ) ... ;; ... esac) esac Case statement end while While loop (while ... do ... done) do Do/For/While loop start (do ... until ...) done For/While loop end if Conditional statement (if ... else ... elif ... fi) in For loop selection then Conditional statement start else Conditional statement alternative elif Conditional statement end until Do loop end fi Conditional statement end SEE ALSO
echo(1), expr(1), pwd(1), true(1). SH(1)
All times are GMT -4. The time now is 12:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy