IBM Support

JR42936: Import of IBM hex float data requires setting Native Endian as byte order to work on Little Endian platforms.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Import of IBM hex float data requires setting Native Endian
    as byte order to work on Little Endian platforms.
    
    
    
    
    There is a restriction in PxEngine in importing IBM hex float
    column:
    The Byte Order property must be set to Native endian.
    Native endian means using the machine's default endian.
    On Linux and window it will use default little endian to read
    IBM hex float.
    However, IBM mainframe data contains IBM hex float column is in
    Big endian format.
    If Native endian is selected the value imported for BINARY
    columns (integer) will be
    wrong since it is in big endian format for IBM maiframe data,
    including PLI data
    used by the customer.
    
       This APAR is really the completion of   APAR JR40573, "DS job
    does not read PL/I copybook correctly - EBCDIC binary format -
    float data type  " .
    The patch for that APAR shipped  and was included in 8.7 Fixpack
    1. APAR JR40537 the import of the IBM hex floating
    point format data work, but it was later discovered that the
    import
    would only work if the Edianness of the the machine running the
    import was Big Endian (the same Endianess as IBM Mainframe) .
    

Local fix

Problem summary

  • The original PxEngine code that handles IBM hex float requires
    that the Byte Order must be set to Native Endian.  This is not
    correct and causing error in converting Integer columns if the
    machine that handles IBM hex float is a Little Endian machine.
    This is caused by that the data that contains IBM hex float
    downloaded from Mainframe machine is in Big Endian format.
    

Problem conclusion

  • To fix this issue Byte Order restriction using Native Endian
    for IBM hex float is removed so that user can select the Byte
    Order based on the data format.  The new behavior is that when
    Big Endian is selected as Byte Order no runtime error message is
    displayed and Integer columns will be converted correctly.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR42936

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-05-25

  • Closed date

    2012-07-09

  • Last modified date

    2013-01-14

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • 1
    

Fix information

  • Fixed component name

    WIS DATASTAGE

  • Fixed component ID

    5724Q36DS

Applicable component levels

  • R810 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
14 January 2013