Visit our Home Pages on the Internet: Communications Server for Windows NT http://www.networking.ibm.com/csn/csnprod.htm +----------------------------------------------------------------------+ DATE: 05/15/97 DESCRIPTION: README FILE FOR IBM Communications Server for Windows NT version 5.0 APAR: JR10525 This package contains APAR fixes to the product above. This package can be distributed to any one who has a license for this product. +----------------------------------------------------------------------+ IMPORTANT: This APAR fix replaces files on both the CSNT server and the SNA API client machine. If you have previously installed other APAR fixes to the CSNT v5.0 SNA API client component, you may need to reinstall those APAR fixes after installing this fix package. PREREQUISITES : IBM Communications Server for Windows NT version 5.0 The CSNT server must have the following two services installed: Gateway Service for NetWare SAP Agent The CSNT server must have the following network protocol installed: NWLink IPX/SPX Compatible Transport The CSNT Windows NT API Client requires one of the following Windows NT network services to be installed : Client Service for NetWare or Novell NetWare Client for Windows NT The CSNT Windows NT API Client requires the following Windows NT protocol to be installed : NWLink IPX/SPX Compatible Transport The CSNT Windows 95 API Client requires one of the following Windows 95 network services to be installed : Client Service for NetWare or Novell NetWare Client for Windows 95 The CSNT Windows 95 API Client requires the following Windows 95 protocol to be installed : IPX/SPX Compatible Protocol PROBLEMS FIXED: APAR Number Description JR10525 Add IPX/SPX connectivity for SNA API clients INSTALLATION INSTRUCTIONS: jr10525.exe is a self-extracting file containing the shipped executables. To support IPX/SPX connectivity, the replacement files for the server must be installed at the server, and the appropriate replacement files for the API client must be installed on the client machines. The replacement binaries identifed below are to provide the support for CSNT 5.0 SNA API clients (Windows 95 and Windows NT) the ability to communicate over IPX/SPX based LANs. These binaries are inclusive in their suppport (TCP/IP support and IPX/SPX support are both included) and are to be viewed as a comprehensive replacement of their previous version. The PARTS LIST is as follows: JR10525.TXT - this readme file SRV.EXE - contains CSNT server replacement files NTCLI.EXE - contains WinNT SNA API client replacement files 95CLI.EXE - contains Win95 SNA API client replacement files Running SRV.EXE generates the following CSNT server files: CSCM.DLL CSSEC.DLL PCSNOPS.EXE Running NTCLI.EXE generates these Windows NT client API files: CCM.DLL SSET.DLL LUX.DLL CSCCFG.EXE CSCENU.DLL CCT.DLL PCSMFCX.DLL MILLUTIL.DLL PCMFCENU.DLL PCSW32X.DLL MSGIO.DLL NSTRC.DLL MESSAGE.DLL Running 95CLI.EXE generates these Windows 95 client API files: CCM.DLL SSET.DLL LUX.DLL CSCCFG.EXE CSCENU.DLL CCT.DLL PCSMFCX.DLL MILLUTIL.DLL PCMFCENU.DLL PCSW32X.DLL MSGIO.DLL NSTRC.DLL MESSAGE.DLL Installing the server portion of the fix on the system: 1) Be SURE you have downloaded jr10525.exe in BINARY format. 2) Verify that you have the necessary services and protocol (indicated in the Prerequisites section, above) installed on the CSNT server. 2) On the CSNT server machine or on a shared drive, create a temporary directory, copy jr10525.exe into the temporary directory, and then run jr10525.exe to uncompress it. Then, run the resulting SRV.EXE file to uncompress it into the three server replacement files. 3) Stop Communications Server for Windows NT (including your node, Node Operations, Node Configuration, Log Viewer, and any other CS/NT components you have started). Stop "IBM SNA Client Services" from the Services Control Panel Applet. 4) Back up your existing versions of the three CS/NT server files listed in the above parts list. 5) Copy the new versions of the files from the temporary directory to the directory where CS/NT is installed. The default directory for CS/NT is IBMCS. 6) Shutdown and Restart the CS/NT server machine. 7) Restart your CS/NT node. Installing the client portion of the fix on the Windows NT client machine: 1) After installing the server portion of the fix as described above, verify that you have the prerequisite service(s) and protocol installed on the Windows NT client machine. 2) Make a new temporary subdirectory on the server or a shared drive and copy NTCLI.EXE to the new directory. Then, run NTCLI.EXE to uncompress it. Note that if you have Windows NT and Windows 95 clients, you should not use the same temporary directory for uncompressing NTCLI.EXE and 95CLI.EXE since the resulting files created by each have the same filenames. Use a separate directory for each client operating system. 3) Stop any applications on the Windows NT client machine that may be using the SNA client APIs and back up the existing versions of the files generated when you ran NTCLI.EXE. Reference the parts list above for the appropriate files to back up. 4) Copy the new files from the temporary directory where you ran NTCLI.EXE to the directory on the Windows NT client where the SNA client APIs are installed. The default name for this directory is CSNTAPI. 5) Shut down and restart the client machine and restart any applications that use the CSNT SNA client APIs. Installing the client portion of the fix on the Windows 95 client machine: 1) After installing the server portion of the fix as described above, verify that you have the prerequisite service(s) and protocol installed on the Windows 95 client machine. 2) Make a new temporary subdirectory on the server or a shared drive and copy 95CLI.EXE to the new directory. Then, run 95CLI.EXE to uncompress it. Note that if you have Windows NT and Windows 95 clients, you should not use the same temporary directory for uncompressing NTCLI.EXE and 95CLI.EXE since the resulting files created by each have the same filenames. Use a separate directory for each client operating system. 3) Stop any applications on the Windows 95 client machine that may be using the SNA client APIs and back up the existing versions of the files generated when you ran 95CLI.EXE. Reference the parts list above for the appropriate files to back up. 4) Copy the new files from the temporary directory where you ran 95CLI.EXE to the directory on the Windows 95 client where the SNA client APIs are installed. The default name for this directory is CSNTAPI. 5) Shut down and restart the client machine and restart any applications that use the CSNT SNA client APIs. CONFIGURATION CONSIDERATIONS: Windows 95 and Windows NT Client Configuration: Server names may be specified as TCP/IP hostnames, TCP/IP addresses or SPX server names in the 'Configure APPC Server List' and 'Configure LUA Sessions' via the Client configuration panels. To specify an SPX server name, append '%' to the server name. For example: ABC - TCP/IP hostname for server ABC 1.2.3.4 - TCP/IP address for server 1.2.3.4 ABC% - SPX server ABC CONTACT FOR SUPPORT: If you have any questions, please call the IBM SUPPORT CENTER for your Country. For example in the USA call: 1-800-992-4777 IBM COPYRIGHT INFORMATION: IBM Communications Server for Windows NT version 5.0 Copyright International Business Machines Corporation 1997. All rights reserved. Note to U.S. Government Users - Documentation related to restricted rights - Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. LIMIT OF LIABILITY: License to the contained APAR fixes is conditioned upon the recipient holding a license to the prerequisite product. The license terms and conditions of the APAR fixes are the same as those for the prerequisite product. Please see the product license for specifics.