I am new to Unix so will really appreciate if someone can guide me on this.
What I want to do is:
Step1: Read binary file - pick first 2 bytes, convert from hex to decimal. Read the next 3 bytes as well.
2 bytes will specify the number of bytes 'n' that I want to read and write... (1 Reply)
I am on AIX Unix. I want to read a flat file for a string in a certain byte. I want to find the value: 943034 in column 56; and write out just those records to another file. Also, could I get the line/record number of where it was found in the input file?
Thank you,
sboxtops (1 Reply)
Been searching for about 3 hours for similar functionality that I can get examples of how to output text from variables into certain locations in a file. I would like to incorporate this into a script. I have not been able to find a command example that does it all in one method. I find part of... (1 Reply)
Hi all, I need help.
I have an input text file (input.txt) like this:
21 GTGCAACACCGTCTTGAGAGG 50
21 GACCGAGACAGAATGAAAATC 73
21 CGGGTCTGTAGTAGCAAACGC 108
21 CGAAAAATGAACCCCTTTATC 220
21 CGTGATCCTGTTGAAGGGTCG 259
Now I need to count A/T/G/C numbers at each character location in column... (2 Replies)
Hi, I am trying to use an awk command to replace specific character positions on a line beginning with 80 with contents of another file.
The line beginning with 80 in file1 is as follows:
I want to replace the 000000000178800 (positions 34 - 49) on this file with the contents of... (2 Replies)
hi.
I have a Fixed Length text file as input where the character positions 4-5(two character positions starting from 4th position) indicates the LOB indicator. The file structure is something like below:
10126Apple DrinkOmaha
10231Milkshake New Jersey
103 Billabong Illinois
... (6 Replies)
I have a pipe delimited file and I'm trying to write a script that will give the character/byte positions of each pipe in the file. There may be some simple way but I don't know what it is... Can someone help with this?
Ex: file has output below
abc|def|ghi|
I want the script to tell the... (1 Reply)
Hi,
I have a file with hundreds of lines. I want to search for particular lines starting with 4000, search and replace the 137-139 position characters; which will be '000', with '036'. Can all of this be done without opening a temp file and then moving that temp file to the original file name.
... (7 Replies)
I have a fixed-length positional file. I am trying to replace content of position 4-13 (length=10) with xxxxxxxxxx.
Sample 2 rows in this file:
H0187459823 172SMITH, JOE
H0112345678 172DOE, JANE
In this example 87459823 (from 1st line) and 12345678 (from 2nd line) (both in position... (3 Replies)
Discussion started by: Diver181
3 Replies
LEARN ABOUT SUSE
fiz
FIZ(1) General Commands Manual FIZ(1)NAME
fiz - analyze damaged zoo archive for data revovery
SYNOPSIS
fiz archive[.zoo]
DESCRIPTION
Fiz is used to analyze damaged zoo archives and locate directory entries and file data in them. The current version of fiz is 2.0 and it
is meant to be used in conjunction with zoo version 2.0. Fiz makes no assumptions about archive structure. Instead, it simply searches
the entire subject archive for tag values that mark the locations of directory entries and file data. In a zoo archive, a directory entry
contains information about a stored file such as its name, whether compressed or not, and its timestamp. The file data are the actual data
for the archived file, and may be either the original data, or the result of compressing the file.
For each directory entry found, fiz prints where in the archive it is located, the directory path and filename(s) found in it, whether the
directory entry appears to be corrupted (indicated by [*CRC Error*]), and the value of the pointer to the file data that is found in the
directory entry. For each block of file data found in the archive, fiz prints where in the archive the block begins. In the case of an
undamaged archive, the pointer to file data found in a directory entry will correspond to where fiz actually locates the data. Here is
some sample output from fiz:
****************
2526: DIR [changes] ==> 95
2587: DATA
****************
3909: DIR [copyrite] ==> 1478
3970: DATA
4769: DATA
****************
In such output, DIR indicates where fiz found a directory entry in the archive, and DATA indicates where fiz found file data in the ar-
chive. Filenames located by fiz are enclosed in square brackets, and the notation "==> 95" indicates that the directory entry found by
fiz at position 2526 has a file data pointer to position 95. In actuality, fiz found file data at positions 2587, 3970, and 4769. Since
fiz found only two directory entries, and each directory entry corresponds to one file, one of the file data positions is an artifact.
Once the locations of directory entries and file data are found, the @ modifier to zoo's archive list and extract commands can be used and
the archive contents selectively listed or extracted, skipping the damaged portion. This is further described in the documentation for
zoo(1).
In the above case, commands to try giving to zoo might be x@2526,2587 (extract beginning at position 2526, and get file data from position
2587), x@3090,3970 (extract at 3090, get data from 3970) and x@3909,4769 (extract at 3909, get data from 4769). Once a correctly-matched
directory entry/file data pair is found, zoo will in most cases synchronize with and correctly extract all files subsequently found in the
archive. Trial and error should allow all undamaged files to be extracted. Also note that self-extracting archives created using sez (the
Self-Extracting Zoo utility for MS-DOS), which are normally executed on an MS-DOS system for extraction, can be extracted on non-MSDOS sys-
tems in a similar way.
SEE ALSO zoo(1)BUGS
Random byte patterns can occasionally be incorrectly recognized as tag values. This occurs very rarely, however, and trial and error will
usually permit all undamaged data to be extracted.
DIAGNOSTICS
Fiz always exits with a status code of 0.
FUTURE DIRECTIONS
Automation of data recovery from a damaged archive is potentially achievable. However, since damaged archives occur only rarely, fiz as it
currently stands is unlikely to change much in the near future.
AUTHOR
Rahul Dhesi
Jan 31, 1988 FIZ(1)