Re: Client Access vs Access Client - 27x132 font size

True that, Joe.

As for the RFE thing - this has become really important as the place to do
just that - tell IBM when something is broke.

And if you or anyone is a COMMON member, I suggest you specify the source
on the RFE - COMMON is one of the options.

I'm on the CAAC, and we review RFEs marked as from COMMON first - IBM do
listen to our assessments, and using that source will get it looked at
sooner by the CAAC.

Anyhow, enough of my shameless plug! Request away, my friend!

Vern


On 4/12/2018 7:21 AM, Joe Pluta wrote:

Yes, I think you're right, Vern. I just wanted to make sure I was seeing
what I thought I was seeing, and this list is incredibly helpful as an
extra pair of eyes.

For a number of reasons I haven't been very active in the RFE cycle of
late, but between this and some things I see in the SQL parser for RDi, it
may be time to break out the old RFE pen again.

IBM can't fix something if they don't know it's broken!


Hi Joe

One aspect of all this might be, ACS is not derived from Personal
Communications 5250 (as in Client Access) - I believe it comes through the
Host-On-Demand product stream - that is also Java-based and has been around
for 10, 15, ?? years.

One reason I say that is the extension on the emulator files - HOD.

It is likely that Host-On-Demand never behaved in every way as PC5250
did. But who among us ever tried HOD other me and the other person? (Just
kidding, just kidding!)

I would suggest submitting an RFE and present as justification of this
request that if IBM want to give us equivalent functionality, this setting
needs to be there.

Cheers
Vern

On 4/11/2018 5:24 PM, Joe Pluta wrote:

-snip-
It doesn't "seem" simple. It is simple. I want it to act the way it
did before, no matter how much you dislike it. You are making it more
complicated than it is, and to be honest, more complicated than it's
worth. I wanted to respond out of politeness because you've put a lot of
effort into your argument, but I sense that I'm edging out of the polite
lane, so I'm just going to leave it here.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD