CFF - EBCDIC Binary data
Posted: Tue Aug 03, 2004 8:05 am
Hi all
We have a download from the mainframe in ebcdic/binary format. This means that we need to know the length of the record to determine when the next record starts - i.e. no CR/LF to do that for us.
We are reading each record in as one column (or at least, thats what i want to do), because i only need certain columns starting/ending at certain positions.
The problem is that the record has a possible record length of 24032 - it is variable length.
when i add the metadata of the column, what length should i specify? 24032 on CHARACTER takes up all the records when viewing the data, so i get one record in the column instead of the 1000 records (test data) i am supposed to.
so.. should i be using CHARACTER? I think not.. How does CFF handle a file in this layout?
If you want to point me in the direction of 'occurs depending on', remember that in the file definition I dont have a maximum occurence, which means i could end up with (on bin4) 9999 possible occurs.
I also want to avoid adding CR/LF characters when downloading the file as it may affect the data when displaying/translating it.
We have a download from the mainframe in ebcdic/binary format. This means that we need to know the length of the record to determine when the next record starts - i.e. no CR/LF to do that for us.
We are reading each record in as one column (or at least, thats what i want to do), because i only need certain columns starting/ending at certain positions.
The problem is that the record has a possible record length of 24032 - it is variable length.
when i add the metadata of the column, what length should i specify? 24032 on CHARACTER takes up all the records when viewing the data, so i get one record in the column instead of the 1000 records (test data) i am supposed to.
so.. should i be using CHARACTER? I think not.. How does CFF handle a file in this layout?
If you want to point me in the direction of 'occurs depending on', remember that in the file definition I dont have a maximum occurence, which means i could end up with (on bin4) 9999 possible occurs.
I also want to avoid adding CR/LF characters when downloading the file as it may affect the data when displaying/translating it.