| Author |
Message
|
| anon_kb |
 Posted: Fri Jul 10, 2015 12:47 am Post subject: [ASBITSTREAM][WSDL] Invalid Wire format retreived |
 |
|
Acolyte
Joined: 13 Nov 2014
Posts: 74
|
Hi guys! Would like to ask for your help about this one. I have a flow using a message set and I'm having the problem of INvalid Wire Format.
| Quote: |
| SET wholeMsg = ASBITSTREAM(InputBody, InputRoot.Properties.Encoding,InputRoot.Properties.CodedCharSetId); |
Did I missed something?. I tried the different suggestions here and still I'm getting same error. Thanks.
Last edited by anon_kb on Mon Jul 13, 2015 9:59 pm; edited 1 time in total |
|
| Back to top |
|
 |
| inMo |
| Posted: Fri Jul 10, 2015 6:47 am Post subject: |
|
|
Master
Joined: 27 Jun 2009
Posts: 216
Location: NY
|
|
| Back to top |
|
|
| anon_kb |
| Posted: Mon Jul 13, 2015 7:24 pm Post subject: |
|
|
Acolyte
Joined: 13 Nov 2014
Posts: 74
|
| Hi Inmo, actually here's my situation I've used a WSDL file given to me to be use as a new message set project. Then I generate the new message defintion based on the WSDL. Did I have done somthing wrong on causing this error? Thanks. |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Jul 14, 2015 1:57 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
If you are using the MRM parser ( why? ) then you *must* specify the message set, message type ( global element name ) and format. MRM simply cannot operate without all 3.
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
| anon_kb |
| Posted: Tue Jul 14, 2015 3:00 am Post subject: |
|
|
Acolyte
Joined: 13 Nov 2014
Posts: 74
|
This is my userlog. Anyway I checked the properties of my message set and it syncs on the message set properties i've set on the compute node.
| Code: |
SET OutputRoot.Properties.MessageDomain = 'MRM';
SET OutputRoot.Properties.MessageSet = 'ExportFlow001';
SET OutputRoot.Properties.MessageType = 'Envelope';
SET OutputRoot.Properties.MessageFormat = 'XML1';
|
| Code: |
The error is :
Jul 10 08:19:18 miaibv19 user:err|error WebSphere Broker v61012[331800]: (BMIAA0Z.BSM_01)[7215]BIP2488E: (.WMB_EBX_ExportDISSUB00_001_UpdateHeaderOrCheckError.Main, 17.13) Error detected whilst executing the SQL statement 'SET wholeMsg = ASBITSTREAM(InputBody ENCODING InputRoot.Properties.Encoding CCSID InputRoot.Properties.CodedCharSetId);'. : BMIAA0Z.c8872a34-3501-0000-0080-f166a9e236cd: /build/S610_P/src/DataFlowEngine/ImbRdl/ImbRdlStatementGroup.cpp: 617: SqlStatementGroup::execute: ComIbmComputeNode: WMB_EBX_ExportDISSUB00_001#FCMComposite_1_7
Jul 10 08:19:18 miaibv19 user:err|error WebSphere Broker v61012[331800]: (BMIAA0Z.BSM_01)[7215]BIP5136E: Invalid Wire Format Identifier ''. : BMIAA0Z.c8872a34-3501-0000-0080-f166a9e236cd: /build/S610_P/src/MTI/MTIforBroker/MtiImbParser2/MtiImbSyntaxElement.cpp: 590: CpContext::loadWorker: :
Jul 10 08:19:18 miaibv19 user:err|error WebSphere Broker v61012[331800]: (BMIAA0Z.BSM_01)[7215]BIP2628E: Exception condition detected on input node 'WMB_EBX_ExportDISSUB00_001.WMB.EBX.AI_EXPORTDIS_SUB'. : BMIAA0Z.c8872a34-3501-0000-0080-f166a9e236cd: /build/S610_P/src/DataFlowEngine/ImbCommonInputNode.cpp: 1856: ImbCommonInputNode::run: ComIbmMQInputNode: WMB_EBX_ExportDISSUB00_001#FCMComposite_1_24
Jul 10 08:19:18 miaibv19 user:info WebSphere Broker v61012[331800]: (BMIAA0Z.BSM_01)[7215]BIP3002I: Exception thrown by throw node 'WMB_EBX_ExportDISSUB00_001.WBI_Sub_ErrorHandler.Rollback UserExceptions'; text is 'User Exception - Invalid Data formats encountered'. : BMIAA0Z.c8872a34-3501-0000-0080-f166a9e236cd: /build/S610_P/src/DataFlowEngine/BasicNodes/ImbThrowNode.cpp: 265: ImbThrowNode::evaluate: ComIbmThrowNode: WMB_EBX_ExportDISSUB00_001#FCMComposite_1_8.WBI_Sub_ErrorHandler#FCMComposite_1_10
|
[/quote] |
|
| Back to top |
|
|
| inMo |
| Posted: Tue Jul 14, 2015 5:20 am Post subject: |
|
|
Master
Joined: 27 Jun 2009
Posts: 216
Location: NY
|
Where are you telling ASBITSTREAM about your settings? From the help documentation I previously posted:
| Quote: |
The ASBITSTREAM field function uses parameters supplied by the caller for:
Encoding
CCSID
Message set
Message type
Message format
Options |
|
|
| Back to top |
|
|
| anon_kb |
| Posted: Thu Jul 16, 2015 3:52 am Post subject: |
|
|
Acolyte
Joined: 13 Nov 2014
Posts: 74
|
Hi INmo.. problem solved. thanks  |
|
| Back to top |
|
|
| inMo |
| Posted: Thu Jul 16, 2015 5:57 am Post subject: |
|
|
Master
Joined: 27 Jun 2009
Posts: 216
Location: NY
|
Great. You posted your original code as:
| Code: |
| SET wholeMsg = ASBITSTREAM(InputBody, InputRoot.Properties.Encoding,InputRoot.Properties.CodedCharSetId); |
Are you able to post the revised code you used to close the loop for future readers? |
|
| Back to top |
|
|
| anon_kb |
| Posted: Thu Jul 16, 2015 10:12 pm Post subject: |
|
|
Acolyte
Joined: 13 Nov 2014
Posts: 74
|
| Hi Inmo, All I did was that I checked again my project and I found out that I'm using a old message set. Sorry for the mistake. I've updated the message set and problem solved. I also discovered that the input file given to me has some deficiencies also. |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Jul 17, 2015 11:02 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| All I did was that I checked again my project and I found out that I'm using a old message set |
I'm calling you a liar ( in the nicest way possible! ). Your ASBITSTREAM call did not specify the SET, TYPE and FORMAT parameters, and therefore it could not possibly work. Are you claiming that you did not fix that, but it is now working somehow?
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
|
|
