App Connect

 View Only
Expand all | Collapse all

ISO Bitmap Conversion

  • 1.  ISO Bitmap Conversion

    Posted Thu September 02, 2021 02:23 PM
    Hi Team,

    We are using ISO8583 library that provided in Help Section of App Connect.

    For testing the ISO DFDL Parser, We are using sample ISO Message specified by IBM on github.

    In the sample ISO Message given by IBM, BitMap is present in different format. But DFDL Parser able to parse the sample ISO Message.

    But If we generate ISO Message by our own its not working as expected. Bitmap string is different from generated one and the sample one
    provided by IBM

    Can some one please help me to understand the bitmap format of the sample iso message provided by IBM.

    Is there any reference or documentation is available for generating the similar kind of ISO Message?

    Currently we have no clue how that ISO is generated and which format bitmap is encoded , etc




    ------------------------------
    SELVAKUMAR ANANTHARAJ
    ------------------------------


  • 2.  RE: ISO Bitmap Conversion

    Posted Thu September 02, 2021 05:34 PM

    Without having your data, I cannot be certain.  My guess is the endianness of the generated message differs from the sample.  The endianness is the byte order.  While this normally applies to multi-byte characters like UTF-8, it is possible for byte wise data to be similarly impacted.

    As stated here: https://www.ibm.com/docs/en/app-connect/11.0.0?topic=formats-iso8583-messaging-standard, the Bitmap is :

    A message always includes a primary bitmap whose individual bits indicate which of the later fields are present in this particular message instance. The primary bitmap specifies whether fields 1 - 64 are present. If a secondary bitmap is also included, it specifies whether fields 65 - 128 exist. The standard also provides for a tertiary bitmap, which is rarely used. The bitmaps can appear in 8-byte 'packed' format or 16-byte 'unpacked' format.

    If you are using the unpacked form, then the endianness could be swapping the bytes.

    Other than the information on Github, we do not have additional information on how the model or data was generated.  These were posted 6-7 years ago, so we may not have that information.  I did notify the author in case he wants to add more detail.

    If you need assistance with this, please open a case and provide your sample message and error.



    ------------------------------
    MATTHEW SEGALL
    ------------------------------

    Original Message