ebcdic - Issue with comp3 fields in COBOL source file -


we have used below process in loading file(with comp3 data) informatica mainframe.

  1. ftpd mainframe file in binary mode unix server
  2. imported source cobol copybook vsam file type
  3. set source file properties fixed width , codepage ibm ebcdic english ibm1047.
  4. verified usage in source comp3 relevent fields

even above steps not map comp3 fields correct. when code page changed ascii map string data.

could please let know missing?

when code page changed ascii map string data. 

that's because character encoding only applies string data. bytes of data such 'packed' bytes or binary data bytes have no meaning after being converted different character encoding unless first converted character representations.

what platform running cobol? in cobol, meanings of various "comp" data types change depending on hardware platform , potentially os. (i suppose specific compiler though don't know of examples.) without knowing how specific cobol maps data types memory bit patterns, there's no way guess how "mainframe 'packed'" data should handled.


Comments

Popular posts from this blog

ios - UICollectionView Self Sizing Cells with Auto Layout -

node.js - ldapjs - write after end error -

DOM Manipulation in Wordpress (and elsewhere) using php -