Thanks for your response! I ran your code on the file and got the following output;
This is very close but for the 2nd product only 2 out of its 3 fields are printed. (the 1st product only had 2 fields). Each product may have numerous fields, sorry if i was vague explaining this. I've had a good look through the code and i'm not sure why only 2 fields are printed.
Thanks
Last edited by Franklin52; 10-12-2015 at 10:32 AM..
Reason: Please use code tags
Have a column "address" which is combination of city, region and postal code like.
Format is : city<comma><space>region<space>postal code
abc, xyz 123456
All these three city, region and postal code are not mandatory. There can be any one of the above. In that case a nell... (2 Replies)
hey guys...
Im looking to do the following:
1
2
3
4
5
6
7
8
9
Change to:
1 4 7
2 5 8
3 6 9
Did use | perl -lpe'$\=$.%3?$":"\n"' , but it doesnt give me the matrix i want. (3 Replies)
Here is my source, i have million lines like this on a file.
disp0201.php?poc=4060&roc=1&ps=R&ooc=13&mjv=6&mov=5&rel=5&bod=155&oxi=2&omj=5&ozn=1&dav=20&cd=&daz=& drc=&mo=&sid=&lang=EN&loc=JPN
I want to split this into columns in order to load in database, anything starts with"&mjv=6" as first... (13 Replies)
Hi,
I have a file sample_1.txt (300k rows) which has data like below:
* Also each record is around 64k bytes
11|1|abc|102553|125589|64k bytes of data
10|2|def|123452|123356|......
13|2|geh|144351|121123|...
25|4|fgh|165250|118890|..
14|1|abc|186149|116657|......... (6 Replies)
i have file1.txt
asdas|csada|130310|0423|A1|canberra
sdasd|sfdsf|130426|2328|A1|sydney
Expected output : on eaceh third and fourth colum, split into each two characters
asdas|csada|13|03|10|04|23|A1|canberra
sdasd|sfdsf|13|04|26|23|28|A1|sydney (10 Replies)
Hi,
I have a similar input format-
A_1 2
B_0 4
A_1 1
B_2 5
A_4 1
and looking to print in this output format with headers. can you suggest in awk?awk because i am doing some pattern matching from parent file to print column 1 of my input using awk already.Thanks!
letter number_of_letters... (5 Replies)
Hello :)
I am in this situation:
Input: two tab-delimited files, `File1` and `File2`. `File2` (`$2`) has to be parsed by patterns found in `File1` (`$1`).
Expected output: tab-delimited file, `File3`. `File3` has to contain the same rows as `File2`, plus the corresponding value in... (5 Replies)
Hi all,
Newbie here, so please bear over with my stupid question :)
I have used far too long time today on figuring this out, so I hope that someone here can help me move on.
I have some annotation data for a transcriptome where I want to split a column containing NCBI accession IDs into a... (7 Replies)
Hi,
I am trying to split the following output into two columns, where each column has Source: Destination:
OUTPUT TO FILTER
$ tshark -r Capture_without_mtr.pcap -V | awk '/ (Source|Destination): /' | more
Source: x.x.x.x
Destination: x.x.x.x
Source:... (2 Replies)
Discussion started by: sand1234
2 Replies
LEARN ABOUT OSF1
stl_key
stl_key(4) Kernel Interfaces Manual stl_key(4)NAME
stl_key - setld kit manufacturing key files
DESCRIPTION
Each software product that is distributed as subsets for the setld(8) command has an associated key file. The key file's name consists of
the product's unique 3-letter name and a 3-digit version number with the string .k for a suffix. The key file is used by the software kit-
ting program kits(1) in producing software distribution packages.
A key file has a global data section and a subset descriptor section. The sections are separated by a line containing only two percent
signs (%%).
The global section specifies the product-level attributes of the product. In this section, lines that begin with number signs (#) are com-
ments and are ignored by the kits utility. Attributes are specified as name/value pairs separated by equals signs (=). There must be no
white space surrounding the equals sign. There are four mandatory attributes and two optional attributes. Attributes must have non-null
values. The attributes are:
NAME Mandatory. Specifies the name of the product. The value for NAME is a text string of up to 40 characters. If the string con-
tains blank spaces, it must be enclosed in apostrophes ('').
CODE Mandatory. Specifies the 3-character product code for the product, for example, OAT.
VERS Mandatory. Specifies the 3-digit version code for the product, for example, 100.
MI Mandatory. Specifies the pathname of the master inventory file for the product.
ROOT Optional. A single-digit integer that is set to 1 if the product is the base operating system. In all other cases, this flag
must be a zero (0). If missing, this attribute defaults to zero.
COMPRESS Optional. A single-digit integer that is set to 1 to create compressed subset files using the compress(1) utility, thereby sav-
ing space on the distribution media. To suppress compression, this attribute is a zero (0). If missing, this attribute defaults
to zero.
The subset descriptor section contains one subset descriptor line for each subset in the product. Comments are not permitted in this sec-
tion.
A subset descriptor contains subset-specific attributes in four fields separated by TAB characters. These fields are:
Subset name A character string up to 15 characters in length, composed of the 3-letter product code (for example, OAT), a mnemonic iden-
tifying the subset (for example, DCB), and the 3-digit version code (for example, 100). All letters in the subset name must
be uppercase.
Reserved This field must be a single period.
Flags A 16-bit unsigned integer
Bit 0 is the ``sticky bit,'' indicating when set that the subset cannot be removed.
Bit 1 indicates when set that the subset is optional.
Bits 2 to 7 are reserved.
Bits 8 to 15 are undefined.
Description A short description of the subset, delimited by single quotation marks (''); for example, 'Document Building Tools'
The subset descriptors must be listed in the order in which the subsets are to be installed by setld.
RESTRICTIONS
Comments in the subset descriptor section will cause serious problems when encountered by the kits program.
TAB formatting in the subset descriptors is tightly enforced by the kits program.
EXAMPLES
The following example illustrates the key file for a hypothetical product kit: # Key file for the Orpheus Document Building Tools kit
# # Product-level attributes. # NAME='Orpheus Authoring Tools' CODE=OAT VERS=100 MI=OAT00.mi ROOT=0 COMPRESS=1 # # Subset def-
initions follow. # %% OATDCB100 . 0 'Document Building Tools' OATDCBDOC100 . 2 'Document Tools Documenta-
tion'
RELATED INFORMATION
Commands: kits(1), setld(8)
Files: stl_comp(4), stl_ctrl(4), stl_image(4), stl_mi(4)
Documents: Guide to Preparing Product Kits delim off
stl_key(4)