Author |
Message
|
kash3338 |
Posted: Wed May 25, 2011 11:35 pm Post subject: Error in XMLNSC Message set |
|
|
Shaman
Joined: 08 Feb 2009 Posts: 709 Location: Chennai, India
|
Hi,
We are trying to validate a message before it is sent to the Output queue. The flow structure is as below,
MQInput --> Compute --> MQOutput
In the compute node, the mapping is done as per the xsd available and the Message set properties is set in this node,
SET OutputRoot.Properties.MessageDomain = 'XMLNSC';
SET OutputRoot.Properties.MessageSet = 'CDLJ6Q8002001';
We have set the Validation to Content and Value at the MQOutput node. But when the message is validated, we get the error,
"Validation is enabled but pre-processed schemas cannot be located for the specified message set".
We also tried using a RCD node before the MQOutput node and still get the same error.
We have created the Message set using xsd provided and it is a valid xsd.
What can be the issue in this? The version details are as below,
MB Version: 6.1.0.3
Domain: XMLNSC
In the Message setm Default Message Domain is "XMLNSC". |
|
Back to top |
|
 |
smdavies99 |
Posted: Thu May 26, 2011 12:05 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Is the message set deployed to the Execution Group?
Please take a usertrace and post ALL the error messages. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
kimbert |
Posted: Thu May 26, 2011 1:23 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Your error message is BIP5028. In v7 the answer is given in the error message. You did not quote the entire error message, so I don't know whether v6.1.0.3 contains the clue that you need.
The answer is: use the message set name, not the 13-character identifier. |
|
Back to top |
|
 |
kash3338 |
Posted: Thu May 26, 2011 1:23 am Post subject: |
|
|
Shaman
Joined: 08 Feb 2009 Posts: 709 Location: Chennai, India
|
smdavies99 wrote: |
Please take a usertrace and post ALL the error messages. |
Find the user trace below:
ParserException BIP5028E: The XMLNSC parser cannot find a deployed message set with name ''CDLJ6Q8002001''.
The XMLNSC parser is attempting to validate an XML message or a message tree, but the specified message set cannot be located in this execution group. This situation can arise for one of the following reasons:
- The message set has not been deployed to this execution group.
- In the message set properties, XMLNSC is not the 'Default message domain' and is not a 'Supported message domain'.
- The message set has been identified using its 13-character identifier; you must use the message set name.
- There was an error during the preprocessing of the XML schemas in the message set.
Check that the specified message set has been successfully deployed.
The message set is deployed to the execution group. The Message Set BAR has both the .xsdzip and .dictonary files. |
|
Back to top |
|
 |
kimbert |
Posted: Thu May 26, 2011 1:30 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
|
Back to top |
|
 |
fjb_saper |
Posted: Thu May 26, 2011 2:16 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
kash3338 wrote: |
ParserException BIP5028E: The XMLNSC parser cannot find a deployed message set with name ''CDLJ6Q8002001''.
- The message set has been identified using its 13-character identifier; you must use the message set name.
|
Just in case you missed the hint kimbert gave you.
Go back to the design phase.
Did you assign a name to the message set (optional in the toolkit)?
Use the message set name and not the identifier.  _________________ MQ & Broker admin |
|
Back to top |
|
 |
kash3338 |
Posted: Thu May 26, 2011 10:32 am Post subject: |
|
|
Shaman
Joined: 08 Feb 2009 Posts: 709 Location: Chennai, India
|
|
Back to top |
|
 |
|