MQSeries.net :: View topic - JDBCProvider configurable service problem

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » JDBCProvider configurable service problem

JDBCProvider configurable service problem

« View previous topic :: View next topic »

Author

Message

PEPERO

Posted: Tue Oct 30, 2012 9:01 pm Post subject: JDBCProvider configurable service problem

Disciple

Joined: 30 May 2011
Posts: 177

Hi all;
I've defined a JDBCProvider configurable service within the broker to be connected to a DB2 database and performing some inqueries.
Using the following attributes set

Code:

connectionUrlFormat = jdbc:db2://DEVZ11:446/SAMPLEDB:user=TSOUSR1;password=USRPASS;
databaseName = SAMPLEDB
databaseType = DB2
databaseVersion = 9.1
.
.
.
securityIdentity = db2usr
serverName = DEVZ11
type4DatasourceClassName = com.ibm.db2.jcc.DB2XADataSource
type4DriverClassName = com.ibm.db2.jcc.DB2Driver

in which the db2usr security identity has being defined using the mqsisetdbparms command as follows

Code:

mqsisetdbparms BRK4Z11 -n jdbc::db2usr -u TSOUSR1 -p USRPASS

The flow using JDBCProvider configurable service through a javacompute node throws an exception indicating the SQLSTATE=42815 and ERRORCODE=-4461 with a description of "Null userid is not supported" since any parameters related to the userid has being fullfilled.

smdavies99

Posted: Tue Oct 30, 2012 11:05 pm Post subject:

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Please do a search on this forum for

Quote:

connectionUrlFormat

and why you must never change it. It is a FORMAT pattern.

This problem appears every few months (sadly)
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.

PEPERO

Posted: Tue Oct 30, 2012 11:59 pm Post subject:

Disciple

Joined: 30 May 2011
Posts: 177

Thanks so much.

PEPERO

Posted: Wed Nov 07, 2012 9:22 am Post subject:

Disciple

Joined: 30 May 2011
Posts: 177

So how is it possible to pass the DB2 package name?
I've tried it through the "environmentParms" and set it to "PACKAGE=MYPKG" but it couldn't distinguish tha package name. It shows the SQLCODE=-551 with the package name equal to "NULLID" even if the userid has all the requested functions privilages.

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » JDBCProvider configurable service problem

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Protected by Anti-Spam ACP