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 » Websphere Message Broker Probelm Using ASBISTREAM.

Post new topic  Reply to topic
 Websphere Message Broker Probelm Using ASBISTREAM. « View previous topic :: View next topic » 
Author Message
jith
PostPosted: Tue Jun 22, 2010 3:19 am    Post subject: Websphere Message Broker Probelm Using ASBISTREAM. Reply with quote

Newbie

Joined: 22 Jun 2010
Posts: 5

Hi,

I have message flow starting with SOAP Input Node. After the SOAP node in compute node i am using below ESQL code.

DECLARE options INTEGER BITOR(FolderBitStream, ValidateContent,ValidateValue);
SET Environment.Variables.InputMessage= InputRoot;
SET Environment.Variables.InputMessage.SOAP.Body.q0:ch_OPERATION}.ceb:message.ceb:m_control.v1:initiator_id = 'XXXXXXXX';
SET Environment.Variables.InputMessage = CAST(ASBITSTREAM(Environment.Variables.InputMessage.SOAP OPTIONS options CCSID 1208)AS CHARACTER ENCODING 1208);

When i ran the message flow the Environment.Variables.InputMessage populated with null value.

below i have also placed the USER log error message
2010-06-20 19:26:45.257629 4268 UserTrace BIP2539I: Node 'MetlifeUKeServices.ValuationServiceFanOut_MF.LogMessage_Compute': Evaluating expression ''options'' at ('MetlifeUKeServices.ValuationServiceFanOut_MF_LogMessage_Compute.Main', '35.104'). This resolved to ''options''. The result was ''4294979584''.
2010-06-20 19:26:45.257678 4268 UserTrace BIP6068W: A request was made to serialize a bitstream from element ''SOAP'' using parser ''MQROOT''. The result was zero bytes long.
The node or ESQL ASBITSTREAM function requested that an element serialize its bitstream and this resulted in no bytes being written.

If the output bitstream should not have been zero bytes long, ensure that the correct element was specified.
If the parser name is blank or set to a root parser, associate an owning parser with the element:
If created in ESQL, the DOMAIN clause of the CREATE statement can be used.
If created using the user-defined extension API use a method that allows a parser to be specified.


NOTE : The same ESQL code i am using in other flow its working fine (Other flow starting with MQInput node node)

Could you please anyone help me out to resolve this issue.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue Jun 22, 2010 4:22 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Environment does not hold the parser information, unless you specifically create a node in it that has a parser assigned.

Your "Set Environment.Variables.InputMessage = InputRoot" does not do what you think it does.

It seems a lot easier to just work with OutputRoot?
Code:
DECLARE options INTEGER BITOR(FolderBitStream,ValidateContent,ValidateValue);
SET OutputRoot= InputRoot;
SET OutputRoot.SOAP.Body.q0:ch_OPERATION}.ceb:message.ceb:m_control.v1:initiator_id = 'XXXXXXXX';
SET Environment.Variables.InputMessage = CAST(ASBITSTREAM(OutputRoot.SOAP OPTIONS options CCSID 1208)AS CHARACTER ENCODING 1208);
Set OutputRoot = InputRoot;
Back to top
View user's profile Send private message
jith
PostPosted: Tue Jun 22, 2010 5:01 am    Post subject: Websphere Message Broker Probelm Using ASBISTREAM. Reply with quote

Newbie

Joined: 22 Jun 2010
Posts: 5

Thanks for your reply.

Same ESQL Code is working in Other Flow (Other Flow starting with MQINPUT Node).

The problem is current flow i am using SOAP Input node.
Back to top
View user's profile Send private message
kimbert
PostPosted: Tue Jun 22, 2010 5:29 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

Thanks for quoting the error message in full - it always helps. The error message actually tells you what to do, and it agrees with mqjeff:
Quote:
If the parser name is blank or set to a root parser, associate an owning parser with the element:
If created in ESQL, the DOMAIN clause of the CREATE statement can be used.


Quote:
Same ESQL Code is working in Other Flow (Other Flow starting with MQINPUT Node).
Hmmm. I ran across the road without checking for traffic last week, and I didn't get run down. Doesn't make it a good idea.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Websphere Message Broker Probelm Using ASBISTREAM.
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.