ksh command substitution not executing block commands

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Vi quick substitution commands

I have a script that has quite a lot of these types of entries: hello=$(who am i) good=$(blahblah) what i want to do is replace the $( and the ) with `` so that they look like this: hello=`who am i` good=`blahblah` I tried this: :%s~=$(&&)$~=`&&`$~g

2. Shell Programming and Scripting

Using Sed to do a substitution inside ksh

I'm trying to do an ls from inside of a ksh script. I loop through the results one line at a time and attempt to do a substitution using sed to convert YYYYMMDD from the older files into the newer files. Basically sometimes the ETL load runs over midnight and half the files are off by one day...

3. Shell Programming and Scripting

Using commands inside sed substitution

Dear Friends, Please let me know how to use the date command inside the substitution flag replacement string. echo "01 Jan 2003:11:00:06 +0100" | sed 's/$.*$/`date -d \1 "+%Y%m%d%H%M%S"`/' I want to supply \1 string to Here mention below as part of replacement string, date -d <Here>...

4. Shell Programming and Scripting

bad substitution error in ksh

Hello, In bash I can use the following: TMP=12345 MID=${TMP:1:1} the expected result is: 2 but when using KSH I'm getting a ''bad substitution" error. What is the correct syntaxin ksh? Thanks

5. Shell Programming and Scripting

bad substitution error in ksh

hi, i created a shell script having the following content: #! /usr/bin/ksh FROM="myemail@domain.com" MAILTO="someemail@domain" SUBJECT="TEST" BODY="/export/home/adshocker/body.txt" ATTACH="/export/home/adshocker/attach.prog" echo $ATTACH ATTACH_NAME="${ATTACH##*/}" echo $ATTACH_NAME...

6. Shell Programming and Scripting

variable substitution in ksh

Hi I have a variable BIT1 which holds some value. Is there a way to retrieve the value of this variable indirectly via another variable, lets say SUBSET_BIT_NUM=1, so the call will look something like this: sundev1 $ echo ${BIT${SUBSET_BIT_NUM}} ksh: ${BIT${SUBSET_BIT_NUM}}: bad substitution ...

7. Solaris

Substitution not working in ksh

Hi, Following code is working in bash but not in ksh. Can someone please send me an alternative? #!/bin/ksh fname="EOA.dmp" echo $fname logname=${fname/.dmp/.log} echo $logname I am getting below error in ksh "testcmd: logname=${fname/.dmp/.log}: 0403-011 The specified substitution...

8. AIX

Substitution not working in ksh

Following code is working in bash but not in ksh. Can someone please send me an alternative? #!/bin/ksh fname="EOA.dmp" echo $fname logname=${fname/.dmp/.log} echo $logname I am getting below error in ksh "testcmd: logname=${fname/.dmp/.log}: 0403-011 The specified substitution is not...

9. Shell Programming and Scripting

KSH variable substitution

Hi folks Please let me know if anyone knows how to handle this. My KSH script -> testscript.ksh cmd=$1 ENV="devl" echo $cmd This is how I call the script ./testscript.ksh 'ps -ef | grep br$ENV' How do I get this to print the below text i.e $ENV should be substituted with the value...

10. Shell Programming and Scripting

ksh substitution

Hello, I thought it was possible to use several time a #! entry on a script but it doesn't seems to work. My need is to have a part of a ksh script without substitution so it would look like #!/bin/ksh -- first part --- #!/bin/ksh -f -- part without substitution -- #!/bin/ksh --...

LEARN ABOUT BSD

return

exit(1)                                                            User Commands                                                           exit(1)

NAME

       exit, return, goto - shell built-in functions to enable the execution of the shell to advance beyond its sequence of steps

SYNOPSIS

   sh
       exit [n]

       return [n]

   csh
       exit [ ( expr )]

       goto label

   ksh
       *exit [n]

       *return [n]

DESCRIPTION

   sh
       exit  will  cause the calling shell or shell script to exit with the exit status specified by n. If n is omitted the exit status is that of
       the last command executed (an EOF will also cause the shell to exit.)

       return causes a function to exit with the return value specified by n. If n is omitted, the return status is that of the last command  exe-
       cuted.

   csh
       exit  will cause the calling shell or shell script to exit, either with the value of the status variable or with the value specified by the
       expression expr.

       The goto built-in uses a specified label as a search string amongst commands. The shell rewinds its input as much as possible and  searches
       for a line of the form label: possibly preceded by space or tab characters. Execution continues after the indicated line. It is an error to
       jump to a label that occurs between a while or for built-in command and its corresponding end.

   ksh
       exit will cause the calling shell or shell script to exit with the exit status specified by n. The value will be the  least  significant  8
       bits of the specified status. If n is omitted then the exit status is that of the last command executed. When    exit occurs when executing
       a trap, the last command refers to the command that executed before the trap was invoked. An end-of-file will also cause the shell to  exit
       except for a shell which has the ignoreeof option (See set below) turned on.

       return  causes a shell function or '.' script to return to the invoking script with the return status specified by n. The value will be the
       least significant 8 bits of the specified status.  If n is omitted then the return status is that of the last command executed.  If  return
       is invoked while not in a function or a '.' script, then it is the same as an exit.

       On this man page, ksh(1) commands that are preceded by one or two * (asterisks) are treated specially in the following ways:

       1.  Variable assignment lists preceding the command remain in effect when the command completes.

       2.  I/O redirections are processed after variable assignments.

       3.  Errors cause a script that contains them to abort.

       4.  Words,  following a command preceded by ** that are in the format of a variable assignment, are expanded with the same rules as a vari-
           able assignment. This means that tilde substitution is performed after the = sign and word splitting and file name generation  are  not
           performed.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE         |      ATTRIBUTE VALUE        |
       |Availability                 |SUNWcsu                      |
       +-----------------------------+-----------------------------+

SEE ALSO

       break(1), csh(1), ksh(1), sh(1), attributes(5)

SunOS 5.10                                                          15 Apr 1994                                                            exit(1)

Shell Programming and Scripting