View previous topic :: View next topic
|
Author |
Message |
shreya19
New User
Joined: 13 Mar 2014 Posts: 34 Location: USA
|
|
|
|
Sent a file from mainframe to linux. Linux file count exceeds mainframe file count by 13. Exported the same mainframe flatfile to excel sheet via ftp, excel sheet number of rows exceeds by 40 as compared to mainframe file. What could be the reason? |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10872 Location: italy
|
|
|
|
probably you are sending as text a dataset that contains binary data |
|
Back to top |
|
|
sergeyken
Senior Member
Joined: 29 Apr 2008 Posts: 2010 Location: USA
|
|
|
|
shreya19 wrote: |
Sent a file from mainframe to linux. Linux file count exceeds mainframe file count by 13. Exported the same mainframe flatfile to excel sheet via ftp, excel sheet number of rows exceeds by 40 as compared to mainframe file. What could be the reason? |
Without any details on your particular case please do not expect to receive any meaningful advice.
So far the only possible answer is:
1) find where the problem is coming from?
2) fix this problem
3) run the fixed version of your job/script/whatever |
|
Back to top |
|
|
daveporcelan
Active Member
Joined: 01 Dec 2006 Posts: 792 Location: Pennsylvania
|
|
|
|
I concur with Enrico.
What we have experienced is that when selected 'hex' data is converted from Ebcdic to Ascii, the character is changed to a carriage return or line feed.
This makes one line into two.
Do this a few times and you have 40 extra records.
What we had to do was convert packed decimal data to numeric before transmission. |
|
Back to top |
|
|
don.leahy
Active Member
Joined: 06 Jul 2010 Posts: 765 Location: Whitby, ON, Canada
|
|
|
|
daveporcelan wrote: |
I concur with Enrico.
.....
What we had to do was convert packed decimal data to numeric before transmission. |
We sometimes call this “converting the file to baby talk”. |
|
Back to top |
|
|
|