| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Recive message without Set Length |
« View previous topic :: View next topic » |
| Author |
Message
|
| smdavies99 |
 Posted: Sat Jul 07, 2012 5:00 am Post subject: |
 |
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| mona wrote: |
compute node :
SET len = LENGTH(InputRoot.BLOB.BLOB) ;
SET sub = CAST(len as CHARACTER);
SET sub = CAST('0x'||sub as INTEGER);
SET OutputLocalEnvironment.TCPIP.Receive.Length = sub;
----------------
TCPIP receive :
Record detection : Fixed Length (byte = 0)
---------------
can you help me? |
What does a usertrace output of the above coe show? Are you getting the length?
What does the data look like as is comes over the wire? Wireshark can help here.
What does the raw data look like when read by the first TCP node?
| Code: |
declare cLength char;
set cLength = cast(InputRoot.BLOB.BLOB as char CCSID 1208);
set OutputLocalEnvironment.TCPIP.Receive.Length = trim(right(cLength,4));
|
Something like the above may work a little better than your code. This depends upon how the length is setup in the fixed lenght part but answering my questions first will help you resolve that one.
_________________
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 |
|
 |
| mona |
| Posted: Sat Jul 07, 2012 8:40 am Post subject: |
|
|
Novice
Joined: 14 Mar 2012
Posts: 19
|
my default: first 2 byte in message not content of length of message, so I don't use it bytes.I want get stream of data(hex or ...) without using first 2 byte of message.
e.g data
| Quote: |
0800202001000080000299000071
53580103393939393030303301000715
8C75B70D4A6E623E601F1E7AA6F89DF7
CE08932B8B77032597D4F00FEC0DADBC
181CEFF6E2B325EFB48920C975F54624
7094B58559D88915719276767D525252
7261618A09A7141AE2A47701563AAFA2
8DCC9F575827633F92D9844F3DAF7161
37CD
|
result of trace:
| Quote: |
BIP2632I: Message received and propagated to 'out' terminal of MQ input node '.InputNode'.
BIP6060I: Parser type ''Properties'' created on behalf of node '.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
BIP6061I: Parser type ''MQMD'' created on behalf of node '.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
BIP6061I: Parser type ''XMLS'' created on behalf of node '.InputNode' to handle portion of incoming message of length '4243' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
BIP3574I: The following connection was opened: ID ''localhost'' on Hostname ''1414'' on Port ''TCPIP Server Input'' in TCPIP input node ''TCP_POSFlow'' in message flow '{4}'.
BIP3907I: Message received and propagated to 'open' terminal of input node 'TCP_POSFlow.TCPIP Server Input'.
BIP6060I: Parser type ''Properties'' created on behalf of node 'TCP_POSFlow.TCPIP Server Input' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
BIP4015I: Message propagated to the 'out' terminal of node 'TCP_POSFlow.Compute' with the following message trees: 'OutputLocalEnvironment, OutputRoot, InputExceptionList'.
BIP3563I: A record has been received from Hostname ''localhost'' on Port ''1414'' in TCPIP receive node ''TCPIP Server Receive'' in message flow ''TCP_POSFlow''.
BIP3903I: Node (class='ComIbmTCPIPServerReceiveNode', name='TCPIP Server Receive') propagating to 'out' terminal.
The specified node is about to propagate a message to the specified terminal.
No user action required. This is an information message.
BIP6063I: A parser of type ''Properties'' was created on behalf of node 'TCP_POSFlow.TCPIP Server Input' to handle the input stream, beginning at offset '0'.
BIP6064I: A parser of type ''BLOB'' was created on behalf of node 'TCP_POSFlow.TCPIP Server Input' to handle the input stream, beginning at offset '0'. The parser type was selected based on value ''NONE'' from the previous parser.
BIP2638I: The MQ output node 'TCP_POSFlow.out' attempted to write a message to queue ''out'' connected to queue manager ''QMGR''. The MQCC was '0' and the MQRC was '0'.
BIP2622I: Message successfully output by output node 'TCP_POSFlow.out' to queue ''out'' on queue manager ''QMGR''.
BIP3560I: A record has been received from Hostname ''localhost'' on Port ''1414'' in TCPIP input node ''TCPIP Server Input'' in message flow ''TCP_POSFlow''.
BIP6063I: A parser of type ''Properties'' was created on behalf of node 'TCP_POSFlow.TCPIP Server Input' to handle the input stream, beginning at offset '0'.
BIP6069W: The broker is not capable of handling a message of data type ''BLOB''.
The message broker received a message that requires the handling of data of type ''BLOB'', but the broker does not have the capability to handle data of this type.
Check both the message being sent to the message broker and the configuration data for the node. References to the unsupported data type must be removed if the message is to be processed by the broker.
BIP6064I: A parser of type ''BLOB'' was created on behalf of node 'TCP_POSFlow.TCPIP Server Input' to handle the input stream, beginning at offset '0'. The parser type was selected based on value ''NONE'' from the previous parser.
BIP2638I: The MQ output node 'TCP_POSFlow.fail' attempted to write a message to queue ''fail'' connected to queue manager ''QMGR''. The MQCC was '0' and the MQRC was '0'.
BIP2622I: Message successfully output by output node 'TCP_POSFlow.fail' to queue ''fail'' on queue manager ''QMGR''.
BIP2632I: Message received and propagated to 'out' terminal of MQ input node '.InputNode'.
BIP6060I: Parser type ''Properties'' created on behalf of node '.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
BIP6061I: Parser type ''MQMD'' created on behalf of node '.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
BIP6061I: Parser type ''XMLS'' created on behalf of node '.InputNode' to handle portion of incoming message of length '226' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
|
|
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
