I don't understand your comment. As previously indicated the FLAG(I,I) option became the default at the same time as DBCS.
Therefore, the compiler error message WILL appear in the listing IMMEDIATELY after the line inserted by the translator (indicating the column in that line with the problem). If a CICS application programmer can't "recognize" a translator inserted line with Move "alphanumeric literal" to DFHnnnn field as being inserted by the translator and/or if that same programmer can't recognize that the column that the message is pointing to is within an alphanumeric literal, then NO "messages and codes" manual is ever going to help that programmer (IMHO) "Shmuel Metz , Seymour J." <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > In <[EMAIL PROTECTED]>, on 06/28/2005 > at 08:48 AM, Joe Zitzelberger <[EMAIL PROTECTED]> said: > > >While column 50 might look blank iff you are using a printed listing > > (a rarity in the days of syntax highlighting editors > > Editors? It doesn't exist in the source file, so the editor doesn't > see it. > > >and a waste of trees) > > The term "listing" also includes DASD files with A or M carriage > control. Have they stopped translating out nondisplayable characters? > > >the surrounding columns would have something like: > > Move 'a 0d 2 ic$k34 d pd e,x d' to DFHEI1234 > > Why would you get the error message for alphanumeric text? I don't see > a SI or SO there. > > > >That should be enough for anyone to realize it is a translator > >problem. > > It would if the compiler were complaining about one of those > characters. > ---------------------------------------------------------------------- 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
