Re: Character differences between WDSC and SEU

Thanks for the reply Chuck.

The DSPPFM of the source member is as shown below:
*...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8....+....9....+....0....+....1..
00020110030505436H Indent('|')
FFFFFFFFFFFFFFFFFC4C9889A474754444444444444444444444444444444444444444444444444444444444444444444444444444444444
0002011003050543680954553DDFDD0000000000000000000000000000000000000000000000000000000000000000000000000000000000

and the CCSID of the source file is:
Coded character set identifier . . . . . . : CCSID 500

Any thoughts?


----- Message from CRPence <CRPbottle@xxxxxxxxx> on Thu, 04 Mar 2010
12:08:30 -0800 -----
To:
wdsci-l@xxxxxxxxxxxx
Subject:
Re: [WDSCI-L] Character differences between WDSC and SEU
The issue may be on the server versus the client. Is so, ...

Which glyph [i.e. the visible "character"] is presented by STRSEU
is not of very much interest. What is the hex code point of the
character, and what is the CCSID of the file [or CCSID of the SRCDTA
field]? The DSPPFM allows viewing the actual hex code point; use
the F10=Hex, then F11=Over\Under, and then read & record the hex
digits top-down, directly under the character which presumably is,
like with STRSEU, displayed as '|'.

Regards, Chuck

mgarrison@xxxxxxxxxx wrote:

When I am using SEU a source member has the keyword INDENT('|')
on the H spec and when I bring up the same source member in WDSC
it shows the H spec keyword as INDENT('!'). What preference can I
set in WDSC to show the keyword correctly?