IBM Support

JR53253: THE CHECKSUM STAGE PRODUCED A DIFFERENT CHECKSUM NUMBER WHEN SCHEDULED FROM DIRECTOR USING EVERY OR DAILY OPTIONS.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • With the same input data, the checksum stage produced a
    different checksum number when scheduled from Director using
    Every or Daily options.
    

Local fix

  • NA
    

Problem summary

  • ERROR DESCRIPTION:
    With the same input data, the checksum stage produced a
    different checksum number when scheduled from Director using
    Every or Daily options.
    
    LOCAL FIX:
    NA
    

Problem conclusion

  • This problem only occurred when the record being checked had
    null column values.  A patch is available which corrects the
    issue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR53253

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    912

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-05-05

  • Closed date

    2015-07-20

  • Last modified date

    2015-07-20

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

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

Fix information

  • Fixed component name

    WIS DATASTAGE

  • Fixed component ID

    5724Q36DS

Applicable component levels

  • R850 PSY

       UP

  • R910 PSY

       UP

  • RB30 PSY

       UP

  • RB31 PSY

       UP

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

Document Information

Modified date:
07 January 2022