IBM Communications Server for Windows Version 6.1.2.3 is a CSD upgrade that includes FixPack 3 updates. It is a full install, and only FixPacks greater than FixPack 3 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 IBM Communications Server!
Check the web sites listed in section 4 for the latest information about this product.
Disk space of 25 MB is required on a startup drive for temporary use and 125 MB on any HDD for permanent use.
SNA API clients run on any hardware required by Windows 2000, Windows XP, or Windows Server 2003.
Remote Administration clients run on any hardware required by Windows 2000, Windows XP, or Windows Server 2003.
Additionally:
SNA API clients require either:
Windows platforms that are out of service (such as Windows NT) are not supported with Communications Server Version 6.1.2 and later.
[Return to top of subsection] [Return to top of document] [Table of Contents]
Avoid using national language characters in the product installation path when you install Communications Server. On some Web servers, these characters can prevent Web Administration from locating product files.
[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 Communication Server 6.1.2.3 is a refresh of the 6.1.2 GA code and includes all FixPack 3 updates. It is a full install, and only FixPacks greater than FixPack 3 should be installed after this installation.
IBM provides corrective maintenance by providing:
Each FixPack includes an installation batch file to rename production modules and copy or install new updates. The FixPack includes only APAR maintenance and is not a full product installation. You must have the previous general availability product level installed.
[Return to top of subsection] [Return to top of document] [Table of Contents]
Removing previous versions of Communications Server
Communications Server APAR JR21456 provides a cleanup package that removes prior level Communication Server code and registry information. To ensure a complete uninstallation of the product, you can download the cleanup package (JR21546) from http://www.ibm.com/support/docview.wss?rs=2262&uid=swg24009834
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.
If Personal Communications cannot be successfully uninstalled, go to
the following Communication Server support page and search the Hints
and Tips for additional information:
http://www.ibm.com/software/network/commserver/windows/support
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.
Removing previous versions of Communications Server for Web Admin
The uninstall program for Web Administration uses Windows Scripting Host (cscript.exe) to automate the removal of the virtual directories from your Web Server. If Windows Scripting Host is not installed on your computer or cannot be located by the uninstall program, some virtual directories will not be removed.
After you uninstall a previous version of Communications Server, verify that the following virtual directories have been removed from your Web Server configuration. This must be done before you can install Version 6.1.2.
csc
csc-bin
csc-pubs
csc-html
Removing previous versions of Communications Server for Client Access
You should run regsvr32.exe against cwbzzodb.dll and cwbzzidx.dll. See Repair after installing or uninstalling Client Access for more information.
[Return to top of document] [Table of Contents]
[Return to top] [Table of Contents]
With this function, a client application can search for and find Communications Server TN3270 and TN5250 services on the Windows server. Active Directory will return the Windows server's IP address and port number to the application, allowing the client to connect to the server. This works for applications using the Lightweight Directory Access Protocol (LDAP) V3 APIs or Active Directory Services Interface (ADSI) APIs on a Windows client.
To locate services within the Active Directory, specify these arguments in the filter argument of ldap_search as part of the directory search call API:
CN=IBM_CSNT* objectclass=serviceConnectionPoint
The search call provides the TN server's IP address and port number to the serviceBindingInformation parameter.
With Communication Server 6.1.2.3, an option is provided to not publish TN3270 services to the LDAP Active Directory. By setting the "TN3270AdvtToADS" keyword under HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Communications Server\CurrentVersion\Config with a DWORD value "0", the TN3270 advertisements will be disabled.
Steps to disable publishing:
[Return to top of subsection] [Return to top of document] [Table of Contents]
In the WTS environment, application-level tracing works the same way as before. Each user can start the trace facility, and only captures the application level trace entries from his applications. One user is not able to capture another user's application trace entries.
The trace facility is changed so that the user in WTS session id 0 can access the trace options for the device driver tracing, and receives the device driver trace entries. All users in WTS sessions other than session ID 0 cannot access the trace options for the device driver and will not receive any device driver trace entries.
Windows typically assigns WTS session id 0 to the first user of the WTS Server machine. Remote desktops are not assigned WTS session id 0. The format of the trace configuration file is updated to identify device driver trace options. The main trace facility window indicates whether the user can or cannot trace the device driver activity from this WTS session.
Command-line tracing has been updated to allow users other than in WTS session ID 0 to do the kernel-level tracing. Users can issue kernel level tracing options such as APPN and APPC, and Connectivity through the CSTRACE command.
The Options > Preferences menu allows you to change default trace parameters, such as those listed below. Click Reset to revert all settings.
The trace record truncation length for APPC and APPN API functions can be specified as one of the following:
LAN/LLC2 and EEDLC connectivity records can also be truncated at 128 bytes.
You can choose to have unformatted trace data written to internal trace buffers that can be saved later. You can also have the data written directly to a single file or multiple fixed-length files.
For this setting, you can also select what size trace buffer to use. Increase this setting to collect more data before the trace buffer wraps and you start to lose old data.
Default : 1024 KB
Minimum : 1 KB
Maximum : 49 152 KB
Default : 512 KB
Minimum : 256 KB
Maximum : 4096 KB
To stop trace when a specific message is issued to the Message Log, enter the message number in this input box (for example, PCS2110E). By default, there is no entry and trace only stops when you click Stop or select the Stop item from the Trace menu.
The trace file is located in the specified directory. This field shows the default working directory.
To change the default file name, enter the new name in the input box. You can also browse to the location of the file.
[Return to top of subsection] [Return to top of document] [Table of Contents]
The following options have been added. The commands and parameters are not case-sensitive.
CSTRACE LIST /L [file name]
CSTRACE START /L [file name]
CSTRACE STOP /L [file name]
CSTRACE APPLY /L [file name]
To enable the autostart option, use the following command:
CSTRACE AUTO /e 1 /L [file name]
To disable the autostart option, use the following command:
CSTRACE AUTO /e 0
To turn on APPC API and LAN tracing, the format of the trace options file should be as follows:
/f 3 /c 7 /o 1
/f 4 /c 33 /o 2
To set other command-line trace options, refer to the Quick Beginnings book, Appendix D, at http://www.ibm.com/software/network/commserver/windows/library/index.html.
For syntax help, issue the commands cstrace help
or cstrace (without additional parameters).
Refer to the Quick Beginnings document for additional CSTRACE
parameter information.
APPNT.bat is a sample command-line starting file with a description of options. APPNF.bat is a sample command-line batch file to get and format traces.
[Return to top of subsection] [Return to top of document] [Table of Contents]
You can add flags to the SNAFORMAT command, in order to create a summary and detail file. The syntax is as follows:
SNAFORMAT filename +|-s +|-d +|-h
where
filename is the name of the input trace file
(with typical .TLG extension)+s produces a summary file. The output file
has the same name as the input file, with a .SUM
extension. The -s flag does not produce a
summary file.+d produces a detail file. The output file
has the same name as the input file, with a .DET
extension. The -d flag does not produce a
detail file.+h includes HPR header data in the summary
and details files if specified. The -h flag does not
include HPR header data in the summary and detail files,
but it does format the line data flows.
The default flag settings are +s +d +h.
Type the SNAFORMAT command without any parameters
to show supported options.
The following procedure details the proper usage of the SNAFORMAT utility.
SNAFORMAT NSTRC.TLG
By default, summary and detail files are produced. The NSTRC.SUM file shows a summary of data flow events. The NSTRC.DET file gives detailed trace information, as well as all data in the original .TLG file.
[Return to top of subsection] [Return to top of document] [Table of Contents]
DISABLE_IP_ADDRESS_RESOLUTION parameter in the ASCII
configuration (.ACG) file, which prevents the call to the DNS. This
eliminates the 5 to 10 second delay.
The following example shows how to code the new parameter in the ACG file. The possible values are 0=False (address resolution is enabled) and 1=True (address resolution is disabled).
TN3270E_DEF=( AUTO_LOGOFF=0 DEFAULT_POOL_NAME=PUBLIC ENABLE_FILTERING=0 FILTER_PREFERENCE=HOSTNAME_FIRST FREQUENCY=60 KEEPALIVE_TYPE=TN_NONE LOGOFF=30 LU_TAKEOVER=0 LU_TAKEOVER_TIMER=10 TIMER=10 DISABLE_IP_ADDRESS_RESOLUTION=1 )
[Return to top of subsection] [Return to top of document] [Table of Contents]
Communications Server TN3270 Server implements the Contention Resolution Function. This function addresses problems with Keyboard Restore, Implied Keyboard Restore, Bid, and Signal. The implementation improves the performance of TN3270E clients and enhances functionality of applications that utilize such clients.
This feature includes the updates necessary to support and implement the RFC2355 Contention Resolution extension. Clients (such as IBM WebSphere Host On-Demand 7.02 or later) that support this RFC negotiate functionality during connection setup.
[Return to top of subsection] [Return to top of document] [Table of Contents]
IP Hostname support is provided for Enterprise Extender. This includes sending the IP Hostname on LOCATE and also supporting Connection Networks when IP Hostname is used.
To avoid unnecessary DNS lookups in an IPv4 environment, the EEDLC device definition has an option to not use the hostname. This function is for performance improvement for connection network use where the default is to pass both the IP address and the host name on Locate control vectors.
If all nodes are within the same firewall, the hostname will resolve to the same IP address on all nodes, and therefore the IP address can be directly used. However, if the nodes have a firewall between them, then hostname must be used so that the IP address is correctly resolved on each side. This is especially true if a router or firewall between the nodes is performing a redirection, proxy, or address translation function, so addressing by hostname must be used instead of the IP address.
[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 user ID field can also be the value System. In that case, the TP is run with SYSTEM authority and the only workstation that can be accessed is the system console.
[Return to top of subsection] [Return to top of document] [Table of Contents]
C:\IBMCS install directory.
[Return to top of subsection] [Return to top of document] [Table of Contents]
Communications Server for Windows provides an enhanced configuration panel for adapter support. This includes a configuration wizard that shows you if the adapters installed on the workstation are enabled or disabled. Only adapters bound to the LLC2 protocol are displayed in the list.
If you select Use first available LAN adapter, Communications Server uses the first enabled LAN adapter, sorted by adapter number.
The following is a typical configuration:
Adapter 0 (disabled)
Adapter 1 (enabled) Token Ring
Adapter 2 (enabled) Ethernet
In this case, Adapter 1 is used because Adapter 0 is disabled.
If your configuration is dependent on a specific adapter (for example, Adapter 2), do not enable the Use first available LAN adapter option. This is because the operating system might reassign the adapter numbers when you add an adapter, and your preferred adapter might not be the first available adapter. In this situation, select the preferred adapter from the list.
[Return to top of subsection] [Return to top of document] [Table of Contents]
LU62_TIMEOUT option allows you to terminate the
LU 6.2 session on completion of the conversation. The
LU62_TIMEOUT_VALUE specifies the time (in seconds) after
which the session will be terminated if not used by a new
conversation.
The following example shows the .ACG file entry.
LU62_TIMEOUT=( LU62_TIMEOUT_RESOURCE_TYPE=GLOBAL_TIMEOUT LU62_TIMEOUT_VALUE=20 )
The feature is configurable only in the ACG configuration file. The setting is global on all LU 6.2 sessions with the exception of the IBM Service TPs such as the CPSVCMGR session and CP-CP CPSVCMG sessions.
New in APAR JR20407 (included in 6.1.2.3), three new options have
been added for LU62_TIMEOUT_RESOURCE_TYPE:
LOCAL_LU_TIMEOUT = 2 PARTNER_LU_TIMEOUT = 3 MODE_TIMEOUT = 4
With these new types there is also a new parameter
LU62_TIMEOUT_RESOURCE_NAME
which specifies the LOCAL_LU name, PARTNER_LU name, or MODE name.
The LU62_TIMEOUT is used only for sessions with the
specified LU, PARTNER_LU or MODE name. Again, CPSVCMG and CPSVRMGR
sessions are not deactivated by this timeout.
[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]
RTP_TUNING=( PATH_SWITCH_ATTEMPTS=30 SHORT_REQ=0 )
The path switch timeout values are as follows:
You can change the PATH_SWITCH_ATTEMPTS parameter value
to get a desired interval between path switch attempts. This affects
the delay between retries. The equation is the path switch timeout
divided by the number of switch attempts set with this parameter.
Regardless of the parameter value, the minimum allowed delay is 5 seconds.
The SHORT_REQ setting specifies the number of times to send a Status Request before deciding that an RTP connection is disconnected and starting Path Switch processing.
The timer value range is 0 to 255 (seconds). The default value is 6. If 0 is specified, then the default of 6 is used.
[Return to top of subsection] [Return to top of document] [Table of Contents]
NODE
stanza of the .ACG file. The value 1 enables the feature.
GVRN_SUPPORT=1
This can also be enabled through the Node Configuration GUI tool. Define the Node then under the Advanced options, find the Enable GVRN Support check box.
[Return to top of subsection] [Return to top of document] [Table of Contents]
To set a connection network to be a non-limited resource, you must
add the following value to the CONNECTION_NETWORK stanza
in the .ACG file.
INHERIT_PORT_LIMITED_RESOURCE=YES
In addition, set the value IMPLICIT_LIMITED_RESOURCE=NO
in the PORT stanza for the port specified for the
connection network.
[Return to top of subsection] [Return to top of document] [Table of Contents]
For the latest drivers, please contact the adapter supplier. For adapters not listed above, contact the adapter supplier to determine whether the adapter is supported for Communications Server for Windows. The adapter vendor must provide the proper protocol stack drivers to run with Communications Server for Windows version 6.1.2.
LAN adapters supported by Microsoft may also work with Communications Server for Windows. Similarly, IP LAN and WAN adapters supported by Microsoft are also supported for Enterprise Extender.
[Return to top of subsection] [Return to top of document] [Table of Contents]
To enable Express Logon, select the checkbox on the ELF support configuration window located under the TN3270E Server definition hierarchy. The configuration window requires you to identify the DCAS that will be used. The DCAS can be identified by its IP address or by its host name and port number.
[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]
[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]
The following Communications Server functions are supported (on an as-is basis) through previously released TMEs using the IBMCSNT Plus module. New versions of TME may not support these features.
A detailed description of the IBMCSNT Plus module and its functions is contained in the readme.htm file in the ..\tme directory of the Communications Server product CD.
[Return to top of subsection] [Return to top of document] [Table of Contents]
A detailed description of the Tivoli Ready Enablement support is contained in the readme.htm file in the .. \tme directory of the Communications Server product CD.
[Return to top of subsection] [Return to top of document] [Table of Contents]
-Q/-q - Quiet mode to suppress popups.
This option will address the following
-S/-s - Suppress registry collection . This option when used suppresses registry collection and hence output infobundler will not collect registry.dat and csntreg.dat.
Note : The default infobundler behavior will be to show popups and collect registry information when ran with no options.
[Return to top of subsection] [Return to top of document] [Table of Contents]
The Windows default value of 1 configures the computer to use the RFC1469 Token Ring Multicast address for IP multicasts. Setting the value to 0 configures the computer to use the subnet broadcast address for IP multicasts.
Use the following procedure to enable SLP support on Windows:
MyComputer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
If the string value TrFunctionalMcastAddress already exists, reset the value in the following manner:
[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]
Refer to the SNA Node Configuration online help for more information on these parameters.
[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]
MDAC 2.1 is available from the Microsoft Web site.
[Return to top of subsection] [Return to top of document] [Table of Contents]
To restore the registry information that allows the Communications Server or SNA API client to be the OLE DB provider, run regsvr32.exe against the files cwbzzodb.dll and cwbzzidx.dll. If you have uninstalled Client Access, reregister the following files using regsvr32.exe:
[Return to top of subsection] [Return to top of document] [Table of Contents]
Windows 95, Windows 98, and Windows NT are out of support, so the SNA API Client for those platforms is provided as is, with no support.
[Return to top of subsection] [Return to top of document] [Table of Contents]
PowerBuilder has provided a fix in the PowerBuilder 6.5.1 maintenance release, and the sample works correctly with PowerBuilder 6.5.1.
[Return to top of subsection] [Return to top of document] [Table of Contents]
The required iSeries OLE DB Provider header files (ad400.h and da400.h) are shipped with Communications Server. They are included in the ..\ibmcs\sdk\win32\h directory on the Communications Server product CD.
[Return to top of subsection] [Return to top of document] [Table of Contents]
Note: After the step where you choose Add a new device from the list of devices and click Next, the Find New Hardware window is displayed. Choose No, I want to select the hardware from a list, then click Next before continuing with the next step in the procedure.
[Return to top] [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]
WTC > WTS with Personal Communications and SNA API Client > CS/Windows > z/OS
[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]
There are 3 batch files included with this new feature. These batch files update the registry with entries required for this feature. The batch files to be used for enabling or disabling this feature are:
If the option needs to be changed from append to replace or vice-versa, close all the applications, close the trace GUI (tracedg.exe) and run the relevant batch file.
Run Delete.bat after product(SNA API Client) uninstall. If Delete.bat is not run after product uninstall, some registry keys related to the product will remain in the system.
C:\CSNTAPI>INFOB
It will go through a series of 13 steps and finally collect the information (11 documents mentioned below) in trace.zip. trace.zip will be located in the directory where the traces exist.
For any problem reported, please run infobundler and send IBM support trace.zip 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]
Remote configuration can only configure a Communications Server of the same version level. For example, Version 6.1.2 remote configuration can only configure a Version 6.1.2 Communications Server node.
Use Communications Server Web Administration to administer and configure multiple levels of Communications Server remotely.
[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]
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]
To prevent the error message from displaying, change the DDE application type from Netscape to NSShell for HTML file types in the Windows Folder Options dialog. Refer to the relevant Netscape tip at http://help.netscape.com/kb/consumer/19980522-7.html.
[Return to top of subsection] [Return to top of document] [Table of Contents]
Tivoli, Tivoli Ready, Tivoli Management Environment, and TME are trademarks of Tivoli Systems Incorporated in the United States, other countries, or both.
Lotus and Domino are trademarks or registered trademarks of Lotus Development Corporation in the United States, other countries, or both.
Microsoft, Windows, Windows NT, Windows 2000, Windows XP, and Windows 2003 are trademarks or registered trademarks of Microsoft Corporation in the United States, other countries, or both.
Java, the Java logo, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.