webMethods

webMethods

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

Problems with flat file parsing by default record

  • 1.  Problems with flat file parsing by default record

    Posted Fri January 11, 2013 05:12 PM

    Hello folks,

    we are trying to create a simple flat file with all rows following the same record definition. Therefore we don’t see the need for a record identifier. But if we create the flat file content without record identifiers, parsing the content results in an exception.

    To be more specific:

    We have a record definition looking like this:
    Record-identifier: I
    Field1 Extractor: 1-11
    Field2 Extractor: 11-21
    Field3 Extractor: 21-31

    This is defined in a dictionary and used as record reference in a flat file schema using newline as record delimiter (we also tested carriage return line feed). There is no other record definition referenced or defined in this schema.

    The flat file content then looks like this:
    IField1cont Field2cont Field3cont

    This is parsed correctly into a document with three fields containing Field1cont, Field2cont, and Field3cont

    Now if we are going to use this flat file without the record identifier, we have a content like
    Field1cont Field2cont Field3cont

    We push all field extractors left in the record definition so the fields are expected at 0-10, 10-20 and 20-30. Then we set this record definition as Default Record for the flat file schema. When testing the schema with the afroementioned content we receive a “Found no valid records” error.

    There must be something very simple and basic missing, but I can’t find anything in the documentation.

    Greetz
    Jochen


    #Flow-and-Java-services
    #Integration-Server-and-ESB
    #webMethods


  • 2.  RE: Problems with flat file parsing by default record

    Posted Mon January 14, 2013 05:01 PM

    Hi,

    After making the change (We push all field extractors left in the record definition so the fields are expected at 0-10, 10-20 and 20-30) …Did you create the SDT Schema document type…


    #Integration-Server-and-ESB
    #Flow-and-Java-services
    #webMethods