We have been been testing the IACS client on MACs as well as Windows
systems and I agree that the client is nice but one huge drawback for our
implementation is that one of our main macros written long ago to do
screen scraping from our IBMi application into a CICS mainframe
application no longer works and needed to be completely rewritten.
It's a very complicated script and was not able to be converted into the
new XML based scripting language.
We also found that the tabs function does not work well. I am sure that
IBM will work out the tabs issue soon enough ( if they have not already
done so)
The scripting macros is a big issue at least for us.
Jim
Sent from my iPad
> On Oct 7, 2015, at 19:01, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:
>
> Jim
>
> I agree that the ACS client is really nice - AND there are a few subtle
> differences that can hinder acceptance due to unfamiliarity - and maybe
> finding setup procedures that are as "easy"- read that "familiar"- as
> those that have been in use for 20 years.
>
> You've given us a lot of help in this area in these lists, Pete has some
> stuff in his monthly email, and being newish, with a different
> (expanded?) set of knobs, some standard guidance will help a lot.
>
> Cheers
> Vern
>
> On 10/7/2015 4:06 PM, Jim Oberholtzer wrote:
> > The older client will still connect for those things the client
supports.
> > If the new OS or client supports additional function, clearly they
won't be
> > there.
> >
> > That said, the new client is Faster, Thinner, Easier to
update/maintain,
> > why not just dump the old iSeries Access client for the new ACS
client?
> >
> > On Tue, Oct 6, 2015 at 2:06 PM, David Gibbs <david@xxxxxxxxxxxx>
wrote:
> >
> >> On 10/6/2015 1:57 PM, Szepesi Frigyes wrote:
> >>
> >>> Rumours are that Client Access will be discontinued on V7R2,
iSeriess
> >>> Access Client Solutions replaces it. Does it mean that I can not
> >>> connect to a machine on V7R2 by using (the old) Client Access?
> >>>
> >> I can't imagine that they will prohibit the native client access
product
> >> to connect ... they probably just won't provide support for it.
> >>
> >> david
> >>
> >>
> >>
> >> --
> >> IBM i on Power Systems: For when you can't afford to be out of
business!
> >>
> >> I'm riding 100 miles (a full century) in the American Diabetes
> >> Association's Tour de Cure to raise money for diabetes research,
education,
> >> advocacy, and awareness. You can make a tax deductible donation to
my ride
> >> by visiting [1]
http://gmanesig.diabetessucks.net. My goal is $6000
but any
> >> amount is appreciated.
> >>
> >> See where I get my donations from ... visit
> >> [2]
http://listsig.diabetessucks.net/map for an interactive map (it's
a geeky
> >> thing).
> >> --
> >> 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: [3]
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 [4]
http://archive.midrange.com/midrange-l.
> >>
> >>
>
> --
> 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: [5]
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 [6]
http://archive.midrange.com/midrange-l.
>
References
Visible links
1.
http://gmanesig.diabetessucks.net/
2.
http://listsig.diabetessucks.net/map
3.
http://lists.midrange.com/mailman/listinfo/midrange-l
4.
http://archive.midrange.com/midrange-l
5.
http://lists.midrange.com/mailman/listinfo/midrange-l
6.
http://archive.midrange.com/midrange-l
midrange.com
