If you didn't upgrade your COBOL as well as z/OS, then I would be REALLY surprised in this change occurring. The COBOL documentation talks about the change from NODBCS to DBCS as the "default" compiler option - in newer releases of Enterprise COBOL. There should ALSO be a change from FLAG(I) to FLAG(I,I) so that these messages SHOULD have appeared in the source code exactly by the line that had the problem.
FYI, What the change from NODBCS to DBCS means is that *if* you have "hex" OD and OE in your alphanumeric literals, they are treated as DBCS control characters. NOTE WELL: COBOL compiler messages (IGY) are *not* documented; they are "self-documenting". If your application programmers can't figure out these specific messages, I would suggest additional training for them. If they don't know WHY they are getting the messages now (but not before), then I suggest you provide them references to the COBOL Migration Guide which does talk about such changes (NODBCS to DBCS). Finally, it does sound as if you may want to switch your site default to NODBCS - unless you also have DBCS applications. The difference between COBOL2 and COBOL3 compiler options MAY influence some of this, but isn't the real problem with these messages. "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
