<much snippage>

Concerning the COBOL compiler message:

 "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."

The original problem has been "diagnosed" and hopefully solved.  However,
there has been a (semi)reasonable discussion on whether any/all COBOL
programmers would know what to do with this message.  Tom Ross of IBM has
already indicated that - unlike most compiler messages - this one MIGHT need
additional information.

It seems to me that the "problem" (with the message) is that two very
different types of programs/programmers MIGHT receive this message.

A) Programmers creating Unicode or other multi-lingual applications *AND*
who use DBCS characters within alphanumeric literamals.

B) Programmers who have either themselves or via a preprocessor/translator
had data inserted into their source code.

OBVIOUSLY, there is no way for the compiler to know which of these has
occurred.  Neither would any type of documentation (either compiler message
nor Messages & Codes manual).

  ***

It would seem possible (likely?) that IBM *might* accept a PMR (with a SUG
closing) to change this - and/or to accept a SHARE requirements addressing
this specific message.  

Again (to me) it would seem that the message could be clearer (even though
*I* understood the original message) if it stated something like:

 "IGYPS0157-E   A shift-out <X'0E'>  was found in column 50 without a
matching shift-in <X'0F'> in a nonnumeric or national literal.  This may be
caused by either an incorrectly bounded DBCS character string or by
non-displayable data entered in a quoted literal while the DBCS compiler
option is specified. The literal was processed as written."

----------------------------------------------------------------------
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

Reply via email to