IBM Support

JR58272: SUPPORT UNIVARCHAR/UNICHAR DATATYPES FOR SYBASE ASE IN SYBASE ENTERPRISE STAGE.

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

  • In Sybase Enterprise stage add support to read/write to Sybase
    ASE containing univarchar/unichar datatype.
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users using Sybase Operator to read/write from Sybase ASE using
    datatype unichar / univarchar
    ****************************************************************
    PROBLEM DESCRIPTION:
    Support for use of unichar / univarchar datatypes in Sybase
    Operator for Sybase ASE
    ****************************************************************
    RECOMMENDATION:
    Apply the patch to use the tables containing unichar /
    univarchar in Sybase ASE.
    
    ****************************************************************
    

Problem conclusion

  • No new datatypes have been added to stage properties.
    
    When there are unichar/univarchar columns, they need to be
    mapped to either char with Unicode, NChar, Varchar with Unicode,
    NVarchar.
    
     ASERead -->
     1.sybase datatype unichar can be mapped to Char with Unicode or
    NChar
     2.sybase datatype univarchar can be mapped to Varchar with
    Unicode or NVarchar
    
     ASEWrite -->
     1. sybase datatype unichar can be mapped to Char with Unicode
    or NChar
     2. sybase datatype univarchar can be mapped to Varchar with
    Unicode or NVarchar
    
     ASEUpsert -->
     1. sybase datatype unichar can be mapped to char and length
    shouldn't be specified
     2. sybase datatype univarchar can be mapped to varchar and
    length shouldn't be specified
    
     Unicode characters can be read from and inserted to tables
    containing unichar/univarchar datatypes. However we cannot
    create new tables from Sybase EE with unichar/univarchar
    columns.
    
     In case of ASE Upsert, the Unicode characters can only be
    inserted based on the Sybase server charset and locale that is
    available.
     For example, Japanese characters can be inserted from Sybase EE
    stage only if the corresponding charset is available on the
    Sybase server.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR58272

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    B30

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-08-09

  • Closed date

    2017-11-02

  • Last modified date

    2017-11-02

  • 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

  • RB31 PSY

       UP

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

Document Information

Modified date:
02 November 2017