Fixed width file with newline field separators

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Alter Fixed Width File

Thank u so much .Its working fine as expected. ---------- Post updated at 03:41 PM ---------- Previous update was at 01:46 PM ---------- I need one more help. I have another file(fixed length) that will get negative value (ex:-00000000003000) in postion (98 - 112) then i have to...

2. UNIX for Dummies Questions & Answers

Replace the unexpected newline char with space in a Fixed width file

Input eg: Ouput Expected. The #rd line had the unexpted new line, which need to be replaced with space. I was planing to go with checking the length of each line using awk and if the length is less than the defeined limit, (12 in above case) will replace the newline with space. ...

3. UNIX for Dummies Questions & Answers

Length of a fixed width file

I have a fixed width file of length 53. when is try to get the lengh of the record of that file i get 2 different answers. awk '{print length;exit}' <File_name> The above code gives me length 50. wc -L <File_name> The above code gives me length 53. Please clarify on...

4. Shell Programming and Scripting

Fixed width file comparision not working

when i used diff/cmp/cat -v commands i am getting the difference cmp command cmp -l file1 file2 |head -1 1300 15 10 Manually checked records. record length and data matched. diff file1 file2 3C3 <record information Manually checked records. record length and data matched....

5. Shell Programming and Scripting

Comparing two fixed width file

Hi Guys I am checking the treads to get the answer but i am not able to get the answer for my question. I have two files. First file is a pattern file and the second file is the file i want to search in it. Output will be the lines from file2. File1: P2797f12af 44751228...

6. Shell Programming and Scripting

Fixed-Width file from Oracle

Hi All, I have created a script which generates FIXED-WIDTH file by executing Oracle query. SELECT RPAD(NVL(col1,CHR(9)),20)||NVL(col2,CHR(9))||NVL(col3,CHR(9) FROM XYZ It generates the data file with proper alignment. But if same file i transfer to windows server or Mainframe...

7. UNIX Desktop Questions & Answers

Help with Fixed width File Parsing

I am trying to parse a Fixed width file with data as below. I am trying to assign column values from each record to variables. When I parse the data, the spaces in all coumns are dropped. I would like to retain the spaces as part of the dat stored in the variables. Any help is appreciated. I...

8. Shell Programming and Scripting

Changing particular field in fixed width file

I have a fixed width file and i need to change 36th field to "G" in for about random 20 records? How can I do it?

9. UNIX for Advanced & Expert Users

Converting field into fixed width csv

Hi I have a file having record as - 1,aaa,a123,a I need this converted to as 2nd col to 5 chars wide & 3rd col to 6chars wide such as - 1,aaa ,a123 ,a How we could achieve this? Thx in advance.

10. UNIX for Dummies Questions & Answers

Fixed Width file using AWK

I am using the following command at the Unix prompt to make my 'infile' into a fixed width file of 100 characters. awk '{printf "%-100s\n",$0}' infile > outfile However, there are some records with a special character "�" These records are using 3 characters in place of one and my record...

LEARN ABOUT BSD

passwd

PASSWD(5)							File Formats Manual							 PASSWD(5)

NAME

       passwd - password files

DESCRIPTION

       Passwd  files are files consisting of newline separated records, one per user, containing ten colon (``:'') separated fields.  These fields
       are as follows:

	       name	     user's login name
	       password      user's encrypted password
	       uid	     user's id
	       gid	     user's login group id
	       class	     user's general classification (unused)
	       change	     password change time
	       expire	     account expiration time
	       gecos	     general information about the user
	       home_dir      user's home directory
	       shell	     user's login shell

       The name field is the login used to access the computer account, and the uid field is the number associated with it.  They should  both	be
       unique across the system (and often across a group of systems) since they control file access.

       While  it  is  possible	to  have multiple entries with identical login names and/or identical user id's, it is usually a mistake to do so.
       Routines that manipulate these files will often return only one of the multiple entries, and that one by random selection.

       The login name must never begin with a hyphen (``-''); also, it is strongly suggested that neither upper-case characters or dots (``.'') be
       part  of  the  name, as this tends to confuse mailers.  No field may contain a colon (``:'') as this has been used historically to separate
       the fields in the user database.

       The password field is the encrypted form of the password.  If the password field is empty, no password will be required to gain	access	to
       the  machine.   This is almost invariably a mistake.  Because these files contain the encrypted user passwords, they should not be readable
       by anyone without appropriate privileges.

       The group field is the group that the user will be placed in upon login.  Since this system supports multiple groups (see  groups(1))  this
       field currently has little special meaning.

       The class field is currently unused.  In the near future it will be a key to a termcap(5) style database of user attributes.

       The change field is the number in seconds, GMT, from the epoch, until the password for the account must be changed.  This field may be left
       empty to turn off the password aging feature.

       The expire field is the number in seconds, GMT, from the epoch, until the account expires.  This field may be left empty to  turn  off  the
       account aging feature.

       The gecos field normally contains comma (``,'') separated subfields as follows:

	       name	     user's full name
	       office	     user's office number
	       wphone	     user's work phone number
	       hphone	     user's home phone number

       This information is used by the finger(1) program.

       The user's home directory is the full UNIX path name where the user will be placed on login.

       The shell field is the command interpreter the user prefers.  If the shell field is empty, the Bourne shell (/bin/sh) is assumed.

SEE ALSO

       chpass(1), login(1), passwd(1), getpwent(3), mkpasswd(8), vipw(8) adduser(8)

BUGS

       User information should (and eventually will) be stored elsewhere.

7th Edition							    May 8, 1989 							 PASSWD(5)

Shell Programming and Scripting