Kbase P139006: 4GL/ABL: Errors (87) and (143) running CHUI client that modifies a field FORMAT in Unicode mode.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/16/2009 |
|
Status: Verified
SYMPTOM(s):
4GL/ABL: Errors (87) and (143) running CHUI client that modifies a field FORMAT in Unicode mode.
** Input value: should be yes
o. (87)
** tst1.p: Unable to evaluate field for assignment. (143)
The tst1.out output file contains the above errors if the CHUI batch client is started with the -cpinternal utf-8 client session startup parameter.
Using the SET or UPDATE statements to read input from a file where the input field contains the "skip" character ("-"), the ABL client faisl to correctly handle the data if the -cpinternal UTF-8 session startup parameter is used.
Running the following code in a batch 4GL Character client process:
DEFINE VARIABLE C1 AS CHARACTER NO-UNDO.
DEFINE VARIABLE C2 AS CHARACTER NO-UNDO.
DEFINE VARIABLE L1 AS CHARACTER NO-UNDO.
DEFINE VARIABLE H1 AS HANDLE NO-UNDO.
INPUT FROM tst1.txt.
OUTPUT TO tst1.out.
FORM C1 L1 C2 WITH FRAME F1.
ASSIGN
H1 = L1:HANDLE
H1:FORMAT = "yes
o"
H1:LABEL = "Testing 1234".
SET C1 L1 C2 WITH FRAME F1.
INPUT CLOSE.
OUTPUT CLOSE.
Where tst1.txt has the following data:
- - -
The session is started using a command similar to one of the following:
pro -b -p tst1.p -cpinternal utf-8
pro -b -p tst1.p -cpinternal utf-8 -cpstream utf-8
pro -b -p tst1.p -cpinternal utf-8 -cpstream utf-8 -ucc
FACT(s) (Environment):
No errors are generated when the TTY batch 4GL session is started without the -cpinternal utf-8 client session startup parameter. For example, the client does not generate any errors when using one of the following startup commands:
pro -b -p tst1.p
pro -b -p tst1.p -cpstream utf-8
pro -b -p tst1.p -cpstream utf-8 -ucc
All Supported Operating Systems
Progress 9.1E
OpenEdge 10.1B
OpenEdge 10.1C
OpenEdge 10.2A
CAUSE:
Bug# OE00179233
FIX:
Upgrade to OpenEdge 10.1C04 or later.