I do not understand why the RDp Screen designer is not able to handle unicode fields correct.
A DDS field definition like this:
A WSINF2 100G O 10 4
A CCSID(1200 50)
is displayed like this: (no difference to the "old" SDA)
is this my fault or is the screen designer still unable to handle real unicode fields?
perhaps somone could help me....
This topic has been locked.
4 replies Latest Post - 2012-09-24T15:05:11Z by e.m.
Pinned topic RDp Screen Designer still not able to handle unicode?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-09-24T15:05:11Z at 2012-09-24T15:05:11Z by e.m.
Re: RDp Screen Designer still not able to handle unicode?2010-08-20T11:03:12Z in response to SystemAdminScreen Designer does support G type fields without the CCSID keyword as "pure DBCS" fields containing double byte data without shift characters.
However, if I understand your scenario correctly, you are using the CCSID keyword to specify a display width of 50 for the 100 bytes of unicode data.
Screen Designer does not interpret the CCSID keyword for either encoding or display purposes. This is an enhancement request that I can enter on your behalf.
If anyone else is hitting this problem, please post here, so that we can properly prioritize this enhancement against our limited resources.
Re: RDp Screen Designer still not able to handle unicode?2010-08-24T13:46:53Z in response to SystemAdminThanks for your answer and yes you got me right.
Perhaps you could set it on your "nice to have" list.
Until it works correct, we use the old way and design the screens by hand. :(
RolandM 2700016D271 PostACCEPTED ANSWER
Re: RDp Screen Designer still not able to handle unicode?2012-08-22T16:50:50Z in response to SystemAdminHi,
I opened a PMR concerning this issue. IBM des not see this as a bug as the CCSID never was supported in the screendesigner. The asked me to open an RFE and/or post a message to this thread.
This is what I posted to the PMR:
"Unfortunately, these statements are unsatisfactory. Specifying CCSID as
a keyword for a display box with the use of *MIN or *LEN is nothing
When replacing RDP PDM and SDU is, the screen designer to be at least as
good - not bad!
I don't see this as an RFE but clearly as a bug. The PTFs listed in the
request for OS400 had solved the same problem, but only for the compiler
(Talking about the following PTFs
V5R4 -- SI43089
V6R1 -- SI43090
V7R1 -- SI43091