Please visit the IBM CS/NT support page for product Hints/Tips, APAR downloads, redbooks and other product information at http://www-306.ibm.com/software/network/commserver/windows/support/ Information about IBM Communications Servers can be found at http://www-306.ibm.com/software/network/commserver/ *+-------------------------------------------------------------------+ * * DATE: September 30, 2004 * * APAR: JR20407 * * DESCRIPTION: README FILE IBM Communication Server V6.1.2 for * Windows FIXPACK1. * * PRODUCT: IBM Communication Server V6.1.2 for Windows * * This package contains APAR fixes to the product above. This * package can be distributed to any one who has a license for * this product. * *+-------------------------------------------------------------------+ * * PREREQS: IBM Communications Server V6.1.2 for Windows. * * PACKAGE Description: FIXPACK1 - This package includes the all * APAR maintenance for IBM communications Server v6.1.2 * for Windows Server and API CLIENT since General Availability. * * Some of the apar maintenance has introduced new function and * is documented in the NEWFUNC_SERVER.TXT AND NEWFUNC_CLIENT.TXT * files supplied in the server and client packages. * *+-------------------------------------------------------------------+ * Package includes the following files: * * JR20407.EXE: Self extracting binary that includes all fixpack1 * files including SERVER1.EXE, APIPACK1.EXE, * NEWFUNC_SERVER.TXT, README_SERVER.TXT, * README_CLIENT.TXT AND NEWFUNC_CLIENT.TXT. * * SERVER FILES: * * SERVER1.EXE: Self extracting zip file including Fixpack1 files to be * installed on the CS 6.1.2 Server machine. * INSTFIX.BAT: Installation batch file used to install files contained * in package server1.exe on the CS 6.1.2 Server box. * * README_SERVER.txt: Text file to document contents and * installation instructions for server package. * * NEWFUNC_SERVER.TXT: Text file to document new function supplied * in current server package. * * * CLIENT FILES: * * APIPACK1.EXE: Self extracting zip file including Fixpack1 files * to be installed on CS 6.1.2 API CLIENT machine. * * README_CLIENT.TXT: Text file to document contents and * and installation instructions for client package. * * NEWFUNC_CLIENT.TXT: Text file to document new function supplied * in the client package. * * CLINSTFIX.BAT: Batch file supplied in APIPACK1 to install the * file updates to the SNA API CLIENT workstation. +-----------------------------------------------------------------+ * * APARS INCLUDED IN THIS PACKAGE: * * APARS after CS612 GA : JR19449 Resolves 4 problems on the APICLIENT. JR19492 Cumulative Service APAR for CS/6.1.2. JR19517 BLUESCREEN running EEDLC in PDLNDOEM.SYS. JR19595 TRAP in WINSLI32.DLL using SLI API on server JR19828 TN3270 SERVER connection error TNS0010E. JR19920 BLUESCREEN in APPN.SYS running EEDLC. JR19932 GSKIT DENIAL-OF-SERVICE VULNERABI JR20053 TN3270 Server HANG after network outage. JR19694 CSTRACE AUTO fails if CS installed on other than C:drive. JR19779 NODEOPS allows starting of node when already running. JR19784 SLI_BID gets posted with incorrect data length (0). JR19787 TN3270 SERVER LU HUNG and fails to reconnect. JR19788 APICLIENT problem with SLI-BIND or SLI-STSN extensions. JR19912 SNA HANG when CPs up on link other than pref. NN Srv. lnk. JR19921 SNA LINKs fail to retry to recover link. JR20032 SNA CP-CP sessions fail to switch to prefered NNS. JR20159 EEDLC LIVENESS TIMER default changed to ENABLED. JR20275 Updates to STOP NODE AND LOCATE processing. JR20329 TN3270 SERVER sessions fail to reconnect to same LU. JR19572 APICLIENT HANGs running PCOM 3270 LUA using cut/paste. JR20147 Update CSTRACE to add WRITE-T0-DISK and msgid option. JR20175 Severe Performance problems running HPR over EEDLC. JR20436 CPIC app. HANG running dependent LU62 sessions. +-------------------------------------------------------------------+ FILES that will be upgraded by SERVER Fixpack Installation: Directory of C:\IBMCS ( Communication server Installation Directory ) 09/22/2004 12:37 PM 11,109 appnt.bat 09/22/2004 12:32 PM 826 appnf.bat 09/22/2004 12:32 PM 78,263 ocdnts50.dat 09/22/2004 01:49 PM 28,672 adminpre.dll 09/22/2004 01:55 PM 389,120 adminserver.dll 09/22/2004 02:38 PM 32,768 anutil.dll 09/22/2004 02:55 PM 20,480 anybsd.dll 09/22/2004 03:03 PM 32,768 tn3270d.dll 09/22/2004 02:54 PM 270,336 socketsm.dll 09/22/2004 02:56 PM 20,480 anyqryss.dll 09/22/2004 02:57 PM 110,592 snapmm.dll 09/22/2004 02:49 PM 118,784 snasm.dll 09/22/2004 02:38 PM 20,480 anytrace.dll 09/22/2004 02:39 PM 32,768 anytrc.dll 09/22/2004 02:39 PM 20,480 anytrfmt.dll 09/22/2004 02:56 PM 28,672 anyws2in.dll 09/22/2004 01:30 PM 94,208 Pcscapi.dll 09/22/2004 02:50 PM 20,480 anywsipc.dll 09/22/2004 01:09 PM 425,984 apitrc32.dll 09/22/2004 01:00 PM 151,552 pcsmfcx.dll 09/22/2004 01:31 PM 286,720 pccfgenu.dll 09/22/2004 01:31 PM 81,920 vacgverf.dll 09/22/2004 02:16 PM 493,056 ocdconvt.dll 09/22/2004 01:31 PM 90,112 NODEINIT.DLL 09/22/2004 01:47 PM 36,864 cscm.dll 09/22/2004 01:45 PM 49,152 csformat.dll 09/22/2004 02:03 PM 53,248 csmpccfg.dll 09/22/2004 01:46 PM 188,416 csnia.dll 09/22/2004 02:38 PM 159,744 mptncmm.dll 09/22/2004 01:47 PM 40,960 cstlm.dll 09/22/2004 01:01 PM 143,360 mfcxlite.dll 09/22/2004 02:04 PM 40,960 ldlc.dll 09/22/2004 02:55 PM 32,768 anyws32.dll 09/22/2004 02:38 PM 20,480 ipc.dll 09/22/2004 02:40 PM 114,688 ippmm.dll 09/22/2004 12:54 PM 32,768 adaptinst.exe 09/22/2004 01:39 PM 1,515,520 pcscfg.exe 09/22/2004 03:05 PM 172,032 tn5250wn.exe 09/22/2004 02:00 PM 434,176 pcsnops.exe 09/22/2004 03:02 PM 229,376 tn3270wn.exe 09/22/2004 02:55 PM 20,480 sxmap.exe 09/22/2004 01:58 PM 49,152 rapiserver.exe 09/22/2004 12:54 PM 675,904 snaformat.exe 09/22/2004 02:39 PM 20,480 anyloadr.exe Directory of C:\WINNT\system32 09/22/2004 12:51 PM 36,864 nstrc.dll 09/22/2004 12:54 PM 40,960 Message.dll 09/22/2004 01:29 PM 77,824 winsli32.dll Directory of C:\WINNT\system32\drivers 09/22/2004 01:20 PM 28,672 appnnode.exe 09/22/2004 12:52 PM 16,384 trcboot.exe 09/22/2004 02:59 PM 342,932 anysosgw.sys 09/22/2004 02:23 PM 62,464 pdlndldl.sys 09/22/2004 02:42 PM 37,200 anydlc.sys 09/22/2004 02:26 PM 14,624 pdlnadci.sys 09/22/2004 01:18 PM 1,515,456 appn.sys 09/22/2004 01:19 PM 123,136 appnapi.sys 09/22/2004 01:22 PM 389,472 appnbase.sys (for Windows 2K and above) 09/22/2004 01:09 PM 388,704 appnbase.sys (for Windows NT only) 09/22/2004 02:59 PM 11,400 anysosdd.sys Directory of C:\Program Files\IBM\Trace Facility 09/22/2004 01:07 PM 32,768 cstrcser.exe 09/22/2004 01:07 PM 32,768 cstrace.exe 09/22/2004 02:07 PM 24,576 csstart.exe 09/22/2004 01:06 PM 118,784 trcgui.exe * *+-------------------------------------------------------------------+ * * PACKAGE INSTALLATION INSTRUCTIONS: * * 1. Download JR20407.EXE in Binary format into a temporary directory. * * 2. Run JR20407.exe to uncompress the package which will include * SERVER1.EXE and APIPACK1.EXE. * * To expand SERVER1 package run SERVER1.EXE which will generate * a FILES sub-dir including all server package files. There will * also be registrychange.exe, servicestest.exe, killpcs_agnt.exe * and instfix.bat in current directory but only required for the * package installation. * * If you have SNA API Client Services (Split-stack API Client/Server), * copy APIPACK1.EXE in the client workstation and ref. the * client readme for installation instructions. * * In previous CS/WIN 611 fixpack3 we shipped an NLSPACK3.ZIP * package...There has been no NLS updates since 612 GA so there is * no NLSPACK package included in fixpack1. * * We have included new function updates with this fixpack package. * See the newfunc_server.txt and newfunc_client.txt files for more * details on the new updates in server and client packages. * * 3a.There is a problem with CS/612 GA installation where Trace * Facility does not get installed correctly when CS/612 is * installed on a drive other than the boot drive. The problem * should be resolved prior to installing the server fixpack. * * The Trace Facility gets installed OK on the user supplied * drive but the registry is incorrectly updated to reflect the * BOOT drive for the new trace service CSTRCSER.EXE. * The problem is resolved by modifying the registry to * reflect the IBMCS drive (user supplied) for Service * CSTRCSER.EXE. * * Use regedit to update value for IMAGEPATH key under * \HKLM\SYSTEM\CURRENTCONTROLSET\SERVICES\ * CSTRCSER\ to correct CSTRCSER.EXE path location. * * 3b.INSTFIX.BAT checks if any version of PCOMM * is installed and if true, does not update the Trace Facility * and CS/WIN 6.1.2 will use the Trace Facility installed by PCOM. * If you have installed PCOMM 5.7 CSD3 or PCOMM 5.8 on CS/WIN * 6.1.2, PCOMM will not have installed it's trace facility. * In that case, instfix should be modified to update trace facility by removing * the following line: * * if defined PCOMM_Root goto :CompletedInstall * * 4. Stop Communications Server for Windows (including your node, * Node Operations, Node Configuration, Log Viewer, and any other * CS/WIN components you have started). Note that there may still * be CS/WIN-related services running on the machine after stopping * these applications, but this is normal and should not affect * the installation of this fix pack package. * * 4a. Stop ALL Window applications on this box since a reboot will * be required after running INSTFIX.BAT maintenance installation. * * 4b.Refer the INSTFIX.BAT for details on various installation options. * * INSTFIX.BAT can be run with the following options to preserve * output to a log file. * * INSTFIX > FIX_PACK_1.TXT 2>&1 * for silent install including errors in the log. * * NOTE1: INSTFIX.BAT issues "NET STOP APPNNODE" to * stop APPNNODE Services. * * NOTE2: INSTFIX.BAT also issues "NET STOP LDLCSERV" to * stop LDLCSERV Services. * * INSTFIX.BAT also issues "CSTRACE STOP and CSTRACE SHUTDOWN" to * stop CSTRCSER trace Service. * * NOTE3: INSTFIX will rename the current or target files being * replaced to &file.pre6121, then copy the updated files. * * IF for some reason you rerun INSTFIX.BAT, you will receive * errors during each rename because the &file.prefixpack1 * file will already exist.The original copy of the file will * be preserved in &file.pre6121 and available as a * backup for restore purposes. * * If for some reason you need to restore or backout this * fixpack, you would have to manually rename the * updated file names and restore the original files. * * NOTE4: INSTFIX.BAT issues VER to determine Windows NT or 2000 version. * For Windows 2000 user, INSTFIX.BAT will copy * APPNBASE.SYS as APPNBASE.SYS(default). * For Windows NT user, INSTFIX.BAT will copy * APPNBNT.SYS as APPNBASE.SYS * * NOTE5: After all the files are copied, INSTFIX.BAT automatically issues * "SERVICESTEST -c LDLCSERV" command to initialize LDLCSERV service. * * NOTE6: INSTFIX.BAT automatically issues "NET START LDLCSERV" to * start LDLCSERV service. * * NOTE7: The default value of the registry key * HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Communications Server\ * CurrentVersion\VersionNumber will be modified from 6120 to 6121. * * 5). After running INSTFIX.BAT confirm ALL component parts listed above * reflect new dates. If they do NOT, then you must manually copy them * after you REBOOT but prior to starting any CSNT Services. ALL files * must reflect updated dates or CSNT will not function properly. * * 6). Shutdown and Restart WINDOWS to reboot the machine. * * * 7). You can now start CSNT Node Operations and configure the new * available functions. * * 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-IBM-SERV * * IBM COPYRIGHT INFORMATION: * * IBM Communications Server V6.1.2 for Windows. * * Copyright International Business Machines Corporation 2004. * 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. * ************************************************************************