Professional Documents
Culture Documents
Unicode Overview:
1. Run transaction UCCHECK for a set of input custom programs. Locate the problematic lines in the programs. 2. Find out one program for which the onl Unicode error is !Unicode chec"s acti#e$ flags not chec"ed in program attributes %this can be achie#ed b gi#ing all custom programs as input and going through the errors&. Use the button on application toolbar to set the Unicode flag for this program and then correct all errors. '. "r$e/%alse: a. Unicode character set contains almost all the characters used worldwide. b. UCCHECK reports the all the s nta( errors in an )*)+ program. c. )ll search helps must be using matchcode ,-s in a Unicode s stem. d. ,n a Unicode s stem. a program can be e(ecuted without the !Unicode chec"s )cti#e$ flag being chec"ed. e. /apping of Unicode characters for 0)+ characters can be seen in table 1122. f. UCCHECK predicts the runtime problems for an )*)+ program in a Unicode s stem. 3. %ill in &e 'lan(s: a. 0)+ s stems must be upgraded to a 4444444444 s stem first before it is con#erted to a Unicode s stem. b. Upgrade from 5on Unicode to Unicode s stem in#ol#es changes in 44444444. 44444444. 44444444. 44444444 and 44444444. c. +rogram 44444444 chec"s the s stem for /atchcode ,-s. d. ,n a standard set6up. a 0)+ s stem can run in on one 44444444 at a time.
+age 1
/arch 2227
+age 2
/arch 2227