All of a sudden this morning, I started receiving a FOC303 message on all my reports that had previously been running fine. There have been no code changes to any of the reports. What would cause this to suddenly appear? I've got 15 to 20 reports that need to be run and they all come back with the same error.

This message has been edited. Last edited by: kerry,

quote:

(FOC303) CONTROL LINE NOT RECOGNIZED IN FOCEXEC: The subcommand in the Dialogue Manager starts with a dash and appears to be a control line, but is not correct. Check the list of valid commands.

You may not have changed the code in any of the reports, but there are several ways of introducing an error upon execution of a program:

- INCLUDE - Has any of the included code been modified?
- C:\ibi\srv53\wfs\etc\edasprof.prf - Regular WebFOCUS and Dialogue Manager code can be included in this profile file - it will run for every WebFOCUS call
- C:\ibi\client53\wfc\etc\site.wfs - This site profile file may have an included fex configured for "_site_profile" - it will run for every WebFOCUS call

The location of the config files may have changed for WF 7.

(FOC303) CONTROL LINE NOT RECOGNIZED IN FOCEXEC:
"The subcommand in the Dialogue Manager starts with a dash and appears to be a control line, but is not correct. Check the list of valid commands."

One way this can occur is if your fex has dynamic content that includes a leading numeric value (perhaps in a dynamically generated -INCLUDE, or a DM &var, providing DATA for a MODIFY). If the numeric value suddenly went negative (say, in reaction to recent events on Wall Street ), and the leading minus sign falls in column 1 or 2, it will look like a line of dialog manager code, and you earn a FOC303.