This flag is for backwards compatibility. Some may experience problems with database-driven widgets with Profound UI Version 5, Fix Pack 8.0 and later when a data source uses derived fields with character concatenation.
Before Profound UI Version 5, Fix Pack 8.0, database-driven widgets read from the database in EBCDIC before sending the response back to the browser. To support more character sets, Profound UI was changed to read from the database in Unicode.
This configuration option helps when all of the following are true:
- The Profound UI installation was upgraded from a level prior to Version 5, Fix Pack 8.0 to a version after Version 5, Fix Pack 10.2.1
- Database-driven widgets fail to show data after upgrading.
- There is an error in the job log or network response: "Character conversion between CCSID 1208 and CCSID 65535 not valid."
- Changing the view or display file is not reasonable.2
Where do you save this configuration option? Here.
1 This configuration option is available with versions after Profound UI Version 5, Fix Pack 10.1. Thus, if Profound UI was upgraded to Fix Pack levels 9.0, 9.1, 10.0, or 10.1 of Version 5, then Tech Support must provide a patch in order to use this option.
2 When an SQL view uses derived character fields, then the CCSID of the field is sometimes 65535; hence, the DB-driven widget fails. Casting the character field with the CCSID parameter is one way to fix the problem. For example, even though the underlying fields have CCSID of 37, the following clause has a CCSID of 65535:
FRSTNAME || ' ' || LASTNAME
Since each field is 30 characters in length, this clause explicitly sets the CCSID so that the DB-driven widget works:
CAST ( FRSTNAME || ' ' || LASTNAME AS CHAR ( 61 ) CCSID 37 )
The CCSID of a field in a view can be found using the command line program, DSPFFD: