I have a file with 6 columns. I want to check if column 1 and 2 fall between column 5 and 6 I want to call them as "TRUE_genes" if not then call them as "FALSE_genes". I can do it for checking one column but how to mention about two columns.
I want to check if a zip code is valid, using a variable that stores the zipcode. I am not sure how I would do this in a script. I know that simply checking for the numerical range of the number will not work, because '1' would be '00001' in zip code format. I know when I am in shell, I can use... (5 Replies)
Hi,
I want to match and print columns that match.
So my file looks like this:
h1 20 30 h1 25 27
h2 50 70 h2 90 95
h2 60 80 h2 70 75
h3 130 150 h3 177 190
h4 140 190 h4 300 305
So there are 6 columns. Column 1 and 4 are names. I am able to get the... (2 Replies)
I'm writing a KSH shell script that's using SQL though DB2.
If I have a table defined and populated
db2 "create table tb(num int,letter char(4))"
db2 "insert into tb values(111,a)
db2 "insert into tb values(112,b)
db2 "insert into tb values(111,c)
How can I check if a letter user... (0 Replies)
Hi,
Is there a function in awk or sed which will check the case of the columns.
If my column 8 is in lower case then I want to change my column 10 data in lower case and vice versa.
I know in awk we have tolower and toupper functions but can we manipulate the data based on the case ??
... (3 Replies)
Hi,
File contains with TAB delimeter file,i want check the 2,3 are not null
test1@gmail.com 100 test
test2@gmail.com 101 test
test3@gmail.com test
test4@gmail.com 102
OUTPUT
test1@gmail.com 100 test
test2@gmail.com 101 test
Please help me with one single command in... (2 Replies)
Hello Experts,
File contains 10 columns with | delimeter. 1,3,4,5,7,9 columns are required columns means it should contains values.
i need those records, rest of it will contain or not contain data.
test1.txt:
a@a.com|a|b|c|d|e|f|g|h|i
|a|b|c|d|e|f|g|h|i
b@b.com|a||c|d|e|f|g|h|i... (7 Replies)
Hi, I need to create weekly files from daily records stored in individual monthly filenames from 1999-2010. my sample file structure is like the ones below:
daily record stored per month:
199901.xyz, 199902.xyz, 199903.xyz, 199904.xyz ...199912.xyz
records inside 199901.xyz (original data... (4 Replies)
Hi,
I have a tab delimited text file with multiple columns. The second and third columns include numbers that have not been sorted. I want to extract rows where the second column includes a value between -0.01 and 0.01 (including both numbers) and the first third column includes a value between... (1 Reply)
Hi all,
I am kind of stuck with printing my desired output. Please help me if you know how it can work.
My input file(tab separated):
NW_0068.1 41,16 100,900
NW_0699.1 4,2,19 200,700,80
My Output file (desired):
NW_0068.1 41,16 100,900 100 - 141
NW_0068.1 41,16 100,900 ... (3 Replies)
Discussion started by: sam_2921
3 Replies
LEARN ABOUT OPENDARWIN
comm
COMM(1) BSD General Commands Manual COMM(1)NAME
comm -- select or reject lines common to two files
SYNOPSIS
comm [-123i] file1 file2
DESCRIPTION
The comm utility reads file1 and file2, which should be sorted lexically, and produces three text columns as output: lines only in file1;
lines only in file2; and lines in both files.
The filename ``-'' means the standard input.
The following options are available:
-1 Suppress printing of column 1.
-2 Suppress printing of column 2.
-3 Suppress printing of column 3.
-i Case insensitive comparison of lines.
Each column will have a number of tab characters prepended to it equal to the number of lower numbered columns that are being printed. For
example, if column number two is being suppressed, lines printed in column number one will not have any tabs preceding them, and lines
printed in column number three will have one.
The comm utility assumes that the files are lexically sorted; all characters participate in line comparisons.
DIAGNOSTICS
The comm utility exits 0 on success, and >0 if an error occurs.
SEE ALSO cmp(1), diff(1), sort(1), uniq(1)STANDARDS
The comm utility conforms to IEEE Std 1003.2-1992 (``POSIX.2'').
HISTORY
A comm command appeared in Version 4 AT&T UNIX.
BSD June 6, 1993 BSD