| Author |
Message
|
| usr_12345 |
 Posted: Tue May 14, 2013 9:01 am Post subject: MQInput input file. |
 |
|
Novice
Joined: 14 May 2013
Posts: 11
|
How would be go about an MQInput node take input from a file (large file, about 35 to 50 mb) placed at a particular directory.
When i try using test message flow, it throws an outOfMemory error.
thanks. |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Tue May 14, 2013 9:27 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Are you sure you want to use MQInput? Maybe FileInput would be better. IN either case, try the BLOB parser.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue May 14, 2013 9:29 am Post subject: Re: MQInput input file. |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| usr_12345 wrote: |
| How would be go about an MQInput node take input from a file (large file, about 35 to 50 mb) placed at a particular directory. |
Well for a start I'd use a FileInput node to read a file not an MQInput node.
| usr_12345 wrote: |
| When i try using test message flow, it throws an outOfMemory error. |
Have you reviewed the Large Message Sample supplied with the product? Have you reviewed the InfoCenter articles on Handling Large Messages for either XML or non-XML payloads, whichever is relevant to you?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| usr_12345 |
| Posted: Tue May 14, 2013 10:40 am Post subject: |
|
|
Novice
Joined: 14 May 2013
Posts: 11
|
I'm afraid i cannot use BLOB, since there's a message set (cobol) that i want to use and BLOB is not allowing that.
Regards to large file, i want to process line by line from that file but not the whole file at once, hence i did not look through the articles on large messages.
I just tried using FileInput node, but it archived the whole file without doing anything. I bet, not using the messageSet was the issue there. How can we enforce it to use message set. |
|
| Back to top |
|
|
| usr_12345 |
| Posted: Tue May 14, 2013 11:00 am Post subject: |
|
|
Novice
Joined: 14 May 2013
Posts: 11
|
My bad. The record detection and delimiter were not set right, its working now with FileInput node.
Is there a record detection option for BOLB using MQInput. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue May 14, 2013 12:13 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| usr_12345 wrote: |
| Is there a record detection option for BOLB using MQInput. |
The MQInput node (as distinct from the FileInput node) only ever reads a single message. If you want to consider it the equivalent of a FileInput node with the Records And Elements tab built in it's not a bad analogy.
With both of these nodes what you get from the Out terminal is a message tree built from what the node considers a record; either the record the File node detected or one single MQ message. If you use BLOB, there's no structure to it. If you use XMLNSC, an XML parser is associated with it. You mention a COBOL copybook so you'd use a message set. If the MQ message contains 1-n copybook records then you simply need to construct a message set which describes this, i.e. has the copybook structure as an unbounded repeating element.
Hope this clarifies things.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| usr_12345 |
| Posted: Tue May 14, 2013 12:20 pm Post subject: |
|
|
Novice
Joined: 14 May 2013
Posts: 11
|
| sounds good. Thanks to both of you. |
|
| Back to top |
|
|
|
|
