When I retrieve data from EBCDIC based machines, particularly IBM mainframes and AS/400s, sometimes I get what appears to be garbage. Why and how do I resolve the issue?
Location: http://www.jguru.com/faq/view.jsp?EID=92410 Created: Jun 30, 2000 Modified: 2000-07-01 18:42:04.364 Author: Joe Sam Shirah (http://www.jguru.com/guru/viewbio.jsp?EID=42100) Question originally posed by Joe Sam Shirah PREMIUM (http://www.jguru.com/guru/viewbio.jsp?EID=42100 These machines use CCSIDs ( Coded Character Set Identifiers ) for National Language Support. While in general, data will be converted sensibly for Java, under certain conditions data will be created, often inadvertently, with a CCSID of 65535. This code means “binary data, do not convert.” While the best answer is to get the data to a proper CCSID, this is not always possible and a good JDBC driver for these platforms will have a property like “convert binary” or “translate CCSID 65535 data.” Set this property and the garbage ( which is actually EBCDIC data being displayed on an ASCII machine, ) becomes good data.
Related Questions
- When I retrieve data from EBCDIC based machines, particularly IBM mainframes and AS/400s, sometimes I get what appears to be garbage. Why and how do I resolve the issue?
- Is it acceptable to have entry and exit data from different curriculum based assessment tools?
- What confidentiality and integrity properties are provided for SILK data sent across machines?
