Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace PL/I Compilers
Created by Guest
Created on Oct 31, 2018

XMLCHAR Builtin function to support DBCS

Enhance XMLCHAR PL/I built-in function, to support the DBCS characters. Today it supports only Single byte Alphanumeric, numeric, decimals and String values.

Idea priority Urgent
  • Guest
    Reply
    |
    Dec 8, 2020

    his requirement has been re-assessed.  It is not likely that this will be implemented in the next 12-24 months and so it is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then. 

    But perhaps a requirement should be opened to allow DBCS in the XMLUCHAR function? (that generates XML as UTF-8)

  • Guest
    Reply
    |
    Jan 14, 2020

    Hi Team, can someone help with the status of this request please..

  • Guest
    Reply
    |
    Aug 29, 2019

    Team, any more questions on my request ? We would need PL/1 to be flexible for handling DBCS characters also during XMLCHAR function execution.. This is much in demand.. Please try to have a look at this.. Thanks

  • Guest
    Reply
    |
    Apr 16, 2019

    #1. No plans for having XML data element names as DBCS in near future as well.
    #2. DBCS data stored within the PL1 character variable has to be supported in XMLCHAR function.
    For our scenario, we have declared the variable as datatype CHAR, do you think I need to declare it as GRAPHIC? and is GRAPHIC data type is supported in XMLCHAR function ?
    Data has to be written to the buffer along with the shift-in & shift-out codes, which helps identifying DBCS.

    In our case,
    #1.Actual DBCS data ==> 静岡県静岡市葵区紺屋町17‐1
    #2.I believe PL1 read the single byte Hex value of it, and recognized it like this ==> ・」、シ、ェ・」、シ、ォ&R、ャ<]、Z、ュ。1。7」!。1

    #3.After applying XMLCHAR function, the data is formatted within tags like this ==> ・」、シ、ェ・」、シ、ォ&R、ャ<]、Z、ュ。1。7」!。1
    ==> You can see < symbol from the #2 is replaced with < in #3 after applying XMLCHAR. probably PL1 see it as a special character.

    Fixing this would help our application to achieve lot many things in PL1.

  • Guest
    Reply
    |
    Dec 18, 2018

    We're tentatively accepting this until we get an answer to our earlier questions

  • Guest
    Reply
    |
    Nov 19, 2018

    Is the requirement for 1) that data element names in DBCS are supported or 2) that DBCS data be supported? or both?

    Another way to ask 2) would be to ask if structure elements with the GRAPHIC attribute are to be supported?

    For 2) should the data simply be written to the buffer? or should the data be enclosed in shift-codes?