| Author |
Message
|
| servi |
 Posted: Tue Jul 08, 2008 1:41 am Post subject: Adding Keyword information to MXSD files |
 |
|
Novice
Joined: 19 Mar 2008
Posts: 22
Location: Madrid, España
|
Hello,
¿Are there any way to display Keyword information in the bar file asociated with a message set (.mxsd)? 
I add an XML comment (as spec. the doc. for XML files) in the mxsd file to add the MQSI keyword but it is not displayed in the Properties->Keywords. 
<?xml version="1.0" encoding="UTF-8">
<!-- $MQSI author = John MQSI$>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:include schemaLocation=".wmqi21.mxsd"/>
<xsd:complexType name="C35A3609_Sal_TYPE">
<xsd:annotation>
.........
</xsd:annotation>
</xsd:element>
</xsd:schema>
¿Are MQSI Keywords only reserved to message flows, jars, esql and MessageSet?
Thanks in advance. |
|
| Back to top |
|
 |
| Vincent Beukers |
| Posted: Tue Mar 17, 2009 6:05 am Post subject: keyword location/notation .mxsd versioning in the runtime |
|
|
Newbie
Joined: 08 Aug 2008
Posts: 6
Location: Koedoik
|
Hello,
can someone please answer this question because i'm also looking for the solution to see the version of the .mxsd in the runtime.
All the versions of the other sources are displayed only this one remains.
I can't find the answer anywhere in this forum.
Tnx in advance!  |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Mar 17, 2009 7:11 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
You do not deploy mxsd files. You deploy message sets. A message definition file is not separately deployable
The product documentation is referring to other types of XML file which *are* deployable ( e.g. xslt ). |
|
| Back to top |
|
|
| Vincent Beukers |
| Posted: Tue Mar 17, 2009 7:30 am Post subject: |
|
|
Newbie
Joined: 08 Aug 2008
Posts: 6
Location: Koedoik
|
Hi kimbert,
I know that you deploy the message Set. But the .mxsd has it's own version. The version of the message Set is showing in the info list in the runtime. I want to see the version of the .mxsd in the (keyword) list also.
Just like you dont deploy a subflow. You deploy the main flow.
But you can see the version of the subflows in the runtime by doing the right 'moves'.
I like to know the 'moves' to see the version of the .mxsd in the runtime (not in the barfile..sorry if that is confusing here).
Is that even possible? |
|
| Back to top |
|
|
| Hari |
| Posted: Tue Mar 17, 2009 4:28 pm Post subject: |
|
|
Centurion
Joined: 21 Nov 2002
Posts: 117
Location: USA
|
Hope this helps....Enter the text in the .mset file under the Documentation textfield
$MQSI MXSD VERSION = ver MQSI$
You can replace MXSD VERSION with whatever text you want to see, while for the ver insert your version number. |
|
| Back to top |
|
|
| servi |
| Posted: Wed Mar 18, 2009 4:17 am Post subject: |
|
|
Novice
Joined: 19 Mar 2008
Posts: 22
Location: Madrid, España
|
Hello Hari,
The problem of this solution is that you need to modify the .mset documentation each time you create a new .mxsd version.
It would be better if the Broker shows also the mxsd files properties.
Regards. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Mar 18, 2009 4:22 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
If you know the version of the Message Set that is deployed, then you know the version of all of the Message Definitions inside that Message Set.
It's not clear at all why the Message Set would not change version if you change one of the components of it - that is, one of the Message Definitions in the Message Set. It's a different Message Set at that point! |
|
| Back to top |
|
|
| Vincent Beukers |
| Posted: Wed Mar 18, 2009 4:55 am Post subject: |
|
|
Newbie
Joined: 08 Aug 2008
Posts: 6
Location: Koedoik
|
| Quote: |
| If you know the version of the Message Set that is deployed, then you know the version of all of the Message Definitions inside that Message Set. |
If you change anything within a .mxsd and you syncronize is, only the version of de .mxsd is updated +1, not the version of the. mset. The version of the .mxsd is also changed more often.
Thats is why i want to know which version is running in the runtime.
At this point, i assume Ãt issnt possible. 
| Quote: |
| It would be better if the Broker shows also the mxsd files properties. |
This would be the solution to the problem. |
|
| Back to top |
|
|
| Vincent Beukers |
| Posted: Tue Jul 07, 2009 12:58 am Post subject: .mxsd in the runtime |
|
|
Newbie
Joined: 08 Aug 2008
Posts: 6
Location: Koedoik
|
Hello folks!
Can someone tell me if there is an update somewhere that will solve this problem? Or are they busy working to solve it?
I'll still want to see the version of de .mxsd in the runtime.
Tnx in advance! |
|
| Back to top |
|
|
| shanson |
| Posted: Tue Jul 07, 2009 3:16 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
I'm afraid that version info is only available at the message set level, not .mxsd.
It is not something that will change in the next release either. The first problem is that all details of the mxsd are lost by the time a message set has been compiled into a .dictionary file for the MRM parser runtime. The second problem is that the admin perspective does not know about anything other than message sets.
Feel free to submit a formal requirement. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jul 07, 2009 3:21 am Post subject: Re: .mxsd in the runtime |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Vincent Beukers wrote: |
Hello folks!
Can someone tell me if there is an update somewhere that will solve this problem? Or are they busy working to solve it?
I'll still want to see the version of de .mxsd in the runtime.
Tnx in advance! |
You'd have a better chance by asking your IBM rep to support your request for spec modification ... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
