Tom, >Well I hate the missing line number for DB2 msgs while using the integrated >compiler. >This is a pain. Sample > >IGYDS0208-I DSNH4760I The DB2 SQL Coprocessor is using the level 2 >interface under DB2 V8 >IGYDS0210-S DSNH332I CHARACTER CONVERSION FROM CCSID 1140 TO CCSID >1208 IS NOT SUPPORTED, REASON 001 >IGYDS0210-S DSNH332I CHARACTER CONVERSION FROM CCSID 1208 TO CCSID >1140 IS NOT SUPPORTED, REASON 002 >IGYDS0208-I DSNH4764I SQL OPTION "CCSID(273)" IS IN EFFECT
>Unfortunally not line number was given so which one cause the problem????? Roland, I tried some tests and you do get line numbers when the SQL messages apply to specific source lines. The messages you reference do not refer to a specific SQL statement. The coprocessor interface level is determined when we process your COBOL compiler option SQL and call DB2 to establish comunication. Character conversion happens whenever COBOL calls DB2 V8 (or later) since DB2 converts everything to Unicode (CCSID 1208) and then back again when it sends us a message. (The conversion should be automatically enabled on z/OS 1.7 or later, are you on an older z/OS? ) SQL OPTIONS also do not relate to a source line, but to the options in effect. We do not give line numbers for COOBL Options in effect either. Do you have any suggestions about what to improve here? Maybe this is a case where a compiler messages manual IS needed, since the messages do not relate to COBOL or SQL language, but to language processing. Cheers, TomR >> COBOL is the Language of the Future! << ---------------------------------------------------------------------- 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
