|
Problem |
SQLCODE104 is received when running
WebSphere® Application Server for z/OS® naming client BBONMC. This occurs
when running in codepages with DB2® MIX=YES.
If you run with Katakana code page, specifying CCSID=1390 and MIX=YES, you
will experience a failure. This is part of the bootstrap process. The
naming client will issue the following messages:
BBOU0135E The NameSpace configuration has encountered an unknown
problem. Namespace configuration is terminating.
BBOU0118W Configuration was unsuccessful at binding (local) IDR to the
namespace
BBOU0127E THE CONFIGURATION OF THE GLOBAL NAMESPACE HAS FAILED.
NAMESPACE CONFIGURATION HAS NOT BEEN COMMITTED.
and the naming server issued the following:
DSNT408I SQLCODE = -104, ERROR: ILLEGAL SYMBOL "and". SOME SYMBOLS THAT
MIGHT BE LEGAL ARE: <END-OF-STATEMENT>
This message is indicating that the "and" symbol is not recognized by the
DB2 sql parser. |
|
Cause |
The cause of this problem is that there is an SQL
statement that gets executed during the naming client execution that has
an "and" keyword in lower case. The code page being used does not map
upper and lower case letters to the same place, therefore the lower case
"and" is not recognized by DB2. |
|
Solution |
The problem can be resolved by using two DB2 subsystems
when running WebSphere Application Server and LDAP databases and specify
MIXED=NO on one of the DB2 subsystems.
Note: This restriction is not in WebSphere Application Server
for z/OS V5. You can upgrade to Application Server V5 to avoid this
problem also.
|
|