IBM Support

PM19001: EZYXW12W (BADVALUE) MESSAGE WHEN COLOR SPECIFIED AS RGB VALUE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An application using the XWindows APIs can specify a color value
    to be used for some objects, and will retrieve some basic color
    configurations (such as background) from the server system
    (workstation).  The value can be specified as either a name or a
    hex RGB value.  If the RGB form is used and any part of the hex
    value is specified using upper case letters, the API will treat
    the value as a name instead of the intended RGB specification.
    This will result in a message similar to the following:
    
    EZYXW12W XtlibWarning:  badValue cvtStringToPixel XtToolkitError
          Color name "#AEAEB2B2C3C3" is not defined
    

Local fix

  • Use lower case characters in any RGB specifications.  For the
    above example, this would be #aeaeb2b2c3c3.
    
    
    Related info:
    II13291
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the IBM Communications Server   *
    *                 for z/OS Version 1 Release(s) 10, 11 and 12  *
    *                 IP: X Windows X11R66                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Running an X11 java application using   *
    *                      RGB hexadecimal values to specify       *
    *                      colors for objects, the application     *
    *                      can receive the following message:      *
    *                                                              *
    *                        EZYXW12W XtlibWarning: badValue       *
    *                          cvtStringToPixel XtToolkitError     *
    *                          Color name "#AEAEB2B2C3C3" is not   *
    *                          defined                             *
    *                                                              *
    *                      This occurs when the RGB value is       *
    *                      specified in upper case hexadecimal     *
    *                      EBCDIC.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An application using the X Windows APIs can specify a color
    value to be used for some objects, and will retrieve basic
    color configurations (such as background) from the server
    system (workstation).  The value can be specified as either a
    name or a hexadecimal RGB value.
    
    If the RGB form is used and any part of the hexadecimal value
    is specified using upper case EBCDIC letters, the API will
    treat the value as a name instead of the intended RGB
    specification.
    
    This occurs because X Windows does not consider that the RGB
    value can be EBCDIC. So the case conversion routine in cmsColNm
    converts the value as if it is ASCII, resulting in the following
    message:
    
    EZYXW12W XtlibWarning:  badValue cvtStringToPixel XtToolkitError
             Color name "#AEAEB2B2C3C3" is not defined
    
    KEYWORD: XWINDOWS
    +-------------------------------------------------------------+
    + Please check our Communications Server for OS/390 homepages +
    + for common networking tips and fixes.  The URL for these    +
    + homepages can be found in Informational APAR II11334.       +
    +-------------------------------------------------------------+
    

Problem conclusion

  • To resolve these problems, the following changes have been
    made:
    
    1. The X Windows case conversion code (X11R66 level),cmsColNm,
       has been modified to correctly convert EBCDIC hexadecimal
       RGB values to lower case.
    
    2. The following have been recompiled to include the changes:
         EZYDX113 EZYDX116 EZYAX11
    
    * Cross Reference between External and Internal Names
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM19001

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    1B0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2010-07-23

  • Closed date

    2010-10-15

  • Last modified date

    2011-01-03

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

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

    UK61517 UK61518 UK61519

Modules/Macros

  • EZYAX11  EZYDX113 EZYDX116
    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R1A0 PSY UK61517

       UP10/12/08 P F012

  • R1B0 PSY UK61518

       UP10/12/08 P F012

  • R1C0 PSY UK61519

       UP10/12/08 P F012

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1B0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"DO NOT USE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1B0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 January 2011