This comes back from the command center at random times when I paste a
new command in there. Doesn't matter what it is, as long as it is
syntactically correct (i.e. it wil execute in the other tool I use).

Capitalization results in the same message.

Is there some special symbol I'm supposed to by putting in front of
the front of a legal statement?


SQL0104N An unexpected token "create table
XTECH.CJ35MQI_TICKETBOOKSTATUS" was found following
"BEGIN-OF-STATEMENT". Expected tokens may include: "<space>".

The only thing that seems to cure this is to shut down the DB2 tools
and start over, something that makes one wonder about the tool.

I think you may be experiencing an "unannounced" or "unsupported"
feature of command center.
I'd open a PMR if you really want a solution.
HTH, Pierre.

Brandon Smith wrote:

> This comes back from the command center at random times when I paste a
> new command in there. Doesn't matter what it is, as long as it is
> syntactically correct (i.e. it wil execute in the other tool I use).
>
> Capitalization results in the same message.
>
> Is there some special symbol I'm supposed to by putting in front of
> the front of a legal statement?
>
>
> SQL0104N An unexpected token "create table
> XTECH.CJ35MQI_TICKETBOOKSTATUS" was found following
> "BEGIN-OF-STATEMENT". Expected tokens may include: "<space>".
>
> The only thing that seems to cure this is to shut down the DB2 tools
> and start over, something that makes one wonder about the tool.

--
Pierre Saint-Jacques - Reply to: sescons at attglobal dot net
IBM DB2 Cerified Solutions Expert - Administration
SES Consultants Inc.

The SQL Parser has failed to parse the statement sufficiently through to
be convinced even about the beginning.
Could it be the paste also delivered seom control characters (??)
May, or may not be a tool problem....
Cheers
Serge