11-29-2018
In which editor did you originally write the code?
The script runs fine for me but when I write it in a text editor like OpenOffice and then paste it into vi then I get a problem similar to the one you describe.
And indeed, the command cat -A hello then shows all kind of characters that don't belong there.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am trying to set up a variable based on the name of the file.
function script_name {
if
then
job_name='MONITOR'
return job_name;
elsif
then
job_name='VERSION'
return job_name
fi
}
for i in `ls *log`
do
script_name $i
done. (4 Replies)
Discussion started by: oracle8
4 Replies
2. Shell Programming and Scripting
:b:hi,
I have a script as given below:
pr_det="1"
if
then
awk ' BEGIN {printf("%23s","session")}' >> report.txt
awk ' BEGIN {printf "\n"} ' >> report.txt
else
awk ' BEGIN {printf("%55s","file_dsc")} ' >> report.txt
awk ' BEGIN {printf("%101s","no_recs")} '... (1 Reply)
Discussion started by: jisha
1 Replies
3. Shell Programming and Scripting
year=`date '+%Y'`
month=`date '+%m'`
day=`date '+%d'`
day=`expr $day - 1`
case $month in
1 | 3 | 5 | 7 | 8 | 10 | 12);;
if($day =7 ); then
$day=6
fi
4 | 6 | 9 | 11);;
if ; then
$day=31
fi
2);;
if ; then
if ; then (2 Replies)
Discussion started by: dannyd_y
2 Replies
4. Linux
Hi ,
I am getting an error when I run the script for checking word "view" in a file . I am using if statement. like this
if
then
VW_VAR=` cat $TN.${ecmdate}.sql1 | grep -i view | awk '{print $3}' | cut -d '.' -f2 `
echo " VW_$VW_VAR "
sed -e... (16 Replies)
Discussion started by: capri_drm
16 Replies
5. Shell Programming and Scripting
HI i am getting error while executing the given statement
for filename in `cat a/file.lst`
do
if then
echo "Exit Code Description :File $filename - is missing in Input Directory" >a.log
exit
else
count1=`awk 'END {print NR}' $filename`
echo "$count1">>a.log
count2=`awk 'END {print... (4 Replies)
Discussion started by: ravi214u
4 Replies
6. UNIX for Dummies Questions & Answers
Hi,
This is my script to catch any oracle errors.
In this, the $sqlerr returns
ORA-01017: invalid username/password; logon denied
when i specify wrong username/password
the if condition is failing. how can i resolve the issue.
the if statement gives error
sqloutput=`sqlplus -s -L... (1 Reply)
Discussion started by: Swapna173
1 Replies
7. UNIX for Dummies Questions & Answers
Hi, can someone please tell me what is wrong with this code? I just want it to check if the file size is greater than 2000kb.
if
Thanks!
---------- Post updated at 09:23 PM ---------- Previous update was at 09:21 PM ----------
I should probably post the full code:
#!/bin/sh... (9 Replies)
Discussion started by: Bengel
9 Replies
8. UNIX for Dummies Questions & Answers
Hi all,
After so many tries and searching online for ideas, I had trouble accomplishing this. Is it possible to do something like this in KSH to run an if statement on a return code?
Unfortunately the code below fails... Would anyone know how to fix the below attempt?
if "$`{pkginfo... (3 Replies)
Discussion started by: chatguy
3 Replies
9. Shell Programming and Scripting
I am working on script for stale nfs.
the file consists of
cat data01stale.log
- - - - /abcd/backup
- - - - /abcd/data
Script (16 Replies)
Discussion started by: nareshkumar522
16 Replies
10. UNIX for Dummies Questions & Answers
Good morning,
I am 100% mew to Unix and am trying to troubleshoot why a pgm written 3 years ago, suddenly is not working properly. It is part Perl with some UNIX commands thrown in. I need to verify what the UNIX commands are doing before I can continue with my other troubleshooting.
print... (7 Replies)
Discussion started by: jaacmmason
7 Replies
EX(1) General Commands Manual EX(1)
NAME
ex, edit - text editor
SYNOPSIS
ex [ - ] [ -v ] [ -t tag ] [ -r ] [ +command ] [ -l ] name ...
edit [ ex options ]
DESCRIPTION
Ex is the root of a family of editors: edit, ex and vi. Ex is a superset of ed, with the most notable extension being a display editing
facility. Display based editing is the focus of vi.
If you have not used ed, or are a casual user, you will find that the editor edit is convenient for you. It avoids some of the complexi-
ties of ex used mostly by systems programmers and persons very familiar with ed.
If you have a CRT terminal, you may wish to use a display based editor; in this case see vi(1), which is a command which focuses on the
display editing portion of ex.
DOCUMENTATION
The document Edit: A tutorial (USD:14) provides a comprehensive introduction to edit assuming no previous knowledge of computers or the
UNIX system.
The Ex Reference Manual - Version 3.7 (USD:16) is a comprehensive and complete manual for the command mode features of ex, but you cannot
learn to use the editor by reading it. For an introduction to more advanced forms of editing using the command mode of ex see the editing
documents written by Brian Kernighan for the editor ed; the material in the introductory and advanced documents works also with ex.
An Introduction to Display Editing with Vi (USD:15) introduces the display editor vi and provides reference material on vi. In addition,
the Vi Quick Reference card summarizes the commands of vi in a useful, functional way, and is useful with the Introduction.
FILES
/usr/share/misc/exstrings error messages
/usr/libexec/exrecover recover command
/usr/sbin/expreserve preserve command
/etc/termcap describes capabilities of terminals
~/.exrc editor startup file
/tmp/Exnnnnn editor temporary
/tmp/Rxnnnnn named buffer temporary
/usr/preserve preservation directory
SEE ALSO
awk(1), ed(1), grep(1), sed(1), grep(1), vi(1), termcap(5), environ(7)
AUTHOR
Originally written by William Joy
Mark Horton has maintained the editor since version 2.7, adding macros, support for many unusual terminals, and other features such as word
abbreviation mode.
BUGS
The undo command causes all marks to be lost on lines changed and then restored if the marked lines were changed.
Undo never clears the buffer modified condition.
The z command prints a number of logical rather than physical lines. More than a screen full of output may result if long lines are
present.
File input/output errors don't print a name if the command line `-' option is used.
There is no easy way to do a single scan ignoring case.
The editor does not warn if text is placed in named buffers and not used before exiting the editor.
Null characters are discarded in input files, and cannot appear in resultant files.
4th Berkeley Distribution October 21, 1996 EX(1)