Ensure that the broker user ID (or the group of which it
is a member) has been granted the necessary authorizations.
If
the started task ID does not have execute authorization on the DSNACLI
plan, you get the errors listed in the scenario. If ODBC tracing is
turned on, you also see the following entries in the
traceodbc file
for the broker:
SQLAllocConnect( hEnv=1, phDbc=&1c6bacec )
SQLAllocConnect( )
---> SQL_ERROR
SQLError( hEnv=1, hDbc=0, hStmt=0, pszSqlState=&19ca445c, pfNativeError=&19ca4458,
pszErrorMsg=&1c3d9e50, cbErrorMsgMax=1024, pcbErrorMsg=&19ca4444 )
SQLError( pszSqlState="58004", pfNativeError=-99999, pszErrorMsg="{DB2 for OS/390}
{ODBC Driver}
SQLSTATE=58004
ERRLOC=2:170:6
RRS "CREATE THREAD" failed using DB2 system:DFL0 and Plan:DSNACLI RC=08 and REASON=00f30034",
pcbErrorMsg=159)
---> SQL_SUCCESS
SQLError( hEnv=1, hDbc=0, hStmt=0, pszSqlState=&19ca445c, pfNativeError=&19ca4458,
pszErrorMsg=&1c3d9e50, cbErrorMsgMax=1024, pcbErrorMsg=&19ca4444 )
SQLError( pszSqlState="42505", pfNativeError=-922, pszErrorMsg="{DB2 for OS/390}
{ODBC Driver}
DSNT408I
SQLCODE = -922, ERROR: AUTHORIZATION FAILURE: PLAN ACCESS ERROR.
REASON 00F30034
DSNT418I
SQLSTATE = 42505 SQLSTATE RETURN CODE DSNT415I
SQLERRP = DSNAET03 SQL PROCEDURE DETECTING ERROR ERRLOC=2:170:8", pcbErrorMsg=371 )
---> SQL_SUCCESS
If the started task ID does not
have SELECT authorization on tables SYSIBM.SYSSYNONYMS, SYSIBM.SYSDATABASE
and SYSIBM.SYSTABLES, and if ODBC tracing is turned on, you see the
following type of entry in the traceodbc file:
SQLTables( hStmt=1, szTableQualifier=Null Pointer, cbTableQualifier=0,
szTableOwner="MA15USR", cbTableOwner=-3, szTableName=Null Pointer,
cbTableName=0, szTableType=Null Pointer, cbTableType=0 )
SQLTables( )
---> SQL_ERROR