Personal Communications 3270 Version 4.1 copy/paste bug?

I am trying to copy/paste APL text, including functions, using Personal
Communications 3270 Version 4.1 into another program. This is working
well except for one particular case, which I suspect is a bug in PC/3270.

If I attempt to copy/paste the {equalunderbar}, also know as {match},
character a \ {backslash} character is pasted into the application. I get
the same character if I copy/paste a \ {backslash} character, which is
distinct from what I get if I copy/paste the APL \ {slope} character. All
three characters are distinct on the 3270 display, so I suspect a bug in
the data being copied to the clipboard for pasting into other
applications.

Is there an APAR/fix for PC/3270 v4.1 to correct this? Is this same bug
present in later releases of PC/3270? Depending upon the answer I might
be interested in upgrading from v4.1 to a later release.

Can anyone help me sort this out?

-- Dave
-----------------------------------------------------------
dhdurgee<at>verizon<dot>net
-----------------------------------------------------------

Dave,

Match is one of several newer APL2 characters which are processed
differently than old APL characters. As I understand it (this was before my
time), the 3270 datastream did not provide native support for these
characters and was enhanced to support them using an escape character.
Basically, each of these characters is preceeded by an escape character
which tells the terminal emulator/controller that a new APL2 character is to
follow. (I don't guarantee this explanation is completely accurate; I've
never been a 3270 data stream guy and it's been a long time since I looked
into it.)

Although PCOMM correctly handles these characters in transmissions to and
from the host and the display, PCOMM's code for processing clipboard
operations does not handle them correctly. I looked into this 6 or 7 years
ago and got lost in the complexities of 3270 data streams and the PCOMM
development community. I do not think anyone ever generated a fix or
work-around for the problem. For sure, I still see it in Personal
Communications 5.9 (which I believe is the latest release.)

BTW The problem is even worse if you're trying to paste the data into
something other than PCOMM. Although PCOMM recognizes the EBCDIC APL
characters, it does not have code to translate APL characters from the
EBCDIC codepage to the ASCII or Unicode codepages supported by Workstation
APL2. If you need to move code or data between the host and workstations,
we strongly urge you to use APL2's )OUT and )IN system commands to write and
read files and upload or download them in binary.

Sorry I can't give you better news.

David Liebtag
IBM APL Products and Services

PS. I hope you prove me wrong and find a way to make it work. If you do,
please let me know!!! :-)