OBA does not tell you the exact token, line, or string
which causes a parsing error. It simply
returns "Unexpected token".
The status line does give a clue as to how far you might
have gotten through the code, but it is not enough to
pinpoint the problem.
Logged In: YES
user_id=1727174
Originator: NO
I second this: I see other errors in OnBA provide at least a symbol name (ie, PilotMain_00)
The global is globalCodeFixupList[i].index; The only trouble would be finding which fixup it's in, which there may be a global sitting around somewhere else for.