Jim, I remember their was a bug (e.g.APAR) because CONVERSION 1140,1200; /* Latin-1 to UTF-16, *RECLM* */ CONVERSION 1200,1140; /* UTF-16 to Latin-1, *RECLM* */ wasn't the same like CONVERSION 1140,1200,RECLM; /* Latin-1 to UTF-16, *RECLM* */ CONVERSION 1200,1140,RECLM; /* UTF-16 to Latin-1, *RECLM* */
We run z/OS R4 with current maintenance and have CONVERSION 1252,1200,; /* ASCII WINDOWS --> UTF-16 */ CONVERSION 1200,1252,; /* UTF-16 --> ASCII WINDOWS */ for Enterprise Cobol 3.4 and CONVERSION 1252,1200,ER; /* ASCII WINDOWS --> UTF-16 */ CONVERSION 1200,1252,ER; /* UTF-16 --> ASCII WINDOWS */ for DB2V8 D UNI,ALL shows (for these combination) 01252-01200(13488)-R 01252-01200(13488)-L 01200(13488)-01252-E 01200(13488)-01252-L Just trust the CUNMIUTL utility and run your Cobol and DB2 applications. Seems some parts can be shared between Cobol and DB2 among others like ISPF, NFS. Hopefully in z/OS R8 these conversationt tables will be build undercover on the fly. Roland -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Jim McAlpine Sent: Tuesday, September 19, 2006 3:44 PM To: [email protected] Subject: Re: Unicode and DB2 and Enterprise COBOL OK, I'm looking at the Enterprise COBOL V3R4 Customization Guide chapter 4.4 which has an example of the unicode requirements for both DB2 and COBOL which contains the following statements - CONVERSION 1140,1200; /* Latin-1 to UTF-16, *RECLM* */ CONVERSION 1200,1140; /* UTF-16 to Latin-1, *RECLM* CONVERSION 1140,1200,ER; /* Latin-1 to UTF-16, ER CONVERSION 1200,1140,ER; /* UTF-16 to Latin-1, ER and the following document - ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
