IBM Communications Server for Windows Version 6.4 is an upgrade version of Version 6.1.3 that provides a new functionality of Progressive ARB, Path Switch Delay, IPv6 support for TN3270E and SNA API Client, Java for CPI-C support of Java 1.6. It also provides the latest maintenance updates from Version 6.1.2 & 6.1.3. Version 6.4 is a full install, and if a prior version lower than 6.1.3 is installed, then the prior version must be uninstalled before installing version 6.4.
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 IBM Communications Server!
Check the web sites listed in section 4 for the latest information about this product.
Disk space of 5 MB is required on a startup drive and 175 MB on any hard disk drive for permanent use.
SNA API clients run in 32 bit mode on any hardware required by Windows XP, Windows Server 2003 (Standard Edition or Enterprise Edition), Windows Vista, or Windows Server 2008. SNA API clients require 25 MB on any hard disk drive for permanent use.
Remote Administration clients run on any hardware required by 32 bit operating systems for Windows XP, Windows Server 2003 (Standard Edition or Enterprise Edition), Windows Vista, or Windows Server 2008.
Additionally:
One of the following browsers is required to install Communications Server using the launchpad:
SNA API clients require either:
You can also view the Quick Beginnings documentation from the installation package.
[Return to top of subsection] [Return to top of document] [Table of Contents]
[Return to top of subsection] [Return to top of document] [Table of Contents]
[Return to top of subsection] [Return to top of document] [Table of Contents]
This Communications Server 6.4 is a full install, and only CSDs for 6.4 can be installed after this installation.
IBM provides corrective maintenance through:
You can find the latest fixpacks and CSDs for Communications Server for Windows
under the Websphere brand located at Fix Central :
http://www.ibm.com/support/fixcentral/
[Return to top of subsection] [Return to top of document] [Table of Contents]
For Windows Installer 4.0 on Windows Vista and greater, Communications Server products have verbose logging of the install/uninstall enabled by default. However, for Windows systems prior to Vista, by default, uninstalls initiated from "Add or Remove Programs" will not be logged.
Earlier systems need the following entry added to the machine's registry in order to log uninstalls from "Add or Remove Programs":
In order to log an uninstall, before uninstalling for any of the three Communications Server products, run msilogging_add.reg which is installed under Tools under the main Communications Server install directory to update the registry.
Note: Since Windows Installer logging applies to all products which are installed/uninstalled on the system, leaving this logging enabled can affect performance and disk space.
After uninstalling, run msilogging_remove.reg to remove the entry. Even though the product has been uninstalled, the msilogging files will still be under Tools under the main Communications Server install directory. These files are not uninstalled with the product.
The install logs will be in the log directory specified when installing the product. When the product is uninstalled using "Add or Remove Programs", the uninstall log will be under the machine's TEMP directory. The log file name will have the format MSI***.log where *** is some number. Use the datestamp to determine which file corresponds to the Communications Server uninstall.
[Return to top of subsection] [Return to top of document] [Table of Contents]
Removing previous versions of Communications Server
Communications Server version 6.1.2 APAR JR21456 provides a cleanup package that removes 6.1.2 and prior level Communications Server code and registry information. To ensure a complete uninstallation of prior Communications Server product, you can download the cleanup package (JR21546) from http://www.ibm.com/support/docview.wss?rs=2262&uid=swg24009834
Uninstallation instructions are located in the Quick Beginnings book at http://www.ibm.com/software/network/commserver/windows/library/index.html
You can also view the Quick Beginnings from the installation media.
If Personal Communications is installed on the same machine as Communications Server, you must uninstall Personal Communications before uninstalling Communications Server.
If Personal Communications cannot be successfully
uninstalled, go to the following Communications Server support page and search
Technotes for additional information:
http://www.ibm.com/support/search.wss?tc=SSHQNF&rs=2262&rank=8&dc=DB520+D800+D900+DA900+DA800+DB560&dtm
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.
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.
http://www.ibm.com/software/network/commserver/support.
This Web site provides information and links to code fixes, tips, newsgroups, maintenance, and much more.
[Return to top] [Table of Contents]
NOTE: AnyNet SNA over IP does not support IPV6 addressing. The AnyNet function in the Communications Server for Windows is being sunset in the next release. You should plan to replace this function with Enterprise Extender or the use of a SNA API Client implementation.
[Return to top of subsection] [Return to top of document] [Table of Contents]
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 subsection] [Return to top of document] [Table of Contents]
The required synchronization level can be selected, when defining the Transaction Program from the basic panel of Node configuration application.
[Return to top of subsection] [Return to top of document] [Table of Contents]
This parameter can set/unset in the Configuration GUI under the Node definition Advanced panel, as well as in the .ACG file.
[Return to top of subsection] [Return to top of document] [Table of Contents]
To customize RTP operation, specify one of the following values for the above ARB_SUPPORT keyword in NODE section:
[Return to top of subsection] [Return to top of document] [Table of Contents]
The default value for this parameter is zero, indicating that a path switch attempt can occur as soon as the protocol indicates it is required.
Please refer chapter 23 RTP_TUNNING section in Configuration File Reference manual for more information.
[Return to top of subsection] [Return to top of document] [Table of Contents]
The DISABLE_REMOTE_ACT in the .ACG file is part of LINK_STATION definition. This parameter can be set/unset in the Link Station definition under reactivation panel.
[Return to top of subsection] [Return to top of document] [Table of Contents]
If this occurs, you should manually terminate the SNA API Client executables. The command line utility resetapi.exe is installed with the Windows client APIs. This utility terminates the SNA API Client executables, without requiring a reboot of the client.
[Return to top of subsection] [Return to top of document] [Table of Contents]
Remote Desktop Clients <====> WTS with Personal Communications and SNA API Client <====> CS/Windows <====> z/OS host
[Return to top of subsection] [Return to top of document] [Table of Contents]
Configuration on WTS is as follows:
For example, if the user 1 configuration is located in the file C:\user1\user1.ini and the user 2 configuration is located in C:\user2\user2.ini, the configuration is as follows:
There is no other change to the configuration procedure. The configuration of LUA sessions, transaction programs, and so on remain unchanged. The Personal Communications configuration does not need to be changed. The steps for configuring Personal Communications or any LU application remain the same.
[Return to top of subsection] [Return to top of document] [Table of Contents]
The default values (file size and maximum number of files) can be changed with the command tracedg /s FileSize /n MaxNum. This value is global. The value set by one user will affect all the users.
For example, tracedg /s 92160 /n 20 will create each pcatrace file of size 90k, and the maximum number of files that will be created is 20. After 20 files, the first file will be over-written.
C:>INFOB
It will go through a series of 13 steps and finally collect the information (11 documents mentioned below) in cspd.exe. cspd.exe will be located in the installation directory ( default C:\Program Files\IBM\CS SNA API Client).
For any problem reported, please run infobundler and send IBM support cspd.exe file.
The summary of features of the Infobundler for SNA API Client is as follows:
[Return to top of subsection] [Return to top of document] [Table of Contents]
Schema extensions are provided for Netscape Directory Server and must be added to the server configuration before configuring the SNA API clients. The other supported directory servers already contain the necessary schema definitions. Access control for entries and attributes must be controlled using the directory server's administration utility.
The SNA API LDAP configuration utility allows you to modify the extended entries. The user ID used with this utility must have access to write entries into the directory. You can use the directory administrator ID (which has these permissions) when executing the client configuration utility.
To add the schema extensions to the Netscape server, add the following lines to the slapd.conf file, which is located in the \config directory of the Netscape directory server.
include ibmcs-oc-ns.conf
include ibmcs-at-ns.conf
The exact path name of this directory is dependent on where the directory server is installed and the name of the directory server. See the following example:
drive_letter:\netscape\suitespot\slapd-hostname\config
[Return to top of subsection] [Return to top of document] [Table of Contents]
[Return to top of subsection] [Return to top of document] [Table of Contents]
[Return to top of subsection] [Return to top of document] [Table of Contents]
PATHNAME=C:\IBMCS\apingd.exe to PATHNAME=C:\Program Files\IBM\Communications Server\apingd.exe
This can be changed by either editing the .acg configuration file or from the configuration GUI under "CPIC and APPC -> Transaction Programs."
[Return to top of subsection] [Return to top of document] [Table of Contents]
Communications Server for Windows allows you to configure various levels of encryption (High, Medium, Authenticate Only) for a TN3270(E) or TN5250 port definition. These encryption levels are found in the Security panel of the Define TN3270 Port Definitions dialog.
Some TN3270 or TN5250 clients (such as Host On-Demand Version 5) do not make full use of the SSLv3 information that Communications Server advertises in an SLP packet. These clients connect to the first port with the SSL level, scope, pool, and load that they requested, without regard to the encryption level. The resulting connection might result in a session connecting to a port with a different encryption level than intended.
To avoid this situation, use only one encryption level (High, Medium, or Authenticate Only) for each machine or scope. Ports on a given server can be uniquely targeted by enabling and disabling Security and Client Authentication.
[Return to top of subsection] [Return to top of document] [Table of Contents]
[Return to top of subsection] [Return to top of document] [Table of Contents]
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, and Windows Server 2008 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]