SQL0104 - Token amp;1 was not valid. Valid tokens: amp;2
SQL0104 - Token &1 was not valid. Valid tokens: &2
Invalid iSeries Access ODBC SQL Syntax message
Probable cause:
The application generated an SQL statement with incorrect syntax. For help with problem determination, use the ODBC trace tool, provided with the ODBC Administrator, to look at the SQL.LOG.
See SQL0114 - Relational database &1 not the same as current &2 server if "*" is the token.
The SQL statement is using a literal that exceeds the 32K size limitation.
Consider using a parameter marker instead of a literal. This reduces the size of the statement while allowing you to pass the maximum field size woth of data.
The application is using incorrect syntax for left outer join. Some applications default to a proprietary left outer join syntax of *= in the WHERE clause (PowerBuilder 3.0 & 4.0, Crystal Reports). Check with your application vendor. Most provide an ini setting or a configuration value to use ODBC left outer join syntax.
Your ODBC Data Source Name (DSN) configuration uses the wrong decimal separator character. Some users have set the decimal separator parameter of the ODBC connection to a comma instead of a period.