Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Using an array with a case statement in KSH
Top Forums Shell Programming and Scripting Using an array with a case statement in KSH Post 302565558 by otheus on Tuesday 18th of October 2011 07:54:05 AM
Old 10-18-2011
You're doin' great for a scripting newb.

The do ... done are not necessary here.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Case Statement

Can anyone please tell me why this wont work! Thanks so much! #!/bin/sh for file do case $file in *.*.*) echo Cannot have more than 1 dot exit ;; *'**'*) echo Cannot have more than 1 asterisk exit ;; *'*'*|?.) echo this is a target (19 Replies)
Discussion started by: Zeta_Acosta
19 Replies

2. UNIX for Dummies Questions & Answers

CASE statement

Hi, I am writing a bash shell script. My script has a few user defined parameters. When the script runs the first thing it does is make sure that these parameters are valid. One of the parameters is called YEAR. A valid input for YEAR can be 1997-2000. One way I have come up with to ensure... (3 Replies)
Discussion started by: msb65
3 Replies

3. Shell Programming and Scripting

ksh case statement

I am trying to write a ksh script using the case statement to select certain directories to remove. The directories that I am looking for are in the following format 2008-10-10. I want to exclude all other files/directories that contain anything other the 4 digit year,a dash, 2 digit month, a... (2 Replies)
Discussion started by: dgilc
2 Replies

4. UNIX for Dummies Questions & Answers

case statement in UNIX scripting (ksh)

Hi, I have a script like below : #!/bin/ksh echo "Do you want to export all docs ?" read alld echo "Do you want to export template or report only " read temr case && ] #arguments ;; case && ] #arguments ;; case && ] #arguments ;; (4 Replies)
Discussion started by: luna_soleil
4 Replies

5. Shell Programming and Scripting

ksh "case" statement question

Hi I have the following case statement: case $larg in *_* ) a=${larg%_*}; b=${larg#*_}; ;; *^* ) a=${larg%^*}; b=${larg#*^}; ;; esac I cannot figure out what *_* and *^* stand for... Also what a=${larg%_*}; b=${larg#*_}; and a=${larg%^*}; b=${larg#*^}; ... (1 Reply)
Discussion started by: aoussenko
1 Replies

6. Shell Programming and Scripting

case statement

Hi, I am writing case statement to execute some finction, my requirement is once one of the case statement is executed again it has to prompt for the option. for script in `echo "$Script_Selected"` do case $script in 1) getNoOFActUsers ;; 2) moveServerrOORotation ;; ... (2 Replies)
Discussion started by: Satyak
2 Replies

7. Shell Programming and Scripting

How to remove a defined character on an array variable in a do while statement in ksh

I have a korn shell code here on a while do statement which replace the string stored on an array removing double quotes characters on it but it doesn't work. example record: appointmentDate = "tree" which value should result to tree #!/bin/ksh # Remove " on string records let recordCount=3... (5 Replies)
Discussion started by: ryukishin_17
5 Replies

8. Shell Programming and Scripting

data array needs to change upper case to lower case

Hi all, i have a data array as followes. ARRAY=DFSG345GGG ARRAY=234FDFG090 ARRAY=VDFVGBGHH so on.......... i need all english letters to be change to lower case. So i am expecting to see ARRAY=dfsg345ggg ARRAY=234fdfg090 ARRAY=vdfvgbghh so on........ If i have to copy this data in... (8 Replies)
Discussion started by: usustarr
8 Replies

9. Shell Programming and Scripting

Case statement

Hello, The standard case statement :- case "$1" in "IE0263") commands;; "IE0264") commands;; esac is it possible to have :- case "$1" in "IE0263" OR "IE0878") commands;; "IE0264") commands;; esac Thanks (4 Replies)
Discussion started by: jmahal
4 Replies

10. Shell Programming and Scripting

ksh case statement issue

Hi. I wrote the following case statement to replace a series of 'ELIF' statements as it looks better and is easier to maintain. However, for some reason the commands don't fully work in this format. Take option 1. It should call a script that runs in the background but it doesn't work. Can anyone... (3 Replies)
Discussion started by: user052009
3 Replies

LEARN ABOUT CENTOS

lksh

LKSH(1) 						    BSD General Commands Manual 						   LKSH(1)

NAME

     lksh -- Legacy Korn shell built on mksh

SYNOPSIS

     lksh [-+abCefhiklmnprUuvXx] [-+o opt] [-c string | -s | file [args ...]]

DESCRIPTION

     lksh is a command interpreter intended exclusively for running legacy shell scripts.  It is built on mksh; refer to its manual page for
     details on the scripting language.  It is recommended to port scripts to mksh instead of relying on legacy or idiotic POSIX-mandated behav-
     iour, since the MirBSD Korn Shell scripting language is much more consistent.

LEGACY MODE

     lksh has the following differences from mksh:

     o	 lksh is not suitable for use as /bin/sh.

     o	 There is no explicit support for interactive use, nor any command line editing or history code.  Hence, lksh is not suitable as a user's
	 login shell, either; use mksh instead.

     o	 The KSH_VERSION string identifies lksh as ``LEGACY KSH'' instead of ``MIRBSD KSH''.

     o	 lksh only offers the traditional ten file descriptors to scripts.

     o	 lksh uses POSIX arithmetics, which has quite a few implications: The data type for arithmetics is the host ISO C long data type.  Signed
	 integer wraparound is Undefined Behaviour.  The sign of the result of a modulo operation with at least one negative operand is unspeci-
	 fied.	Shift operations on negative numbers are unspecified.  Division of the largest negative number by -1 is Undefined Behaviour.  The
	 compiler is permitted to delete all data and crash the system if Undefined Behaviour occurs.

     o	 The rotation arithmetic operators are not available.

     o	 The shift arithmetic operators take all bits of the second operand into account; if they exceed permitted precision, the result is
	 unspecified.

     o	 The GNU bash extension &> to redirect stdout and stderr in one go is not parsed.

     o	 The mksh command line option -T is not available.

     o	 Unless set -o posix is active, lksh always uses traditional mode for constructs like:

	       $ set -- $(getopt ab:c "$@")
	       $ echo $?

	 POSIX mandates this to show 0, but traditional mode passes through the errorlevel from the getopt(1) command.

     o	 lksh, unlike AT&T UNIX ksh, does not keep file descriptors > 2 private.

SEE ALSO

     mksh(1)

     https://www.mirbsd.org/mksh.htm

     https://www.mirbsd.org/ksh-chan.htm

CAVEATS

     lksh tries to make a cross between a legacy bourne/posix compatibl-ish shell and a legacy pdksh-alike but ``legacy'' is not exactly speci-
     fied.

     The set built-in command does not have all options one would expect from a full-blown mksh or pdksh.

     Talk to the MirOS development team using the mailing list at <miros-mksh@mirbsd.org> or the #!/bin/mksh (or #ksh) IRC channel at
     irc.freenode.net (Port 6697 SSL, 6667 unencrypted) if you need any further quirks or assistance, and consider migrating your legacy scripts
     to work with mksh instead of requiring lksh.

MirBSD								    May 2, 2013 							    MirBSD
All times are GMT -4. The time now is 01:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy