IBM Communications Server for Windows
Version 6.4 FixPack 2
Readme

© Copyright International Business Machines Corp. 2010
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/Windows Version 6.4 FixPack 2 is an upgrade that includes FixPack 2 updates. It is not a full install, and requires that CS/Windows V 6.4 GA level 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]

1.1 New in this fixpack

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]

1.2 Product fix history

This update includes fixes to the CS/Windows 6.4 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.4 APARs.
  2. This fixpack should only be applied to CS/Windows 6.4 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]

1.3 Files included

The Fixpack 2 release includes the following files:

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

nlspack.exe:

    Self extracting executable that contains FixPack 2 language files to be installed on the CS/Windows 6.4 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.4 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]

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

nlspack.exe: Includes the language packages for all the languages, which CS/Windows 6.4 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]

2.2 Install instructions - NLS

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]

2.2.1 Integrated with server or client update

Instructions to update the server package with the NLS updates:

  1. Replace the pcsnops.exe, adminstrings.dll, trcmsg.dll, tnsmsg.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 CSCENU.DLL,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]

2.2.2 Separate, after server or client update

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 JR37587.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.4 would use the Trace Facility installed by PCOMM. If you have installed PCOMM 5.7 CSD3 or PCOMM 5.8 on CS/Windows 6.4, PCOMM will not install its Trace Facility. In this case, NLS_INSTFIX will update the CS/Windows 6.4 Trace Facility.

If versions of PCOMM prior to 5.7 CSD3 are installed, you will not have any of the CS/Windows 6.4 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 JR37588.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]

3 Server update information
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]

3.1 APARs included

APARS included from FixPack 2
JR34211PUNAME SENT TO HOST ON REQACTPU WHEN NO_PUNAME_TO_HOST=1 SET.
JR34028LUs COULD NOT BE RE-ESTABLISHED WHEN CICS RESET SOME TN3270 SESSIONS.
JR36022PROBLEM WITH DOWNSTREAM FIXED PACING WITH DLUR WHEN WINDOW SIZE 0.
JR34029LUs HANG WHEN BOTH PARTNER TRYING TO ACTIVATE THE SESSION AT THE SAME TIME.
JR34031SYSTEM CRASH WHILE STOPPING THE NODE, WHEN THE SESSION IS ACTIVE.
JR33954CONFIGURATION APPLICATION TRAP, WHEN ATTEMPTING TO CONFIGURE EICON CONNECTION.
JR34512TRNSDT MISSING FILES.
JR36023GSKIT TLS HANDSHAKE RENEGOTIATION WEAK SECURITY CVE-2009-3555.
JR36025MEMORY LEAK IN APPNBASE WITH NMVT ALERTS QUEUED.
JR36026CS/Windows CRASH WHILE PROCESSING APPC DATA WITH INCORRECT LENGTH.
JR35775SLI_OPEN HANG AFTER LINK OUTAGE AND RECOVERY.
JR36021BLUE SCREEN, WHEN THE DLUR-DLUS PIPE FAILS DURING THE ACTIVATION OF A DLUR INTERNAL PU.
JR37433HIGH CPU USAGE, WHEN TN3270E CLIENT HAS ISSUED LARGE SYSREQ KEYSTROKES, WHILE SERVER WAITING FOR A DATA FROM HOST.
JR37455UNABLE TO ESTABLISH NEW SESSION AFTER TAKEOVER / GIVEBACK TO APPL. RESIDING ON VTAM BEYOND DLUS/NNS.
JR37217PCS3001E AND PCS5501E MESSAGE WHILE STARTING TN3270 SERVER AFTER APPLYING IP FILTER TO RUNNING NODE.
JR37751PCS3001E : MISSING OF TN3270E MESSAGES IN THE RESOURCE FILE.

APARS included from FixPack 1
JR33070SLOW PERFORMANCE RUNNING LU62 TRANSACTIONS ON SNA API CLIENT.
JR33954ERROR WHEN ATTEMPTING TO CONFIGURE EICON CONNECTION.

[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:\Program Files\IBM\Communications Server" (Communications Server installation directory) 

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

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

14/10/2010  17:24               161 IBM_Communications_Server_for_Windows.6.4.0.swtag
14/10/2010  17:22               217 PTF_V6.4.0.2_for_Communication_Server_Windows.6.4.0.2.fxtag

Directory of %systemroot%\system32\drivers 

25/10/2010  17:28            38,544 anydlc.sys
25/10/2010  16:37         1,622,745 appn.sys
25/10/2010  16:39           124,956 appnapi.sys
25/10/2010  16:31           400,157 appnbase.sys
25/10/2010  16:39            32,768 appnnode.exe
25/10/2010  16:59            24,576 csit.exe
25/10/2010  17:08            49,152 csrcmds.exe
25/10/2010  16:29            40,960 cstrcser.exe
25/10/2010  17:12            20,480 ibmcs.exe
25/10/2010  16:56            20,480 ibmsa.exe
25/10/2010  17:21            28,672 ldlcserv.exe
25/10/2010  17:21            40,960 ldlcserv6.exe
25/10/2010  16:32           103,193 llc2.sys
25/10/2010  16:21            10,776 nstrcnt.sys
25/10/2010  17:23            77,552 pdlnacom.sys
25/10/2010  17:23            15,856 pdlnadci.sys
25/10/2010  17:23            39,952 pdlnafac.sys
25/10/2010  17:23            92,480 pdlnampa.sys
25/10/2010  17:23            39,472 pdlnaoem.sys
25/10/2010  17:19             6,784 pdlncbas.sys
25/10/2010  17:19           160,448 pdlncfwk.sys
25/10/2010  17:19            12,800 pdlndint.sys
25/10/2010  17:21            64,512 pdlndldl.sys
25/10/2010  17:20            72,704 pdlndldl6.sys
25/10/2010  17:20            70,656 pdlndlpb.sys
25/10/2010  17:20            18,944 pdlndoem.sys
25/10/2010  17:20            53,248 pdlndqll.sys
25/10/2010  17:20            67,584 pdlndsdl.sys
25/10/2010  17:18             8,592 pdlnebas.sys
25/10/2010  17:18            50,496 pdlnecfg.sys
25/10/2010  17:21            67,776 pdlnemap.sys
25/10/2010  17:18            12,768 pdlnemsg.sys
25/10/2010  17:18            19,968 pdlnepkt.sys
25/10/2010  17:22            59,408 pdlnshay.sys
25/10/2010  17:21            22,480 pdlnslea.sys
25/10/2010  17:22            54,320 pdlnsv25.sys
25/10/2010  17:22            58,784 pdlnsx25.sys
25/10/2010  16:59            40,608 qeldrvr.sys
25/10/2010  17:04            53,248 rapiserver.exe
25/10/2010  16:21            20,480 trcboot.exe

Directory of %systemroot%\system32 

25/10/2010  16:21            24,576 fmt_util.dll
25/10/2010  16:20            36,864 nstrc.dll

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

25/10/2010  16:29            36,864 cstrace.exe
25/10/2010  16:29            32,768 cstrccom.dll
25/10/2010  16:28            28,672 fmteng.dll
25/10/2010  16:28            28,672 pcsfmtpi.dll
25/10/2010  20:25           132,496 trcgui.exe

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

25/10/2010  16:28            32,768 pctrcres.dll
25/10/2010  16:28            28,672 trcmsg.dll

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

3.3 New function - server

New function added in FixPack 2
1. LU62 INIT SELF ENQUEUE Option

When dependent LU6.2 sessions are activated from CS/Windows, an INIT-SELF message is sent to VTAM. In CS/Windows 6.4.0.2, the format of the INIT-SELF message was altered to not queue multiple INIT_SELF. If this LU62_INIT_SELF_ENQUEUE flag is set(LU62_INIT_SELF_ENQUEUE=1) then CS/Windows will use the Old format of the INIT-SELF which included the ENQUEUE parameter. The LU62_INIT_SELF_ENQUEUE in the .ACG file is part of the NODE definition.

The following example shows the .ACG file entry. 

   NODE=(
     ANYNET_SUPPORT=NONE
     CP_ALIAS=A
     DEFAULT_PREFERENCE=NATIVE
     DISCOVERY_SUPPORT=NO
     DLUR_SUPPORT=MULTI_SUBNET
     FQ_CP_NAME=A.A
     ARB_SUPPORT=ANY
     LU62_INIT_SELF_ENQUEUE=1
     GVRN_SUPPORT=0
     SUPPRESS_LUWID=0
     NO_PUNAME_TO_HOST=0
     DLUR_REX_PACING_SUPPORT=0
     MAX_LOCATES=150
     MAX_LS_EXCEPTION_EVENTS=200
     NODE_ID=05D00000
     NODE_TYPE=END_NODE
     REGISTER_WITH_CDS=1
     REGISTER_WITH_NN=ALL
     SEND_TERM_SELF=0
     SLI_CLOSE_SYNC_SUPPORT=0
     TP_SECURITY_BEHAVIOR=VERIFY_EVEN_IF_NOT_DEFINED
)

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.4.0.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. Active LUs Display

 Now, csdisplay can display all the LUs 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 LUs or active LUA Application Sessions 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. Snaformat enhance to format the Control Vector (X'82')
The snaformat tools is been updated to format the CV'82' Subarea characteristics subfields, the formatted trace will be presented in the .det file.

[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 JR37587.EXE in Binary format into a temporary directory.

  2. Run the JR37587.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 API_Client.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 separately. 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.4 would use the Trace Facility installed by PCOMM. If you have installed PCOMM 5.7 CSD3 and above on CS/Windows 6.4, PCOMM will not install its Trace Facility. In this case, INSTFIX will update the CS/Windows 6.4 Trace Facility.

      If versions of PCOMM prior to 5.7 CSD3 are installed, you will not have any of the CS/Windows 6.4 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.4
      3. Re-install CS/Windows 6.4
      4. Install PCOMM 5.8 (or PCOMM 5.7 CSD3 or later)
      5. Apply CS/Windows 6.4 Fixpack1 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_2.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.pre6402, then copy the updated files.

    If for some reason you rerun INSTFIX.BAT, you will receive errors during each rename because the &file.pre6402 file will already exist. The original copy of the file will be preserved in &file.pre6402 and available as a backup for restore purposes.

    If for some reason you need to restore or back out 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 6402.

  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 Stopping/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]

4 Client update information
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]

4.1 APARs included

New APARs included in FixPack 2
JR36070 TRNSDT MISSING FILES.

New APARs included in FixPack 1 since CSNT6.4 GA
None.

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

4.2 New function - client

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]

4.3 Install instructions - client

Installing the fixpack on the system:
  1. Be SURE you have downloaded the 6.4 FixPack 2 APAR package (JR37588.exe) in BINARY format.
  2. Create a temporary directory, copy the JR37588.exe, and Run JR37588.exe, which will extract API_Client.exe and nlspack.exe for the API Client
  3. Run API_Client.exe to extract all the API Client updated files
  4. Stop ALL running SNA API client applications on this machine. Check the Task Manager and stop any running API CLIENT EXEs 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 *.pre6402, then install/copy the updated the DLLs and EXEs 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 separately. 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]

4.4 Files updated - client

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) 

25/10/2010  17:47            45,056 AMISC.DLL
25/10/2010  17:48            49,152 ASPRT.DLL
25/10/2010  17:47           126,976 CCM.DLL
25/10/2010  17:47            77,824 CCS.DLL
25/10/2010  17:47           159,744 CCT.DLL
25/10/2010  17:54           131,072 CSCCFG.EXE
25/10/2010  17:54            53,248 CSCENU.DLL
25/10/2010  16:55            98,304 ibmslp.dll
25/10/2010  17:51            61,440 MGRLVL.DLL
25/10/2010  16:20            36,864 nstrc.dll
25/10/2010  17:53            40,960 RESETAPI.EXE
25/10/2010  17:53            32,768 SETCO.EXE
25/10/2010  17:51           102,400 SSET.DLL
25/10/2010  17:53            57,344 TESTLU62.EXE
25/10/2010  17:53            65,536 TRACEDG.EXE
25/10/2010  16:41            36,864 TRNSDT.DLL
25/10/2010  17:48            32,768 WAPPC32.DLL

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

14/10/2010  20:05               166 IBM_SNA_API_Client_for_Windows.6.4.0.cmptag
14/10/2010  20:05               216 PTF_V6.4.0.2_for_SNA_API_Client_for_Windows.6.4.0.2.fxtag

[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, 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 International Business Machines Corporation in the United States, other countries, or both.

Lotus and Domino are trademarks or registered trademarks of International Business Machines 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]