IBM Support

IC81453: ERROR "79784 LOCALE NOT SUPPORTED" WHEN LOADING A JAR WITH PL_PL.MAZOVIA LOCALE

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

  • Even though the locale (pl_pl.Mazovia) exists, the engine is not
    able to load a java UDR with the locale set and returns the
    following error msg:
    
    (79784) - Locale not supported.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Customers that want to extend the default Java Charsets with *
    * a custom CharsetProvider                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * For this defect customer has developed its own               *
    * CharsetProvider. Java allows customers to extend the default *
    * character sets by placing a jar file with CharsetProvider in *
    * $JRE/lib/ext directory.                                      *
    *                                                              *
    * In this case, customer was trying to user their Mazovia.jar  *
    * Charset provider by putting it in                            *
    * $INFORMIXDIR/extend/krakatoa/jre/lib/ext, but they were      *
    * getting "locale not supported" error. The reason for this is *
    * because, we have hardcoded the list of GLS codesets, with    *
    * their corresponding Java Charset names.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to IDS.11.50.xC10                                    *
    ****************************************************************
    

Problem conclusion

  • Fix was to allow customer to use the custom CharsetProvider. The
    way the fix works is that after we have already checked that the
    codeset is not supported (in our static mapping), then I do a
    dynamic check to see if the Java Runtime actually supports the
    codeset or not. If the JRE happens to support the codeset, then
    no error is returned.
    
    Upgrade to IDS.11.50.xC10
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC81453

  • Reported component name

    INFORMIX SERVER

  • Reported component ID

    5725A3900

  • Reported release

    B50

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-02-15

  • Closed date

    2017-06-15

  • Last modified date

    2017-06-15

  • 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

    INFORMIX SERVER

  • Fixed component ID

    5725A3900

Applicable component levels

  • RB50 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSGU8G","label":"Informix Servers"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B50","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 June 2017