3270 screens

[cedarlakebuzzards]

I have a program that does full screen 3270 operations. it seems to
work correctly except when the letters A or B (X'C1', X'C2') follow the
attribute byte. 1 or more characters are then skipped. If I insert a
space between the attribute and the letter, it display correctly.

My question is does anyone know if the TSO TPUT macro alters the
datastream? maybe I should look at the TN3270 emulator?

Thanks.
Ed

[Greg Price]

I have a program that does full screen 3270 operations. it seems to
work correctly except when the letters A or B (X'C1', X'C2') follow the
attribute byte. 1 or more characters are then skipped. If I insert a
space between the attribute and the letter, it display correctly.
My question is does anyone know if the TSO TPUT macro alters the
datastream? maybe I should look at the TN3270 emulator?
Thanks.
Ed

The TPUT macro should not alter the data in the buffer you pass
to TPUT. Sounds like you need to trap the actual data stream
given to TPUT - I would be surprised if the glitch came from any
further downstream than that, but it is theoretically possible, of
course.

Some TN3270 clients provide the facility of logging a data stream
trace - that would be a good point of capture.

If you wrote the program, then TSO TEST may well be all you
need to locate the problem.

In any event, check the data stream passed to TPUT first.

Cheers,
Greg

[mfnoel]

In debugging KICKS 3270 output I've found it useful to look at the 3270 stream as the tn3270 client sees it. I know you can do this with the free C3270 client (it's called logging) and I imagine most other tn3270 clients provide similar functionality.

TPUT may alter the datastream (depending on STFSMODE). Watch out for 0x01, 04, 06, 14, 17, 24, 26. 37, 3D. They can get turned into colons.

Post by cedarlakebuzzards
I have a program that does full screen 3270 operations. it seems to
work correctly except when the letters A or B (X'C1', X'C2') follow the
attribute byte. 1 or more characters are then skipped. If I insert a
space between the attribute and the letter, it display correctly.
My question is does anyone know if the TSO TPUT macro alters the
datastream? maybe I should look at the TN3270 emulator?
Thanks.
Ed

[Tony Harminc]

Post by mfnoel
In debugging KICKS 3270 output I've found it useful to look at the 3270 stream as the tn3270 client sees it. I know you can do this with the free C3270 client (it's called logging) and I imagine most other tn3270 clients provide similar functionality.
TPUT may alter the datastream (depending on STFSMODE). Watch out for 0x01, 04, 06, 14, 17, 24, 26. 37, 3D. They can get turned into colons.

Recent versions of Wireshark also offer decoding of TN3270.

Tony H.

[Rick Fochtman]

TPUT does not alter the input stream. You might be afflicted by the fact
that X'C1' and X'C2' are also possible 3270 order codes. Since all
characters delivered to a 3270 MUST be acceptable EBCDIC characters, the
variety of order codes must also be valid EBCDIC characters.

Rick
-----------------------------------------------

I have a program that does full screen 3270 operations. it seems to
work correctly except when the letters A or B (X'C1', X'C2') follow the
attribute byte. 1 or more characters are then skipped. If I insert a
space between the attribute and the letter, it display correctly.
My question is does anyone know if the TSO TPUT macro alters the
datastream? maybe I should look at the TN3270 emulator?
Thanks.
Ed