| Author |
Message
|
| p.cradwick |
 Posted: Wed Apr 04, 2007 7:38 pm Post subject: MRM |
 |
|
Acolyte
Joined: 16 May 2001
Posts: 56
|
This is a pretty basic problem but it has me stumped. I have just started using Toolkit 6.0.2 and have created two message sets from cobol copybooks. It all looks fine - message definition fits with the cpy. However when I set up a flow with MQInput and set domain as MRM I don't see any message sets in the drop down. Same with RCD node. If I simply put the values in and do a trace, this is what I get:
(0x01000000):Properties = (
(0x03000000):MessageSet = 'IOLBRequest-MsgSet'
(0x03000000):MessageType = 'LUULCC8002001'
(0x03000000):MessageFormat = 'CWF1'
(0x03000000):Encoding = 546
[Those are the values I typed in appearing in the msg properties - then follows errors:]
2007-04-05 15:07:51.302776 2744 ParserException BIP5285E: Message Translation Interface Parsing Errors have occurred:
Message Set Name : ''IOLBRequest-MsgSet''
Message Set Level : '1'
Message Format : ''CWF1''
Message Type Path : ''LUULCC8002001''
Review further error messages for an indication to the cause of the errors.
2007-04-05 15:07:51.302787 2744 ParserException BIP5180E: CWF Error : Unknown message type
The CWF parser or writer has received an unknown message type identifier in the message properties.
The specified message set (''LUULCC8002001'') does not contain a message type with this identifier.
[end of quote]
...but the properties defines the message set as: 'IOLBRequest-MsgSet' which is my name for the message set.
Can anyone see what I have done wrong?
thanks
Peter |
|
| Back to top |
|
 |
| AkankshA |
| Posted: Wed Apr 04, 2007 8:01 pm Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
Checkout if in your message flow project you have referred your message set project or not???
_________________
Cheers |
|
| Back to top |
|
|
| Mensch |
| Posted: Wed Apr 04, 2007 9:33 pm Post subject: |
|
|
Disciple
Joined: 17 Jul 2005
Posts: 166
|
Hi,
I think problem is with creation of message set.
Could you please give us the steps that you followed while creating the message set?
_________________
Thanks and Regards ,
Mensch |
|
| Back to top |
|
|
| Mensch |
| Posted: Wed Apr 04, 2007 9:41 pm Post subject: |
|
|
Disciple
Joined: 17 Jul 2005
Posts: 166
|
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Apr 05, 2007 2:20 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
I think this is your problem:
| Quote: |
| Message Type Path : ''LUULCC8002001'' |
This field should contain the name of the message definition. 'LUULCC8002001' looks very much like the unique ID of the message set. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 05, 2007 3:16 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And make sure when importing your cobol copy book that you use the platform the MB resides on and not the platform the copy book came from... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| p.cradwick |
| Posted: Fri Apr 06, 2007 5:28 pm Post subject: Message Set creation with Cobol cpy |
|
|
Acolyte
Joined: 16 May 2001
Posts: 56
|
I agree Mensch, I think the problem lies with the MsgSet creation as this doesn't seem to be recognised by the nodes.
From memory, I created a message set called: ''IOLBRequest-MsgSet'' specifying CWF. I then created a message definition file using the copybook:
01 W-REQUEST-MESSAGE.
05 W-WP-REQUEST-HEADER.
10 W-HEADER-VERSION PIC 9(2).
10 W-CHANNEL PIC X( .
10 W-SERVICE-VERSION PIC 9(2).
10 W-SERVICE-NAME PIC X(50).
05 W-REQUEST-DATA.
=====> 10 WI-R001-DATA.
=====> 15 WI-R001-ARGN-ID PIC X(32).
=====> 15 WI-R001-BALANCE-DATE PIC X(.
=====> 10 PIC X(4.
This produced the file IOLBRequest.mxsd:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="WREQUESTMESSAGE">
<xsd:sequence>
<xsd:element name="W_WP_REQUEST_HEADER" type="wrequestmessage_w__wp__request__header">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<cwfInclRep messageSetDefaultRep="CWF1" skipCountTrailing="0">
<cwfAggrRep accessor="readWrite" contentSize="62" offset="0" size="62"/>
</cwfInclRep>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="W_REQUEST_DATA" type="wrequestmessage_w__request__data">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<cwfInclRep messageSetDefaultRep="CWF1" skipCountTrailing="0">
<cwfAggrRep accessor="readWrite" contentSize="88" offset="62" size="88"/>
</cwfInclRep>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:group name="wrequestmessage_w__wp__request__header">
<xsd:sequence>
<xsd:element name="W_HEADER_VERSION">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<cwfInclRep messageSetDefaultRep="CWF1">
<cwfSimpleRep accessor="readWrite" addrUnit="byte" contentSize="2" offset="0" signFormat="trailing" signed="false" size="2" typeName="MRCWFExternalDecimalRep" width="2"/>
</cwfInclRep>
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:short">
<xsd:minInclusive value="0"/>
<xsd:maxInclusive value="99"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="W_CHANNEL">
<xsd:annotation>
<xsd:appinfo source="http://www.wsadie.com/appinfo">
<initialValue kind="SPACE"/>
</xsd:appinfo>
<xsd:appinfo source="WMQI_APPINFO">
<cwfInclRep messageSetDefaultRep="CWF1">
<cwfSimpleRep accessor="readWrite" addrUnit="byte" characterSize="1" contentSize="8" offset="2" paddingCharacter="SPACE" size="8" typeName="MRCWFStringRep" width="8"/>
</cwfInclRep>
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="8"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="W_SERVICE_VERSION">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<cwfInclRep messageSetDefaultRep="CWF1">
<cwfSimpleRep accessor="readWrite" addrUnit="byte" contentSize="2" offset="10" signFormat="trailing" signed="false" size="2" typeName="MRCWFExternalDecimalRep" width="2"/>
</cwfInclRep>
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:short">
<xsd:minInclusive value="0"/>
<xsd:maxInclusive value="99"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="W_SERVICE_NAME">
<xsd:annotation>
<xsd:appinfo source="http://www.wsadie.com/appinfo">
<initialValue kind="SPACE"/>
</xsd:appinfo>
<xsd:appinfo source="WMQI_APPINFO">
<cwfInclRep messageSetDefaultRep="CWF1">
<cwfSimpleRep accessor="readWrite" addrUnit="byte" characterSize="1" contentSize="50" offset="12" paddingCharacter="SPACE" size="50" typeName="MRCWFStringRep" width="50"/>
</cwfInclRep>
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:complexType name="wrequestmessage_w__wp__request__header">
<xsd:group ref="wrequestmessage_w__wp__request__header"/>
</xsd:complexType>
<xsd:group name="wrequestmessage_w__request__data">
<xsd:sequence>
<xsd:element name="WI_R001_DATA" type="wrequestmessage_w__request__data_wi__r001__data">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<cwfInclRep messageSetDefaultRep="CWF1" skipCountTrailing="0">
<cwfAggrRep accessor="readWrite" contentSize="40" offset="62" size="40"/>
</cwfInclRep>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="fill_0">
<xsd:annotation>
<xsd:appinfo source="http://www.wsadie.com/appinfo">
<initialValue kind="SPACE"/>
</xsd:appinfo>
<xsd:appinfo source="WMQI_APPINFO">
<cwfInclRep messageSetDefaultRep="CWF1">
<cwfSimpleRep accessor="readWrite" addrUnit="byte" characterSize="1" contentSize="48" offset="102" paddingCharacter="SPACE" size="48" typeName="MRCWFStringRep" width="48"/>
</cwfInclRep>
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="48"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:complexType name="wrequestmessage_w__request__data">
<xsd:group ref="wrequestmessage_w__request__data"/>
</xsd:complexType>
<xsd:group name="wrequestmessage_w__request__data_wi__r001__data">
<xsd:sequence>
<xsd:element name="WI_R001_ARGN_ID">
<xsd:annotation>
<xsd:appinfo source="http://www.wsadie.com/appinfo">
<initialValue kind="SPACE"/>
</xsd:appinfo>
<xsd:appinfo source="WMQI_APPINFO">
<cwfInclRep messageSetDefaultRep="CWF1">
<cwfSimpleRep accessor="readWrite" addrUnit="byte" characterSize="1" contentSize="32" offset="62" paddingCharacter="SPACE" size="32" typeName="MRCWFStringRep" width="32"/>
</cwfInclRep>
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="32"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="WI_R001_BALANCE_DATE">
<xsd:annotation>
<xsd:appinfo source="http://www.wsadie.com/appinfo">
<initialValue kind="SPACE"/>
</xsd:appinfo>
<xsd:appinfo source="WMQI_APPINFO">
<cwfInclRep messageSetDefaultRep="CWF1">
<cwfSimpleRep accessor="readWrite" addrUnit="byte" characterSize="1" contentSize="8" offset="94" paddingCharacter="SPACE" size="8" typeName="MRCWFStringRep" width="8"/>
</cwfInclRep>
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="8"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:complexType name="wrequestmessage_w__request__data_wi__r001__data">
<xsd:group ref="wrequestmessage_w__request__data_wi__r001__data"/>
</xsd:complexType>
<xsd:element name="msg_WREQUESTMESSAGE" type="WREQUESTMESSAGE">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<MRMessage messageDefinition="/0/msg_WREQUESTMESSAGE;XSDElementDeclaration$MRObject"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:schema>
and messageSet.mset:
<?xml version="1.0" encoding="UTF-8"?>
<msgCoreModel:MRMessageSet xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:MSGModel="http://www.ibm.com/msgmodel/2003/MSGModel" xmlns:msgCoreModel="http://www.ibm.com/msgmodel/2003/MSGCoreModel" name="IOLBRequest-MsgSet" namespacesEnabled="false" msetVersionNo="" currentMessageSetId="//@MRMessageSetID.0">
<MRMessageSetRep xsi:type="MSGModel:MRCWFMessageSetRep" name="CWF1" daysInFirstWeekOfTheYear="Four" firstDayOfWeek="Monday" timeZoneID="0" allowLenientDateTimes="false"/>
<MRMessageSetID repositoryId="-1082479518" messageSetId="1"/>
</msgCoreModel:MRMessageSet>
and as someone pointed out: "LUULCC8002001" is the message Type ID.
The message set appears in the MessageSet folder in the Administration View in the toolkit so it seems as though the toolkit recognises the message set, so why doesn't it appear in the node dropdowns???
Peter |
|
| Back to top |
|
|
| p.cradwick |
| Posted: Fri Apr 06, 2007 5:38 pm Post subject: |
|
|
Acolyte
Joined: 16 May 2001
Posts: 56
|
Further to the last post, the smiley faces in the copybook should be the chars "eight" followed by "close round bracket".
Thought I'd paste the messageSet generation log file in case someone can see something...
Importing file: C:\WBIMB-Workspaces\WBIMB\Workspace\CommonFlows\SetupFiles\MsgSetSource\WMB100CA.CPY
Import options for COBOL:
EXTENSION_COB=FP
EXTENSION_CBL=FP
PLATFORM_SELECTION=0
EXTENSION_CCP=FP
CODEPAGE=037
NUMPROC=PFD
EXT_DECIMAL_SIGN=EBCDIC
FLOATING_POINT_FORMAT=1
QUOTE=DOUBLE
NSYMBOL=NATIONAL
ENDIAN=Big
TRUNC=STD
REMOTE_ENDIAN=Big
EXTENSION_CPY=DS
SCHEMA_TARGET_NAMESPACE_URI=null
CREATE_DEFAULT_VALUES_FROM_INITIAL_VALUES=false
CREATE_FACETS_FROM_LEVEL_88_VALUE_CLAUSES=false
CREATE_NULL_VALUES_FOR_FIELDS=false
NULL_CHARACTER=SPACE
STRING_PADDING_CHARACTER=SPACE
Creating global element "msg_WREQUESTMESSAGE" for type "WREQUESTMESSAGE"
Creating message "msg_WREQUESTMESSAGE" from global element "msg_WREQUESTMESSAGE"
Setting Padding Character for elements of type String "SPACE"
Elapsed time processing this message definition file: 0.734 seconds
Number of warnings for this message definition file: 0
Number of files processed: 1
The data is coming from a mainframe and being processed on a Windows server.
Peter |
|
| Back to top |
|
|
| kimbert |
| Posted: Sat Apr 07, 2007 9:37 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Like I said, Mesage Type should be set to the name of the message. In your case this is 'msg_WREQUESTMESSAGE'. |
|
| Back to top |
|
|
| p.cradwick |
| Posted: Mon Apr 09, 2007 4:03 pm Post subject: |
|
|
Acolyte
Joined: 16 May 2001
Posts: 56
|
Thanks kimbert, you were correct. Once I had the type right as you suggested, it worked fine. I also discovered why the parameters didn't show up in the drop downs...I hadn't referenced the message set when setting up the flow.
Thanks again
Peter |
|
| Back to top |
|
|
| chris boehnke |
| Posted: Thu Jul 30, 2009 2:17 pm Post subject: |
|
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
"" I hadn't referenced the message set when setting up the flow. ""
Peter,
Could you tell me how to reference the message set when setting up the message flow? What should I do to get it done?
Thanks in advance
Chris |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jul 30, 2009 2:33 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| chris boehnke wrote: |
"" I hadn't referenced the message set when setting up the flow. ""
Peter,
Could you tell me how to reference the message set when setting up the message flow? What should I do to get it done?
Thanks in advance
Chris |
In the project properties when looking for Project References checkmark your message set. Of course you need to have it open in the workspace... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
