|
On Aug 9, 2016, at 11:38 AM, DrFranken <midrange@xxxxxxxxxxxx> wrote:
COMPLETELY Disagree.
Sure there are some hiccups but it is SO VASTLY better than the old client that the niggles and the bits while annoying to some are hugely outweighed by the benefits.
And it's people like those on this list that will push and test the thing until it breaks. This is why IBM pays attention here to get those things corrected.
I have been using this thing since early beta releases and I absolutely HATE when I have to go back to the old emulator.
- Larry "DrFranken" Bolhuis
www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
On 8/9/2016 11:33 AM, Paul Nelson wrote:
The more I see these issues, the more the phrase "Not ready for prime time"--
comes to mind.
And then I chuckle at the number of trouble tickets I see at one of
my clients after their rush to Windows 10. I wonder if the guy who
got a raise for beating the June 30th deadline for the first phase of
the rollout will have a job by Labor Day.
Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of Tyler, Matt
Sent: Tuesday, August 09, 2016 10:04 AM
To: midrange-l@xxxxxxxxxxxx
Subject: iAccess CLient SOlutions 5250 "quirk"
So I think I found another problem with ACS product this time in the
5250 plugin. Here is the RFE I created to address this (and no I
cannot create any other request to IBM without going through another
vendor (who I don't trust to get stuff right) and I think publishing
problems like these helps others voice their need to have IBM fix),
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=
92754
We before had an issue with display files where two fields shared the
attribute position and the solution from IBM was to just move one of
the fields over one place; this does work to fix the problem BUT this
is not a solution IMO because ACS 5250 version 1.1.6.0 will break, in
production, our
5250 windows and to fix this by moving fields on screens would cause
a significant cost for something that works fine with version 1.1.5.1.
This should not have to wait for 1.1.6.1 this should be fixed in
1.1.6.0 if
1.1.6.0 is going to still be offered for download.
Thanks, Matt
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
