Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Future consideration
Workspace App Connect
Created by Guest
Created on Feb 12, 2015

dfdl:testBit() function implementation

Visa Europe use a customised form of ISO8583, in which one of the fields , named Tag, is currently length 1. There is an urgent requirement where the field can be either 1, 2 or 3 bytes long, which can be achieved by using a choice and discriminators. The field is longer than one if bits 4-8 of the first byte are all on, so the discriminator can be easily written using the dfdl:testBit() function, but unfortunately it is not implemented.

Idea priority Urgent
RFE ID 66281
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Reply
    |
    Feb 2, 2021

    RFE Review. Apologies for the length of time this RFE has been held in Uncommitted Candidate status. Although this enhancement idea has only received a single vote since 2015, we wish to preserve the RFE as rounding out further elements of the DFDL specification, including testBit, remains on our long-term radar. We continue to document these areas on this page of the KC: https://www.ibm.com/support/knowledgecenter/en/SSTTDS_11.0.0/com.ibm.etools.mft.doc/df00150_.html

    Status of the RFE is maintained as Uncommitted Candidate.

  • Guest
    Reply
    |
    Oct 7, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

  • Guest
    Reply
    |
    Feb 20, 2015

    Having thought about it a bit more, the workaround in my previous comment does not work. Having decided it is not a 1 byte field, the target is now 2 bytes long, so testing for x'7F' will not work. We need to test for bit 9 in the two bytes field. Unfortunately, the fn:substring function cannot be used as it only takes a string data type. Therefore the implementation of this RFE is very important for the customer.

  • Guest
    Reply
    |
    Feb 19, 2015

    ok, there is a workaround for the length 3 case, use
    discriminator test="{. le xs:hexBinary('7F')}

  • Guest
    Reply
    |
    Feb 18, 2015

    Yes, I agree with the workaround, which is good for now, as it has allowed me to code a discriminator for the case when there is a choice of length 1 and length 2 Tags.
    However, in the very near future we will be asked to implement a length 3 tag as well in the choice, and the condition for this is : once we worked out it is not length one, i.e. bits 4 to 8 of the first byte are all on ( use the workaround for this ), then if the first bit of the 2nd byte is on, the tag is length 3. The possible combinations for this is 2 to the power of 7, and using the wrokaround would make the discriminator bigger than the rest of the xsd, that's the reason I raised this as urgent.

  • Guest
    Reply
    |
    Feb 13, 2015

    Thank you for raising this requirement. I understand from Steve Hanson that you have discussed the particular ISO8583 use case which you are faced with, and can use a choice with 8 options (8 possibilities, with varying values for bits 1,2 and 3 yet each of which has bits 4-8 all set on) to workaround this issue and continue to use the ISO8583 DFDL model. This said, we agree that the addition of a testBit function to DFDL would be a good enhancement for the product. Status of this RFE is updated to Uncommitted Candidate.