... I tried to write script in perl but the sript was giving funny values and wasted 3 hrs. I didn't want to put the scipt coz that sript doesn't make any sense.
...
Ah, the glorious messiness of Perl:
As Larry Wall says - "Easy things should be easy, and hard things should be possible." Amazon.com Message
Hello,
I am new to unix and need help with a problem. I have 2 files each containing multiple columns of information ie;
File 1 :
A B C D E
1 2 3 4 5
File 2 :
F G
6 7
I would like to merge the information from File 2 to File 1 so that the data reads as follows;
File 1:
A... (4 Replies)
Hi,
1. Each message starts with date
2. There is blank line between each message
3. Each message does not contain same number of lines.
Any help in merging multiple lines in each message to a single line is much appreciated.
AIX: Korn Shell
Error log file looks like below.
... (5 Replies)
Hi,
My input is
<message>
looking for a big
<message>Does fit my G74 laptop. Makes the 10 pound.
<message>
<message>This bag is the only one I could find to fit my awesome ASUS G74S.
<message>
<message>
Great bag my only wish is that they had put a pocket in which to store and... (6 Replies)
I have two files like this:
fileA.net
A
B
C
fileA.dat
1
2
3
and I want the output
output_expected
A 1
B 2
C 3
I know that the easier way is to do a paste fileA.net fileA.dat, but the problem is that I have 10,000 couple of files (fileB.net with fileB.dat; fileC.net with... (3 Replies)
Hi,
My requirement is search for the flat files in the location that are generated in a day and merge them into a single flat file.
In the merged file as well particular column value should go into particular column.
awk 'NR=1 FNR>1' $(ls -rt flatfile1_v_*)
when i use this command for... (4 Replies)
Dear all,
I have a simple question. I have a file like below (separated by tab):
col1 col2 col3 col4 col5 col6 col7
21 66745 rs1234 21 rs5678 23334 0.89
21 66745 rs2334 21 rs9978 23334 0.89
21 66745 ... (4 Replies)
Respected Members.
Hello.
This is my first post in the forum. I will try to follow all the rules as prescribed by the forum. In case of non-compliance, I request you to kindly give me some more time to understand and abide by them.
I am working on two files. I wish to merge the two files... (6 Replies)
I Want to merge multiple lines based on the 1st field and keep into single record.
SRC File:
AAA_POC_DB.TAB1
AAA_POC_DB.TAB2
AAA_POC_DB.TAB3
AAA_POC_DB.TAB4
BBB_POC_DB.TAB1
BBB_POC_DB.TAB2
CCC_POC_DB.TAB6
OUTPUT
-----------------
'AAA_POC_DB','TAB1','TAB2','TAB3','TAB4'... (10 Replies)
As part of some report generation, I've written a script to fetch the values from DB. But, unluckily, for certain Time ranges(1-9.99,10-19.99 etc), I don't have data in DB.
In such cases, I would like to write zero (0) instead of empty. The desired output will be exported to csv file.
... (1 Reply)
Discussion started by: kumar_karpuram
1 Replies
LEARN ABOUT NETBSD
join
JOIN(1) BSD General Commands Manual JOIN(1)NAME
join -- relational database operator
SYNOPSIS
join [-a file_number | -v file_number] [-e string] [-j file_number field] [-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. (The argument to -a must not be
preceded by a space; see the COMPATIBILITY section.)
-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 form 'file_number.field', where file_number is a file number and field is a field number. 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.
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. (To distinguish between
this and -a file_number, join currently requires that the latter not include any white space.)
-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_num-
ber.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 don't require modification and should not be used.
SEE ALSO awk(1), comm(1), paste(1), sort(1), uniq(1)STANDARDS
The join command is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
BSD April 28, 1995 BSD