IBM Communications Server for Windows Version 6.1.3 is an upgrade that provides a new Windows Installer (previously called MicroSoft Installer = MSI) interface plus fixes and updates from 6.1.2. Version 6.1.3 is a full install, and if a prior version is installed, then the prior version must be uninstalled before installing version 6.1.3.
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 2000, Windows XP, Windows Server 2003 (Standard Edition or Enterprise Edition), or Windows Vista. 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 2000, Windows XP, Windows Server 2003 (Standard Edition or Enterprise Edition), or Windows Vista.
Additionally:
One of the following browsers is required to install Communications Server using the launchpad:
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.
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.1.3 is a full install, and only CSDs for 6.1.3 can be installed after this installation.
IBM provides corrective maintenance by providing:
[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.
Removing previous versions of Communications Server for Client Access
For removing version 6.1.2 or earlier versions, you should run regsvr32.exe against cwbzzodb.dll and cwbzzidx.dll. See Repair after installing or uninstalling Client Access for more information.
For removing version 6.1.3, go to Add/Remove programs and select the program and remove.
[Return to top of document] [Table of Contents]
[Return to top] [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 extended call is not supported by Communications Server for Linux or Communications Server for AIX. CPI-C in Communications Server for Windows has been changed to automatically issue the APPC TP_ENDED verb when the last conversation is deallocated. With this change, the TP_End call is still allowed but no longer required. Old Communications Server for Windows applications using TP_End will not be affected, while new programs written without TP_End will also end properly. This allows increased portability of CPI-C program code between IBM's Communications servers for Windows, AIX, and Linux.
[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 example shows the .ACG file entry.
NODE=(
ANYNET_SUPPORT=NONE
CP_ALIAS=CPNAME
DEFAULT_PREFERENCE=NATIVE
DISCOVERY_SUPPORT=NO
DLUR_SUPPORT=MULTI_SUBNET
FQ_CP_NAME=NETID.CPNAME
GVRN_SUPPORT=0
SUPPRESS_LUWID=1
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
)
[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]
Communication Server for OS/2 provided both fixed pacing and two way fixed pacing. Communications Server for Windows provides only adaptive pacing. The requirement for fixed pacing is to limit the maximum size of the pacing windows to reduce buffering requirements and reduce delays to other applications using the same link. Although Communications Server for Windows will still use adaptive pacing, fixed pacing can be simulated by setting a low limit for MAX_RECEIVE_PACING_WINDOW. The MAX_RECEIVE_PACING_WINDOW in the .ACG file is part of MODE definition. For example, the "FIXEDPAC" mode can be defined as follows:
MODE=(
MODE_NAME=FIXEDPAC
AUTO_ACT=0
COMPRESSION=PROHIBITED
COS_NAME=#CONNECT
ENCRYPTION_SUPPORT=NONE
DEFAULT_RU_SIZE=1
MAX_INCOMING_COMPRESSION_LEVEL=NONE
MAX_NEGOTIABLE_SESSION_LIMIT=3
MAX_OUTGOING_COMPRESSION_LEVEL=NONE
MAX_RU_SIZE_UPPER_BOUND=4096
MIN_CONWINNERS_SOURCE=1
PLU_MODE_SESSION_LIMIT=3
RECEIVE_PACING_WINDOW=2
MAX_RECEIVE_PACING_WINDOW=5
)
In this example, the pacing window starts at 2 (RECEIVE_PACING_WINDOW) and has 5 as the maximum value (MAX_RECEIVE_PACING_WINDOW). Note that the send pacing window is adaptive without a specified limit unless the remote node has the mode set with MAX_RECEIVE_PACING_WINDOW.
The MAX_RECEIVE_PACING_WINDOW parameter can be set by editing the .acg configuration file or using the DEFINE_MODE verb of the NOF API. The MAX_RECEIVE_PACING_WINDOW parameter can be set by the NOF call. The NOF variable used to define this parameter is max_receive_pacing_win.
[Return to top of subsection] [Return to top of document] [Table of Contents]
For the latest drivers, contact the adapter vendor. For adapters not listed above, contact the adapter vendor 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.3.
LAN adapters supported by Microsoft may also work with Communications Server for Windows. Similarly, IP LAN adapters supported by Microsoft Windows are also supported for Enterprise Extender.
[Return to top of subsection] [Return to top of document] [Table of Contents]
This value is defined in the Windows registry key "NumberRcvBuffers" (type DWORD) under "HKLM\System\CurrentControlSet\Services\pdlndldl\Parameters". Valid values are in the range 128 through 1024. To change the value, type "regedit" from a command line, and then find "NumberRcvBuffers" and "modify" to set the new value between 128 and 1024. A reboot is required for a change in this value to take effect.
Before editing the registry, see Microsoft article http://support.microsoft.com/kb/256986 for instructions and warnings.
[Return to top of subsection] [Return to top of document] [Table of Contents]
In previous versions, the discovery function was always enabled and could not be disabled. To reduce unnecessary network traffic with version 6.1.3, an option has been added to allow discovery to be disabled. It is now disabled by default.
This option is defined in the Windows registry by the key "EnableDiscovery" (type DWORD) under "HKLM\SOFTWARE\IBM\Communications Server\CurrentVersion\RAPI". Valid values are 0 (default) for disabled and 1 for enabled. If the registry key is deleted, discovery is enabled. To change the value, type "regedit" from a command line. then find "EnableDiscovery" parameter and "modify" to change the value. A reboot is required for a change in this value to take effect.
Before editing the registry, see Microsoft article http://support.microsoft.com/kb/256986 for instructions and warnings.
This can be verified via the trace utility by enabling the trace item User Services->SNA Node Operations->Procedure Trace. Start SNA Node operations. The following trace items will be found in the formatted trace file.
[77] 10/10 12:54:17.25,(004C) len=24, User services.SNA Node Operations.0001, 00000D70:00000CF8 DiscoveryThread starting [78] 10/10 12:54:17.25,(004D) len=50, User services.SNA Node Operations.0001, 00000D70:00000CF8 RAPIServer User requested discovery to be disabled [79] 10/10 12:54:17.25,(004E) len=64, User services.SNA Node Operations.0001, 00000D70:00000CF8 DiscoveryThread user requested to disable discovery via registryFrom this it can be verified that the discovery is disabled and multicast are not being sent.
[Return to top of subsection] [Return to top of document] [Table of Contents]
Use these samples to build your own configurations. It is recommended that you make copies of the samples rather than change them. The copies of the samples may be modified by using a text editor or by using Communications Server for Winows Node Configuration GUI. Use of the samples will require the following changes:
[Return to top of subsection] [Return to top of document] [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 Communications 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\Configuration with a DWORD value "0", the TN3270 advertisements will be disabled.
Steps to disable publishing:
The Windows registry value for the TCP/IP parameter for packet multicast must be changed from its default value for SLP support. This parameter determines whether IP multicasts are sent using the Token Ring Multicast address (as described in RFC 1469) or using the subnet broadcast address.
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]
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. The above behavior is applicable only for 6.1.2
For 6.1.3, Trace facility GUI is changed so as to handle Kernel level tracing even in non zero sessions. This change is done so as to support Kernel level tracing in Microsoft Vista since Vista does not have a session 0 even for the console session. However, this implementation currently has a limitation and requires administrative privilleges. In case of Domain users, using Command line tracing option will allow non administrator users to trace the kernel level options.
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 B, 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 batch file to start traces with a description of options. APPNF.bat is a sample command-line batch file to stop, save 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]
Hostname support is provided for Enterprise Extender. This includes sending the Hostname on LOCATE and also supporting Connection Networks when Hostname is used.
To avoid unnecessary DNS lookups, the EEDLC device definition has an option to not use the hostname. For IPv4 this function is for performance improvement for connection network use where the default is to pass both the IP address and the hostname on Locate control vectors. It also helps for defined links that are frequently activated and deactivated. The hostname is resolved when the node is started, but if Donot use hostname is set on the EEDLC definition, then it is not resolved again when the link is activated.
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]
IPv6 can be configured with either hostname or IP address.
[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:\Program Files\IBM\Communications Server 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]
1. PATH_SWITCH_ATTEMPTS - Number of path switch attempts to set on new RTP connections. Specify a value in the range 1-255. If you specify 0(zero), Communications Server for Windows uses the default value of 6.
2. SHORT_REQ - Limits the number of times a Status Request is sent before Communications Server for Windows determines that an RTP connection is disconnected and starts Path Switch processing. Specify a value in the range 1-255. If you specify 0(zero), Communications Server for Windows uses the default value of 6.
3. Four Path switch timers - Path switch time is the length of time in seconds for which Communications Server for Windows attempts to path switch a disconnected RTP connection. This parameter is specified as four separate time limits for each of the valid transmission priorities in order: LOW, MEDIUM, HIGH, and NETWORK. Each these must be in the range 1-65535. The value you specify for each transmission priority must not exceed the value for any lower transmission priority. If you specify 0(zero) for any of these values, Communications Server for Windows uses the corresponding default value as follows:
LOW_PATH_SWITCH_TIME = 480 seconds (8 minutes) MEDIUM_PATH_SWITCH_TIME = 240 seconds (4 minutes) HIGH_PATH_SWITCH_TIME = 120 seconds (2 minutes) NETWORK_PATH_SWITCH_TIME = 60 seconds (1 minute)NOTE: The path switch times must be ordered so that LOW > MEDIUM > HIGH > NETWORK.
The RTP_TUNING path switch timers (ALL 4) must be greater that the link timeout for the links being used. For example, EEDLC links are tested every "Inactivity timer" and is retried for "Connect retry count" before an error is detected. These parameters are configured under the IBM EEDLC for Ipv4 or IPv6 panel and EEDLC Device. The default values are inactivity timer = 10 seconds and connect retry count = 3. This means that a link failure could take (3 + 1) x 10 = 40 seconds. Prior to detecting the link failure, the path switch attempts will use the failing link and therefore be unsuccessful. When the path switch attempts fail, the sessions being routed over the HPR pipe will be terminated.
4. MAX_REFIFO_TIME - The RTP protocol uses a timer called the Re-FIFO Timer. The value of this timer is calculated as part of the protocol, but this parameter 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 (zero) means that the timer is not limited and can take any value calculated by the protocol. The default value for this parameter is 4000 milliseconds with a minimum value of 250 milliseconds. If a value specified is 1 - 249 milliseconds, 250 milliseconds is used.
Previous to this change, there was no limit on the refifo time, but now a limit is set by default. To return to previous behavior, you may set a limit of 0 (zero) as described.
5. MAX_SHORT_REQ_TIME - The RTP protocol uses a timer called the Short Request Timer. The value of this timer is calculated as part of the protocol, but this parameter 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 (zero) means that the timer is not limited and can take any value calculated by the protocol. The default value for this parameter is 8000 milliseconds with a minimum value of 500 milliseconds. If the value specified is 1-499 milliseconds then a value of 500 milliseconds is used.
Previous to this change, there was no limit on the short request time or the refifo time, but now a limit is set by default. To return to previous behavior, you may set a limit of 0 (zero) as described.
Example of RTP_TUNING changing the default path switch times in .acg file.
RTP_TUNING=(
PATH_SWITCH_ATTEMPTS=6 RANGE = 0,255 default = 6
SHORT_REQ=0 RANGE = 0,255 default = 6
LOW_PATH_SWITCH_TIME=240 RANGE = 1,65535 default = 480 seconds
MEDIUM_PATH_SWITCH_TIME=120 RANGE = 1,65535 default = 240 seconds
HIGH_PATH_SWITCH_TIME=100 RANGE = 1,65535 default = 120 seconds
NETWORK_PATH_SWITCH_TIME=60 RANGE = 1,65535 default = 60 seconds
MAX_SHORT_REQ_TIME=8000 RANGE = 0,24000 default = 8000 milliseconds
MAX_REFIFO_TIME=4000 RANGE = 0,12000 default = 4000 milliseconds
)
Display RTP_TUNING was also added to csdisplay rtn in the form:
Low Path Switch Time 480 Medium Path Switch Time 240 High Path Switch Time 120 Network Path Switch Time 60 Path Switch Attempts 6 Short Request Retry Limit 6 Maximum Short Request Time 8000 Maximum Refifo Time 4000
[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]
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]
-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]
[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\Communiactions 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]
Reference IBM software group statement at: http://www.ibm.com/support/docview.wss?uid=wws1e333ce0912f7b152852571f60074d175 Reference timing limitations from VMware at: http://www.vmware.com/pdf/vmware_timekeeping.pdf
[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, and Windows Vista 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]