Author |
Message
|
Savis |
Posted: Mon Mar 01, 2004 12:18 am Post subject: ODBC connection in WBIMB 5 |
|
|
Novice
Joined: 19 Nov 2003 Posts: 10
|
I've found some information regarding wmqi 2.1 saying that he user/password for the odbc connection has to be the same for all connections.
Is this still the case in 5.0 ? I can't find any properties/attributes to set for a unique ODBC connection in the messageflow. Or do I need to set something up using a commandline tool or similar?
Kind Regards
// Savis |
|
Back to top |
|
 |
jefflowrey |
Posted: Mon Mar 01, 2004 6:01 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
You set the username and password on the ODBC connection, instead of in the message flow.
SQLServer supports this kind of ODBC connection, and as of 8.1, so does DB2.
I don't know about others (oracle, etc) but I suspect they do as well. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
JT |
Posted: Mon Mar 01, 2004 6:09 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003 Posts: 1564 Location: Hartford, CT.
|
The command is mqsisetdbparms. The following excerpt is from the WMQIMB v5.0 Information Center:
Use the mqsisetdbparms command to associate a specific userid and password with each Data Source Name (DSN) used in Database and Compute nodes. Where the same DSN is used in multiple nodes (referring to the same database instance), the same userid and password combination is used. |
|
Back to top |
|
 |
jefflowrey |
Posted: Mon Mar 01, 2004 7:28 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
 _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
Deeko |
Posted: Wed Mar 03, 2004 2:15 am Post subject: |
|
|
 Acolyte
Joined: 16 May 2001 Posts: 72 Location: Edinburgh, UK
|
Watch out with mqsisetdbparms and Windows based brokers. I was told by IBM there's a problem when using password greater than 6 characters and there's a fix available.
Regards,
Derek. |
|
Back to top |
|
 |
|