Re: Permanent I/O Error occured to DSPF

Ok,

I added some code to '-' fill the fields but I still get the same error.

I'm not sure rather to feel better or worse...but apparently the x'00'
fill of the field was in keeping with the specs. Of course, now I'm
back to were I started....

Charles

On Mon, Oct 13, 2008 at 10:27 AM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

Ok this makes no sense at all.

I've narrowed down the problem field to a char(15) in my subfile grid.

If the field is full of text, there's no issue. However, if the field
isn't full of text, the trailing spaces get replaced by x'00'. For
my last set of tests, I was able to get the last record loaded to the
subfile to contain a "short" name so that you can see what's in there
in the dump:

S000IV CHAR(15) 'TALBOTS INC. '
VALUE IN HEX 'E3C1D3C2D6E3E240C9D5C34B404040'X

But here's the IBM 5250 Trace:
TALBOTS INC....
ecdcdee4cdc4000
31326320953b000

And here's the PowerTerm Trace:
0EA0: 20 00 0F E3 C1 D3 C2 D6 E3 E2 40 C9 D5 C3 4B 00 |...TALBOTS INC..|
0EB0: 00 00 20 11 18 54 1D 60 20 20 00 01 00 20 11 18 |.....è.-........|

**Both traces show "TALBOTS INC" followed by three x'00' instead of three x'40'

Note that with this particular field, there's a hidden "long" char(25)
field overlaying it in the DDS.
A S000IV 15 B 10 67
A TEXT( 'Customer Name' )
A DSPATR( &G0000R )
A CHANGE( 03 'Modified?' )
A G0000R 1A P
A H000IV 25 H

In fact, the program actually moves the data to the hidden "long"
field and not the "short" visible one. But the data in the long field
looks good in the dump:
H000IV CHAR(25) 'TALBOTS INC. '
VALUE IN HEX
'E3C1D3C2D6E3E240C9D5C34B40404040404040404040404040'X



WTF?

Charles


On Sat, Oct 11, 2008 at 5:02 PM, Simon Coulter <shc@xxxxxxxxxxxxxxxxx> wrote:

On 11/10/2008, at 6:46 AM, Charles Wilt wrote:

Ok, I've got the trace data from PC5250, can anybody point me in the
direction of a manual of the 5250 data stream or give me some other
tips so I can make heads or tails out of the data in the trace?

The "current" 5250 data-stream reference is a combination of the 5494
Remote Control Unit Functions Reference, the DSM APIs, the TN5250 and
TN5250E RFCs, plus a few APARs related to WSG and Unicode enablement.

I think this is still true in VRM610 documentation. I haven't
specifically searched for an updated reference but I suspect
nothing's changed.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------



--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.