|
Terry Richardson wrote:
I don't think this has any bearing at all on how the file is handled/defined. What are the symptoms you are seeing?
I've got a program that is trying to write double byte data. The file has a CCSID of 937, and has one field that is defined as "O" in the DDS. The O field has a CCSID of 937. There are a bunch of regular "A" fields that have a CCSID of 37. When we process English data the program works fine ... but when we try to write double byte data, we get a CPF5035 with a reason code of 22. The data in the field appears to be completely normal (DBCS wise). It has a shift in, a bunch of double byte data, a shift out, then a few blanks. The only thing that is odd about the record that we're trying to write is that some of the fields are renamed via I specs (although not the field with the double byte data in it). To answer Tommy's question, the program is pretty old and there hasn't been a reason to change it (till now, maybe). We are on V5R2, if it makes any difference (recently upgraded, now we can use service entry points WOOT!). david
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.