We get that error occasionally, and it's pretty tough to diagnose
exactly what is going wrong.  We find that if we make a simple change
to the macro (add a few blank spaces somewhere) and save the file, it
usually takes care of the problem.

I think (and I'm just guessing here) that there is probably a problem
with the tokenized macro in the macro cache.  Changing the last
modified date/time will force the db2www cgi program to reread and
re-tokenize the macro.

Like I said, that's just a guess as to why this works, but regardless,
it generally solves the issue.

Mike E.

On 8/8/06, Mike Cunningham <MCUNNING@xxxxxxx> wrote:
We started getting an error sent from net.data that has "Incorrect
symbol <varies> encountered in macro <varies> at line <varies>" If we
restart the Apache server right away when we catch this the error goes
away without making any changes to the macro or any of the includes
(just about all of our macros have includes) so we can prove it's not a
constant error. The errors will start at random times and then go away
by themselves. We were able to force it to happen by putting an error in
one of the includes (add an extra @) and then taking it away again. No
errors in any logs (that we can find). Anyone else come across this
error before?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.