Re: Client Access Express on a CISC 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--

Express requires a TCP/IP connection only and can do everything "classic"
32-bit CA/400 can, except:
    1. shared folders
    2. virtual print
    3. graphical access
    4. backwards support for 16-bit CA/400 APIs
    5. NetSoft router

For #1 and #2, Express assumes you have NetServer available. Express itself
offers no access to the IFS. #3, #4 and #5 have been jettisoned.

Express is only supported (with tech support and open APARs) down to V4R2.
However, if you're willing to live without the facilties above (and,
remember, Express only works with a TCP/IP direct connection), Express is
known to work down to at least V3R2.

See http://www.as400.ibm.com/clientaccess/express.htm for more info.

> Client Access Express ("Express") has a smaller cleaner footprint than
> the classic Client Access for Win95/98/NT ("Classic").  But I also

Be aware though, that the above statement is an urban legend of the highest
order. Although Express does abandon the four CWB file and print resident
processes, those were hardly huge resource consumers (yes, they provided
potential conflicts with BIOS and laptops, but they aren't pigs). The
primary chunks of Express, display, printer and data transfer are lifted
directly from "classic" versions and have the same memory and disk space
footprints they always did.

Rule of thumb: If what you have is working, upgrading to Express can safely
be deferred for now.

rp


+---
| 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
+---