=================================================================
    Readme File for AS/400 Client Access for Windows 95/NT
                       February 1997
(c) Copyright IBM Corporation 1996, 1997.  All rights reserved.
=================================================================

    IMPORTANT: Be sure to check Informational APAR II09209 for
    the latest information for the Windows 95/NT client.  If your
    PC has an internet browser installed and configured, an internet
    browser icon is created in the Client Access program folder.
    This icon opens the Readme.htm file in your internet browser
    and allows you to link to all the latest Client Access
    information, including Informational APAR II09209.  The web
    also includes links to other related web pages.


-----------------------------------------------------------------
TABLE OF CONTENTS
-----------------------------------------------------------------

1.0  OS/400 PROGRAM TEMPORARY FIXES (PTFs)
2.0  POTENTIAL SECURITY EXPOSURE
3.0  SNA SERVER
     3.1  SERVER CONFIGURATION
     3.2  SERVER PERFORMANCE
     3.3  KNOWN PROBLEMS
4.0  RESTRICTIONS
5.0  INSTALLATION NOTES AND KNOWN PROBLEMS
6.0  SDLC PERFORMANCE
7.0  TWINAX Connections for Windows NT 4.0
8.0  TWINAX Connections for Windows 95
9.0  PC5250 Integration
10.0 Availability of SCS Print Drivers for Windows NT

-----------------------------------------------------------------

1.0  OS/400 PROGRAM TEMPORARY FIXES (PTFs)
-----------------------------------------------------------------
   See Informational APAR II09209 for a list of the required
   OS/400 program PTFs.


2.0  POTENTIAL SECURITY EXPOSURE
----------------------------------------------------------------
   The initial release of Microsoft Windows 95 contains a
   potential security exposure if you use the File and Printer
   Sharing for Microsoft Networks option.  Microsoft has provided
   a fix for this problem (MSPWLUPD.EXE) that is available by
   calling Microsoft directly, or by downloading it from their
   internet page (http://www.microsoft.com/).


3.0  SNA SERVER
----------------------------------------------------------------

   3.1  SNA SERVER CONFIGURATION
   -------------------------------------------------------------
   If you are using an SNA Server as the communications provider
   for Client Access, you need to configure the SNA Server so that
   a local LU name is assigned to each workstation using the SNA
   Server.  Without this configuration, Client Access will not be
   able to connect to any AS/400 systems.

   This configuration is done on the SNA Server, not on the SNA
   Server clients.  There are two methods you can use to configure
   the local LU name.  Both methods are on the SNA Server
   Administration menu.

   Method 1
     Select the 'Member of Default Outgoing Local APPC LU Pool'
     checkbox on the APPC LU Properties dialog for at least one of
     the local LUs.  This allows workstations that do not specify
     a local LU to connect to an AS/400 system using one of the
     LUs configured in this manner.

   Method 2
     Assign each user or group a specific local LU.  In the
     Properties dialog for each user or group listed in the Users
     and Groups Window, select the Default Local LU.

   3.2  SNA SERVER PERFORMANCE
   ----------------------------------------------------------------
   Performance may be impacted for some Client Access
   APIs and programs that use those APIs if the QSERVER mode is not
   configured on the SNA Server.  The mode can be configured using
   the SNA Server Admin program.  Use the following values for the
   QSERVER mode:

   Parallel session limit               64
   Minimum contention winner limit      32
   Partner min contention winner limit   0
   Automatic activation limit            0
   Enable automatic partnering           X (checkbox selected)
   High priority mode                    X (checkbox selected)
   Pacing send count                     7
   Pacing receive count                  7
   Max send RU size                   1024 (default)
   Max receive RU size                1024 (default)


   3.3  KNOWN PROBLEMS
   ------------------------------------------------------------------

   SNA Windows 95 client - possible data corruption using TCP/IP
   ------------------------------------------------------------------
   When transferring a large amount of data using the SNA Server
   Windows 95 client configured to use TCP/IP sockets to communicate
   with the server, some data bytes (15-20 bytes) may be corrupted
   when passed to the Win32 application.  Microsoft has a fix available
   to correct this problem (SNA95.ZIP, win95.TXT).  If you have an
   internet connection, you can download the fix from the
   following URL:

   ftp://ftp.microsoft.com/bussys/winnt/sna-unsup-ed/fixes/sna211a/WIN95

   The following URL is another place to look if you are having other
   Windows NT related problems:

   ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes


4.0  RESTRICTIONS
---------------------------------------------------------------------


   PERSONAL COMPUTERS USING STACKER DISK COMPRESSION
   -------------------------------------------------
   Client Access will not install on hard disks that have been
   compressed using the Stacker program.


   PERSONAL COMMUNICATIONS VERSION 4.1 FOR WINDOWS 95
   --------------------------------------------------
   If you are using Personal Communications Version 4.1 for Windows 95,
   you will not be able to install the PC5250 display and printer
   emulation provided with Client Access.


   SPECIFYING ENVIRONMENT NAMES
   ----------------------------
   When specifying the name for an environment, do not use any file
   system characters, such as colon (:), forward slash (/), or  back
   slash (\) as part of the environment name.  The environment name
   is used as part of the profile name.  If file system characters
   are used, the export function will fail and Client Access will fail
   to automatically create the default PC5250 workstation profile.


5.0  INSTALLATION NOTES AND PROBLEMS
---------------------------------------------------------------------

   ANYNET CONNECTION PROBLEM
   -------------------------
   If you are not able to connect to the AS/400 using Anynet and
   receive an Anynet-04 error message in the NetSoft event log,
   the problem could be caused by not having enough free space on
   your PC's hard disk.  Try freeing up additional space on the
   hard disk.  Also, empty the Windows 95/NT recycle bin if it has
   anything in it.


   SNA INCOMING REMOTE COMMAND OVER ANYNET
   --------------------------------------------------------------
   If you want to run incoming remote commands on your PC over an
   AnyNet connection, you must configure the AS/400 as described
   below.  For this example, the LU name of the PC is 'MYPC', and
   the name of the AS/400 system from which to send remote commands
   is 'MYAS400'.

   1. Create an APPC controller on the AS/400 for your PC, using the
      CRTCTLAPPC command with the appropriate parameter values as follows:

          CRTCTLAPPC CTLD(MYNEWCTLR) LINKTYPE(*ANYNW) RMTCPNAME(MYPC)

   2. Add an entry for your PC to the AS/400 APPN configuration list, which
      must have the same Remote Control Point as the APPC controller
      created in step 1.  For example:

          ADDCFGLE TYPE(*APPNRMT) APPNRMTE((MYPC *NETATR MYAS400 MYPC))

   3. Add an entry in the AS/400 TCP/IP host entries table for the AnyNet
      host name for your PC.  This host name is formed by combining the
      LU name of your PC, the network identifier of your PC, and the
      string 'SNA.IBM.COM'.  For example:

          ADDTCPHTE INTNETADR('9.5.13.77') HOSTNAME((MYPC.APPN.SNA.IBM.COM))

   4. Vary on the controller created in step 1.  For example:

          VRYCFG CFGOBJ(MYNEWCTLR) CFGTYPE(*CTL) STATUS(*ON)

   If the above completed successfully, you should be able to run remote
   commands on MYPC sent from MYAS400, provided that MYPC is connected to
   MYAS400 using AnyNet and that security checks pass.  The sender of the
   remote command must specify the remote control point name, MYPC, as
   the value of the RMTLOCNAME parameter of RUNRMTCMD.


   TCP/IP
   ------
   If you are using TCP/IP to connect to the AS/400 system, the TCP/IP
   licensed program (57xx-TC1) must be installed on the AS/400 system.


   NETWORK DRIVES
   ------------------------------------------------
   --  Network drives will not work on personal computers that are
       running in MS-DOS (16-bit) compatibility mode.  The personal
       computer may hang when you try to connect a network drive.
       See Client Access message CWBBS0112 in the online User's Guide
       for additional information on a possible fix for this problem.

   --  Network drives and network print may not function due to
       missing Windows 95 registry entries needed to run these
       programs.  See Client Access message CWBBS0018 in the online
       User's Guide for information on how to correct this problem.


   MIGRATING A CONFIGURATION USING NETSOFT NS/ROUTER 2.11
   -------------------------------------------------------
   If you are using the NetSoft NS/Router 2.11 provided with Client
   Access and you are migrating a previous configuration, you will
   need to specify the name of the configuration file you want to
   migrate.

   The name of the configuration file depends on the communication
   package you used for the Windows 3.1 client.  If you used the
   communications package provided with the Windows 3.1 client, the
   name of the configuration file is NSD.INI.  NSD.INI is located in
   the Windows directory (default).  If you did not use the communications
   package provided with the Windows 3.1 client, refer to the online
   help to determine the name used for the configuration file.


   PROBLEMS WHEN SELECTING CANCEL IN SETUP
   ---------------------------------------
   If you cancel out of the setup program, you get a screen to
   verify if you really want to cancel.  Selecting Resume may
   cause the PC to hang.  The workaround is to cancel out of the
   setup program and then restart it.


   PERSONAL COMPUTERS USING SPANISH WINDOWS 95
   -------------------------------------------
   A problem occurs where all of the Client Access files do not get
   copied to the PC when your:
   -- PC is using the Spanish National Language Version of
      Windows 95 and
   -- You change the default installation path (target drive and
      directory)
   -- You use non-English characters, such as tilde n, in the path.

   If you specify a different installation path, make sure you use
   only English characters.


   PERSONAL COMPUTERS USING GERMAN WINDOWS 95
   ------------------------------------------
   If you try to do a silent install and the response file is stored
   on a server, the installation will fail.  This problem occurs on
   personal computers using the German National Language Version of
   Windows 95.  To work around this problem, copy the response file
   to the hard disk on the PC.

   For information on how to use silent install, see the Silent
   Installation topic under the Tips and Techniques/Client Access
   section of the Client Access online User's Guide.


   SPECIAL FONTS FOR PC5250 AND GRAPHICAL ACCESS
   -------------------------------------------------------------------
   See the following topics in the online Client Access User's Guide
   for information on how to install the fonts for PC5250 and Graphical
   Access.

   How to...
      PC5250
       -- Special Fonts for PC5250
       -- Using PC5250 with DBCS Languages
      Graphical Access
       -- Special Fonts for Graphical Access
       -- Using Graphical Access with DBCS Languages


   PC5250 FOR TAIWAN, KOREA, AND THE PEOPLE'S REPUBLIC OF CHINA
   -------------------------------------------------------------------
   Client Access includes versions of PC5250 for Taiwan, Korea, and
   the People's Republic of China.  See the following topic in the
   online Client Access User's Guide for information on how to install
   one of these versions on your personal computer.

   How to...
      PC5250
      -- Using PC5250 with DBCS Languages


   USING THE SCS PRINTER DRIVER WITH THE GREEK NLV
   ------------------------------------------------
   The IBM SCS printer driver assumes that the default EBCDIC code
   page for a system configured for the Greek language is 875.  Some
   printers may not support the 875 code page.  If the printer
   does not support the 875 code page, the output will not be
   valid for the printer.

   If this occurs, you can correct the problem by selecting a table
   that uses the 423 EBCDIC code page as follows:

   1. Select the Properties for the printer by clicking the right
      mouse button on the printer icon.
   2. Select the Details tab page.
   3. Click the Setup button.
   4. Click the Job Properties button.
   5. Click the New Table button.
   6. Locate the folder that contains the table files (*.tbl).
      The default location for these files is the directory where
      Client Access is installed.
   7. Select the 036501A7.TBL file and click OK.
   8. Click OK on each of the dialogs as you exit the Properties.

   You should now be able to use the printer.  To change back to
   the default selection, repeat steps 1 through 5 and click on
   the Defaults button.  Then click on OK to exit.


6.0  SDLC PERFORMANCE
-----------------------------------------------------------------

   Use the following Line mode settings to obtain the best SDLC
   performance:

   -- For a switched line, "Constant Request-to-Send" should be
      set only if the modem supports full duplex.

   -- For a non-switched line (leased line or point-to-point),
      "Constant Request-to-Send" should be set if you are using
      full-duplex and a non-multi-dropped line.  Otherwise, this
      setting should be "Line Turnaround Required".

   Line Turnaround Required is the default setting and should be
   used for half-duplex or dialup connections.  Constant
   Request-to-Send improves throughput but requires a full-duplex
   point-to-point circuit.

7.0 TWINAX Connections for Windows NT 4.0 
------------------------------------------------------------------
   For Window NT 4.0 32-bit twinax device drivers are automatic-
   ally installed by Client Access.  If you are unable to connect
   using TWINAX the most likely reasons are IRQ, IO port, or 
   memory conflicts.  To resolve these problems use the Windows
   NT diagnostics program.  You can run the program by going to
   Start->Programs->Administrative Tools->Windows NT Diagnostics.
   In the diagnostics program use the resource tab to check for
   IRQ, IO port, and memory conflicts.

8.0 TWINAX Connections for Windows 95
------------------------------------------------------------------
   Please check the informational APAR II09209 or the 
   the internet readme for information on the availability of 
   32bit VXDs for Client Access connections over TWINAX for 
   Windows 95 users.

9.0  PC5250 Integration
-------------------------------------------------------------------
   The PC5250 Emulation function delivered with Client Access has
   been integrated more into the base function with this release.  
   It is now necessary to establish a connection through client 
   access before you can use the emulator.  For most users there
   will be no difference, but users that only brought up the 
   emulator without signing on through Client Access may now see a
   Client Access signon screen when the first emulator session is
   started.

10.0 Availability of SCS Print Drivers for Windows NT
--------------------------------------------------------------------
   The SCS print drivers for Client Access on Windows NT were not ready
   to be shipped with the rest of the client.  To obtain the SCS print
   drivers you will need to install PTF SF37523.  Refer to the Client
   Access home page or the information APAR for more information.

11.0 Client Access and Laptop Computers.
--------------------------------------------------------------------
   Client Access has been tested with IBM Thinkpads using LAN, Async, 
   and TWINAX connections.  We have found that other laptops often have
   IRQ, IO port, or memory conflicts with the TWINAX cards.  Addition-
   ally we have found that devices installed in the laptops do not 
   always report their resources correctly to the Windows NT operating
   system.  If you are using a laptop and are unable to make a 
   connection you may need to consult your product documentation to 
   determine if there is a resource conflict.

