IBM Sterling Transformation Extender

Sterling Transformation Extender

Come for answers, stay for best practices. All we're missing is you.


#Sterling
#Supplychain
 View Only
  • 1.  BINARY text ITEM

    Posted 02/14/07 06:50 PM

    Originally posted by: SystemAdmin


    I am converting Mercator v6.5 to DSTX v8.0.1.1 and came accross a problem with an MQ tree.

    In v6.5 I analyze the tree and it returns 2 Warnings and 0 Errors.
    In v8.0.1.1, I analyze, the tree returns 5 Warnings and 6 Errors.

    Error:
    L190 - BINARY text ITEM used as COMPONENT neither FIXED nor SIZED
    - COMPONENT 18 of TYPE 'MessageDescriptor Header MQSeries' (error)

    The item is defined as a Binary Text Item, Min size 0, Max size 32.
    The MessageDescriptor Header Group is defined with Sequence subclass, Implicit Format.

    Any ideas? I just ran accross this issue so I haven't had a chance to investigate further.

    Thank you.
    #IBMSterlingTransformationExtender
    #DataExchange
    #IBM-Websphere-Transformation-Extender


  • 2.  Re: BINARY text ITEM

    Posted 02/15/07 01:42 PM

    Originally posted by: DDDD_123


    Hello MercatorMan:

    Please change the properties like this.

    Min: 32
    Max: 32

    and analyze the type tree.

    Thx.
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender
    #DataExchange


  • 3.  Re: BINARY text ITEM

    Posted 02/15/07 01:46 PM

    Originally posted by: DDDD_123


    In addition to the my previous reply,

    You have to change one more BINARY text ITEM field like this.

    Min: 24
    Max: 24

    analyze the type tree. Hope this helps.

    Thx.
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender
    #DataExchange


  • 4.  Re: BINARY text ITEM

    Posted 02/16/07 01:18 PM

    Originally posted by: SystemAdmin


    That's what I needed, thank you.
    #IBMSterlingTransformationExtender
    #DataExchange
    #IBM-Websphere-Transformation-Extender


  • 5.  Re: BINARY text ITEM

    Posted 02/19/07 09:37 PM

    Originally posted by: SystemAdmin


    Just FYI. Binary data is required to be sized or of a fixed size. So, you either had to set up your tree to pad to the length of the item, have the min and max match so it is "sized", or have the group in which this item resides for the sizing on the item.

    In v6.5 this rule was not enforced. It is in v8.x. This is why you see the difference between the two versions.

    Yvonne
    Resistance is NOT futile.
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender
    #DataExchange