Re: iACS vs. Client Access on V7R2

[Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>]

Justin,

With the recent announcements I think we are down to two things, both of
which are being worked on feverishly by our friends in Rochester.  With the
SQL scripting now being supported 90% of what everyone uses is either in
the Access Client or in the *ADMIN server.    The two (maybe three) items I
am aware of are high on the list of items to complete.

On Thu, Oct 8, 2015 at 7:45 AM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

> For PC5250, I'm with you 100%.  There are other components of IBMi Access
> for Windows that don't have a comparable replacement.
>
> -----Original Message-----
> From: Jim Oberholtzer [mailto:midrangel@xxxxxxxxxxxxxxxxx]
> Sent: Wednesday, October 07, 2015 4:06 PM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> Subject: Re: iACS vs. Client Access on V7R2
>
> 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?
>
> --
> 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.