Topic
  • 3 replies
  • Latest Post - ‏2013-03-20T19:16:50Z by SystemAdmin
SystemAdmin
SystemAdmin
4179 Posts

Pinned topic ImbRecoverableException caught from worker->parseNext

‏2013-03-19T15:09:10Z |
Hello,

FTM 2.0
WebSphere Message Broker Toolkit - Message Broker 7.0.0.5

I am trying to process a sequential file created on the mainframe:
a) fixed lenght 80
b) with CR/LF at the end of each line, except for the last:
c) the first record is a header

ADD-COMMENT2013031400000002
130314000001This is a comment 1
130314000002This is a comment 2

I have used this copybook to create the message set

---------------------------------------------------------------
01 MTS-ADD-COMMENT-REQUEST.
03 MTS-HEADER PIC X(80).
* 05 MTS-COM-TRN-NAME PIC X(11) VALUE 'ADD-COMMENT'.
* 05 MTS-COM-TRN-DATE PIC X(08).
* 05 MTS-COM-TRN-COUNT PIC 9(08).
* 05 FILLER PIC X(53).
* 03 MTS-COMMENT REDEFINES MTS-HEADER PIC X(80).
* 05 MTS-COM-TRN-REF-NUM PIC X(12).
* 05 MTS-COMMENTS PIC X(68).
* 01 MTS-ADD-COMMENT-RESPONSE PIC X(80).

The copybook did not work; I would get only "ImbRecoverableException caught from worker->parseNext"; so I commented all lines leaving only MTS-HEADER; now I got something.

This is what I get on rInputBody - MRM; I used RFHUTIL to send the file to a MQ queue.

MRM
MTS_HEADER:CHARACTER:ADD-COMMENT2013031400000002
MTS_HEADER:CHARACTER:
130314000001This is a comment 1
MTS_HEADER:CHARACTER:
130314000002This is a comment 2
CHARACTER:ImbRecoverableException caught from worker->parseNext.

does anyone know how to fix this parse error??

Thanks
Tony
Updated on 2013-03-20T19:16:50Z at 2013-03-20T19:16:50Z by SystemAdmin
  • kimbert@uk.ibm.com
    kimbert@uk.ibm.com
    515 Posts

    Re: ImbRecoverableException caught from worker->parseNext

    ‏2013-03-19T22:30:15Z  
    You must be new to message broker.

    The error message that you are seeing is only a summary line. Message broker actually gives very good diagnostic messages. The best way to diagnose and fix message flow problems is:
    • disconnect the debugger
    • add Trace nodes to the message flow
    • take a user trace, and read it carefully. It contains a lot of useful information, and it also contains the full text of all error messages issued by the message flow.

    Post again when you have the real error message.
  • SystemAdmin
    SystemAdmin
    4179 Posts

    Re: ImbRecoverableException caught from worker->parseNext

    ‏2013-03-20T19:12:17Z  
    You must be new to message broker.

    The error message that you are seeing is only a summary line. Message broker actually gives very good diagnostic messages. The best way to diagnose and fix message flow problems is:
    • disconnect the debugger
    • add Trace nodes to the message flow
    • take a user trace, and read it carefully. It contains a lot of useful information, and it also contains the full text of all error messages issued by the message flow.

    Post again when you have the real error message.
    I created a user and a system trace file; used the whole morning going thru the thousands of lines and I did not find anything that would explain the parse error.

    I ran the transaction with debugger and I got these variables:

    MRM
    MTS_HEADER ADD-COMMENT2013031400000002
    MTS_HEADER \r\n130314000001This is a comment 1
    MTS_HEADER \r\n130314000002This is a comment 2
    ImbRecoverableException caught from worker->parseNext.

    it should be
    MRM
    MTS_HEADER ADD-COMMENT2013031400000002
    MTS_HEADER 130314000001This is a comment 1
    MTS_HEADER 130314000002This is a comment 2

    the CR/LF(\r\n) is appearing in the record and moving the content to the right.

    how do I define the message set to not consider CR/LF?
  • SystemAdmin
    SystemAdmin
    4179 Posts

    Re: ImbRecoverableException caught from worker->parseNext

    ‏2013-03-20T19:16:50Z  
    I created a user and a system trace file; used the whole morning going thru the thousands of lines and I did not find anything that would explain the parse error.

    I ran the transaction with debugger and I got these variables:

    MRM
    MTS_HEADER ADD-COMMENT2013031400000002
    MTS_HEADER \r\n130314000001This is a comment 1
    MTS_HEADER \r\n130314000002This is a comment 2
    ImbRecoverableException caught from worker->parseNext.

    it should be
    MRM
    MTS_HEADER ADD-COMMENT2013031400000002
    MTS_HEADER 130314000001This is a comment 1
    MTS_HEADER 130314000002This is a comment 2

    the CR/LF(\r\n) is appearing in the record and moving the content to the right.

    how do I define the message set to not consider CR/LF?
    The tabs did not appear in my reply; I had to edit it to show how it appeared:

    MRM
    MTS_HEADER ADD-COMMENT2013031400000002
    MTS_HEADER \r\n130314000001This is a comment 1
    MTS_HEADER \r\n130314000002This is a comment 2