Page 1 of 1

Unicode Data Fields not supported by Converter?

Posted: Mon Aug 23, 2010 5:59 am
by t.s.h
When I convert a DDS File with the following field definition:

Code: Select all

A            WBDESC        40G  O  6 15CCSID(1200 20) 
the converter generates a char field:

Code: Select all

{"i-d":"WBDESC","field type":"output field","value":{"fieldName":"WBDESC","designValue":"[WBDESC]","dataType"
:"char","formatting":"Text","trimLeading":"false","trimTrailing":"true","textTransform":"none","dataLengt
h":"40"} 
and

Code: Select all

WBDESC         40A  H  
this cause an error during the creation of the rpg program.
Is there a workaround to use unicode fields?

Re: Unicode Data Fields not supported by Converter?

Posted: Tue Aug 24, 2010 8:44 am
by t.s.h
edit:
With some manual work I get the DDS-source and prg working
I set a referecnce in the designer to a unicode file field and changed the field definition in

Code: Select all

A          R MS5010FB                  SFL    
A  61 62     QPUI000001     1A  O  2  2        
A  61 62     WBDESC        40G     2  4CCSID(1200 20)     
but than I receive the following error code during execution:

Code: Select all

Nachrichten-ID . . . . :   PUI0013       Bewertung  . . . . . . :   40        
Nachrichtenart . . . . :   Abbruch                                            
Sendedatum . . . . . . :   24.08.10      Sendezeit  . . . . . . :   14:36:26  
                                                                              
Nachricht . . . :   Unsupported data type.                                    
Cause . . . . . :   An attempt was made to open file MS5010FM in library *LIBL
  which contains one or more fields of unsupported type.                      
Recovery  . . . :   Contact the person responsible for program maintenance to 
  determine the cause of the problem.                                         

Re: Unicode Data Fields not supported by Converter?

Posted: Tue Aug 31, 2010 8:39 am
by David
Unicode fields are not supported in Profound UI at this time. We may add support for these in a future release.