IBM Communications Server for Windows
Version 6.4 FixPack 7
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.4 FixPack 7 is an upgrade that includes FixPack 7 updates. It is not a full install, and requires that CS/Windows V 6.4 or V6.4.0.1 or V6.4.0.2 or V6.4.0.3 or V6.4.0.4 or V6.4.0.5 or V6.4.0.6 level should be installed to install fixpack 7. Only fixpacks greater than FixPack 7 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 7 are included.

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

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 or FixPack 2 or FixPack 3 or FixPack 4 or FixPack 5 or FixPack 6. Only fixpacks greater than FixPack 7 should be installed after this installation.

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

The Fixpack 7 release includes the following files:

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

nlspack.exe:

Self extracting executable that contains FixPack 7 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]

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

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, 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]

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 JR55473.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 > nlsfp7.txt 2>&1 (silent install)
   • INSTFIX chs "C:\Program Files\IBM\Communications Server" (specify the directory)
   • INSTFIX chs "C:\Program Files\IBM\Communications Server" > nlsfp7.txt 2>&1 (silent install, specify directory)
7. Reboot and start the CS/Windows node.

NOTE:

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.9 or PCOMM 6.0 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.
2. In order to use GSKit 8 please refer to section 3.2 on retrieving the latest GSKit level from Fix Central.
3. If the fixpack7 is installed on top of CS/Windows v6.4.0.4 or V6.4.0.3 then TN3270 SSL port may not get activated. To fix, please refer to section 3.2 on updating to the latest GSKit level.

SNA API 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 JR55488.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 New function - server
3.3 Install instructions - server

[Return to top] [Table of Contents]

APARS included from FixPack 7
JR55374	SOME TN3270 SESSIONS MAY HANG WHEN HOST APPL TERMINATES
JR55055	GSKIT HASH SELECTOR LOGIC DOES NOT SELECT FROM ALLOWED SET FOR TLS1.2
JR54811	GSKIT FIX FOR CONNECTION TIMEOUT RECOVERY OF SESSION
JR54157	JVM CRASH FROM WCPIC32.DLL
JR53780	MALFORMED ECPARAMETERS CAUSES INFINITE LOOP (CVE-2015-1788)
JR53585	CSWIN NODE TAKES A LONG TIME TO START
JR53091	The RC4 BAR MITXVAH ATTACK FIX REMOVES RC4 CIPHERS FROM SSL
JR52865	GSKit EPHEMERAL RSA VULNERABILITY (CVE-2015-0138)
JR52855	GSKIT FREAK VULNERABILITY Fix
JR52832	AFTER OUTAGE CP-CP SESSIONS RETRY TOO QUICKLY THEN GIVE UP
JR52457	RSETUP RETRY TIMER IS TOO SHORT
JR52421	AUTOLOGON SUPPORT BIT IS LEFT ON WHEN REPLYING TO LOCATE

APARS included from FixPack 6
JR48173	WTSQUERYUSERTOKEN FAILED
JR48671	REFIFO NOT ENABLED ON CPSVCMG PIPE
JR51151	TRCGUI FAILS TO START
JR49449	SLI_OPEN/RUI_INIT REJECTED AFTER LU RESET
JR49602	CP-CP SESSIONS MAY NOT RECOVER AFTER OUTAGE
JR51178	SNA 3270 PRINTER SESSION DOES NOT RECOVER AFTER HOST APPLICATION RESTART
JR51189	DLUR INTERNAL PU DOES NOT AUTO-ACTIVATE WHEN LU FROM POOL IS ACCESSED

APARS included from FixPack 5
JR45675	SLI_CLOSE AND SLI_BID ON API CLIENT PRODUCE WRONG RESULTS.
JR46455	CSWIN INCORRECTLY REPORTS PRINTER SESSIONS ONLINE TO HOST
JR47065	UNABLE TO READ FIRST COUNTER VALUE
JR47520	HPR HANG DUE TO HOST GAP MESSAGE PACKET BEING DROPPED IN THE NETWORK.
JR47527	VRN DELETED FROM TOPOLOGY AFTER 15 DAYS.
JR47510	POSSIBLE HANG OR CRASH WHEN APPLICATION EXIT WITHOUT PROPER CLEANUP.

APARS included from FixPack 4
JR39438	PCS5920E SEEN WHEN STARTING CSWIN FROM COMMAND LINE BUT NOT WHEN USING NODE OPS TOOL
JR41157	TRAP IN TN3270 SERVER
JR41158	CPIC API USES INCORRECT LU
JR41892	MEMORY LEAK IN TN3270 SERVER WHEN USING SSL
JR42892	TN3270 SERVER HANGS WHEN A BIND WITH USER DATA IS RECEIVED
JR43387	PRINTER LOSES CONNECTION WHEN SSCP TAKEOVER OCCURS
JR44768	CRASH IN APPN.SYS
JR44764	ASSERT IN NRTPAPI.C
JR44778	805000B RECEIVED WHEN LOGGING IN TO 3270 APPLICATION
JR44767	MODIFICATIONS TO RTP_TUNING TO ALLOW SMALLER REFIFO AND SRT CAPS

APARS included from FixPack 3
JR37752	PCS3001E WITH STYSTEM ERROR 1813.
JR38860	NEW FUNCTION: SUPPORT FOR GSKIT 8 TLS 1.2
JR39149	Cumulative APARS for Communication Server for Windows v6.4.0.3

APARS included from FixPack 2
JR34211	PUNAME SENT TO HOST ON REQACTPU WHEN NO_PUNAME_TO_HOST=1 SET.
JR34028	LUs COULD NOT BE RE-ESTABLISHED WHEN CICS RESET SOME TN3270 SESSIONS.
JR36022	PROBLEM WITH DOWNSTREAM FIXED PACING WITH DLUR WHEN WINDOW SIZE 0.
JR34029	LUs HANG WHEN BOTH PARTNER TRYING TO ACTIVATE THE SESSION AT THE SAME TIME.
JR34031	SYSTEM CRASH WHILE STOPPING THE NODE, WHEN THE SESSION IS ACTIVE.
JR33954	CONFIGURATION APPLICATION TRAP, WHEN ATTEMPTING TO CONFIGURE EICON CONNECTION.
JR34512	TRNSDT MISSING FILES.
JR36023	GSKIT TLS HANDSHAKE RENEGOTIATION WEAK SECURITY CVE-2009-3555.
JR36025	MEMORY LEAK IN APPNBASE 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	BLUE SCREEN, WHEN THE DLUR-DLUS PIPE FAILS DURING THE ACTIVATION OF A DLUR INTERNAL PU.
JR37433	HIGH CPU USAGE, WHEN TN3270E CLIENT HAS ISSUED LARGE SYSREQ KEYSTROKES, WHILE SERVER WAITING FOR A DATA FROM HOST.
JR37455	UNABLE TO ESTABLISH NEW SESSION AFTER TAKEOVER / GIVEBACK TO APPL. RESIDING ON VTAM BEYOND DLUS/NNS.
JR37217	PCS3001E AND PCS5501E MESSAGE WHILE STARTING TN3270 SERVER AFTER APPLYING IP FILTER TO RUNNING NODE.
JR37751	PCS3001E : MISSING OF TN3270E MESSAGES IN THE RESOURCE FILE.

APARS included from FixPack 1
JR33070	SLOW PERFORMANCE RUNNING LU62 TRANSACTIONS ON SNA API CLIENT.
JR33954	ERROR WHEN ATTEMPTING TO CONFIGURE EICON CONNECTION.

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

New function added in FixPack 7
1. Support for GSKit v8 maintenance stream 8.0.50.57
	The Communications Server for Windows v6.4.0.7 media pack contains the full release level of the product that supports GSKit 8 level 8.0.50.57. This level fixes a problem where TLS 1.2 clients may be allowed ciphers that are not specified correctly. This fix makes sure that only TLS 1.2 allowed ciphers are available for negotiations. The Communications Server for Windows 6.4.0.7 also include other APARs that remove less secure ciphers such as RC4, and specifies more higher secure ciphers.
	The GSKit package for CS Windows is included in the full package refresh image found on Fix Central and in the entitled APAR JR55055, also found on Fix Central. The Fixpack package that provides the partial fix installation to bring an existing Communications Server for Windows install to the 6.4.0.7 level does not include the JR55055, or GSKit 8.0.50.57 level. If the Fixpack installation package is installed, the JR55055 will also need to be installed to set the TN3270 Server SSL level to 8.0.50.57.

New function added in FixPack 6
1. Support for GSKit v8 maintenance stream 8.0.50.31
	The Communications Server for Windows v6.4.0.6 media pack contains the full release level of the product that supports GSKit 8 level 8.0.50.31. This GSKit update addresses multiple issues, including: a crash in TN3270 Server function with a large number >1500 of SSL sessions under stress. In order to use GSKit 8 level 8.0.50.31, you will need to order this media pack and install the product. The Fixpack 6.4.0.6 (Fixpack 6) does not contain the GSKit 8 release package.Hence, the product upgrade with fixpack will maintain at the GSK level, where the IBM Communications Server installed with media pack.

New function added in FixPack 5
1. Support for GSKit v8 maintenance stream 8.0.50.5
	The Communications Server for Windows v6.4.0.5 media pack contains the full release level of the product that supports GSKit 8 level 8.0.50.5 . In addition to this support, GSKit 8 provides the ability to negotiate higher ciphers for SSL communinications with TN3270 clients. In order to use GSKit 8 level 8.0.50.5, you will need to order this media pack and install the product. The Fixpack 6.4.0.5 (Fixpack 5) does not contain the GSKit 8 release package.Hence, the product upgrade with fixpack will maintain at the GSK level, where the IBM Communications Server installed with media pack.

New function added in FixPack 4
1. RTP_TUNING Parameter Changes
	Communications Server for Windows v6.4.0.4 provides lower upper limits of two APPN protocol timers detailed below. MAX_SHORT_REQ_TIME: Required Keyword Type Unsigned Number Default 8000 Range 5-24000 Multiples Allowed? No The RTP protocol uses a timer called the Short Request Timer. The value of the timer is calculated as part of the protocol, but MAX_SHORT_REQ_TIME specifies a maximum value in milliseconds, beyond which the timer cannot increase. In some situations, setting this maximum value can improve performance. Setting a value of 0 means that the timer is not limited and can take any value calculated by the protocol. The minimum value is 5 milliseconds, with a default value of 8000 milliseconds. If the specified value is 1-4 milliseconds, a value of 5 milliseconds is used. MAX_REFIFO_TIME: Required Keyword Type Unsigned Number Default 4000 Range 5-12000 Multiples Allowed? No The RTP protocol uses a timer called the Re-FIFO Timer. The value of the timer is calculated as part of the protocol, but MAX_REFIFO_TIME specifies a maximum value in milliseconds, beyond which the timer cannot increase. In some situations, setting this maximum value can improve performance. Setting a value of 0 means that the timer is not limited and can take any value calculated by the protocol. The minimum value is 5 milliseconds, with a default value of 4000 milliseconds. If the specified value is 1-4 milliseconds, a value of 5 milliseconds is used.

New function added in FixPack 3
1. Support for GSKIT 8 and TLS 1.2
	The Communications Server for Windows v6.4.0.3 media pack contains the full release level of the product that supports GSKit 8 and TLS 1.2. In addition to this support, GSKit 8 provides the ability to negotiate higher ciphers for SSL communinications with TN3270 clients. In order to use GSKit 8 with TLS 1.2, you will need to order this media pack and install the product. The Fixpack 6.4.0.3 (Fixpack 3) does not contain the GSKit 8 release package.Hence, the product upgrade with fixpack will maintain at the GSK level, where the IBM Communications Server installed with media pack. The fixpack will support GSK TLS Renegotiation mentioned under New function added in Fixpack2.

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]

Installing the fixpack on the system:

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

2. Run the JR55473.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.2 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.9 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.9 (or PCOMM 5.7 CSD3 or later)
      5. Apply CS/Windows 6.4 Fixpack7 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_7.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 *.pre6407, then copy the updated files.

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

6. After running INSTFIX.BAT, confirm ALL component 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]

Section Table of Contents
4.1 APARs included in SNA API Client
4.2 New functions added in SNA API Client
4.3 Install instructions for SNA API Client
4.4 Install instructions for Remote Admin Client

[Return to top] [Table of Contents]

New APARs included in FixPack 3, FixPack 4, FixPack 5, FixPack 6 and FixPack 7

None.

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]

New function added in FixPack 6

SNA API Client Authentication variables support

The SNA API Client design is to assume authentication has previously occurred, so the SNA API Client only passes the userid and no password to the server. If this fails, then the SNA API Client tries to authenticate again, this time passing both the userid and password to the server. When the SNA API Client is configured to use userid and password to authenticate to the CSWIN Server, authentication failures for that userid may be seen in the Windows security event log. This behavior is very old, and changing it could risk breaking existing environments that are working. An option to change this behavior has been introduced: If the system environment variable CS_CLIENT_AUTHENTICATE_KEY is give the value "TRUE", both the userid and password will be sent on the initial authentication attempt. A reboot may be required for this environment variable setting to take effect. To restore the original behavior, remove this environment variable, then reboot.

New function added in FixPack 2, FixPack 3, FixPack 4, FixPack 5 and FixPack 7

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.4 FixPack 7 APAR package (JR55488.exe) in BINARY format.
2. Create a temporary directory, copy the JR55488.exe, and Run JR55488.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 *.pre6407, 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]

Installing the fixpack on the system:

1. Downloaded the 6.4 FixPack 7 APAR package (JR55522.exe) in BINARY format.
2. Create a temporary directory, copy the JR55522.exe, and Run JR55522.exe, which will extract RAdminClient.exe for the Remote Admin Client.
3. Stop ALL running Remote Admin Client applications on this machine.
4. INSTFIX.BAT is an installation batch file. INSTFIX.BAT will backup the files by renaming the files to *.pre6407, then copy the updated DLLs and EXEs to the install folder. View the comments included in INSTFIX.BAT usage instructions.

Note: If language is not mentioned then english language will get installed by default.

[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

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