Download
Abstract
Service Update for Communications Server for Windows, Version 6.1.2 -- Latest Fix Pack (JR29522)
Download Description
Contents:
- Description
- APARs fixed
- New functions and enhancements
- Legal statements
- Prerequisites
- Installation instructions
- Download instructions
Description:
This package includes the latest IBM Communications Server component APAR maintenance since Version 6.1.2 availability. All of the APAR maintenance supersedes previous APAR maintenance since general availability of the product.
FixPack 5 is the last formal maintenance for the CS/WIN 6.1.2 level. No further maintenance is planned, but individual problem-specific fixes may be produced on request. It is recommended that CS/WIN be upgraded to v6.1.3 or v6.4. For available maintenance for those levels, see:
http://www.ibm.com/software/network/commserver/windows/support/download.html
APARs fixed by FIXPACK 5:
JR29522 Cumulative Service APAR for CS/6.1.2 FixPack 5
JR28764 RAPIPIPE ANONYMOUS ACCESS MAY BE SECURITY CONCERN
JR28759 MULTIPLE RTP PIPES WITH SAME COS BETWEEN 2 ADJACENT CONTROL POINTS
JR28594 TRNSDT INCORRECT TRANSLATION OF CHARACTER E086
JR28547 TRAP IN MSGIO.DLL WHEN ISSUING CSSTOP
JR28327 TN3270 SERVER MAY SEND TWO BID REQUESTS TO CLIENT
JR28294 DETAIL DISPLAY OF TN3270 SESSION FAILS TO SHOW SECURITY
JR28065 CRASH IN APPN.SYS AFTER HOST CONNECTION IS BROKEN OR LOST
JR27955 LUA HANG IF NOTIFY SENT BEFORE ACTLU RSP
JR27528 ERROR PCS7000E AP_PARAMETER_CHECK WHEN CONFIGURING BUSTECH LINK
JR27472 IBMCS.ERR AND IBMCS.DBG WERE CREATED SOMETIME AFTER INSTALLING FIXPACK4
JR27449 UNBIND CAUSES INTERNAL CLEANUP EVEN IF ANOTHER RU'S RESPONSE IS ALREADY QUEUED
JR27253 BSOD WHILE STOPPING THE CS/WIN NODE WITH LUA APPLICATION ACTIVE
JR26764 RAPISERVER ISSUING MULTICASTS CAUSING UNWANTED TRAFFIC ON THE NETWORK
JR26513 BLUESCREEN CRASH IN X25 DURING LINKSTATION RECOVERY
JR26404 LOOP IN CP-CP SESSION RECOVERY WHEN SWITCHING BACK TO PNNS AFTER PNNS LINK COMES BACK UP
JR26010 BLUESCREEN / CRASH IN APPNAPI.SYS RUNNING LUA APPL
API CLIENT APARs fixed by FixPack 4:
NONE
APARs fixed by FIXPACK 4:
JR25146 Cumulative Service APAR for CS/6.1.2 FixPack 4
JR23011 TRAP in TN3270WN.EXE when using EXPLICIT LUs instead of a POOL.
JR23166 CPIC ERROR 080F6051,SECURITY VIOLATION with USERID.
JR23168 Services set to MANUAL fail to start at boot when running csstart -a.
JR23366 HANG RUNNING ARTIC X25 WITH CS/WIN 612.
JR23367 Windows Performance Monitor not show CS/WIN OBJECTS after CS installation
JR23522 CRASH in LLC2 when cycling NODE or rebooting.
JR23674 TRAP IN TNSERVER module TN3270wn.exe processing RUI_TERM.
JR23909 ANYNET GATEWAY MEMORY LEAK
JR24119 CRASH IN APPNBASE during boot up time.
JR24223 RUI_INIT FAILS WITH INVALID_COMMAND_COUNT error.
JR24759 INFO BUNDLER fails to create CSPDDATA.EXE after installing fixpack3.
JR24771 IBM SNA CLIENT Services fails to start after installing Fixpack3.
JR24932 UNINSTALL may fail when user is a DOMAIN ADMIN. vs LOCAL ADMINISTRATOR.
JR25010 BLUESCREEN IN APPNAPI while processing the RUI verb after RUI_TERM response being processed.
JR25017 BLUESCREEN IN APPNBASE ON LOCATE(rsp) RARE OCCURRENCE
JR25142 EEDLC IPV6 ADDRESS SUPPORT.
JR25143 IBMCSADMIN CAPABILITIES.
JR25144 QUERY_CONVERSATION ADDED TO CSDISPLAY.
JR25145 MAX_RECEIVE_PACING_WIN IN MODE DEFINITION.
JR25156 TN3270 server trap causing cycle of the node to recover.
JR25210 ADDITIONAL RTP TUNING PARAMETERS.
API CLIENT APARs fixed by FixPack 4:
NONE
FIXPACK 3.2 changes from FIXPACK 3.1
a) The instfix.bat has been changed to update a registry key to reflect a new site for submitting diagnostic data:
path="HKLM\SOFTWARE\IBM\Communications Server\CurrentVersion\Configuration"
name="Information Sender URL"
value="ftp://ftp.emea.ibm.com/toibm/windows"
type=REG_SZ
FIXPACK 3.1 changes from FIXPACK 3
a) The copy command in instfix.bat (copy ntcmpenu.bat "%snaroot%\\ntcmpd.bat") had a "\\" which should have been a "\". This prevents the updated ntcmpd.bat from being copied into place. Because the previously exiting file was renamed to ntcmpd.bat.pre6123 by instfix.bat, then this file effectively does not exist. The Information Bundler (csntpd.exe) uses this file when capturing and packaging data to be sent to IBM Support, so that data will not be captured. This file should be manually copied into place from the FixPack 3 or 3.1 package if it is missing on a server where FixPack 3 has already been installed.
b) In the NLSPACK, the ntcmp*.bat files were omitted from FixPack 3 and have been included in FixPack 3.1. These files replace the default English ntcmpd.bat with one written using the selected language, so the Information Bundler displays messages in the appropriate language.
c) The README.HTM file has been updated appropriately to reflect these changes.
d) The above items are the only differences between FixPack 3.1 and FixPack 3. If FixPack 3 is already installed, do not install FixPack 3.1; take note of the items above and correct them as appropriate.
APARs fixed by FIXPACK 3:
JR22681 Cumulative Service APAR for CS/6.1.2 FixPack 3
JR20878 TRAP IN SPLITSTACK - CLIENT SERVER
JR20883 APAR TO DOCUMENT CS/WINDOWS V612 Fixpack2.
JR21008 CRASH IN APPN.SYS HANDLING EEDLC link deactivation.
JR21053 SLI-CLOSE HANG ON SNA API CLIENT.
JR21104 NF to Information Bundler to run Silent/Quiet.
JR21107 NODE FAILS TO START AT BOOT DUE TO PDLNDLDL.SYS.
JR21180 Disable Active Directory for TNSERVER.
JR21204 VTAM ABEND0A9 RCFF13 ISTRPCRS due to CS/WIN HPR.
JR21237 CRASH IN SNAPS APPN.SYS.
JR21250 Add CONNECTION KEEP ALIVE for implicit EEDLC links.
JR21259 SNAP UPDATES.
JR21261 CRASH IN TN3270WN.EXE during cleanup up.
JR21299 LU FORMAT ERROR,INVALID CHANGE DIRECTION. Sense 400D0000
JR21316 EEDLC SOURCE PORTS now use 12000-120004.
JR21437 BLUESCREEN using IBM4758 Hardware Encryption card.
JR21518 TNserver LU HANG processing SHUTD/SHUTC.
JR21543 APAR TO DOCUMENT CS/WIN 6.1.1 Fixpack4.
JR21544 AFTER APPLYING JR20053 TN3270 CLIENT can't reconnect.
JR21546 A PACKAGE TO HELP CLEANUP CS/WIN files from bad install.
JR21604 RMCSNT does not remove new 612 device drivers.
JR21848 LUA API changed to handle bind differently.
JR21850 CSDISPLAY COMMAND FAILS TO DISPLAY tnserver data.
JR21942 Link fails to activate after host IPL.
JR22234 BLUESCREEN IN APPNBASE.
JR22419 NODE CONFIG displays wrong adapter/sap.
xxxxxxx NLS updates for non-English installations of Configuration, Node Operations, and Trace Facility tools.
API CLIENT APARs fixed by FixPack 3:
NONE
APARs fixed by FIXPACK 2:
JR20883 Cumulative Service APAR for CS/6.1.2 fixpack 2
JR20370 Support added for SSE BITS in APPN locates.
JR20377 BLUESCREEN in EEDLC reporting link failure.
JR20453 BLUESCREEN in EEDLC in link recovery.
JR20454 Hang in Node Configuration Utility.
JR20352 TRACE format incorrect.
JR20241 Access violation in client CCS.DLL.
JR20491 Trace GUI main menus blank in CS/WIN NLS versions.
JR20436 CPIC appl. hangs running dependent LU62.
JR20487 BLUESCREEN in APPN.SYS processing locates.
JR20566 HPR Performance Enhancements.
JR20830 Trap when selecting SNA counters in MS Perfmon utility.
JR21726 SENSE 20010000 OR 20110000 when running 3270 gateway.
xxxxxxx NLS updates for non-English installations of Configuration, Node Operations, and Trace Facility tools.
API CLIENT APARs fixed by FIXPACK 2:
NONE
APARs fixed by FIXPACK 1:
JR20407 Cumulative Service APAR for CS/6.1.2 fixpack 1
JR19449 Resolves 4 problems on the API CLIENT.
JR19517 BLUESCREEN running EEDLC in PDLNDOEM.SYS.
JR19595 TRAP in WINSLI32.DLL using SLI API on server
JR19828 TN3270 SERVER connection error TNS0010E.
JR19920 BLUESCREEN in APPN.SYS running EEDLC.
JR19932 GSKIT DENIAL-OF-SERVICE VULNERABI
JR20053 TN3270 Server HANG after network outage.
JR19694 CSTRACE AUTO fails if CS installed on other than C:drive.
JR19779 NODEOPS allows starting of node when already running.
JR19784 SLI_BID gets posted with incorrect data length (0).
JR19787 TN3270 SERVER LU HUNG and fails to reconnect.
JR19788 APICLIENT problem with SLI-BIND or SLI-STSN extensions.
JR19912 SNA HANG when CPs up on link other than pref. NN Srv. lnk.
JR19921 SNA LINKs fail to retry to recover link.
JR20032 SNA CP-CP sessions fail to switch to preferred NNS.
JR20159 EEDLC LIVENESS TIMER default changed to ENABLED.
JR20275 Updates to STOP NODE AND LOCATE processing.
JR20329 TN3270 SERVER sessions fail to reconnect to same LU.
JR19572 APICLIENT HANGs running PCOM 3270 LUA using cut/paste.
JR20147 Update CSTRACE to add WRITE-T0-DISK and msgid option.
JR20175 Severe Performance problems running HPR over EEDLC.
JR20436 CPIC app. HANG running dependent LU62 sessions.
API CLIENT APARs fixed by FIXPACK 1:
JR19572 PCOMM 3270 LUA hangs running on SNA API CLIENT.
JR19449 Apar addresses following problems:
Incoming attach intermittently fails.
Multiple user trace problems.
Client password authentication problems using current userid.
Erroneous return code corrected for RUI_INIT verb.
JR19788 SLI BIND or STSN extensions routines not called.
Some of the APAR maintenance introduces new function into the product and is documented in the NEWFUNC_*.TXT files included in this package. Please see NEWFUNC_*.TXT for detailed information on the new functions introduced with this package. A brief summary of the new function:
New function added in FixPack 5
SLI_CLOSE verb Synchronous support
With this feature, administrators can force the SLI_CLOSE verb to return synchronously. This is useful when migrating existing applications from other SNA stacks where the verb returns synchronously.
To enable this feature, do the following:
- Open the SNA node configuration file (.acg) using the SNA Node Configuration Verification utility.
- Add or change the Node definition to include the parameter SLI_CLOSE_SYNC_SUPPORT=1. Configuration files created with the current version of CS/Windows should already contain the keyword.
- Verify the configuration file. See the following example:
NODE=(
ANYNET_SUPPORT=NONE
CP_ALIAS=PRAVEEN
DEFAULT_PREFERENCE=NATIVE
DISCOVERY_SUPPORT=NO
DLUR_SUPPORT=MULTI_SUBNET
FQ_CP_NAME=USIBMNM.PRAVEEN
GVRN_SUPPORT=1
NODE_ID=05D00000
NODE_TYPE=END_NODE
REGISTER_WITH_CDS=1
REGISTER_WITH_NN=1
SEND_TERM_SELF=0
SLI_CLOSE_SYNC_SUPPORT=1
)CANCEL_CONVERSATION
Added a capability to end the conversation without ending the transaction program, when the remote partner has the direction. Now, customer can issue the CANCEL_CONVERSATION APPC verb to cancel the conversation, which internally issue cmcanc to end the conversation.
EEDLC enhancements
Added option for “Do not use Host Name” on an IPV6 Enterprise Extender DLC link. This means that the resolved address will be used at the local node rather than going to the name server on each link activation.
NOTE: In case of IPv6 connection network, only the host name is sent to the remote with A5 Control vector.
CPIC Communications Server Compatibility
Previously, long running CPI-C applications written for Communications Server for Windows had to issue the TP_End (XCENDT) call to release resources held by CPI-C for an active TP instance. When processing End_TP, Communications Server issues the APPC TP_ENDED verb for the specified TP instance. Upon completion of the TP_ENDED verb, Communications Server releases the control blocks associated with that TP instance.
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.
Increase EEDLC receive buffers for performance
The default number of receive buffers for EEDLC is increased from 32 in version 6.1.2 to 256 in version 6.1.2 FP5. This change improves performance on high speed links (such as gigabit ethernet), and on links with a very high number of simultaneous conversations. Increasing the number from the default of 256 ( or 0 default in registry) up to a maximum of 1024 may further improve EEDLC performance. If the value of the receive buffer size is below or above the minimum and maximum limit then the value will be set to minimum or maximum based on the registry value.
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.
Information Bundler enhancements
The information obtained and logged by Dr. Watson is the information needed by technical support personnel to diagnose an application failure. A text file (Drwtsn32.log) is created whenever an error is detected and the default debug as DrWtsn32 is configured. A crash dump file of that application also be created, which will help the support team to figure out the cause of the problem.
With this enhancement, the information bundler will collect the Dr. Watson log "drwtsn32.log" by default. If you want to ship the application dump file along with the information bundler, please use the "csntpd.exe -d" option.
Note: Most of the time we don't need the user.dmp and it is huge, so use option -d to collect the user.dmp, if required.
Increase size of pcwmsg.mlg log
The message log has four important parameters namely Default, increment/decrement, Minimum and maximum Size. Because of the amount of network traffic and the size of the hard disk available in today's server, the size of these has been increased from the previous release as given in the table below.
Previous(in KB) Current (in KB)
--------------- ----------------
Default 64 2048
Minimum 4 32
Maximum 2048 8192
In previous releases, the size of message log can be any value in size of 1kB between 4KB to 2048KB. However, in the current value of message log is restricted to one of the predefined values from 32KB, 64KB, 128KB, 256KB, 512KB, 1024KB, 2048KB, 4096KB, 8192KB.
If the value of the receive buffer size is below or above the minimum and maximum limit, then the value will be set to minimum or maximum based on the registry value.
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.
New function added in FixPack 4
- RTP_TUNING parameters for *_PATH_SWITCH_TIME, MAX_REFIFO_TIME, MAX_SHORT_REQ_TIME.
- EEDLC IPV6 address support
- EEDLC IPV4 and IPv6 will now match incoming links to defined links.
- QUERY CONVERSATION added to CSDISPLAY
- Support of restricting maximum pacing window size:
For detailed information about these new functions, see section 3.3 of the Fix Pack 4 README file.
New function added in FixPack 3
General enhancements
1. An option is provided to NOT publish TN3270 services to the LDAP Active Directory. By setting the "TN3270AdvToADS" keyword under HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Communications Server\current\Version\Config with a DWORD value of "0", the TN3270 advertisements will be disabled.
Steps to disable publishing:
1. Stop the existing running node through pcsnops.exe (SNA Node Ops).
2. Start->Run->Regedit
3. Go to HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Communications Server\CurrentVersion\Config
4. Right click on the right pane (the pane opposite to key browsing).
5. Add a new DWORD key with name TN3270AdvtToADS if it does not exist, and set it to the value to "0".
6. Restart the node.
2. A new configuration parameter has been added to allow a port to be configured to allow only a specific number of implicit inbound links for LAN connections.
The parameter "IMPLICIT_LS_LIMIT" has been added under PORT_LAN_SPECIFIC_DATA. The allowed range of values is between 0 and 65535. A value of 65535 indicates that no implicit links are allowed. The default value is 0 meaning "no limit".
This parameter affects only implicit links, links that are dynamically created to accept an inbound connection where the local SAP, remote SAP, and remote MAC address do not match any explicitly defined links. To limit the total number of inbound links, use the existing PORT parameter INB_LINK_ACT_LIM=0, which is documented in the CS/WIN Configuration File Reference.
SNAFORMAT enhancements
Option (-h) has been added to SNAFORMAT to disable HPR formatting in the summary trace.
By removing the HPR flows you can follow the API flows more easily. Disable the HPR flows by entering:
snaformat -h nstrc.tlg
Information Bundler enhancements
1. Option -q (Quiet mode) has been added to csntpd.exe to suppress popups.
This option will allow you to remotely capture an information bundler (cspddata.exe) and alleviate the requirement to "press any key to continue" and the popup window indicating the registry has been copied.
2. Option -s Suppress registry collection. This option suppresses the registry collection and hence output information bundler will not collect registry.dat nor csntreg.dat.
Note: The default infobundler behavior shows popups and collects registry information when run with no options.
EEDLC IPV4 and IPV6 enhancements
1. EEDLC can now be configured to run IPv4 (IBMEEDLC) and IPv6 (IBMEE006), each protocol using a different DLC: IBMEEDLC for IPV4 and IBMEE006 for IPV6. Ensure you define the outgoing links on the correct DLC type. IPv6 is supported only on the Windows 2003 (SP1) or XP (SP2) and above.
Existing EEDLC definitions from FixPack 2 and earlier, which used a parameter to specify whether the DLC was IPV4 or IPV6, will all be treated as IPV4 definitions because that parameter is no longer used. Links using IPV6 must be reconfigured to the new IBMEE006 DLC.
New function added in previous fixpacks:
SNA NEW FUNCTION
1. SNA Function addition of LU 6.2 session level time-out based on LU, partner LU or mode: LU62_timeout as documented in JR16867 (included in CSNT6.1.2 GA) to terminate the lu62 session on completion of the lu62 conversation. The feature was included in CS/2 and now is configurable only in the CSNT ASCII configuration file. The setting is global on all lu62 sessions with the exception of the IBM Service TPs such as the CPSVCMGR session. The lu62_timeout_value is in seconds.
LU62_TIMEOUT=(
LU62_TIMEOUT_RESOURCE_TYPE=GLOBAL_TIMEOUT
LU62_TIMEOUT_VALUE=20
)
2. 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.
NOTE: LU62_TIMEOUT is configurable only in the ACSII configuration file (.acg).
3. 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.
CLIENT NEW FUNCTION
1. Additional debug trace options.
2. Infobundler is provided to capture key client files required for problem diagnosis.
3. Ability to collect debug data into multiple trace files.
4. Ability to create two message log (MSGLOG.DAT) files.
EEDLC ENHANCEMENTS
1. New function support of option to not use Host Name on Connection Networks: Host name support for Enterprise Extender DLC connection networks is supported in GA code. However, if there is not a firewall in the network that requires host name resolution to an IP address separately on each end, then the host name would not have to be sent on the LOCATEs and resolved on the receiver. This is the way that EEDLC connection networks operate in CSNT6.1.1. There is now a checkbox under the EEDLC device configuration labeled "Do not Use IPV4 Host Name". The default is not checked. If it is checked, then the connection network A5 control vectors do not include the host name (making shorter LOCATEs) and the remote uses the IP address that is sent.
2. If host name resolution fails on an EEDLC link and an IP address is present, then attempt to connect using the IP address.
3. EEDLC link liveness timer is now always on. The range that the liveness timer can be set to was increased from 59 seconds to 255 seconds on either the EEDLC device or on the connection definition. The default remains at 10 seconds.
4. Changed the effective capacity of EEDLC and LLC2 links from 133=16 Meg to 160=157 Meg to improve HPR ramp up performance (throughput is improved).
COMMAND LINE TRACE ENHANCEMENTS
1. Trace to multiple trace files is supported from the command line (cstrace). The file size and the number of files can be specified.
2. Stop trace from the command line based on message ID.
3. Autostart trace option was incorrectly documented as /f instead of /e.
4. APPNT.BAT has been updated describing new functions. APPNT.bat is a batch file to start traces from the command line. The default API option is to truncate the data at 128 bytes. IPSTRACE is on by default. Increased the trace buffer size.
5. CSTRACE SHUTDOWN is added to APPNF to reset trace flags. APPNF.bat is a batch file to stop and format traces.
6. SNAFORMAT ENHANCEMENTS:
SNAFORMAT creates summary and detail files on traces with SDLC, EEDLC dlcs and SLI, RUI, CPIC and APPC apis by formatting the nstrc.tlg to nstrc.sum and nstrc.det.
7. Support for TCP/IP Version 6 has been added in this fixpack. The function is currently supported only on WINDOWS 2003.
PROBLEM DETERMINATION ENHANCEMENT - INFORMATION BUNDLER FOR API CLIENT
In order to better gather problem documentation for the SNA API Client, we created an Information Bundler batch job, similar to that on the Server. See client readme and newfunc for more details on this problem determination enhancement.
IBM COPYRIGHT INFORMATION:
International Business Machines Corporation 1997, 2008
Licensed program - Property of IBM . All rights reserved.
IBM and WebSphere are trademarks of International Business
Machines Corporation in the United States and/or other countries.
Java is a trademark of Sun Microsystems, Incorporated.
U.S. Government Users Restricted Rights - Use, duplication, or
disclosure restricted by GSA ADP. Schedule Contract with IBM Corp.
LIMIT OF LIABILITY:
License to the contained APAR fixes is conditioned upon the recipient
holding a license to the prerequisite product. The license terms
and conditions of the APAR fixes are the same as those for the
prerequisite product. Please see the product license for specifics.:
Prerequisites
License to the contained APAR fixes is conditioned upon the recipient holding a license to the prerequisite product: Communications Server for Windows NT/2000, Versions 6.1.0 or 6.1.1 with CSD 2.
Note: This Fix Pack should not be installed over CSD 1 or CSD3; it is intended only for CSD2.
Note: Earlier fix packs are not prerequisite to installation of the latest fix pack; all fixes and enhancements provided by earlier fix packs are included in the latest fix pack.
Installation Instructions
Installation instructions are provided in the readme file. Only the latest fix pack is necessary; it is a cumulative package of all previous fix packs. Older files are retained for those who have requirements for specific levels.
Technical Support
Technical Support: Reference the support page for Communications Server
http://www.ibm.com/software/network/commserver/windows/support/
IBM Support Center Handbook, IBM Contacts: http://techsupport.services.ibm.com/guides/contacts.html
Problems (APARS) fixed
Was this topic helpful?
Document Information
Modified date:
02 August 2018
UID
swg24007920