| Author |
Message
|
| bobbee |
 Posted: Tue Sep 16, 2008 12:31 pm Post subject: WMB z/OS DB2 User DB access (-805) |
 |
|
Knight
Joined: 20 Sep 2001
Posts: 545
Location: Tampa
|
My z/OS Broker DB is on instance DB23, obviously this is working. My User DB's are on DB25. The message flow is getting the following error when I try to do a 'SET dummy = SELECT * COUNT(*) from Database.WCL319:
(0x03000000):Text = '{DB2 FOR OS/390}{ODBC DRIVER}{DSN08015} DSNT4
08I SQLCODE = -805, ERROR: DBRM OR PACKAGE NAME DB25..DSNCLINF.17F9DBC41-
6B6CA8C NOT FOUND IN PLAN DSNACLI. REASON 02 DSN
T418I SQLSTATE = 51002 SQLSTATE RETURN CODE DS
NT415I SQLERRP = DSNXEPM SQL PROCEDURE DETECTING ERROR D
SNT416I SQLERRD = -350 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION
DSNT416I SQLERRD = X'FFFFFEA2' X'00000000' X'00000000' X'FFFFFFFF'
X'00000000' X'00000000' SQL DIAGNOSTIC INFORMATION
ERRLOC=1:13:2'
The config file in Broker has the following
ÂCOMMON
APPLTRACE=0
APPLTRACEfilename=/var/wmqi/QM1GBRK/output/traceodbc
CONNECTTYPE=2
DIAGTRACE=0
DIAGTRACE_NO_WRAP=0
MAXCONN=0
MULTICONTEXT=0
MVSDEFAULTSSID=DB23
; SUBSYSTEM
ÂDB23
ÂDB25
MVSATTACHTYPE=RRSAF
PLANNAME=DSNACLI
; DATASOURCES
ÂDB23
ÂDB25
CURRENTSQLID=CSIODBA
The mqsidbsetparms was issued for the Broker ID. What am I missing? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Sep 16, 2008 12:53 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You are addressing both data sources (different release level) with the same driver. This may not be correct and you may have to choose the driver according to the DS. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bobbee |
| Posted: Wed Sep 17, 2008 6:04 am Post subject: |
|
|
Knight
Joined: 20 Sep 2001
Posts: 545
Location: Tampa
|
both datasources should be the same. They directed to two seperate DB2 substsems on the same LPAR. Where do you see the driver specification in what I supplied. At the suggestion of another person we seperated out the susbsystem and datasource because the subsystem Id and datasource id is the same. I am still getting the -805. We have opened up a PMR to get clarification of the -805 with respect to what we are attempting and have configured. This is the new dsnaoini file. What I would like to see is someone's whos is working. That way I can eliminate the dsnaoini configuration.
ÂCOMMON½
APPLTRACE=0
APPLTRACEfilename=/var/wmqi/QM1GBRK/output/traceodbc
CONNECTTYPE=2
DIAGTRACE=0
DIAGTRACE_NO_WRAP=0
MAXCONN=0
MULTICONTEXT=0
MVSDEFAULTSSID=DB23
; SUBSYSTEM
ÂDB23½
MVSATTACHTYPE=RRSAF
PLANNAME=DSNACLI
ÂDB25½
MVSATTACHTYPE=RRSAF
PLANNAME=DSNACLI
; DATASOURCES
ÂDB23½
CURRENTSQLID=CSIODBA
ÂDB25½
CURRENTSQLID=CSIODBA |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Sep 17, 2008 7:49 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Seems the error is clear
| Quote: |
(0x03000000):Text = '{DB2 FOR OS/390}{ODBC DRIVER}{DSN08015} DSNT4
08I SQLCODE = -805, ERROR: DBRM OR PACKAGE NAME DB25..DSNCLINF.17F9DBC41-
6B6CA8C NOT FOUND IN PLAN DSNACLI. REASON 02 DSN
T418I SQLSTATE = 51002 SQLSTATE RETURN CODE DS
NT415I SQLERRP = DSNXEPM SQL PROCEDURE DETECTING ERROR D
SNT416I SQLERRD = -350 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION
DSNT416I SQLERRD = X'FFFFFEA2' X'00000000' X'00000000' X'FFFFFFFF'
X'00000000' X'00000000' SQL DIAGNOSTIC INFORMATION
ERRLOC=1:13:2'
|
Missed linkage ?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bobbee |
| Posted: Wed Sep 17, 2008 9:14 am Post subject: |
|
|
Knight
Joined: 20 Sep 2001
Posts: 545
Location: Tampa
|
| The DBA came back and stated they were on a Private Protocol. They waved their magic wand and suddenly we are at the database. Trying to figure out what type of bullets their wand was loaded with. |
|
| Back to top |
|
|
|
|
