
APAR= II08754
CAWIN KNOWN PROBLEMS


** Last updated 10/29/96 **

This Informational APAR contains information about KNOWN
PROBLEMS using the V3R1M1 Windows 3.1 client.  It continues
in Informational APAR II08757.

**** NOTE ****

Because of a problem with the backslashes not printing,
all places that require a backslash have been changed to
a vertical bar "³".  Make sure when you are actually
entering the path names that you use a backslash.

Because of size limitation on the lines in the informational
PTF, the Known Problems list has been extended into
Informational APAR II08757.  Look there for additional problems.


KNOWN PROBLEMS WITH WINDOWS FOR WORKGROUPS
__________________________________________

There are known problems with Windows for Workgroups
versions 3.11 and earlier. The problems are with Windows.
It is not possible to restart Windows when you are
currently running Windows. The only circumvention is to
restart the machine.

During the Windows 3.1 client installation, there is a time
when Windows needs to be restarted. However, this is not
going to work. You will need to restart the entire
workstation.

During the update process for Windows 3.1, after the update
is complete a message is displayed telling you to restart
windows. However, this is not going to work either. You
will need to exit Windows and run this command from a DOS
session: C:³CAWIN³CAUPDT2.BAT  (where C:³CAWIN is the drive
and path where Windows 3.1 was installed). This will cause
the second update phase to occur. Now restart your
workstation.

In order to find more information about the Windows problem
and a fix for the problem, please refer to this address:

  http://www.microsoft.com/kb/peropsys/windows/q109447.htm

The latest network card fixes for Windows for Workgroups
can be obtained from Microsoft at either:
  -- ftp.microsoft.com
  -- www.microsoft.com


PROBLEMS WITH FSIOP, CA400 and WFWG 3.11
________________________________________

There is a problem if you have installed FSIOP with Lan
Server/400 in an environment with Windows for Workgroup 3.11,
using CA/400 for Windows and have the Microsoft DLC driver
as standard protocol and the Microsoft NetBEUI.  The error
message when configuring Client Access is 9125.

The fix is to change your Windows for Workgroup Network
Configuration/Advanced Protocol Settings.  The settings need
to be set to:  SAPs=8, xsaps0=5 and xstations=5.


PRINTER DRIVER CONFIGURATION
____________________________

The IBM AFP printer driver allows you to print data
(including graphics) from windows applications on printers
that support Advanced Function Printing (AFP). The IBM
SCS printer driver allows your to print data from Windows
applications on printers that support the SNA character
stream (SCS). The SCS driver produces only test and,
therefore, is best used with word processor, spreadsheet,
database, and other text applications.

Since some AS/400-attached printers, like the IBM 3812 and
IBM 3816, can support either AFP or SCS, you must be aware
of the current configuration of the AS/400 printer that
you choose. If the printer is configured to support AFP
data, then it can also print SCS data. If the printer is
configured to support SCS only, then trying to print an
AFP file would cause an error.

To install and configure the printer devices:
  1. Use "Setup" to copy the printer driver files to
     the workstation.
  2. Select "Configuration" from the "Client Access/400
     for Windows" group.
  3. Select "Printer Drivers".
  4. Select a device driver and port. This will install
     the devices to the port. This has to be done once
     for each device that the user wants available to
     Windows.
  5. Open the Windows Control Panel and select "Printers".
  6. Select the appropriate printer device and select
     "Setup" to configure the driver for that device.
  7. Now the printer device should be installed,
     configured and ready to use.

Since Windows supports a maximum of 16 printer devices do
attempt to install more than 16 AFP or SCS printer devices.
This means that if you already have two print devices
installed, you may install only 14 AFP or SCS print devices.


INSTALLING GRAPHICAL ACCESS FOR OS/400 V3R1
___________________________________________

If the Setup screen does not contain the Graphical Access
option, it is because it was not installed on the AS/400.
The product needs to be installed using RSTLICPGM option 8
for product 5763-XC1.

If you installed the product but the AS/400 screens are
still green, you need to apply PTFs SF22954, SF22955,
SF22957 and SF24086 for product 5763-SS1.

The option will be displayed on the V3R6 GO LICPGM menu.

SYSTEM OBJECT ACCESS/AFP VIEWER V3R1
____________________________________

If the Setup screen does not contain the System Object Access
option, it is because it was not installed on the AS/400.
The product needs to be installed using RSTLICPGM option 9
for product 5763-XC1.

The option will be displayed on the V3R6 GO LICPGM menu.

X.25 CONNECTIONS
________________

If you selected the X.25 connection type, you should read
this information on ways to configure the connection to get
around some known problems.  Remember to change all vertical
bars to backslashes in the following example.

1) When defining the strings to be sent to the PAD, if
   your PAD requires a carriage return to recognize the
   command, you must list that carriage return at the
   end of the string. A carriage return is represented
   as the string "³CR" (with no quotes).

   For example, if the command to make a connection
   through an X.25 network is:
     CALL AS/400   <Enter>

   Then the string that needs to be sent to do this:
     CALL AS/400   ³CR

2) There is a problem with handling null received strings
   in the PAD configuration section. If you want to send
   a command, just delay for some time, not receiving
   any particular response, and then send the next string.
   The best way to accomplish this is as follows:

   GROUP X

   String to be sent:  STRING ABC ³CR
   Amount of time to wait for response: whatever you want

   String to receive:  SOME DUMMY STRING
   (it should be some string that should not get received)

   Group to accomplish on success: Group X+1
   Group to accomplish on timeout: Group X+1

   With this setup, the code will send String ABC, delay
   your requested amount of time, and then continue with
   the next group.

3) For best performance, your APPC Controller on the AS/400
   should have the following values:

   The best values for the timers (which are listed in the
   APPC controller) are:

    X.25 response timer = 80  (.1 sec increments) (8  sec)
      - the response timer is the most important timer, and
        may have to be adjusted based on your workstation
        and your network's performance.

    X.25 receive acknowledgment timer = 2 (.1 sec increments)
                                        (0.2 sec)

    X.25 inactivity timer = default set by the AS/400



ODBC REFRESH DRIVERS
___________________

The V3R1 refresh of the Client Access/400 for Windows
client includes an ODBC driver that supports Version 2.0
of the Microsoft ODBC specification.  In order to support
Version 2 of ODBC some new components from Microsoft must
be installed in your ³WINDOWS and ³WINDOWS³SYSTEM
directories.  If you do not already have these files
installed on your system from some other source, you should
install them using the following instructions.  Remember to
change all vertical bars to backslashes.

The Microsoft ODBC files shipped with CA/400 for Windows
are English language versions.  If you have already
installed these Version 2 programs for you national
language then you may not want to replace them with the
English language version.

The files include:
  ODBC.DLL     - The ODBC Driver Manager
  ODBCINST.DLL - The ODBC Driver Installer DLL
  ODBCINST.HLP - The ODBC Driver Installer/Administrator
                  help file
  ODBCADM.EXE  - The ODBC Administrator program

The following directions assume you have a shared folder
assigned as drive I: and that Windows is installed in
the ³WINDOWS directory of the current drive.

For a single-byte system use these commands:
  copy i:³qpwxcwn³odbcadm.exe  ³windows
  copy i:³qpwxcwn³odbc.dll     ³windows³system
  copy i:³qpwxcwn³odbcinst.dll ³windows³system
  copy i:³qpwxcwn³odbcinst.hlp ³windows

For a double-byte Japanese system use these commands:
  copy i:³qpwxcwnd³jdbcadm.exe  ³windows³odbcadm.exe
  copy i:³qpwxcwnd³jdbc.dll     ³windows³system³odbc.dll
  copy i:³qpwxcwnd³jdbcinst.dll ³windows³system³odbcinst.dll
  copy i:³qpwxcwnd³jdbcinst.hlp ³windows³odbcomst.hlp

For a double-byte non-Japanese system use these commands:
  copy i:³qpwxcwnd³odbcadm.exe  ³windows
  copy i:³qpwxcwnd³odbc.dll     ³windows³system
  copy i:³qpwxcwnd³odbcinst.dll ³windows³system
  copy i:³qpwxcwnd³odbcinst.hlp ³windows


NETWARE FOR SAA 2.0 NS/ROUTER
_____________________________

Client Access/400 for Windows supports two sets of APIs:
native Windows and native base DOS. Both sets work
under the IBM supplied router. However, when using the Netware
for SAA 2.0 NS/Router, only the native Windows APIs
will work. The problem is that the Netware router does not
support a DOS reflector for the router Base DOS APIs.


PROBLEMS WITH CUM TAPE 95157 ON MICROCHANNEL WORKSTATIONS
_________________________________________________________

The problem is that after updating Microchannel PC's
connected to the AS/400 via Twinaxial Work Station Emulation
cards (WSE), they fail to connect (error message 5123).
This problem is being fixed with APAR SA44221.

The current fix to the problem:
 - Find a set of install diskettes for the Windows client
   that were made prior to the CUM tape 95157.
 - Find the file VDTWINX.386 in the CAWIN directory on the PC.
 - Rename or delete the VDTWINX.386 file on the PC.
 - Copy the VDTWINX.386 file from the second install
   diskette to the PC.
 - Install from the diskettes (don't run update)
 - Install the latest cum tape
 - Run update to download the PTFs to the PC


**** continue in II08757 for more KNOWN PROBLEMS ****
