IBM Support

JR31866: ABILITY TO HANDLE THE UNEXPECTED CHARACTERS SUCH AS A0 IN THE XML STAGE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as requirement.

Error description

  • Currently the xml stage silently drops records with unexpected
    character in the 801 code.
    
    
    Here is what the customer was expecting. When they saw the
    unexpected characters, they expected this was probably a FATAL
    message.
    
    Now if we go by the transfromation error mapping they have
    chosen in the job. They have specfied FATAL -- > REJECT , Error
    -- REJECT . Warning --> Default
    
    
    Now here are 2 things to consider.
    
    1. Was the data with unexpected character logged as Fatal, Error
    or warning level in the XML transformation? If it were either of
    the above then clearly we have a broken code here, because
    datastage did not send it to the reject link. Unless Reject
    means to silently drop the record and continue processing . This
    needs to be investigated
    
    
    2. What does datastage do for different levels of errors.
    
    
    a. DROP --> The customer is expecting this to be default
    behaviour in case no reject is specified. They are expecting us
    to drop the the invalid row, log informational / warning
    message  and continue with processing. Shouldn't our code be
    working this way in 801 similar to previous 75x releases ?
    Please verify this, If not we have to see if this can be
    enhanced.
    
    b. Fail / FATAL --> We have to verify if by specifying FATAL the
    the job is actually aborting for all 3 levels of transfrmation
    errors ( FATAL , ERROR, WARNING). If not this has to be fixed.
    
    c. REJECT --> To me it appears they are expecting this to work
    very similar to a DROP , except that the bad record will log a
    message, send the invalid row  to reject link and continue
    processsing. This however did not seem to happen in their case
    for unexpected data
    

Local fix

  • This fix is included in 8.0.1 fix pack 3
    

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR31866

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    800

  • Status

    CLOSED REQ

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-01-30

  • Closed date

    2009-02-09

  • Last modified date

    2010-12-09

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

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

Fix information

Applicable component levels

[{"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.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
09 December 2010