There have been so many replies and so many verging topics, that I thought that I would reply (again) to the original message with the actual solutions (in order of preference) to the real problem originally reported here.
Option 1 (preferred) Use the COBOL3 (*NOT* the COBOL2) CICS Translator option for *ALL* LE-enabled COBOL compilers - regardless of CICS product level. If you do this, it does NOT matter if you use the DBCS or NODBCS COBOL compiler option, you will have no problem and you will be able to use all the syntax available with current compilers. Option 2 (still reasonably flexibility), If you are using CICS TS V2.x or Later, then in order to use the COBOL2 translator option (something that isn't recommended, but should work), then for CICS TS V2 (but not V3) you must have applied an APAR for this translator option even to be accepted. When using the translator with CICS TS V2 or V3 and the COBOL2 translator option, then you WILL be able to use either the DBCS or NODBCS COBOL compiler option. You still won't get any compiler message. Option 3 (last choice - but will work), If for some UNKNOWN reason, you absolutely positively MUST use the COBOL2 translator option with CICS TS V1 or earlier, then you ALSO must use the NODBCS COBOL compiler option. This WAS the default in VS COBOL II and the earliest LE-enabled COBOL compilers. It did change (as the default) with later versions/releases of the compiler. As noted elsewhere, you will NOT be able to use the NSYMBOL(NATIONAL) compiler option to support UNICODE development if you are in this situation. *** Bottom-Line: Use the COBOL3 translator option with any supported (or recently supported) CICS release and COBOL compiler and you won't have any problems. I believe this has been the IBM recommendation for a decade or so, but I haven't spent the time researching it. P.S. If you actually have a (currently unsupported) COBOL compiler that supports the CMPR2 compiler option *and* you actually use this option, then you MUST also use the COBOL2 translator option *and* a translator supplied with CICS TS V1 or earlier. However, recent enquiries seem to indicate that such shops and programs are virtually unknown. "Perryman, Brian" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED] i.com>... > Hi folks > > Our developers are getting IGYPS0157-E and IGYPS0158E messages when they try and compile a CICS COBOL program on z/OS 1.4 in Enterprise Cobol of z/OS and OS/390 V3.2. > > I can't find these blasted messages documented anywhere!! Is there some convoluted format for decoding them? > > I suspect it's just a COBOL options member problem, but I need to see the message description. It only seems to happen when the CICS precompiler (CICS 4.1.0) is included first. > > The texts of the messages are: > > IGYPS0157-E A shift-out was found in column 50 without a matching shift-in in a nonnumeric or national literal. The literal was processed as written. > > IGYPS0158-E A nonnumeric or national literal containing double-byte characters was found which exceeded the maximum literal length or reached end of area "B" before terminating. A literal delimiter was placed at column 72 of line nnnn ---------------------------------------------------------------------- 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
