IBM Communications Server for Windows
Version 6.1.3 FixPack 2
Readme

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

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/Windows Version 6.1.3 FixPack 2 is an upgrade that includes FixPack 2 updates. It is not a full install, and requires that CS/Widnows V 6.1.3 GA level or with FixPack 1 should be installed to install fixpack 2. Only fixpacks greater than FixPack 2 should be installed after this installation.

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]

For details on 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 2 are included.

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

This update includes fixes to the CS/Windows 6.1.3 from GA.

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/Windows 6.1.3 APARs.
2. This fixpack should only be applied to CS/Windows 6.1.3 at GA level or with FixPack 1.Only fixpacks greater than FixPack 2 should be installed after this installation.

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

The Fixpack1 release includes the following files:

README.HTM	This ReadMe.htm is included in JR36028.EXE, JR36071.EXE and JR36267.EXE package, which describe about the fixes, new functions, and install instructions.
JR36028.EXE	Self extracting executable that contains Server.exe and nlspack.exe for FixPack 2 files to be installed on the CS/Widnows 6.1.3 Server or Fixpack 1 install.
JR36071.EXE	Self extracting executable that contains Client.exe and nlspack.exe for FixPack 2 files to be installed on the CS/Widnows 6.1.3 API Client or Fixpack 1 install.
JR36267.EXE	Self extracting executable that contains FixPack 2 files to be installed for CS/Windows 6.1.3 Remote Admin Client install.

nlspack.exe:

Self extracting executable that contains FixPack 2 language files to be installed on the CS/Windows 6.1.3 Server and API-Client installation. The English version of this module is installed as part of the server or client install by default. If CS/Windows 6.1.3 was installed on non-English language machine, you must install the appropriate version of this NLS package after the server and client installation.

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

Section Table of Contents
2.1 Files included
2.2 Install instructions

[Return to top] [Table of Contents]

nlspack.exe: Includes the language packages for all the languages, which CS/Windows 6.1.3 supports. Run the appropriate self extracting language pack with the -d option, so that the language files will be extracted with proper directory structure. CS/Windows supported on the following languages:

CHS : Simplified Chinese

CHT : Traditional Chinese

DEU : German

ESP : Spanish

FRA : French

ITA : Italian

JPN : Japanese

KOR : Korean

PTB : Brazilian Portuguese

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

The NLS update can be integrated into and installed as part of the server or client update or can be installed separately after the server or client update by running instfix.bat present in the nlspack.exe.

2.2.1 Integrated with server or client update
2.2.2 Separate, after server or client update

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

Instructions to update the server package with the NLS updates:

1. Replace the pcsnops.exe, adminstrings.dll , trcmsg.dll and pcstrcres.dll in the server package with those included in the respective language pack of nlspack.
   Example: If you are installing the fixpack on French Operating system then replace those modules from nlspack present under ..\FRA\ directory.
2. Copy the file PCCFGXXX.DLL, LDLCXXX.DLL,PCLVWXXX.DLL,PCMFCXXX.DLL and VACGFXXX.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 pccfgxxx.DLL,ldlcXXX.DLL,pclvwXXX.DLL,pcmfcXXX.DLL and vacgfXXX.DLL modules. (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.

Instructions to update the API client package with the NLS updates:

1. Replace the setco.exe, testlu62.exe and tracedg.exe in the client update package with those included from the appropriate sub-directory of this package.
2. Update the client INSTFIX.BAT file with an appropriate rename and copy statement present in the client.exe. See existing rename and copy statements in INSTFIX.BAT for format.

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

Server Install instructions:

1. Install the server updates first, following the instructions in section 3.
2. Stop the CS/Windows node and all applications that use CS/Windows.
3. Copy nlspack.exe of Server, which is present in JR36028.EXE to a temporary directory.
4. Run the nlspack.exe, which will extract all the language packs.
5. Choose the appropriate NLS package based on the CS/Windows language that is installed, and Run the respective language pack.
   Example: If you wanted to install Simplified Chinese language pack then Run chs.exe -d
   This will create a sub-directory chs and extract all the files under chs directory for Simplified Chinese language.
6. Review the comments in the INSTFIX.BAT file for specific usage instructions. For example:
   • INSTFIX chs (no parameters; environment variables will be used to locate the installation location)
   • INSTFIX chs> nlsfp2.txt 2>&1 (silent install)
   • INSTFIX chs "C:\Program Files\IBM\Communications Server" (specify the directory)
   • INSTFIX chs "C:\Program Files\IBM\Communications Server" > nlsfp2.txt 2>&1 (silent install, specify directory)
7. Reboot and start the CS/Windows node.

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

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

Client Install instructions:

1. Install the client updates first.
2. Stop the all applications that use API-CLIENT.
3. Copy nlspack.exe of API Client, which is present in JR36071.EXE to a temporary directory.
4. Run the nlspack.exe, which will extract all the language packs.
5. Choose the appropriate NLS package based on the API Client language that is installed, and Run the respective language pack.
   Example: If you wanted to install Simplified Chinese language pack then Run chs.exe -d
   This will create a sub-directory chs and extract all the files under chs directory for Simplified Chinese language.
6. Review the comments in the INSTFIX.BAT file for specific usage instructions. For example:
   • INSTFIX chs "C:\Program Files\IBM\CS SNA API Client" (specify the directory)

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

Section Table of Contents
3.1 APARs included
3.2 Files updated - server
3.3 New function - server
3.4 Install instructions - server

[Return to top] [Table of Contents]

APARS included from FixPack 2
JR35280	Following CICS reset some TN3270 sessions to internal DLUR LUs could not be re-established
JR36022	PROBLEM WITH DOWNSTREAM FIXED PACING WITH DLUR WHEN WINDOW SIZE 0.
JR35283	LUS HANG IN PSLUIO-P STATE.
JR35284	SYSTEM CRASH PROCESSING SNA STOP COMMAND.
JR35285	ERROR WHEN ATTEMPTING TO CONFIGURE EICON CONNECTION.
JR34512	TRNSDT MISSING FILES.
JR36025	MEMORY LEAK IN KERNEL WITH NMVT ALERTS QUEUED.
JR36026	CS/Windows CRASH WHILE PROCESSING APPC DATA WITH INCORRECT LENGTH.
JR35775	SLI_OPEN HANG AFTER LINK OUTAGE AND RECOVERY.
JR36021	CRASH IN SNA_V5ROUTER.
APARS included from FixPack 1
JR28327	TN3270 SERVER MAY SEND TWO BID REQUESTS TO 3270 CLIENT.
JR28547	TRAP IN MSGIO.DLL WHEN ISSUING CSSTOP.
JR28562	MULTIPLE RTP PIPES WITH SAME COS BETWEEN 2 ADJACENT CONTROL POINTS.
JR28756	TRAP IN CSRCMDS.EXE WHEN STOPPING THE NODE USING CSSTOP.EXE.
JR28764	RAPIPIPE CREATED AND ACCESSED ANONYMOUSLY.
JR28819	TRNSDT INCORRENT TRANSLATION OF CHARACTER E086.
JR28884	XIDS FLOOD THE NETWORK WHEN DUPLICATE CP NAME USED.
JR29664	MEMORY LEAK IN APPNNODE.EXE WITH ALL INCOMING ATTACHES.
JR29793	NODEOPS UTILITY HANGS STARTING THE NODE OR AFTER SCREEN REFRESH.
JR30350	TRAP IN CSRCMDS.EXE WHEN STOPPING THE NODE USING CSSTOP.EXE.
JR32052	SDLC HANG CONDITION CAUSING ALL PROCESSING TO HALT.
JR32262	TN3270 SERVER LU HUNG AFTER OPERATOR CYCLES LU.
JR32589	INTERMITTENT TRAPS IN CSRCMDS WHEN ISSUING CSSTOP.
JR33070	SLOW PERFORMANCE RUNNING LU62 TRANSACTIONS ON SNA API CLIENT.

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

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

Directory of "C:\Program Files\IBM\Communications Server" (Communications Server installation directory)

04/22/2010  09:58 AM            36,864 adaptinst.exe
04/22/2010  10:38 AM            45,056 adminapi.dll
04/22/2010  10:34 AM            32,768 adminpre.dll
04/22/2010  10:38 AM           389,120 adminserver.dll
04/22/2010  10:34 AM            69,632 adminstrings.dll
04/22/2010  10:24 AM            77,824 adRAPIClient.dll
04/22/2010  10:39 AM            40,960 adRAPIStubs.dll
04/22/2010  10:23 AM            53,248 adRapiUtil.dll
04/22/2010  10:51 AM            73,728 aftp.exe
04/22/2010  10:51 AM           151,552 aftpapi.dll
04/22/2010  10:52 AM            28,672 aftpd.exe
04/22/2010  10:51 AM           147,456 aftpserv.dll
04/22/2010  10:49 AM           102,400 anameapi.dll
04/22/2010  11:02 AM            36,864 anutil.dll
04/22/2010  10:29 AM            24,576 ANYINIT.dll
04/22/2010  11:02 AM            24,576 anyloadr.exe
04/22/2010  10:29 AM           110,676 anymsg.dll
04/22/2010  11:02 AM            24,576 anytrace.dll
04/22/2010  11:02 AM            24,576 anytrc.dll
04/22/2010  11:03 AM            24,576 anytrfmt.dll
04/22/2010  11:12 AM            32,768 anyws2in.dll
04/22/2010  11:12 AM            36,864 anyws32.dll
04/22/2010  11:11 AM            24,576 anywsipc.dll
04/22/2010  01:47 PM           434,176 apitrc32.dll
04/22/2010  10:49 AM           167,936 app.dll
04/22/2010  01:47 PM            24,576 appcmsg.dll
04/22/2010  10:22 AM            36,864 cfgmsg.dll
04/22/2010  01:47 PM            20,480 cmnapi32.dll
04/22/2010  09:58 AM            32,768 cpicmsg.dll
04/22/2010  10:33 AM            40,960 cscm.dll
04/22/2010  10:48 AM            32,768 csdisplay.exe
04/22/2010  10:29 AM            32,768 csevtmsg.dll
04/22/2010  10:31 AM            53,248 csformat.dll
04/22/2010  10:52 AM            45,056 csikm.exe
04/22/2010  10:34 AM            36,864 cslba.dll
04/22/2010  10:48 AM            20,480 cslic.exe
04/22/2010  10:30 AM            24,576 csloadfx.dll
04/22/2010  10:02 AM            32,768 csmls.dll
04/22/2010  10:31 AM            49,152 csmmsg.dll
04/22/2010  10:48 AM            45,056 csmodify.exe
04/22/2010  10:32 AM           192,512 csnia.dll
04/22/2010  10:31 AM            20,480 csniaqry.exe
04/22/2010  10:30 AM            28,672 csnlg.dll
04/22/2010  10:03 AM           139,264 CSNTPD.exe
04/22/2010  10:34 AM            32,768 csqel.dll
04/22/2010  10:48 AM            20,480 csquery.exe
04/22/2010  10:33 AM            77,824 cssec.dll
04/22/2010  10:33 AM            45,056 cssma.dll
04/22/2010  10:48 AM            24,576 csstart.exe
04/22/2010  10:48 AM            24,576 csstop.exe
04/22/2010  10:33 AM            45,056 cstlm.dll
04/22/2010  10:31 AM            24,576 csutlc.dll
04/22/2010  10:31 AM            28,672 csutls.dll
04/22/2010  10:32 AM            28,672 csxlib.dll
04/22/2010  10:22 AM            24,576 defsecur.dll
04/22/2010  10:13 AM            32,768 discovrd.dll
04/22/2010  10:06 AM           118,784 dlctrc32.dll
04/22/2010  10:24 AM            32,768 emutocfg.dll
04/22/2010  10:22 AM            57,344 fmtcapi.dll
04/22/2010  10:22 AM            24,576 fmtmsg.dll
04/22/2010  10:23 AM            49,152 FMTNODE.DLL
04/22/2010  10:42 AM            24,576 FMTNOPS.dll
04/22/2010  10:52 AM            24,576 getsense.exe
04/22/2010  10:29 AM            57,344 hotstby.dll
04/22/2010  10:31 AM            24,576 ibmcsprf.dll
04/22/2010  10:30 AM            73,728 ibmsa.dll
04/22/2010  10:30 AM            98,304 ibmslp.dll
04/22/2010  11:02 AM            24,576 ipc.dll
04/22/2010  11:04 AM           118,784 ippmm.dll
04/22/2010  10:45 AM            45,056 ldlc.dll
04/22/2010  10:45 AM            24,576 ldlcenu.dll
04/22/2010  10:29 AM            24,576 limgmt.dll
04/22/2010  10:29 AM            69,632 limgmtd.dll
04/22/2010  10:46 AM            32,768 lspmsg.dll
04/22/2010  09:58 AM            40,960 Message.dll
04/22/2010  09:55 AM            32,768 MILLUTIL.DLL
04/22/2010  11:11 AM           163,840 mptncmm.dll
04/22/2010  10:03 AM           155,648 msgbrwsr.exe
04/22/2010  09:58 AM            28,672 MSGIO.dll
04/22/2010  09:58 AM            28,672 Msgmsg.dll
04/22/2010  10:22 AM            16,384 NI_MSG.DLL
04/22/2010  10:23 AM            94,208 NODEINIT.DLL
04/22/2010  10:42 AM            28,672 nopsmsg.dll
04/22/2010  10:54 AM           460,288 ocdconvt.dll
04/19/2010  09:28 PM            77,422 ocdnts50.dat
04/22/2010  10:22 AM           286,720 pccfgenu.dll
04/22/2010  10:03 AM            73,728 pclvwenu.dll
04/22/2010  10:02 AM            36,864 pcmfcenu.dll
04/22/2010  10:22 AM            94,208 Pcscapi.dll
04/22/2010  10:15 AM            32,768 pcscca.exe
04/22/2010  10:05 AM           966,656 pcscdra.dll
04/22/2010  02:04 PM         1,303,952 pcscfg.exe
04/22/2010  10:02 AM           151,552 pcsmfcx.dll
04/22/2010  02:04 PM           447,888 pcsnops.exe
04/22/2010  09:58 AM            28,672 pcsw32x.dll
04/22/2010  10:23 AM            24,576 PCS_AGNT.EXE
04/22/2010  10:15 AM            36,864 pcs_perf.dll
04/22/2010  10:22 AM            16,384 PCS_STAB.DLL
04/22/2010  11:00 AM            32,768 pdlnafmt.dll
04/22/2010  10:55 AM            32,768 pdlncfgf.dll
04/22/2010  10:56 AM            69,632 pdlncfmt.dll
04/22/2010  10:56 AM            10,752 pdlndfmt.dll
04/22/2010  10:57 AM            24,576 pdlneadu.dll
04/22/2010  10:55 AM            32,768 pdlneptf.dll
04/22/2010  10:58 AM            45,056 pdlnmfmt.dll
04/22/2010  10:59 AM            28,672 pdlnshaf.dll
04/22/2010  10:58 AM            24,576 pdlnslef.dll
04/22/2010  10:59 AM            24,576 pdlnsv2f.dll
04/22/2010  10:59 AM            28,672 pdlnsx2f.dll
04/22/2010  10:56 AM            11,264 pdlwofmt.dll
04/22/2010  10:03 AM            45,056 rasbut.exe
04/22/2010  10:46 AM            24,576 rcmdfmtr.dll
04/22/2010  10:46 AM            45,056 rcmdsa.exe
04/22/2010  10:45 AM            24,576 ropmsg.dll
04/22/2010  10:03 AM            53,248 Servcsnt.exe
04/22/2010  10:16 AM            32,768 slimsg.dll
04/22/2010  10:30 AM            28,672 slpapi.dll
04/22/2010  10:29 AM            24,576 slpform.dll
04/22/2010  09:58 AM           684,145 snaformat.exe
04/22/2010  11:14 AM           114,688 snapmm.dll
04/22/2010  11:11 AM           122,880 snasm.dll
04/22/2010  10:48 AM           102,400 snmpxa.dll
04/22/2010  10:22 AM            73,728 SPELLING.DLL
04/22/2010  10:48 AM            28,672 sxafmt.dll
04/22/2010  10:46 AM            32,768 sxamsg.dll
04/22/2010  11:12 AM            24,576 sxmap.exe
04/22/2010  11:17 AM            36,864 tn3270d.dll
04/22/2010  11:16 AM           233,472 tn3270wn.exe
04/22/2010  11:17 AM            24,576 tn32bind.dll
04/22/2010  11:19 AM            57,344 tn5250d.dll
04/22/2010  11:18 AM           176,128 tn5250wn.exe
04/22/2010  11:17 AM            53,248 tniptkt.dll
04/22/2010  10:29 AM           106,581 tnsmsg.dll
04/22/2010  10:14 AM            20,480 tpstart.exe
04/22/2010  10:29 AM            20,480 vacgcon.exe
04/22/2010  10:29 AM            61,440 vacgfenu.dll
04/22/2010  10:22 AM            81,920 vacgverf.dll
04/22/2010  10:29 AM           110,592 vacgwin.exe
04/22/2010  01:47 PM            65,536 wappc32.dll
04/22/2010  10:02 AM           135,168 wcpic32.dll
04/22/2010  10:49 AM            49,152 winaping.exe
04/22/2010  10:21 AM            24,576 winAPPC.dll
04/22/2010  10:02 AM            24,576 wincpic.dll
04/22/2010  10:21 AM            24,576 winCSV.dll
04/22/2010  01:47 PM            65,536 wincsv32.dll
04/22/2010  10:13 AM            32,768 winms32.dll
04/22/2010  10:14 AM            36,864 winnof32.dll
04/22/2010  10:21 AM            24,576 winrui.dll
04/22/2010  01:47 PM            36,864 winrui32.dll
04/22/2010  10:21 AM            24,576 winsli.dll
04/22/2010  10:21 AM            86,016 winsli32.dll
04/22/2010  10:12 AM            28,672 wpdapi32.dll

Directory of %snaroot%\properties\version where "%snaroot%" is the installation folder of CS/Windows.

04/15/2010  11:45 AM               161 IBM_Communications_Server_for_Windows.6.1.3.swtag
04/15/2010  11:45 AM               208 PTF_V6.1.3.2_for_Communication_Server_Windows.6.1.3.2.fxtag

Directory of %systemroot%\system32\drivers

04/22/2010  11:04 AM            38,512 anydlc.sys
04/22/2010  10:12 AM         1,621,407 appn.sys
04/22/2010  10:14 AM           125,090 appnapi.sys
04/22/2010  10:06 AM           400,227 appnbase.sys
04/22/2010  10:14 AM            32,768 appnnode.exe
04/22/2010  10:34 AM            24,576 csit.exe
04/22/2010  10:45 AM            49,152 csrcmds.exe
04/22/2010  10:04 AM            40,960 cstrcser.exe
04/22/2010  10:49 AM            20,480 ibmcs.exe
04/22/2010  10:31 AM            20,480 ibmsa.exe
04/22/2010  10:57 AM            28,672 ldlcserv.exe
04/22/2010  10:57 AM            40,960 ldlcserv6.exe
04/22/2010  10:07 AM           103,263 llc2.sys
04/22/2010  10:59 AM            77,536 pdlnacom.sys
04/22/2010  11:00 AM            15,840 pdlnadci.sys
04/22/2010  11:00 AM            39,936 pdlnafac.sys
04/22/2010  10:59 AM            92,464 pdlnampa.sys
04/22/2010  11:00 AM            39,456 pdlnaoem.sys
04/22/2010  10:55 AM             6,768 pdlncbas.sys
04/22/2010  10:56 AM           160,416 pdlncfwk.sys
04/22/2010  10:56 AM            12,800 pdlndint.sys
04/22/2010  10:57 AM            64,512 pdlndldl.sys
04/22/2010  10:57 AM            72,704 pdlndldl6.sys
04/22/2010  10:57 AM            70,656 pdlndlpb.sys
04/22/2010  10:57 AM            18,944 pdlndoem.sys
04/22/2010  10:57 AM            53,248 pdlndqll.sys
04/22/2010  10:57 AM            67,584 pdlndsdl.sys
04/22/2010  10:55 AM             8,576 pdlnebas.sys
04/22/2010  10:55 AM            50,480 pdlnecfg.sys
04/22/2010  10:58 AM            67,760 pdlnemap.sys
04/22/2010  10:55 AM            12,736 pdlnemsg.sys
04/22/2010  10:55 AM            19,952 pdlnepkt.sys
04/22/2010  10:58 AM            59,392 pdlnshay.sys
04/22/2010  10:58 AM            22,464 pdlnslea.sys
04/22/2010  10:59 AM            54,304 pdlnsv25.sys
04/22/2010  10:59 AM            58,768 pdlnsx25.sys
04/22/2010  10:34 AM            40,608 qeldrvr.sys
04/22/2010  10:39 AM            53,248 rapiserver.exe
04/22/2010  09:56 AM            20,480 trcboot.exe

Directory of %systemroot%\system32

04/22/2010  09:56 AM            36,864 nstrc.dll
04/22/2010  09:56 AM            24,576 fmt_util.dll

Directory of %snaroot%\Trace Facility where "%snaroot%" is the installation folder of CS/Windows.

04/22/2010  10:04 AM            36,864 cstrace.exe
04/22/2010  10:04 AM            32,768 cstrccom.dll
04/22/2010  10:03 AM            28,672 fmteng.dll
04/22/2010  10:03 AM            28,672 pcsfmtpi.dll
04/22/2010  02:04 PM           128,400 trcgui.exe

Directory of %snaroot%\Trace Facility\en_US where "%snaroot%" is the installation folder of CS/Windows.

04/22/2010  10:03 AM            32,768 pctrcres.dll
04/22/2010  10:03 AM            28,672 trcmsg.dll

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

New function added in FixPack 2
1. Active LUs Display
	Now, csdisplay can display all the LU's used by the LUA application or by the TN3270 Sessions with the new option of ALU. To check the active LUA & TN3270E session, type "csdisplay ALU" from the command Windows prompt. Example output of the "csdisplay ALU" as follows: a) When there is one LUA SSCP-LU and one LUA LU-LU Session active. csdisplay ALU LU Name        LUNAME05 PU Name        PUNAME NAU Address    5 Session Type   LU-LU LU Name        LUNAME09 PU Name        PUNAME NAU Address    9 Session Type   SSCP-LU Configured LUs         15 Active LUs                9 LUA(SSCP)             1 LUA(LU-LU)           1 TN3270(SSCP)        0 TN3270(LU-LU)      0 b) When there is one SSCP-LU TN3270 and one LU-LU TN3270 Session type. csdisplay ALU LU Name        BASELU02 PU Name        PUNAME NAU Address    2 Session Type   TN3270E SSCP-LU, 9.122.19.106 LU Name        BASELU03 PU Name        PUNAME NAU Address    3 Session Type   TN3270E LU-LU, 9.122.19.106 Configured LUs       15 Active LUs               9 LUA(SSCP)            0 LUA(LU-LU)          0 TN3270(SSCP)      1 TN3270(LU-LU)    1 c) When there is no SSCP Connected LU's or active LUA Application Seesions or active TN3270 Session. csdisplay ALU Configured LUs        15 Active LUs                9 LUA(SSCP)             0 LUA(LU-LU)           0 TN3270(SSCP)        0 TN3270(LU-LU)      0
2. Support for GSKIT TLS Renegotiation weak security
	Along with this release, the GSKIT package used for handling SSL secure sessions has a vulnerability update also included in the refresh image. If the CS/Windows product is using TN3270 Server with SSL support enabled, then the GSKIT APAR should be applied or required to install CS/Windows freshly using the Fixpack2 refresh image. After installing CS/Windows 6.1.3.2 and gskbas-7.0.4.27, you can override the new default by setting appropriate value to the RENEGOTIATION key in the TN3270_PORT_DEF section in the config file. RENEGOTIATION takes the value NONE (default), ABBREVIATED, FULL. There are 3 possible functions of the gskit library. (a) NONE         : No renegotiation permitted   (b) ABBREVIATED  : Abbreviated renegotiation permitted (c) FULL         : Full (or abbreviated) renegotiation permitted. The default is NONE. TN3270_PORT_DEF=(      PORT=800      SECURITY=1      CLIENT_AUTHENTICATION=1      SECURITY_LEVEL=HIGH      RENEGOTIATION=NONE ) The Communications Server for Windows provides secure encryption and authentication for TN3270 Server clients by using Secure Socket Layer(SSL). The SSL support is provided by the GSKIT common component from IBM (package name gskta). Refer to the document, JR36023_TLS_SSLv3_Update_CS.pdf, provided with this APAR on Fix Central or on the CS/Windows media provided through Fix Central or Passport Advantage. The JR36023 APAR can be found on the Communications Server for Windows product under the brand "WebSphere" on Fix Central at: http://www.ibm.com/support/docview.wss?rs=2262&uid=swg1JR36023
New function added in FixPack 1
1. Transaction Program Synchronization enhancement
	Previous version of Communication Server for Windows supports only three (Any, None & Confirm ) synchronization level. Added two more synchronization (SYNCPT Negotiable and SYNCPT Required ) to the transaction program definition. # SYNCPT Negotiable The transaction program supports a synchronization level of None, Confirm, or Sync-point. # SYNCPT Required The transaction program supports a synchronization level of Sync-point. The required synchronization level can be selected, when defining the Transaction Program from the basic panel of Node configuration application.
2. Snaformat enhance to format the Control Vector (X'82')
	The snaformat tools is been updated to format the CV'82' Subarea characteristics subfields, the formated trace will be presented in the .det file.

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

Installing the fixpack on the system:

1. Download JR36028.EXE in Binary format into a temporary directory.

2. Run the JR36028.EXE, which will extract Server.exe and nlspack.exe
3. Run Server.EXE with -d option to extract all server files. There are executables included in this package, those are required for fixpack installation. The instfix.bat in current directory is required only for the fixpack installation.
   1. If you have SNA API Client Services (Split-stack API Client/Server), copy JR36071.EXE in the client workstation and see section 4 for install instructions.
   2. nlspack.exe contains non-English language updates. Customers running non-English versions of CS/Windows also need to install NLSPACK package seperately. To install the language pack refer section 2 for NLS install instructions.

4. New function updates have been included with this fixpack package. See section 3.3 for more details on the new updates.
   1. INSTFIX.BAT checks if a PCOMM version less than 5.7 CSD3 is installed and if true, does not update the Trace Facility. CS/Windows 6.1.3 would use the Trace Facility installed by PCOMM. If you have installed PCOMM 5.7 CSD3 and above on CS/Windows 6.1.3, PCOMM will not install its Trace Facility. In this case, INSTFIX will update the CS/Windows 6.1.3 Trace Facility.

      If versions of PCOMM prior to 5.7 CSD3 are installed, you will not have any of the CS/Windows 6.1.3 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/Windows 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 or Remove Programs
      2. Remove CS/Windows 6.1.3
      3. Re-install CS/Windows 6.1.3
      4. Install PCOMM 5.8 (or PCOMM 5.7 CSD3 or later)
      5. Apply CS/Windows 6.1.3 Fixpack 2 maintenance upgrade

5. Stop Communications Server for Windows (including your node, Node Operations, Node Configuration, Log Viewer, and any other CS/Windows components you have started). Note that there may still be CS/Windows-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_1.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.pre6132, then copy the updated files.

   If for some reason you rerun INSTFIX.BAT, you will receive errors during each rename because the file.pre6132 file will already exist.The original copy of the file will be preserved in file.pre6132 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: 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 4: The default value of the registry key HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Communications Server\CurrentVersion\VersionNumber will be changed to 6132.

6. 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.

7. If you want to restrict the user(Non-Administrator) from controlling SNA resources like Stoping/Starting the node/link etc., you have to run the batch file below and follow the step (B) mentioned below.
   1. Run the batch "AccessControlSettings.bat"
   2. 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 "3" to "11".
      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]

Section Table of Contents
4.1 APARs included
4.2 New function - client
4.3 Install instructions - client
4.4 Files updated - client

[Return to top] [Table of Contents]

New APARs included in FixPack 2 since CSNT6.1.3 GA
JR36070	TRNSDT MISSING FILES.
New APARs included in FixPack 1 since CSNT6.1.3 GA
None.

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

New function added in FixPack 2
None.
New function added in FixPack 1
APPC Cancel Conversation support
1.	The CANCEL_CONVERSATION verb is a control verb that will cancel a connection between a local LU and partner LU using a specific transaction program (tp_id) and a conversation (conv_id). The definition of the VCB structure for the CANCEL_CONVERSATION verb is as follows: typedef struct cancel_conversation { unsigned short opcode; /* verb operation code */ unsigned char opext; /* verb extension code */ unsigned char format; /* format */ unsigned short primary_rc; /* primary return code */ unsigned long secondary_rc;/* secondary return code */ unsigned char tp_id[8]; /* TP identifier */ unsigned long conv_id; /* conversation identifier */ } CANCEL_CONVERSATION; Please refer the Client/Server programming guide for usage of this verb.

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

Installing the fixpack on the system:

1. Be SURE you have downloaded the 6.1.3 FixPack 2 APAR package (JR36071.EXE) in BINARY format.
2. Create a temporary directory, copy the JR36071.EXE, and Run JR36071.EXE, which will extract JR36071.exe and nlspack.exe for the API Client
3. Run JR36071.exe to extract all the API Client's updated files
4. 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.
5. INSTFIX.BAT is an installation batch file. INSTFIX.BAT will backup the files to a folder called *.pre6132, then install/copy the updated DLL's and EXE's to the supplied installation folder. View the comments included in INSTFIX.BAT usage instructions.

   Some examples follow:

   • INSTFIX "C:\Program Files\IBM\CS SNA API Client" (to install fixpack)
   • INSTFIX "C:\Program Files\IBM\CS SNA API Client" > CLINSTFIX.LOG 2>&1 (log to file)
6. nlspack.exe contains non-English language updates. Customers running non-English versions of API Client also need to install NLSPACK package seperately. To install the language pack refer section 2 for NLS install instructions.
7. After running INSTFIX, shutdown and restart the machine to complete the installation.

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

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

Directory of "C:\Program Files\IBM\CS SNA API Client" (SNA API Client installation directory)

04/22/2010  11:24 AM            45,056 AMISC.DLL
04/22/2010  11:24 AM            49,152 ASPRT.DLL
04/22/2010  11:24 AM           126,976 CCM.DLL
04/22/2010  11:23 AM            77,824 CCS.DLL
04/22/2010  11:31 AM           131,072 CSCCFG.EXE
04/22/2010  10:30 AM            98,304 ibmslp.dll
04/22/2010  11:28 AM            61,440 MGRLVL.DLL
04/22/2010  09:56 AM            36,864 nstrc.dll
04/22/2010  11:30 AM            40,960 RESETAPI.EXE
04/22/2010  11:30 AM            32,768 SETCO.EXE
04/22/2010  11:28 AM           102,400 SSET.DLL
04/22/2010  11:30 AM            57,344 TESTLU62.EXE
04/22/2010  11:29 AM            65,536 TRACEDG.EXE
04/22/2010  10:16 AM            32,768 TRNSDT.DLL
04/22/2010  11:24 AM            32,768 WAPPC32.DLL

Directory of "C:\Program Files\IBM\CS SNA API Client\properties\version"

04/23/2010  04:43 PM               166 IBM_SNA_API_Client_for_Windows.6.1.3.cmptag
04/23/2010  04:43 PM               206 PTF_V6.1.3.2_for_SNA_API_Client_for_Windows.6.1.3.2.fxtag

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

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]

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]

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

Tivoli, and Tivoli License Management are trademarks of Tivoli Systems Inc. or IBM Corporation 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, Windows Server 2003, Windows Vista, Windows Server 2008 and Windows 7 are trademarks or registered trademarks of Microsoft Corporation in the United States, other countries, or both.

VMware is a registered trademark of VMware, inc.

[Return to top] [Table of Contents]