| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Why did the reset content descriptor work? |
« View previous topic :: View next topic » |
| Author |
Message
|
| tbt102 |
 Posted: Mon Jul 14, 2003 7:04 am Post subject: Why did the reset content descriptor work? |
 |
|
Apprentice
Joined: 21 Apr 2003
Posts: 28
|
Hi all,
o I have a legacy (OS/390) file that is input to a flow as a blob
o I setup a message type that looks at the records as repeating. I added a repeat count and depending on to an existing COBOL copybook then imported it to achieve this
o I'm using a compute node to parse in a repeat count before each record. This lengthen each record by 4 bytes
o I need to trim off the last 4 bytes of each record so that the incoming message continues to fit the copybook/component type. The compute node does this for all messages accept the last record
o Next the blob gets passed to a reset content descriptor node without a problem
Why doesn’t the reset content descriptor fail? The last record in the blob is 4 bytes longer than the others.
Thanks in advance for any help. |
|
| Back to top |
|
 |
| kirani |
| Posted: Mon Jul 14, 2003 10:01 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Complete Flow layout(description) would help in explaining the problem. Do you have any other node connected to this RCD?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| tbt102 |
| Posted: Mon Jul 14, 2003 10:47 am Post subject: |
|
|
Apprentice
Joined: 21 Apr 2003
Posts: 28
|
| Code: |
Input Q ==> Compute ==> RCD ==> Compute ==> Output Q
Blob add from processing
repeat blob 2
count MRM |
[/code]
Thanks |
|
| Back to top |
|
|
| kirani |
| Posted: Mon Jul 14, 2003 12:18 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
It depends on what you are doing in your second compute node.
The message body will actually be parsed when a reference is first made to it during the message flow. WMQI uses "Parse When Needed" approach to parse the message tree. In your case, since the incoming bitstream is greater than the one defined in MRM, your tree gets parsed completly and aligns well with your message defn. So WMQI ignores the trailing 4 bytes and hence doesn't throws any error. If you send a message, which is smaller than the MRM message length defined in MRM, WMQI will throw an excpetion.
I hope I answered your question.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| tbt102 |
| Posted: Tue Jul 15, 2003 2:29 am Post subject: |
|
|
Apprentice
Joined: 21 Apr 2003
Posts: 28
|
kirani,
Yes that answ the question. Thanks. |
|
| 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
|
|
|
|
