IBM Support

JR58664: PARALLEL ENGINE SORT STAGE ON WINDOWS CAN CREATE BAD SORATCH FILE NAMES WHEN USING MULTIBYTE CHARSETS.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • The PX Tsort operator creates and deletes scratch files at
    runtime. It generates unique filenames
     based on the pathname  of the scratch directory, process
    (or thread) number, and a random number. On busy Windows systems
     which are using multibyte character sets, customers have
    observed scratch file names which contain invalid unicode
    characters.
     This led to error messages like:
     APT_CombinedOperatorController,0: Invalid character(s)
    ([xFFFD]) found converting Unicode string (code point:
    C:/TMP/scratch/tsortG6bOSPC[xFFFD]_20170214130147.779000_7840_13
    9430872) to codepage ibm-943_P15A-2003
    

Local fix

Problem summary

  • The PX Tsort operator creates and deletes scratch files at
    runtime. It generates unique filenames
     based on the name of the scratch directory, process (or
    thread) number, and a random number. On busy Windows systems
     which are using multibyte character sets, customers have
    observed scratch file names which contain invalid unicode
    characters.
     This led to error messages like:
     APT_CombinedOperatorController,0: Invalid character(s)
    ([xFFFD]) found converting Unicode string (code point:
    C:/TMP/scratch/tsortG6bOSPC[xFFFD]_20170214130147.779000_7840_13
    9430872) to codepage ibm-943_P15A-2003, substituting.
    

Problem conclusion

  • The scratch file generation code was changed to use character
    conversion routine instead of type casting when creating the
    file name.
    Patches are available which fix the problem.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR58664

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    912

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-11-01

  • Closed date

    2017-11-21

  • Last modified date

    2017-11-21

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

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

Modules/Macros

  •    None
    SERVER
    

Fix information

  • Fixed component name

    WIS DATASTAGE

  • Fixed component ID

    5724Q36DS

Applicable component levels

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

Document Information

Modified date:
21 November 2017