Re: Client Access Express on a CISC system

[jkrueger@xxxxxxxxxxxx]

Answer number 1 gets the prize.  There are definitely things you _cannot_
do on a CISC if you use Express that you _could_ do if you used Classic,
even if you are using TCP/IP connectivity.  First and foremost is access to
printers and the IFS on the AS/400, since NetServer does not exist on your
CISC system.

Janet Krueger
Rochester Technology Center





Jeff Crosby <jlcrosby@fwi.com> on 10/13/99 01:20:08 PM

Please respond to MIDRANGE-L@midrange.com

To:   "Midrange List Server (David Gibbs)" <MIDRANGE-L@midrange.com>
cc:    (bcc: Janet Krueger/dhagroup/US)
Subject:  Client Access Express on a CISC system

I'm getting confused.

Client Access Express ("Express") has a smaller cleaner footprint than
the classic Client Access for Win95/98/NT ("Classic").  But I also
thought that was because some things were "missing" in Express (like
APPC and IFS access).

I thought that Express required Netserver to get at the IFS on the
AS/400.  If this is so, then Express is not usable (for me) on our CISC
(read V3R2) system.

However, I have been told both of the following recently:

1) That is correct.  There are things you _cannot_ do on a CISC if you
use Express that you _could_ do if you used Classic.

2) That is wrong.  As long as you stick with TCP/IP connectivity, you
can do _anything_ in Express that you could do in Classic.

Which is right?

--
-Jeff



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---