| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Msg Model: Choice Group Issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| tigerstone |
 Posted: Wed Sep 17, 2014 6:24 am Post subject: Msg Model: Choice Group Issue |
 |
|
Novice
Joined: 06 Feb 2014
Posts: 20
|
Data Sample1: 1:xxxxx 2:Iyyyyy
Data Sample2: 1:xxxxx 2:Ozzzzz
Complete TDS Message Model:
Types:
Basic Block (Group Indicator '1:', Data Element Seperation: 'Fixed Length')
Local Element: X (Length 5)
Application_I(Group Indicator '2:I', Data Element Seperation: 'Fixed Length')
Local Element: Y (Length 5)
Application_O(Group Indicator '2:O', Data Element Seperation: 'Fixed Length')
Local Element: Z (Length 5)
Application Block (Choice Group, Data Element Seperation: 'Fixed Length')
Local Elements: Application_I (0:1), Application_O(0:1)
The issue is that the program is unable to parse the Application Block. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Sep 17, 2014 6:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Use "1","2","I" and "O" as tags, ":" as a tag/data separator, and build your model like
| Code: |
applicationBlock
Choice:
BasicBlock
AppBlock
Choice: <tag/data separator = "">
AppIBlock
AppOBlock |
And let the tags resolve the choices. |
|
| Back to top |
|
|
| tigerstone |
| Posted: Wed Sep 17, 2014 7:17 am Post subject: |
|
|
Novice
Joined: 06 Feb 2014
Posts: 20
|
And If the data is as such
Data Sample1: 1:xxxxxAAAABBB 2:IyyyyyCCDDDDE
Data Sample2: 1:xxxxxAAAABBB 2:OzzzzzCCDDDDE
That is the Basic Block, Application_I and Application_O complex types have more than 1 Local element. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Sep 17, 2014 7:23 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| tigerstone wrote: |
And If the data is as such
Data Sample1: 1:xxxxxAAAABBB 2:IyyyyyCCDDDDE
Data Sample2: 1:xxxxxAAAABBB 2:OzzzzzCCDDDDE
That is the Basic Block, Application_I and Application_O complex types have more than 1 Local element. |
Then you add the additional elements to the relevant types.
| Code: |
applicationBlock
Choice:
BasicBlock
field1
field2
AppBlock
Choice: <tag/data separator = "">
AppIBlock
field1
field2
AppOBlock
field1
field2 |
the main point is to use tags instead of group indicators, and use tag/data separator to indicate the ":" where it's used.
The rest is just basic message modelling. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
