|
I really try not to use the IBM Navigator client but there are some issues
accessing
some configuration options within the *HTTPP Admin server.
for example: We run our internal DNS server on IBMi and when trying to
update
the server properties some options do not show up in the Admin server.
I have tried several different browsers with the same results.
Have not had time to report to IBM.
I usually start my windows VM and use IBM Navigator to make changes.
Anybody else have any issues with the *admin server?
Jim W Grant
Senior VP, Chief Information Officer
Web: www.pdpgroupinc.com
Email: JWGrant@xxxxxxxxxxxxxxx
Office: (410)584-0339
Fax: (410)584-0336
Cell: (443) 271-3390
From: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 10/08/2015 01:11 PM
Subject: Re: iACS vs. Client Access on V7R2
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
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 IBMiAccess
for Windows that don't have a comparable replacement.supports.
-----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
If the new OS or client supports additional function, clearly they won'tlist
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
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.
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.
--
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.
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.