IBM Communications Server for Windows
Version 6.1.2 FixPack 3 (JR22681)
Readme

© Copyright International Business Machines Corp. 2005
All Rights Reserved
Licensed Material - Property of IBM
US Government Users Restricted Rights - Use, duplication or
disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Table of Contents
1 About this update
2 National Language Support (NLS)
3 Server update information
4 Client update information
5 Uninstall information
6 Web site and support information
7 Notices and trademarks

1 About this update

Section Table of Contents
1.1 New in this fixpack
1.2 Product fix history
1.3 Files included

IBM Communications Server for Windows provides SNA connectivity for Windows systems, allowing it to connect to IBM z/OS Communications Server and other SNA implementations that support LLC, SDLC, X.25, Channel, and Enterprise Extender connections.

CS/WIN Version 6.1.2 FixPack 3 in an upgrade that includes FixPack 3 updates. Is is not a full install, and requires that V 6.1.2 is installed at GA level or with FixPack 1 or FixPack 2 installed. Only fixpacks greater than FixPack 3 should be installed after this installation.

The 6.1.2.3 refresh of CS/WIN provides a complete install package with FixPack 3 integrated. This is not that package. For more information, see the CS/WIN support document "Communications Server for Windows, Version 6.1.2 -- Latest Fix Pack"

This document contains information supplementary to the online help and the publications. It describes such things as newly-added functions, hints, tips, restrictions, and corrections.

Thank you for choosing Communications Server!

[Return to top] [Table of Contents]

1.1 New in this fixpack

For details on other new functions, see the "New function" subsections of the Server and Client update information sections. In addition, all APAR fixes since GA up to and including FixPack 3 are included.

[Return to top of section] [Return to top of document] [Table of Contents]

1.2 Product fix history

This update provides fixes to the CS/WIN 6.1.2 product (6.1 with CSD 2): all fixes up to and including FixPack 3.

Check the web sites listed in section 6 for the latest information about this product.

Notes:

  1. This fixpack will be a pre-requisite of all future CS/WIN 6.1.2 APARs.
  2. This fixpack should only be applied to CS/WIN 6.1.2 at GA level or with FixPack 1 or FixPack 2. Only fixpacks greater than FixPack 3 should be installed after this installation.
  3. The CS/WIN 6.1.2.3 product refresh released in 4th quarter 2005 replaces the 6.1.2 GA product on new install media. The CS/WIN 6.1.2.3 refresh includes FixPack 3 and is equivalent to installing CS/WIN 6.1.2 GA and then applying FixPack 3. FixPack 3 should not be applied to the 6.1.2.3 refresh.

[Return to top of section] [Return to top of document] [Table of Contents]

1.3 Files included

This package includes the following files:

JR22681.EXE Self extracting binary that includes all FixPack 3 files: README.HTM, NLSPACK3.EXE, SERVER3.EXE, APIPACK3.EXE
README.HTM Documentation of content, fixes, new functions, and install instructions for all packages.
NLSPACK3.EXE Self extracting executable that contains FixPack 3 language files to be installed on the CS/WIN 6.1.2 Server machine. The English version of this module is installed as part of the server install by default. If CS/WIN 6.1.2 was installed using a non-English language, you must install the appropriate version of this NLS module after the server installation.
SERVER3.EXE Self extracting executable that contains FixPack 3 files to be installed on the CS 6.1.2 Server machine.
APIPACK3.EXE Self extracting executable that contains FixPack 3 files to be installed on CS 6.1.2 API Client machine.

[Return to top of section] [Return to top of document] [Table of Contents]

2 National Language Support (NLS)

Section Table of Contents
2.1 Files included
2.2 Install instructions

[Return to top] [Table of Contents]

2.1 Files included - NLS

NLSPACK3.EXE: Includes the NLS package update for all CS/WIN 612 languages. While uncompressed will create sub-directories for each of the supported languages listed below.

CHS : Simplified Chinese
CHT : Traditional Chinese
DEU : German
ESP : Spanish
FRA : French
ITA : Italian
JPN : Japanese
KOR : Korean
PTB : Brazilian Portuguese

pccfgXXX.dll: FIXPACK3 update for Configuration Gui.

Note: where xxx will reflect the cs/win supported language.
PCSNOPS.EXE: FIXPACK3 update for Node Ops.
PCSTRCRES.DLL: FIXPACK3 update to Trace update.
NLS_INSTFIX.BAT: Batch file to install NLSPACK3 package updates.

[Return to top of section] [Return to top of document] [Table of Contents]

2.2 Install instructions - NLS

The NLS update can be integrated into and installed as part of the server update or can be installed separately after the server update by running nls_instfix.bat.

2.2.1 Integrated with server update
2.2.2 Separate, after server update

[Return to top of section] [Return to top of document] [Table of Contents]

2.2.1 Integrated with server update

Instructions to update the server package with the NLS updates:

  1. Replace the pcsnops.exe and pcstrcres.dll in the server update package with those included from the appropriate sub-directory of this package.
  2. Copy the file PCCFG.XXX.DLL from the NLS package directory to the server package directory. Note, this file will not exist in the server package because it is unique for each language.
  3. Update the server INSTFIX.BAT file with an appropriate rename and copy statement for the PCCCFGXXX.DLL module. (where XXX reflects the language). See existing rename and copy statements in INSTFIX.BAT for format.

Perform the installation of the server package update. See section 3 for instructions.

[Return to top of section] [Return to top of document] [Table of Contents]

2.2.2 Separate, after server update

Install instructions:

  1. Install the server updates first, following the instructions in section 3.
  2. Stop the CS/WIN node and all applications that use CS/WIN.
  3. Copy NLSPACK3.EXE to a temporary directory.
  4. Uncompress and extract the files from the package using the command:

    NLSPACK3.EXE /d

    The package will expand and create a sub-directory for the NLS updates for each supported CS/WIN language.

  5. Choose the appropriate NLS update based on the CS/WIN language that is installed, and go to that sub-directory.
  6. Review the comments in the NLS_INSTFIX.BAT file for specific usage instructions. For example:
    • NLS_INSTFIX (no parameters; environment variables will be used)
    • NLS_INSTFIX > nlsfp3.txt 2>&1 (silent install)
    • NLS_INSTFIX c:\ibmcs (specify the directory)
    • NLS_INSTFIX c:\ibmcs > nlsfp3.txt 2>&1 (silent install, specify directory)
  7. Reboot and start the CS/WIN node.

NOTE: NLS_INSTFIX.BAT checks if a PCOMM version less than 5.7 CSD3 is installed and if true, does not update the Trace Facility. CS/WIN 6.1.2 would use the Trace Facility installed by PCOMM. If you have installed PCOMM 5.7 CSD3 or PCOMM 5.8 on CS/WIN 6.1.2, PCOMM will not install its Trace Facility. In this case, NLS_INSTFIX will update the CS/WIN 6.1.2 Trace Facility.

If versions of PCOMM prior to 5.7 CSD3 are installed, you will not have any of the CS/WIN 6.1.2 Trace Facility updates or enhancements.

[Return to top of section] [Return to top of document] [Table of Contents]

3 Server update information
Section Table of Contents
3.1 APARs included
3.2 Files updated
3.3 New function
3.4 Install instructions

[Return to top] [Table of Contents]

3.1 APARs included

New APARs included in FixPack 3 since FixPack 2
JR20878TRAP IN SPLITSTACK - CLIENT SERVER
JR21008CRASH IN APPN.SYS HANDLING EEDLC link deactivation.
JR21053SLI-CLOSE HANG ON SNA API CLIENT.
JR21104NF to Information Bundler to run Silent/Quiet.
JR21107NODE FAILS TO START AT BOOT DUE TO PDLNDLDL.SYS.
JR21180Disable Active Directory for TNSERVER.
JR21204VTAM ABEND0A9 RCFF13 ISTRPCRS due to CS/WIN HPR.
JR21237CRASH IN SNAPS APPN.SYS.
JR21250Add CONNECTION KEEP ALIVE for implicit EEDLC links.
JR21259SNAP UPDATES.
JR21261CRASH IN TN3270WN.EXE during cleanup up.
JR21299LU FORMAT ERROR,INVALID CHANGE DIRECTION. Sense 400D0000
JR21316EEDLC SOURCE PORTS now use 12000-120004.
JR21437BLUESCREEN using IBM4758 Hardware Encryption card.
JR21518TNserver LU HANG processing SHUTD/SHUTC.
JR21543APAR TO DOCUMENT CS/WIN 6.1.1 Fixpack4.
JR21544AFTER APPLYING JR20053 TN3270 CLIENT can't reconnect.
JR21546A PACKAGE TO HELP CLEANUP CS/WIN files from bad install.
JR21604RMCSNT does not remove new 612 device drivers.
JR21848LUA API changed to handle bind differently.
JR21850CSDISPLAY COMMAND FAILS TO DISPLAY tnserver data.
JR21942Link fails to activate after host IPL.
JR22234BLUESCREEN IN APPNBASE.
JR22419NODE CONFIG displays wrong adapter/sap.

APARS included from FixPack 2
JR20370Support added for SSE BITS in APPN locates.
JR20377BLUESCREEN in EEDLC reporting link failure.
JR20407CS/WIN 6.1.2 FIXPACK1.
JR20453BLUESCREEN in EEDLC in link recovery.
JR20454Hang in Node Configuration Utility.
JR20352TRACE format incorrect.
JR20241Access violation in client CCS.DLL.
JR20491Trace GUI main menus blank in CS/WIN NLS versions.
JR20436CPIC appl. hangs running dependent LU62.
JR20487BLUESCREEN in APPN.SYS processing locates.
JR20566HPR Performance Enhancements.
JR20830Trap when selecting SNA counters in MS Perfmon utility.
JR21726Sense code 20010000/20110000 when segmenting data running PU concentrator or TN3270E Gateway
JR21848RUI (LUA API) changes in processing incoming BIND

APARS included from FixPack 1
JR19449Resolves 4 problems on the APICLIENT.
JR19492Cumulative Service APAR for CS/6.1.2.
JR19517BLUESCREEN running EEDLC in PDLNDOEM.SYS.
JR19595TRAP in WINSLI32.DLL using SLI API on server
JR19828TN3270 SERVER connection error TNS0010E.
JR19920BLUESCREEN in APPN.SYS running EEDLC.
JR19932GSKIT DENIAL-OF-SERVICE VULNERABI
JR20053TN3270 Server HANG after network outage.
JR19694CSTRACE AUTO fails if CS installed on other than C:drive.
JR19779NODEOPS allows starting of node when already running.
JR19784SLI_BID gets posted with incorrect data length (0).
JR19787TN3270 SERVER LU HUNG and fails to reconnect.
JR19788APICLIENT problem with SLI-BIND or SLI-STSN extensions.
JR19912SNA HANG when CPs up on link other than pref. NN Srv. lnk.
JR19921SNA LINKs fail to retry to recover link.
JR20032SNA CP-CP sessions fail to switch to prefered NNS.
JR20159EEDLC LIVENESS TIMER default changed to ENABLED.
JR20275Updates to STOP NODE AND LOCATE processing.
JR20329TN3270 SERVER sessions fail to reconnect to same LU.
JR19572APICLIENT HANGs running PCOM 3270 LUA using cut/paste.
JR20147Update CSTRACE to add WRITE-T0-DISK and msgid option.
JR20175Severe Performance problems running HPR over EEDLC.
JR20436CPIC app. HANG running dependent LU62 sessions.

[Return to top of section] [Return to top of document] [Table of Contents]

3.2 Files updated - server

The server update of this fixpack will replace existing files with those in these lists.

Directory of C:\IBMCS (Communications Server installation directory) 

10/19/2005  08:09 PM            32,768 adaptinst.exe
10/19/2005  09:57 PM            40,960 adminapi.dll
10/19/2005  09:48 PM            28,672 adminpre.dll
10/19/2005  09:57 PM           389,120 adminserver.dll
10/19/2005  09:19 PM            73,728 adRAPIClient.dll
10/19/2005  10:01 PM            36,864 adRAPIStubs.dll
10/19/2005  09:17 PM            49,152 adRapiUtil.dll
10/19/2005  10:30 PM            69,632 aftp.exe
10/20/2005  09:17 AM            32,768 anutil.dll
10/20/2005  09:48 AM            20,480 anybsd.dll
10/19/2005  09:30 PM            20,480 ANYINIT.dll
10/20/2005  09:18 AM            20,480 anyloadr.exe
10/19/2005  09:31 PM           110,641 anymsg.dll
10/20/2005  09:49 AM            20,480 anyqryss.dll
10/20/2005  09:17 AM            20,480 anytrace.dll
10/20/2005  09:18 AM            32,768 anytrc.dll
10/20/2005  09:18 AM            20,480 anytrfmt.dll
10/20/2005  09:49 AM            28,672 anyws2in.dll
10/20/2005  09:48 AM            32,768 anyws32.dll
10/20/2005  09:38 AM            20,480 anywsipc.dll
10/19/2005  08:38 PM           430,080 apitrc32.dll
10/19/2005  08:10 PM            32,768 cpicmsg.dll
10/19/2005  09:44 PM            36,864 cscm.dll
10/19/2005  10:22 PM            32,768 csdisplay.exe
10/19/2005  09:33 PM            32,768 csevtmsg.dll
10/19/2005  09:40 PM            49,152 csformat.dll
10/19/2005  09:46 PM            32,768 cslba.dll
10/19/2005  10:22 PM            20,480 cslic.exe
10/19/2005  08:21 PM            32,768 csmls.dll
10/19/2005  09:40 PM            45,056 csmmsg.dll
10/19/2005  09:42 PM           188,416 csnia.dll
10/19/2005  09:35 PM            24,576 csnlg.dll
10/19/2005  08:29 PM           135,168 CSNTPD.exe
10/19/2005  09:47 PM            28,672 csqel.dll
10/19/2005  10:22 PM            20,480 csquery.exe
10/19/2005  09:44 PM            73,728 cssec.dll
10/19/2005  09:46 PM            40,960 cssma.dll
10/19/2005  10:22 PM            24,576 csstart.exe
10/19/2005  10:22 PM            24,576 csstop.exe
10/19/2005  09:44 PM            40,960 cstlm.dll
10/19/2005  09:41 PM            20,480 csutlc.dll
10/19/2005  09:41 PM            24,576 csutls.dll
10/19/2005  09:43 PM            24,576 csxlib.dll
10/19/2005  09:36 PM            16,384 cs_waitnt.exe
10/19/2005  09:14 PM            20,480 defsecur.dll
10/19/2005  08:54 PM            32,768 discovrd.dll
10/19/2005  08:39 PM           118,784 dlctrc32.dll
10/19/2005  09:19 PM            32,768 emutocfg.dll
10/19/2005  09:14 PM            53,248 fmtcapi.dll
10/19/2005  09:14 PM            20,480 fmtmsg.dll
10/19/2005  09:16 PM            49,152 FMTNODE.DLL
10/19/2005  10:03 PM            20,480 FMTNOPS.dll
10/19/2005  09:30 PM            53,248 hotstby.dll
10/19/2005  09:34 PM            69,632 ibmsa.dll
10/19/2005  09:34 PM            98,304 ibmslp.dll
10/20/2005  09:18 AM            20,480 ipc.dll
10/20/2005  09:21 AM           114,688 ippmm.dll
10/19/2005  10:14 PM            40,960 ldlc.dll
10/19/2005  09:30 PM            20,480 limgmt.dll
10/19/2005  09:31 PM            65,536 limgmtd.dll
10/19/2005  10:16 PM            32,768 lspmsg.dll
10/19/2005  08:02 PM            32,768 MILLUTIL.DLL
10/20/2005  09:17 AM           159,744 mptncmm.dll
10/19/2005  08:28 PM           155,648 msgbrwsr.exe
10/19/2005  08:09 PM            28,672 MSGIO.dll
10/19/2005  09:16 PM            94,208 NODEINIT.DLL
10/19/2005  07:36 PM             8,943 ntcmpd.bat
10/19/2005  10:39 PM           494,080 ocdconvt.dll
10/19/2005  07:50 PM            78,377 ocdnts50.dat
10/19/2005  09:15 PM           290,816 pccfgenu.dll
10/19/2005  09:13 PM            94,208 Pcscapi.dll
10/31/2005  07:55 AM            32,768 pcscca.exe
10/19/2005  09:29 PM         1,519,616 pcscfg.exe
10/19/2005  08:20 PM           151,552 pcsmfcx.dll
10/19/2005  10:06 PM           434,176 pcsnops.exe
10/19/2005  09:16 PM            24,576 PCS_AGNT.EXE
10/19/2005  09:16 PM            16,384 PCS_STAB.DLL
10/19/2005  10:40 PM            36,864 pdlcsmsg.dll
10/19/2005  10:40 PM            52,076 pdlcsmsg.hlp
10/19/2005  10:49 PM             9,216 pdlwofmt.dll
10/19/2005  08:29 PM            45,056 rasbut.exe
10/19/2005  10:16 PM            20,480 rcmdfmtr.dll
10/19/2005  10:15 PM            40,960 rcmdsa.exe
10/19/2005  08:29 PM            20,480 rmcsnt.exe
10/19/2005  08:29 PM            49,152 Servcsnt.exe
10/19/2005  09:34 PM            24,576 slpapi.dll
10/19/2005  09:33 PM            20,480 slpform.dll
10/19/2005  08:08 PM           675,904 snaformat.exe
10/20/2005  09:52 AM           110,592 snapmm.dll
10/20/2005  09:37 AM           118,784 snasm.dll
10/20/2005  09:46 AM           270,336 socketsm.dll
10/19/2005  09:13 PM            73,728 SPELLING.DLL
10/20/2005  09:48 AM            20,480 sxmap.exe
10/28/2005  06:48 AM            32,768 tn3270d.dll
10/28/2005  06:47 AM           229,376 tn3270wn.exe
10/28/2005  06:48 AM            20,480 tn32bind.dll
10/20/2005  10:05 AM            53,248 tn5250d.dll
10/20/2005  10:04 AM           172,032 tn5250wn.exe
10/20/2005  10:01 AM            49,152 tniptkt.dll
10/19/2005  09:31 PM           110,642 tnsmsg.dll
10/19/2005  10:32 PM           147,456 uninst.dll
10/19/2005  09:31 PM            20,480 vacgcon.exe
10/19/2005  09:32 PM            61,440 vacgfenu.dll
10/19/2005  09:16 PM            81,920 vacgverf.dll
10/19/2005  09:32 PM           110,592 vacgwin.exe

Directory of %systemroot%\system32 

10/19/2005  08:54 PM            24,576 appcmsg.dll
10/19/2005  08:51 PM            20,480 cmnapi32.dll
10/19/2005  09:35 PM            36,864 cslicmon.exe
10/19/2005  08:35 PM            20,480 csloadfx.dll
10/19/2005  08:53 PM            28,672 csvmsg.dll
10/19/2005  09:36 PM            16,384 cs_plusutil.exe
10/19/2005  08:06 PM            24,576 fmt_util.dll
10/19/2005  09:40 PM            20,480 ibmcsprf.dll
10/19/2005  08:10 PM            40,960 Message.dll
10/19/2005  08:04 PM            36,864 nstrc.dll
10/19/2005  08:09 PM            24,576 pcsw32x.dll
10/31/2005  07:55 AM            36,864 pcs_perf.dll
10/19/2005  08:54 PM            24,576 ruimsg.dll
10/19/2005  08:53 PM            65,536 wappc32.dll
10/19/2005  08:18 PM           135,168 wcpic32.dll
10/19/2005  09:13 PM            24,576 winAPPC.dll
10/19/2005  08:18 PM            24,576 wincpic.dll
10/19/2005  09:13 PM            24,576 winCSV.dll
10/19/2005  08:53 PM            65,536 wincsv32.dll
10/19/2005  08:52 PM            32,768 winms32.dll
10/31/2005  07:52 AM            36,864 winnof32.dll
10/19/2005  09:13 PM            24,576 winrui.dll
10/19/2005  08:53 PM            36,864 winrui32.dll
10/19/2005  09:13 PM            24,576 winsli.dll
10/19/2005  09:12 PM            77,824 winsli32.dll
10/19/2005  08:51 PM            28,672 wpdapi32.dll

Directory of %systemroot%\system32\drivers 

10/20/2005  09:22 AM            37,244 anydlc.sys
10/20/2005  09:53 AM            11,400 anysosdd.sys
10/20/2005  09:53 AM           342,932 anysosgw.sys
10/31/2005  07:49 AM         1,569,664 appn.sys
10/31/2005  07:52 AM           124,448 appnapi.sys
10/31/2005  07:55 AM           397,856 appnbase.sys
10/19/2005  08:54 PM            32,768 appnnode.exe
10/19/2005  09:46 PM            20,480 csit.exe
10/19/2005  10:15 PM            45,056 csrcmds.exe
10/19/2005  09:35 PM            16,384 ibmsa.exe
10/20/2005  09:09 AM            28,672 ldlcserv.exe
10/20/2005  09:09 AM            40,960 ldlcserv6.exe
10/19/2005  08:58 PM           102,560 llc2.sys
10/19/2005  10:56 PM            14,624 pdlnadci.sys
10/20/2005  09:09 AM            64,512 pdlndldl.sys
10/20/2005  09:09 AM            70,656 pdlndldl6.sys
10/19/2005  10:50 PM            17,408 pdlndoem.sys
10/19/2005  10:50 PM            65,536 pdlndsdl.sys
10/19/2005  10:51 PM            66,528 pdlnemap.sys
10/19/2005  10:44 PM            18,720 pdlnepkt.sys
10/19/2005  09:47 PM            38,944 qeldrvr.sys
10/19/2005  10:02 PM            49,152 rapiserver.exe
10/19/2005  08:05 PM            16,384 trcboot.exe

Directory of DRIVE_LETTER:\Program Files\IBM\Trace Facility where DRIVE_LETTER is the installation drive of CS/WIN or of PCOMM if PCOMM 5.7 CSD3 or above is installed. 

10/19/2005  07:36 PM             1,456 appnf.bat
10/19/2005  07:36 PM            11,109 appnt.bat
10/19/2005  08:33 PM            32,768 cstrace.exe
10/19/2005  08:34 PM            32,768 cstrcser.exe
10/19/2005  08:30 PM            28,672 fmteng.dll
10/19/2005  08:30 PM            28,672 pcsfmtpi.dll
10/19/2005  08:31 PM           118,784 trcgui.exe

[Return to top of section] [Return to top of document] [Table of Contents]

3.3 New function - server

New function added in FixPack 3
General enhancements
1. An option is provided to NOT publish TN3270 services to the LDAP Active Directory. By setting the "TN3270AdvToADS" keyword under HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Communications Server\current\Version\Config with a DWORD value of "0", the TN3270 advertisements will be disabled.

Steps to disable publishing:

  1. Stop the existing running node throuh pcsnops.exe (SNA Node Ops).
  2. Start->Run->Regedit
  3. Go to HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Communications Server\CurrentVersion\Config
  4. Right click on the right pane (the pane opposite to key browsing).
  5. Add a new DWORD key with name TN3270AdvtToADS if it does not exist, and set it to the value to "0".
  6. Restart the node.

2. A new configuration parameter has been added to allow a port to be configured to allow only a specific number of implicit inbound links for LAN connections.

The parameter "IMPLICIT_LS_LIMIT" has been added under PORT_LAN_SPECIFIC_DATA. The allowed range of values is between 0 and 65535. A value of 65535 indicates that no implicit links are allowed. The default value is 0 meaning "no limit".

This parameter affects only implicit links, links that are dynamically created to accept an inbound connection where the local SAP, remote SAP, and remote MAC address do not match any explicitly defined links. . To limit the total number of inbound links, use the existing PORT parameter INB_LINK_ACT_LIM=0, which is documented in the CS/WIN Configuration File Reference.

SNAFORMAT enhancements
1. Option (-h) has been added to SNAFORMAT to disable HPR formating in the summary trace.

By removing the HPR flows you can follow the API flows easier.. You would disble the HPR flows by entering:

snaformat -h nstrc.tlg

Information Bundler enhancements
1. Option -q (Quiet mode) to suppress popups has been added to csntpd.exe.

This option will allow you to remotely capture an information bundler (cspddata.exe) and allevitate the requirement to "press any key to continue" and the popup window indicating the registry has been copied.

Option -s Suppress registry collection. This option suppresses the registry collection and hence output information bundler will not collect registry.dat nor csntreg.dat.

Note: The default infobundler behavior will be to show popups and collect registry information when ran with no options.

EEDLC IPV4 and IPV6 enhancements
1. EEDLC can now be configured to run IPv4 (IBMEEDLC) and IPv6 (IBMEE006), each protocol using a different DLC: IBMEEDLC for IPV4 and IBMEE006 for IPV6. The outgoing links must be defined on the correct DLC type. IPv6 is supported only on the Windows 2003 (SP1) or XP (SP2) and above Operating Systems.

Existing EEDLC definitions from FixPack 2 and earlier, which used a parameter to specify whether the DLC was IPV4 or IPV6, will all be treated as IPV4 definitions because that parameter is no longer used. Links using IPV6 must be reconfigured to the new IBMEE006 DLC.

IBMCSADMIN capabilities
1. A user who is a member of the IBMCSADMIN group can manage the SNA resources and does not require Administrator authority. With previous releases of Communications Server, only Administrator authority allowed management of SNA resources.

A user who is not part of either Administrator or IBMCSADMIN groups will not be allowed to control SNA resources, such as starting and stopping the node, running command line traces, etc.


New function added in FixPack 2
General enhancements
1. Support for TCP/IP Version 6 has been added in this fixpack. The function is currently supported only on WINDOWS 2003 or XP.

To configure CS/WIN to run with IPV6 you must select IPV6 in the DLC profile provided that IPv6 is installed in the Operating system.

You can configure and run either IPV4 or IPV6 but not both. You can configure only ONE EEDLC dlc per ACG file. You can have separate ACG files to run IPv4 or IPV6. The default is IPV4.


New function added in FixPack 1
General enhancements
1. SNA Function addition of LU 6.2 session level timeout based on LU, partner LU or mode

LU62_timeout as documented in JR16867 (included in CSNT6.1.2 GA) to terminate the lu62 session on completion of the lu62 conversation. The feature was included in CS/2 and now is configurable only in the CSNT ASCII configuration file. The setting is global on all lu62 sessions with the exception of the IBM Service TPs such as the CPSVCMGR session. The lu62_timeout_value is in seconds. 

LU62_TIMEOUT=(
LU62_TIMEOUT_RESOURCE_TYPE=GLOBAL_TIMEOUT
LU62_TIMEOUT_VALUE=20
)
New in this APAR JR20407, three new options have been added for LU62_TIMEOUT_RESOURCE_TYPE:
  • LOCAL_LU_TIMEOUT = 2
  • PARTNER_LU_TIMEOUT = 3
  • MODE_TIMEOUT = 4
With these new types there is also a new parameter LU62_TIMEOUT_RESOURCE_NAME which specifies the LOCAL_LU name, PARTNER_LU name, or MODE name. The LU62_TIMEOUT is used only for sessions with the specified LOCAL_LU, PARTNER_LU or MODE name. NOTE: LU62_TIMEOUT is configurable only in the ACSII configuration file (.acg).


EEDLC enhancements
1. NEW FUNCTION support of option to not use Host Name on Connection Networks: Host name support for Enterprise Extender DLC connection networks is supported in GA code.

However, if there is not a firewall in the network that requires host name resolution to an IP address separately on each end, then the host name would not have to be sent on the LOCATEs and resolved on the receiver. This is the way that EEDLC connection networks operate in CSNT6.1.1.

There is now a checkbox under the EEDLC device configuration labeled "Do not Use IPV4 Host Name". The default is not checked. If it is checked, then the connection network A5 control vectors do not include the host name (making shorter LOCATEs) and the remote just uses the IP address that is sent.

If host name resolution fails on an EEDLC link and an IP address is present, then attempt to connect using the IP address.

2. EEDLC link liveness timer is now always on. The range that the liveness timer can be set to was increased from 59 seconds to 255 seconds on either the EEDLC device or on the connection definition. The default remains at 10 seconds.

3. Changed the default effective capacity of EEDLC and LLC2 links from 133 (16 Mb) to 160 (157 Mb) to improve HPR ramp up performance (throughput is improved).

Command line trace enhancements
Note: If versions of PCOMM prior to 5.7 CSD3 are installed, you will not have any of the CS/WIN 612 Trace facility enhancements.

1. Trace to multiple trace files is supported from the command line (cstrace). The file size and the number of files can be specified. Note that the /w and /n functions are new functions and help is not available for non-English versions.

to copy to multiple nstrcxxx files add /w yyy (where yyy is Kb file size) to the start statement cstrace start

cstrace start /r /w 4000 /n 5

resets traces and writes to nstrc001,nstrc002,nstrc003,nstrc004,nstrc005 each about 4000 KB. When the files are full, tracing continues by cycling through the files.

Note that /w cannot be used with /b and /s.

2. New function is added to stop trace from the command line based on message ID. Note that the /m function is a new function and help is not available for non-English versions.

To stop on message id, run

cstrace start /m PCS4661I

where PCS4661I (the messageid) is issued to the message log.

To disable traces on message ID, run

cstrace stop /m PCS4661I

Tracing then continues until you run

cstrace stop

3. Autostart trace option was incorrectly documented as /f instead of /e. To enable the autostart option use the following command:

cstrace auto /e 1 /l [file name]

To disable the autostart option use the following command:

cstrace auto /e 0

To turn on/off APPC API and EEDLC tracing, the format of the trace option file should be:

/f 3 /c 7 /o 1
/f 4 /c 22 /o 1 2 8

4. APPNT.BAT has been updated describing new functions. APPNT.bat is a batch file to start traces from the command line. The default API option is to truncate the data at 128 bytes. IPSTRACE is on by default. Increased the trace buffer size.

5. CSTRACE SHUTDOWN is added to APPNF to reset trace flags. APPNF.bat is a batch file to stop and format traces.

6. SNAFORMAT ENHANCEMENTS:
SNAFORMAT creates summary and detail files on traces with SDLC, EEDLC DLCs (in addition to existing LLC2 capability) and SLI, RUI, CPIC and APPC apis by formatting the nstrc.tlg to nstrc.sum and nstrc.det.

[Return to top of section] [Return to top of document] [Table of Contents]

3.4 Install instructions - server

Installing the fixpack on the system:
  1. Download JR22681.EXE in Binary format into a temporary directory.

  2. Run JR22681.exe to uncompress the package which will include SERVER3.EXE and APIPACK3.EXE.

    To expand SERVER package run SERVER3.EXE which will generate a Server 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.

    1. If you have SNA API Client Services (Split-stack API Client/Server), copy APIPACK3.EXE in the client workstation and see section 4 for install instructions.
    2. NLSPACK3.exe contains non-English language updates. Customers running non-English versions of CS/WIN need to also install NLSPACK package. English package is installed by default as part of INSTFIX.BAT and does not require separate installation of NLSPACK3.exe. See section 2 for install instructions.

  3. New function updates have been included with this fixpack package. See section 3.3 for more details on the new updates.
    1. There is a problem with CS/WIN 6.1.2 GA installation where the Trace Facility does not get installed correctly when CS/WIN 6.1.2 is installed on a drive other than the boot drive. This should be corrected prior to installing the server fixpack.

      The Trace Facility is installed on the user-designated drive, but the registry is incorrectly updated to reflect the BOOT drive for the new trace service CSTRCSER.EXE. To correct this, modify the registry to reflect the correct drive for the service CSTRCSER.EXE.

      Use regedit to update value for the IMAGEPATH key under \HKLM\SYSTEM\CURRENTCONTROLSET\SERVICES\CSTRCSER\ to the correct CSTRCSER.EXE path location.

    2. INSTFIX.BAT checks if a PCOMM version less than 5.7 CSD3 is installed and if true, does not update the Trace Facility. CS/WIN 6.1.2 would use the Trace Facility installed by PCOMM. If you have installed PCOMM 5.7 CSD3 or PCOMM 5.8 on CS/WIN 6.1.2, PCOMM will not install its Trace Facility. In this case, INSTFIX will update the CS/WIN 6.1.2 Trace Facility.

      If versions of PCOMM prior to 5.7 CSD3 are installed, you will not have any of the CS/WIN 6.1.2 Trace Facility updates or enhancements.

      There is a problem with some versions of PCOMM prior to 5.7 CSD3 where using ADD/REMOVE PROGRAMS to remove PCOMM removes the Service APPNNODE from the REGISTRY. CS will NOT run successfully without this registry entry. While this problem has been resolved in later PCOMM versions you can do the following to address the problem.

      The recommended procedure in this situation is as follows:

      1. Remove PCOMM using ADD/REMOVE PROGRAMS
      2. Remove CS/WIN 612
      3. Re-install CS/WIN 612
      4. Install PCOMM 5.8 (or PCOMM 5.7 CSD3 or later)
      5. Apply CS/WIN 612 Fixpack2 maintenance upgrade

  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.
    1. Stop ALL Window applications on this box since a reboot will be required after running INSTFIX.BAT maintenance installation.
    2. 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, such as for silent install including errors in the log.

    INSTFIX > FIX_PACK_3.TXT 2>&1

    NOTE 1: INSTFIX.BAT issues
    "NET STOP APPNNODE" to stop APPNNODE Services.
    "NET STOP LDLCSERV" to stop LDLCSERV Services.
    "CSTRACE STOP" and "CSTRACE SHUTDOWN" to stop CSTRCSER trace Service.

    NOTE 2: INSTFIX will rename the current or target files being replaced to &file.pre6123, then copy the updated files.

    If for some reason you rerun INSTFIX.BAT, you will receive errors during each rename because the &file.pre6123 file will already exist.The original copy of the file will be preserved in &file.pre6123 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.

    NOTE 3: INSTFIX.BAT issues VER to determine Windows NT or 2000 version.

    For Windows 2000 user, INSTFIX.BAT will copy
    APPNBASE.SYS as APPNBASE.SYS
    LLC2W2K.sys as LLC2.SYS

    For Windows NT and Window 2000 user, INSTFIX.BAT will copy
    APPNBNT.SYS as APPNBASE.SYS
    LLC2NT.sys as LLC2.SYS

    NOTE 4: After all the files are copied, INSTFIX.BAT automatically issues
    "SERVICESTEST -c LDLCSERV" command to initialize LDLCSERV service.
    "NET START LDLCSERV" to start LDLCSERV service.

    NOTE 5: The default value of the registry key HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Communications Server\CurrentVersion\VersionNumber will be changed to 6123.

  5. After running INSTFIX.BAT, confirm ALL component parts listed in section 3.2 reflect new dates. If they do NOT, then you must manually copy them after you REBOOT but prior to starting any IBMCS Services. ALL files must reflect updated dates or IBMCS will not function properly.

  6. Run the batch "AccessControlSettings.bat"

    7. NOTE: If you want restricting the user (NON-Administrator) from controlling SNA resources like Stoping/Starting the node/link etc., you have to run the above batch file and follow the step (7) mentioned below.

  7. If you are running Windows XP or 2003 and above do the following: (For Windows NT and 2000, skip this step.)
    1. Run regedit to start the registry editor (start->run then type regedit).
    2. Navigate to HKLM\Software\IBM\Communications Server
    3. Right-click on Communications Server and select Permissions.
    4. Click the "Add" button.
    5. Click the "Advanced" button.
    6. Click the "Find Now" button.
    7. Select "IBMCSADMIN" from the resulting list and click the "OK" button.
    8. Click the "OK" button.
    9. Select "IBMCSADMIN" from the list.
    10. Check the appropriate box to allow "Full Control".
    11. Click the "OK" button.
    12. Navigate to HKLM\Software\IBM\OEM_CONFIG and repeat the steps from "C" to "K".
    13. Exit the registry editor.

  8. Shutdown and Restart WINDOWS to reboot the machine.

  9. You can now start IBMCS Node Operations and configure the new available functions.

[Return to top of section] [Return to top of document] [Table of Contents]

4 Client update information
Section Table of Contents
4.1 APARs included
4.2 New function
4.3 Install instructions

[Return to top] [Table of Contents]

4.1 APARs included

New APARs included in FixPack 3 since FixPack 2
None.

APARs included from previous fixpacks
JR19572PCOMM 3270 LUA hangs running on SNA API CLIENT.
JR19449Apar addresses following problems:
  • Incoming attach intermittently fails.
  • Multiple user trace problems.
  • Client password authentication problems using current userid.
  • Erraneous return code corrected for RUI_INIT verb.
JR19788SLI BIND or STSN extensions routines not called.
JR20241Trap in CCS.DLL When SNA API Client processes UNBIND from Host and SLI_CLOSE from application at the same time.

[Return to top of section] [Return to top of document] [Table of Contents]

4.2 New function - client

New function added in FixPack 3
General enhancements
1. A new environment variable to specify LU alias has been added to SNA API Client. This environment variable can be used when migrating an application to WTS environment. Many client applications use a hardcoded Local LU alias. When migrating to a WTS environment, this hardcoded Local LU alias needs to be mapped to different LU alias for each user i.e. Local LU alias x for user1 and y for user2. This can be done by configuring the environment variable "LUALIAS<TPsLUALIAS>". Follow the steps below for configuring multiple LU aliases in a WTS environment:

set LUALIAS<LocalLUAlias> = UserLUAlias

where:
LocalLUAlias is the LU alias configured in the configuration file (in CPIC side info)
UserLUAlias is the LU alias required to be used for a particular user.

Note: This environment variable has to configured under user environment variables.



New function added in FixPack 2
Problem determination enhancements
1. A new feature to create two message log files (MsgLog.dat) has been included. This is to reduce the size of each Message log file. Infobundler will collect both the Message Log files.
2. In FixPack 2, a new feature that would collect debug information in multiple trace files (i.e, multiple pcatrace.dat) has been included. Infobundler will collect all the debug trace files. The following notes document how to use this feature.

There are three batch files included with this new feature. These batch files update the registry with entries required for this feature.

The batch files to be used for enabling or disabling this feature are:

  • Append.bat - If all the trace files (pcatrace.dat) are to be kept, use this batch file. As a trace file reaches its maximum size, a new trace file is created. The old trace files are kept even if the application is closed and restarted.
  • Replace.bat - If all the old trace files are to be deleted every time an application is restarted, use this batch file. Every time an application is closed and restarted and the trace GUI (tracedg.exe) is also closed and restarted, all the old trace files (pcatrace.dat)are deleted.
  • Delete.bat - This needs to be used after the product (SNA API Client) is uninstalled to delete the above registry entries.

If the option needs to be changed from append to replace or vice-versa, close all the applications, close the trace GUI (tracedg.exe), and run the relevant batch file.

Run Delete.bat after product (SNA API Client) uninstall. If Delete.bat is not run after product uninstall, some registry keys related to the product will remain in the system.



New function added in FixPack 1
Problem determination enhancements
1. Additional DEBUG Trace options:
Additional tracing has been added to capture more diagnostic information to diagnose problems. Now, when selecting ALL API trace option, additional diagnostic trace information is written to a new file called pcatrace.dat which is created in the client installation directory.
2. Infobundler is provided with this version to capture key client files required for problem diagnoses. It should be run and output sent whenever pursuing a problem with IBM.

To run the infobundler, go to the SNA API Client installation directory (Eg: C:\CSNTAPI) from command line. Run INFOB.exe from command line. i.e, go to command prompt.

c:\CSNTAPI>INFOB

It will go through a series of 13 steps and finally collect the information (11 documents mentioned below) in trace.zip. trace.zip will be located in the directory where the traces exist.

For any problem reported, run the infobundler and send the trace.zip file to IBM Support.

The summary of features of the Infobundler for SNA API Client is as follows:

  1. Bundle MsgLog.dat (error message log file)
  2. Bundle pcatrace.dat (debug trace data file)
  3. Bundle CSNTAPI.TRC (unformatted trace data file)
  4. Bundle CSNTAPI.FMT (formatted trace data file)
  5. Bundle APIERROR.LOG (api error log file)
  6. Bundle Eventlogs
  7. Bundle Dr.Watson Log
  8. Bundle CSNTAPI.INI
  9. Bundle all the Registry Keys. Note that the user environment variables and system environment variables are part of the Registry settings.The user environment variables will correspond to the user running the Infobundler.
  10. Bundle CSNTAPI directory listing
  11. Bundle Windows\system32 directory listing. This will be helpful in determining if the application is using the WINRUI32.DLL, WINAPPC32.DLL etc. from SNA API Client installation or Microsoft Windows installation. We have observed that if these APIs are used from Microsoft Windows installation, the application does not work.
[Return to top of section] [Return to top of document] [Table of Contents]

4.3 Install instructions - client

Installing the fix on the system:
  1. Be SURE you have downloaded the 6.1.2 FixPack 3 APAR package in BINARY format. APAR JR22681 documents and includes the server and client package. It includes both readme and new function text files for both server and client packages.
  2. Create a temporary directory, copy the 6.1.2 APIPACK3.EXE into the temporary directory, and run the file to uncompress it.
  3. Stop ALL running SNA API client applications on this machine. Check the Task Manager and stop any running API CLIENT exe's such as ATTMSG.EXE and LU62MGR.EXE.
  4. CLINSTFIX.BAT is an installation batch file similar to INSTFIX.BAT for the server. CLINSTFIX.BAT will backup the files to a folder called CSNTAPI-Pre612fixpack3, then install/copy the updated the DLL's and EXE's to the supplied installation folder. View the comments included in CLINSTFIX.BAT usage instructions.

    Some examples follow:

    • CLINSTFIX c:\CSNTAPI BACKUP (backs up the directory)
    • CLINSTFIX c:\CSNTAPI NOBACKUP (does not backup the directory)
    • CLINSTFIX c:\CSNTAPI (default is NOBACKUP)
    • CLINSTFIX c:\CSNTAPI BACKUP > CLINSTFIX.LOG 2>&1 (log to file)
  5. After running CLINSTFIX, shutdown and restart the machine to complete the installation.

[Return to top of section] [Return to top of document] [Table of Contents]

5 Uninstall information
Uninstallation of a fixpack is not supported. To revert to a previous level, uninstall the product completely, then install the GA level, then install the desired fixpack level.

Uninstallation instructions are in the Quick Beginnings book at http://www.ibm.com/software/network/commserver/windows/library/index.html

To ensure a complete uninstallation of the product, download the cleanup package (JR21546) from http://www.ibm.com/support/docview.wss?rs=2262&uid=swg24009834

If Personal Communications is installed on the same machine as Communications Server, you must uninstall Personal Communications before uninstalling Communications Server.

All applications using Communications Server should be terminated before you attempt to uninstall the product. Attempting to uninstall Communications Server while an application (such as APING or Personal Communications) is running will cause the uninstall to hang until the application is terminated.

[Return to top of document] [Table of Contents]

6 Web site and support information

Product information
For the latest information about the IBM Communications Server family of products, visit the Communications Server Web site at http://www.ibm.com/software/network/commserver. This Web site provides information and links to headline information, specification sheets, frequently asked questions, education, and much more.

Product support
For the latest support information, visit the Communications Server Support Web site at http://www.ibm.com/software/network/commserver/support. This Web site provides information and links to code fixes, tips, newsgroups, maintenance, and much more.

Technical notes
Search the hints and tips in the IBM Support database at http://www.ibm.com/software/network/commserver/windows/support/.

Technical support
For technical assistance or questions, call the IBM support center for your country. For example, in the United States, call 1-800-IBM-SERV.

[Return to top] [Table of Contents]

7 Notices and trademarks

AnyNet, IBM, iSeries, OS/400, S/390, WebSphere, z/OS, and zSeries are trademarks or registered trademarks of IBM Corporation in the United States, other countries, or both.

Tivoli, Tivoli Ready, Tivoli Management Environment, and TME are trademarks of Tivoli Systems Incorporated in the United States, other countries, or both.

Lotus and Domino are trademarks or registered trademarks of Lotus Development Corporation in the United States, other countries, or both.

Microsoft, Windows, Windows NT, Windows 2000, Windows XP, and Windows 2003 are trademarks or registered trademarks of Microsoft Corporation in the United States, other countries, or both.

Java, the Java logo, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

[Return to top] [Table of Contents]