"15L" decodes as 15 characters wide, left justified. "15T" is the same, but breaking on word boundaries. "15R" is right justified.
I have the widths in hashed file defined way higher than the expected values (there are no extra spaces as well in the data, so i am sure that i am using more width than required)
LIST.DICT hashedfile
The column names obtained from the above command are themselves splitted (not in a single line)
LIST.DICT hashedfile will give you a "file dictionary" (table definition) listing. You can get the column names from that - anything with a type "D" or "I" can be used in a SELECT query.
a) I am trying to write a generic script to obtain the contents of a hashed file, length could vary from 1 till 100 or more. I don't want to use a fixed defined length of the fields by specifying something as "15L".
b) Is there any pre-requisite that the hashed file shoudl be set up in such a way that the splitting doesn't occur - i got the first one (a) sufficient length. But this alone is not solving my problem.
c) I don't know the reason, but while trying I have reset "Record Size" and no matter what I do, delete/recreate the job, reset the record size which was earlier, But I keep getting the each field in new line.
Field1. -4927275313
Field2. Not Applicable
Field3. 2008-05-06 09:06:40
Field4. Test1
Field5. 0
Field1. -4829300379
Field2. Not Applicable
Field3. 2008-03-25 07:38:49
Field4. Test2
Field5. 0
Field1. -4813747248
Field2. Not Applicable
Field3. 2008-03-17 10:51:17
Field4. Test3
Field5. 0
Field1. -4702305701
Field2. Not Applicable
Field3. 2008-01-30 13:14:42
Field4. Test4
Field5. 0
FYI : If at all it helps there is no dot '.' after the fieldname 'Field1'