ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MQSI v2.1

Post new topic  Reply to topic
 MQSI v2.1 « View previous topic :: View next topic » 
Author Message
dweise
PostPosted: Thu Feb 07, 2002 12:10 am    Post subject: Reply with quote

Newbie

Joined: 05 Feb 2002
Posts: 2
Location: Germany

Hi,

We have installed MQSI v2.1 CSD1 on our Windows NT System and have problems with the MRM. First of all I tried to create a messageset of TDWF type. It didn't work, the parser stopped to parse the message at the end of the MQMD and told us that the Bitstream Worker wasn't found. So I tried the example of the control center redbook. It produced the same error message.
Bitstream Worker not found ID of the Descriptor for the physical format 'rmLoadWorker'.
The rmLoadWorker needed for the message-ID and the desriptor is not installed. Either the installation is false or it is not fully installed or the resource is not registered or a unknown bitstream worker was requested.
The bitstream workers are loaded from 'MtiImbParser.lil' when the broker starts.

The dlls and files listed in the error message are all installed. Has someone had the same problem or a tip what I could do?
Back to top
View user's profile Send private message
Miriam Kaestner
PostPosted: Fri Feb 08, 2002 2:16 am    Post subject: Reply with quote

Centurion

Joined: 26 Jun 2001
Posts: 103
Location: IBM IT Education Services, Germany

Have you:
1. assigned and deployed the message set to broker?
2. set the correct MessageFormat (in defaults of MQInput node or in RFH2) to the ID of your TDWF layer?
Back to top
View user's profile Send private message Send e-mail
dweise
PostPosted: Mon Feb 11, 2002 6:05 am    Post subject: Reply with quote

Newbie

Joined: 05 Feb 2002
Posts: 2
Location: Germany

Found out, was the wrong TDS-Format ID Thanks
Back to top
View user's profile Send private message
briones
PostPosted: Fri Feb 15, 2002 3:44 pm    Post subject: Reply with quote

Newbie

Joined: 07 Jan 2002
Posts: 4

OK - I am experiencing the same problem - and attempted to understand "was the wrong "TDS-Format ID" - so I specified the format id from the "tag delimited" tab on both the mqinput node as well as on the message (<Fmt>TSD</Fmt>) - I basically am following the samples from support pac ID05 (which work on 2.1 + CSD)

My questions or request for help seems simplistic - but I just can't get it -- please help by posting it here ...

Back to top
View user's profile Send private message Send e-mail
Tibor
PostPosted: Mon Feb 18, 2002 8:18 am    Post subject: Reply with quote

Grand Master

Joined: 20 May 2001
Posts: 1033
Location: Hungary

Quote:

On 2002-02-15 15:44, briones wrote:
OK - I am experiencing the same problem - and attempted to understand "was the wrong "TDS-Format ID" - so I specified the format id from the "tag delimited" tab on both the mqinput node as well as on the message (<Fmt>TSD</Fmt>) - I basically am following the samples from support pac ID05 (which work on 2.1 + CSD)


There is a new 'feature' in Control Center - you can choose your TDS or CWF identifier from a drop-down list. However, this works incorrectly, because you see a decription but broker needs the identifier

So I used to give same text for description and identifier...
Back to top
View user's profile Send private message
Paul D
PostPosted: Tue Feb 19, 2002 2:11 pm    Post subject: Reply with quote

Master

Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country

See my thread entitled "WMQI v2.1 Issue : Resource Manager: Bitstream Worker cannot be found". I reported this to IBM, they recreated it and sent it back to Hursley for a resolution. Sounds like a bug. As I mentioned in my thread, I'll post something when I get a resolution from them...

Thanks...

Paul
Back to top
View user's profile Send private message Visit poster's website
Paul D
PostPosted: Tue Feb 19, 2002 2:17 pm    Post subject: Reply with quote

Master

Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country

I checked out what Tibor said about the drop down not displaying the identifier, but the name. I'm running the 2.1 CSD#1 version and that looks correct (uses ID of message set). So, it anything, this version/CSD combination corrects this. The problem I reported in the previous reply to this topic still stands, so 2.1 CSD #1 will not fix the bitstream worker problem.
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MQSI v2.1
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
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.