Hi Everyone

I am getting that error message in my reports when I have -SET &ECHO=ALL;. But the reports work perfectly, so it is some kind of warning message I assume. This makes me nervous since I have seen errors like this that start to crash at some point.

Anybody have any idea what might trigger this?My report has a ton of ampers in it but they are all working fine.

Thanks

Jodye

Would it be possible for you to post the line(s) before the '-SET', sounds as if something in the previous line is causing issues.

Jodye,

Watch out for missing semi colons after any -SET. It's the normal reason that folks get this message.

T

Hi Leah and Tony

I found the problem. I was debugging something and had an exit right after table file. Like this...

TABLE FILE CAR
-EXIT

this triggers the error. Which is a strange error given that there is no SET.

I am sure I have seen that error in the past in reports that work perfectly. Do a view source of the html and there is the error at the very end. But I do not have anything to reproduce that right now.

Thanks!

Try forgetting the END sometime, you get a real strange one. As we say, been there, done that.

Jodye,

Leah is correct, any time you have "TABLE FILE FILENAME" without an "END" you will get the following error.

(FOC002) A WORD IS NOT RECOGNIZED: SET
BYPASSING TO END OF COMMAND
(FOC009) INCOMPLETE REQUEST STATEMENT

After it happens enough, you don't think you just go to your fex and begin to look for the section that is missing an "END".

Ive had the same experience as Glenda, as you go on there are a number of errors you will begin to recognise straight away and be able to fix. In fact these two errors still happen to me when im doing multi-statement fex's but ill just flick through it looking for the missing 'END'

if you type in

? (number from error code)

like this:

? 002

and turn the 'display command lines on'

you'll get this description

0(FOC002) A WORD IS NOT RECOGNIZED:A word which is not a reserved word begins a phrase. A reservedword may have been misspelled or there is a syntax error. Reservedwords are IF, BY, AND, etc.:

works for all the error codes ive tried so far and can be a good way of learning more about the errors you may come across

also you can find a summary of all error descriptions here:

Suggestion: when issuing TABLE FILE XXX
issue an 'END' on the next line right away, and then just insert blank lines to write the body of the code. OR when code is completed use your editor do a find on 'table file', note the line number. then do a search on 'end' if you run into two 'table file' commands without an end in between you know what to do. or if you do not run into ANY 'end' commands for a single table file command - same thing. Good luck..
Ira wf 5.3.x aix 533