Posted: Wed Oct 09, 2002 6:43 am Post subject: Deploy on Z/OS Broker
Novice
Joined: 19 Jul 2001 Posts: 14
Hello, I have WMQI broker created on OS/390. When no configuration is deployed yet, and the broker is started it starts without any problem. When I deploy my configuration I can see a message in the SYSTEM.BROKER.ADMIN.QUEUE but any task consume the message. I can't see any error messages.
hello, I repeat my Broker Installation and Customization and now I have these messages in the SYSLOG:
+BIP2321E MQT1BRK 0 DATABASE ERROR: ODBC RETURN CODE '-1'.
+BIP2322E MQT1BRK 0 DATABASE ERROR: SQL STATE '58004'; NATIVE ERROR COD
386
E '-99999'; ERROR TEXT ' DB2 for OS/390 ODBC Driver SQLSTATE=58004
ERRLOC=2:170:6
+BIP2322E MQT1BRK 0 DATABASE ERROR: SQL STATE '42505'; NATIVE ERROR CODE
'-922'; ERROR TEXT ' DB2 for OS/390 ODBC Driver
+BIP2322E MQT1BRK 0 DATABASE ERROR: SQL STATE '58004'; NATIVE ERROR COD
388
E '-99999'; ERROR TEXT ' DB2 for OS/390 ODBC Driver SQLSTATE=58004
ERRLOC=2:171:1;
+BIP2322E MQT1BRK 0 DATABASE ERROR: SQL STATE '58004'; NATIVE ERROR COD
389
E '-99999'; ERROR TEXT ' DB2 for OS/390 ODBC Driver SQLSTATE=58004
ERRLOC=2:170:6
+BIP2053E MQT1BRK 0 THE BROKER MADE AN UNSUCCESSFUL ATTEMPT TO ACCESS
ITS DATABASE TESTDBT WITH USERID MQI.
MQT1BRK is: the broker name, the started taskname and started task user.
MQI is the table owner name and I have a RACF group named MQI.
DBT is the SUBSYSTEM NAME and TESTDBT is the location name.
I can't understand why the started task try to connect with username MQI (I think that MQT1BRK is the correct name).
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