Re: Issue with new IBM Access Client Solutions Emulator (still!)

On 31-Mar-2017 10:14 -0600, Jeff Young wrote:

Just upgraded to latest version.
On prior version, I had a issue when attempting to display data where
the field in question had an X'03' (ETX) as the last position.
I was first informed that this had been fixed in a prior PTF, but I
had the version after that fix.
The new version still has this problem:
System failure on device QPADEV0010 with feedback code 00002301.
Function check. CPF5411 unmonitored by QWSGET at statement *N,
instruction X'3478'.
Dump output directed to spooled file 2, job 846236/VAIJY/QPADEV0010
created on system S06B6D65 on 03/31/17 11:07:04.
Failure for device or member QPADEV0010 file QDQUWSRUN in library
QSYS.
Dump output directed to spooled file 4, job 846236/VAIJY/QPADEV0010
created on system S06B6D65 on 03/31/17 11:07:04.
Function check. CPF5257 unmonitored by QQURB at statement *N,
instruction X'050E'.

When I used the old Client Access Emulator, it works just fine.

I am not authorized to report problems to IBM.

Given there is no possibility to present the non-alphanumeric code point 0x03 as a visible glyph on the report display [file QDQUWSRUN], why not just correct the apparent problem with the underlying data, by ensuring that the character data field contains only /characters/ instead of control codes. Or if the data is legitimate, in a BINARY [or DDS Hex] data-type field, then present the data for that field using an effective HEX() scalar, or replace/translate each of the non-displayable characters as another that is printable/displayable, e.g. presented as a blank. That effect can be encapsulated in a logical file/view without changing the physical data; so instead of changing emulators, just refer to the logical file [every time any displayed/printed reporting is directed against the file].