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 » Problem with InputExceptionList - WMB 6.0

Post new topic  Reply to topic
 Problem with InputExceptionList - WMB 6.0 « View previous topic :: View next topic » 
Author Message
santy
PostPosted: Wed Jul 29, 2009 12:15 am    Post subject: Problem with InputExceptionList - WMB 6.0 Reply with quote

Centurion

Joined: 03 Nov 2006
Posts: 141

Hi,

To get the InputExceptionList in string format, I have written following code -

DECLARE options INTEGER BITOR(FolderBitStream, ValidateContent, ValidateValue);
SET Environment.XML.ExceptionData = InputExceptionList;
DECLARE EXCEPTIONBLOB BLOB ASBITSTREAM(Environment.XML.ExceptionData OPTIONS options CCSID
InputRoot.MQMD.CodedCharSetId);

SET Environment.EXCEPTIONBLOB = EXCEPTIONBLOB;
SET string_exception = CAST(Environment.EXCEPTIONBLOB AS CHAR CCSID InputRoot.Properties.CodedCharSetId
ENCODING InputRoot.Properties.Encoding);
SET Environment.string_exception = string_exception;

But I'm getting below output -

(0x03000000):EXCEPTIONBLOB = X'' (BLOB)
(0x03000000):string_exception = '' (CHARACTER)

So, Is it possible to cast the ExceptionList in CHAR format?
Back to top
View user's profile Send private message
kimbert
PostPosted: Wed Jul 29, 2009 2:32 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

Every message tree is owned by a parser. Sometimes the parser is automatically assigned, and sometimes you need to choose a parser and assign it manually.
When you create a tree under Environment or LocalEnvironment, the default parser will be the 'generic' parser, which does not know how to serialize its tree.
If you want to serialize an environment tree as XML, you need to choose an XML parser ( hint: XMLNSC is a really good one ) and explicitly assign it using the DOMAIN clause of the CREATE statement.

This usually crops up when people try to copy data from XMLNSC or XMLNS into the environment, so congratulations for discovering a new way to make this particular error
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 » Problem with InputExceptionList - WMB 6.0
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.