| Author |
Message
|
| Paul D |
 Posted: Tue Jan 22, 2002 2:38 pm Post subject: |
 |
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
I''m working with 2.1 Tagged Delimited Wire Format Layer and I''m getting
this message from my NT Broker after deployment. Has anyone got this
one before and know what the problem is? I''ve loaded CSD 0 already.
The is my first attempt at using Tagged delimited. Here's the complete
message:
( NTBROKER.default ) Resource Manager: Bitstream Worker cannot be
found: message set id 10, wire format descriptor id rmLoadWorker.
The required bitstream worker for message set id/wire format descriptor
pair (10, rmLoadWorker) has not been installed. This means either that
the installation is not valid (corrupted or incomplete) or that an
unknown bitstream worker has been requested at resource registration
time or at run time.
The bitstream workers are loaded when the MtiImbParser.lil is loaded
when the Broker starts an Execution Group (DataFlowEngine instance).
Check the Application event viewer (or system log) for error messages
when the broker is started or when a resource is deployed to the
broker. Check that the appropriate bitstream worker file (dll or shared
object) exists in the correct directory. E.g. On NT if we send an XML
message to the broker we should have the file bipxmlworker.wrk in the
<MQSI dir>bin directory. Other platforms should have the .wrk files in
the <MQSI dir>/lib directory.
Paul Dix
Northwestern Mutual
I.S.-Middleware Tech Support
|
|
| Back to top |
|
 |
| chanduy9 |
| Posted: Tue Jan 22, 2002 2:52 pm Post subject: |
|
|
Disciple
Joined: 28 Nov 2001
Posts: 177
Location: USA
|
Paul Dix,
After defining the messageset, you have to define the physical format, which is mandatory in WMQSI2.1.
Right click on message set go to Add-->Physical Format, there you have to select the specified parser.
if you any questions shoot it to me.
Chandra. |
|
| Back to top |
|
|
| Paul D |
| Posted: Tue Jan 22, 2002 3:11 pm Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
E-Mail to chanduy9...
I did do that step, so that won't help. I'm trying to set this up for a comma deliminated file. Is there anything special on that tab that I need to set. Here's what I have so far (fields not listed are blank):
TDS Wire Format Identifier: TDS
Messaging Standard: Unknown
Default CCSID: 367 (My broker is on NT for now)
Trim Fix Len String: No Trim
Output Compression Technique: None
Input Compression Technique: None
Boolean True Representation: 1
Boolean False Representation: 0
Boolean Null Representation: 0
Any ideas? |
|
| Back to top |
|
|
| Paul D |
| Posted: Tue Jan 22, 2002 8:38 pm Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
I just figured out that I needed to set the TDS Wire Format Identifier to TDWF, which appears to get me past this initial problem. I'm now getting parser errors during the deploy. A log message being written on the Config Mgr box that lists them. I'll look at those next...
Thanks for the help... |
|
| Back to top |
|
|
| bh |
| Posted: Wed Jan 23, 2002 1:00 am Post subject: |
|
|
Acolyte
Joined: 25 Jun 2001
Posts: 61
|
| Do you try to install the CSD01 (now available) for WMQI V2.1 which seems to 'correct' a lot of things on MRM "2" ? |
|
| Back to top |
|
|
| Paul D |
| Posted: Wed Jan 23, 2002 8:43 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
No, I didn't see that was available. I'll get that on and retry everything. Thanks!!!
Paul |
|
| Back to top |
|
|
| Paul D |
| Posted: Wed Jan 23, 2002 3:29 pm Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
I've applied CSD #1 to WMQI 2.1 and that seems to have fixed my initial problem. Now I'm getting an error during the deploy. It asks me to look at the CWF.log file on my Config Mgr box. It contains several of the following messages about my fields.
TDS Extractor Trace File
========================
Beginning Extract..
Extracting Identification Info
Extracting Project Info
Extracting Messages
Extracting Elements
Extracting Compound Types
Extracting Type Members
Beginning Indexing..
Creating Member IDs to Tags Index Table.
Beginning Validation..
Validating Project
Validating Types
ERROR: TDSValidator::ValidateTypeMemberSimpleElement:
Elements of a non-Boolean simple type in a type with Data Element Separation attribute = Fixed Length
must have one of the following attributes set:
Element Level - Length
Type Member Level - Length Reference
(Element ID: BusTransLineCode)
(Type ID: t_TrustPremiumTransaction)
Return Code: -80
I'm at a loss for why I need to set either the Element Length or the Type Member Level's length reference. I'm trying to parse a excel exported comma delimited file. Looks like this..
field1,field2,field3
There are no tags and the data is of variable length and seperated by commas. The message here says the Data Seperation attribute is = Fixed Length, yet I have it set to "All Elements Delimited" . I do not have it set to fixed length, yet it says that I do. Does this look like a bug? It does to me. Any ideas on what I'm doing wrong or potential workarounds to this?
Thanks!!!
Paul Dix
Northwestern Mutual
I.S.-Middleware Tech Support |
|
| Back to top |
|
|
| Paul D |
| Posted: Thu Jan 24, 2002 11:51 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
I stand corrected on my comment about the bitsteam worker being gone. I got past the deploy errors but still have the following message coming out. It now appears when I have tracing on. My flow goes nowhere. Actually, my trace file continues to grow out of control until I stop the flow. This is running with just one input message. I'm not really sure what to do now. I might consider reinstalling everything.
ParserException BIP5294E: Resource Manager: Bitstream Worker cannot be found: message set id 10, wire format descriptor id rmLoadWorker.
The required bitstream worker for message set id/wire format descriptor pair (10, rmLoadWorker) has not been installed. This means either that the installation is not valid (corrupted or incomplete) or that an unknown bitstream worker has been requested at resource registration time or at run time.
The bitstream workers are loaded when the MtiImbParser.lil is loaded when the Broker starts an Execution Group (DataFlowEngine instance). Check the Application event viewer (or system log) for error messages when the broker is started or when a resource is deployed to the broker. Check that the appropriate bitstream worker file (dll or shared object) exists in the correct directory. E.g. On NT if we send an XML message to the broker we should have the file bipxmlworker.wrk in the <MQSI dir>bin directory. Other platforms should have the .wrk files in the <MQSI dir>/lib directory. |
|
| Back to top |
|
|
| Paul D |
| Posted: Tue Feb 19, 2002 2:06 pm Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
FYI - On 2-18-2002 I opened a case with IBM for this. On 2-19-2002 they reported to me that they reproduced it and it appears to be a bug. A fix for solution should be forthcomming. I will post an update when I get that...
Paul |
|
| Back to top |
|
|
| Paul D |
| Posted: Wed Feb 20, 2002 10:19 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
| Heard back from IBM support. The list box in the input node, default tab, "Message Format" has a bug. Selecting "Tagged Delimited Format" does not work. This will be fixed in 2.1 CSD#2. Changing the value to SWIFT by typing it in manually will fix this problem. |
|
| Back to top |
|
|
| mapa |
| Posted: Thu Feb 21, 2002 5:57 am Post subject: |
|
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
Hi Paul,
Well you got there just ahead of me.
Thank you for sharing this information with me.
I started to evaluate the new MRM with a tagged message format to see if we can move from NEONFormatter. Of course, I ran into the same problem that you reported to IBM.
I tried to change the Message Format in the input node as you said, but get same error. Do I have to switch to SWIFT in the message set too?
I guess I should say good luck to us both in exploring this "new" MRM.
Best regards Magnus Palmér
[ This Message was edited by: mapa on 2002-02-21 06:04 ] |
|
| Back to top |
|
|
| Paul D |
| Posted: Thu Feb 21, 2002 6:19 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
No, you shouldn't. Here's what I have in my input node for an example:
Message Domain: MRM
Message Set: DM95BT0086001
Message Type: TrustPremiumTranMsg
Message Format: SWIFT
Topic:
Note that the Message Type is the identifier field from my message in this message set. Are you at version 2.1 CSD#1? |
|
| Back to top |
|
|
| mapa |
| Posted: Mon Feb 25, 2002 6:05 am Post subject: |
|
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
Yes, I am at CSD01.
I managed to get by the problem at last.
I had to set the Message Format to the same value as in the TDS Wire Format Identifier. I actually used TDWF first and it worked just fine. Then I changed in the MRM to TDS and set the Message Format to TDS and that worked just fine too. As long as you have a matching couple it works it turned out.
Setting the TDS Wire Format Identifier to the same as your added Physical Format->Tagged/Delimited Format would be the neatest thing to do. Then you will have the value in the drop down box of the input node.
This is what I am using now.
(I normally set the RFH2 when sending to the input queue though.)
Thanks for your help once again.
Best regards Magnus Palmér
[ This Message was edited by: mapa on 2002-02-25 06:07 ] |
|
| Back to top |
|
|
| kwelch |
| Posted: Thu Mar 07, 2002 8:28 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 255
|
Hi,
We are attempting to upgrade to WMQI 2.1. We had initial problems installing it over 2.0.1 so decided to try installing it fresh on another NT pc that had never had a prior version. Now we are getting the same message that Paul mentions above about the Bitstream Worker cannot be found. The difference in our problem is we are not trying to use Tagged Delimited data. We are using CWF.
I thought I read somewhere that this would be fixed in CSD #2. Does anyone know when that will be available or if there is a work around for this in the meantime?
Thanks,
Karen
[ This Message was edited by: kwelch on 2002-03-07 10:55 ] |
|
| Back to top |
|
|
| Paul D |
| Posted: Thu Mar 07, 2002 10:16 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
Karen,
MQSI support mentioned that it would be fixed in 2.1 CSD#2. The workaround worked for me, so I did not pursue it any further. The problem was in the list box not recording the value you selected accurately. I'm guessing, but you may want to play around with this. Try typing in the value you want, even if it's not tagged deliminted or swift. If that doesn't work, I'd to support for more advice. They were pretty quick to determine for me this was an existing bug.
Good Luck...
Paul |
|
| Back to top |
|
|
|
|
