Both file1.txt and file2.txt have line separators that are <carriage-return><newline> character pairs instead of just <newline> and neither of these files end with a <newline> character. So, by definition, they are not text files. Since the last lines in file1.txt and file2.txt were incomplete lines, id "At3g02190" might not have been processed correctly (if it had appeared in file3.txt) and code "S" (if it had been the code for any id that was being processed) might not have been handled as desired.
The following script adds trailing <newlines> characters to each input file (in the echo loop at the start of the script) and removes any <carriage-return> characters found in the input (using gsub()) and any empty lines (which were already present in file2.txt and may now have been created by the echo loop) while processing the input files. The logic is similar to Yoda's script, but gets rid of some processing by using a more complex ERE for the field separator:
Code:
#!/bin/ksh
# Add trailing newlines to the input files.
for i in 1 2 3
do echo >> file$i.txt
done
awk -F '[[]|] |th: | *$' '
BEGIN { OFS = "|" }
{ # Get rid of any carriage returns characters in the input files.
gsub(/\r/, "")
}
/^$/ { next } # Skip empty lines.
FNR == 1 { f++ }
f == 1 {# Gather codes for id from 1st file:
if($0 ~ /^[[]/) {# If line start with "[", it contains the code
c = substr($2, 1, 1) # Discard trailing "R", if present.
next
}
code[$2] = c # Otherwise, we have an id; save the code for this id.
next
}
f == 2 {# Gather description for each code from 2nd file:
if(NF == 1) # Save code group heading.
h = $0
else # Save code description.
desc[$2] = $3 OFS h
next
}
{ # We must be looking at the 3rd file. Print description for given id.
print $1, code[$1], desc[code[$1]]
}' file[123].txt
I use the Korn shell, but any shell that accepts basic Bourne shell syntax will work with this script. If you want to run this on a Solaris/SunOS system, change awk to /usr/xpg4bin/awk, /usr/xpg6/bin/awk, or nawk.
The output produced with the sample inputs is:
Code:
At1g53930|O|Posttranslational modification, protein turnover, chaperones|CELLULAR PROCESSES AND SIGNALING
At2g36170|J|Translation, ribosomal structure and biogenesis|INFORMATION STORAGE AND PROCESSING
which seems to match what was requested except that there is no space character immediately after the last "|" in each line.
if;
sqlplus /nolog <<EOF
conn / as sysdba
spool /tmp/start.out
@/oracle/home/start.sql
spool off
exit
EOF
fi
For this code i am getting error:
Test.sh: syntax error at line 7 : `<<' unmatched (8 Replies)
Hi,
I have three ip address say x.x.x.x , y.y.y.y and z.z.z.z
I am connecting to x.x.x.x first and from there i am telnet y.y.y.y and getting into y and from there i am telnet to z
i want to know, can we write a script, which can automatically connect from x to y and from y to z..
is... (1 Reply)
I am about to attempt to connect my sun 280R boxes to a EMC SAN.
I have Qlogic cards that came from Sun.
I am going to load traffic manager, navisphere client.
what else do i need, sun foundation suite ro somehting?
This is the first time ive ever connected to a SAN.
any help would be... (3 Replies)
Okay, here's the situation: I have a UNIX box hosting a website. The website is basically there to hold a .swf file; when you go to the URL, the .swf file loads, and it pulls data from a database on another computer into a cache. The cache holds things for 24 hours. This all works fine, so it's... (7 Replies)
I was wondering if I could get some help with two of my Unix computers.
Bare with me as I am new to this software and, hardly know anything on these computers, except based on what I have already worked with them.
Here is my issue.
I have two unix computers setup together, not connected... (6 Replies)
How would i connect the lines of 2 different files?
Also how would i reissue the command to use an equal signsas the seperators between the fields? (1 Reply)
I am trying to connect to one of the oracle sever using uni through sqlplus
command: sqlplus -s BOXI_ALPH_AUDITOR,Q078_audit$@Q047
But its not getting connected. I tried using some different server using same syntax its working. What differene i found is the password is having no special... (2 Replies)
I am connecting to remote server and try to check if files with timestamp as Today's day are on the directory. Below is my code
TARFILE=${NAME}.tar
TARGZFILE=${NAME}.tar.gz
ssh ${DESTSERVNAME} 'cd /export/home/iciprod/download/let/monthly;
Today=`date +%Y%m%d`;
if ;then
echo "We... (1 Reply)
Shell script for connecting multiple servers and then copying 30 days old files from those server .
HI ,
I have 6 multiple servers
pla1,pla2,pla3,pla4,pla5,pla6
1. These six servers have common shared mount point /var/share
2. Running script from /var/share to connect these servers.I... (1 Reply)
Discussion started by: rcroyal88
1 Replies
LEARN ABOUT MOJAVE
join
JOIN(1) BSD General Commands Manual JOIN(1)NAME
join -- relational database operator
SYNOPSIS
join [-a file_number | -v file_number] [-e string] [-o list] [-t char] [-1 field] [-2 field] file1 file2
DESCRIPTION
The join utility performs an ``equality join'' on the specified files and writes the result to the standard output. The ``join field'' is
the field in each file by which the files are compared. The first field in each line is used by default. There is one line in the output
for each pair of lines in file1 and file2 which have identical join fields. Each output line consists of the join field, the remaining
fields from file1 and then the remaining fields from file2.
The default field separators are tab and space characters. In this case, multiple tabs and spaces count as a single field separator, and
leading tabs and spaces are ignored. The default output field separator is a single space character.
Many of the options use file and field numbers. Both file numbers and field numbers are 1 based, i.e., the first file on the command line is
file number 1 and the first field is field number 1. The following options are available:
-a file_number
In addition to the default output, produce a line for each unpairable line in file file_number.
-e string
Replace empty output fields with string.
-o list
The -o option specifies the fields that will be output from each file for each line with matching join fields. Each element of list
has the either the form 'file_number.field', where file_number is a file number and field is a field number, or the form '0' (zero),
representing the join field. The elements of list must be either comma (',') or whitespace separated. (The latter requires quoting
to protect it from the shell, or, a simpler approach is to use multiple -o options.)
-t char
Use character char as a field delimiter for both input and output. Every occurrence of char in a line is significant.
-v file_number
Do not display the default output, but display a line for each unpairable line in file file_number. The options -v 1 and -v 2 may be
specified at the same time.
-1 field
Join on the field'th field of file 1.
-2 field
Join on the field'th field of file 2.
When the default field delimiter characters are used, the files to be joined should be ordered in the collating sequence of sort(1), using
the -b option, on the fields on which they are to be joined, otherwise join may not report all field matches. When the field delimiter char-
acters are specified by the -t option, the collating sequence should be the same as sort(1) without the -b option.
If one of the arguments file1 or file2 is ``-'', the standard input is used.
EXIT STATUS
The join utility exits 0 on success, and >0 if an error occurs.
COMPATIBILITY
For compatibility with historic versions of join, the following options are available:
-a In addition to the default output, produce a line for each unpairable line in both file 1 and file 2.
-j1 field
Join on the field'th field of file 1.
-j2 field
Join on the field'th field of file 2.
-j field
Join on the field'th field of both file 1 and file 2.
-o list ...
Historical implementations of join permitted multiple arguments to the -o option. These arguments were of the form
'file_number.field_number' as described for the current -o option. This has obvious difficulties in the presence of files named
'1.2'.
These options are available only so historic shell scripts do not require modification. They should not be used in new code.
LEGACY DESCRIPTION
The -e option causes a specified string to be substituted into empty fields, even if they are in the middle of a line. In legacy mode, the
substitution only takes place at the end of a line.
Only documented options are allowed. In legacy mode, some obsolete options are re-written into current options.
For more information about legacy mode, see compat(5).
SEE ALSO awk(1), comm(1), paste(1), sort(1), uniq(1), compat(5)STANDARDS
The join command conforms to IEEE Std 1003.1-2001 (``POSIX.1'').
BSD July 5, 2004 BSD