IBM® Connect:Direct® for Microsoft Windows 6.0.0
Fix List Document

This document describes maintenance updates for IBM® Connect:Direct® for Microsoft Windows 6.0.0. It includes information and instructions for all product features, including the Server, Requester, Common Utilities, Secure+, JRE, PostgreSQL and the SDK. Maintenance updates are always cumulative and provided as fix packs or interim fixes (iFixes).

Contents
•	Important Notices
•	About Fix Packs and iFixes
•	Before running the Installer
•	Applying a Fix Pack or iFix to an existing Installation
•	Performing a new Installation or an Upgrade of an existing Installation
•	Description of iFixes and Updates

Important Notices
•	When upgrading from IBM Sterling Connect:Direct for Microsoft Windows 4.7.0 or 4.8.0 with Secure+ installed and the Secure+ configuration initially was created by a version prior to 4.7.0, then perform the upgrade installation using 6.0.0.2_iFix007 or later (see APAR IT29623).
•	Before applying a fix pack or iFix to IBM Connect:Direct for Microsoft Windows installed in a failover cluster environment, see the instructions in the white paper Deploying IBM Connect:Direct for Microsoft Windows in a Failover Cluster at http://www-01.ibm.com/support/docview.wss?uid=swg27040600.

About Fix Packs and iFixes

Fix packs and interim fixes (iFixes) deliver maintenance and updates to an existing product version of IBM Connect:Direct for Microsoft Windows. They are cumulative and include iFixes as well as updates added since the previous fix pack and in any earlier fix pack. You only need to apply the latest one available. 
Fix packs and critical iFixes can be downloaded from the IBM Fix Central website at https://www.ibm.com/support/fixcentral/. Non-critical iFixes are typically provided by IBM Support in response to a customer PMR to address the reported issue. They can also be requested though IBM Support on demand. 

Fix packs and iFixes are provided as a single installer executable (.exe). File naming conventions refer to the product name, version, fix pack (fp) and iFix (if) if applicable. Here are some examples:

•	Connect:Direct 6.0.0.0_iFix001
6.0.0.0-IBMConnectDirectforMicrosoftWindows-x64-fp0000-if001.exe
•	Stand-alone Connect:Direct Requester 6.0.0.0_iFix001
6.0.0.0-IBMConnectDirectRequesterStandAlone-x86-fp0000-if001.exe
•	Connect:Direct SDK/SDK.Net 6.0.0.0_iFix001
6.0.0.0-IBMConnectDirectSDK-x64-fp0000-if001.exe

Before running the Installer

•	Review the fix list document (CDWin600FixList.rtf) carefully. It provides details on individual fixes, updates and changes included in a fix pack. It includes information on all features including Server, Requester, Common Utilities, Secure+, JRE, PostgreSQL and SDK. 
•	Log on with an account that has appropriate permissions to install software, typically an administrator account. When performing a silent mode installation, make sure the command prompt or batch file already has this permission prior to executing the actual command, for example by using 'Run as administrator' (RAA).
•	It is recommended to have a backup.
•	Close all other applications.

Applying a Fix Pack or iFix to an existing Installation

Use the installer to apply a fix pack or iFix to an existing installation of IBM Connect:Direct for Microsoft Windows 6.0.0. Update mode is enabled by specifying SEPATCH_ONLY_FLAG=1 on the command line (default).
Interactive Mode
To apply a fix pack or iFix interactively, simply double-click the installer in Windows Explorer or run it from the command line. When no arguments are specified, the default command will be equivalent to:
<InstallerExe> /v"SEPATCH_ONLY_FLAG=1 /l*v CDWinPatch.log"
Silent Mode
To apply a fix pack or iFix in silent mode, enter the following command line:
<InstallerExe> /v"SEPATCH_ONLY_FLAG=1 /l*v CDWinPatch.log /qn" /s /w /clone_wait
The command will wait for completion (/w /clone_wait) and return 0 if the operation was successful. Review the log file in case of a failure. Provide this log file when reporting an installation problem to IBM Support.

Performing a new Installation or an Upgrade of an existing Installation

Use the installer to perform a fresh installation of IBM Connect:Direct for Microsoft Windows 6.0.0 or to upgrade from an existing older release.
Interactive Mode
To install or upgrade interactively, enter the following command line and choose install or upgrade during the installation:
<InstallerExe> /v"/l*v CDWinInst.log"
Silent Mode
To install or upgrade in silent mode, configure your server property file (cd_srvr.ini) accordingly and enter the following command line:
<InstallerExe> /v" CD_SRVR_INI_FILE=C:\cd_srvr.ini /l*v CDWinInst.log /qn" /s /w /clone_wait
The command will wait for completion (/w /clone_wait) and return 0 if the operation was successful. Review the log file in case of a failure. Provide this log file when reporting an installation problem to IBM Support.
See the online documentation for details on customizing a silent installation.

Description of iFixes and Updates

iFixes after 6.0.0.0

6.0.0.0_iFix001:  CDWA-524
Description of Issue:  Incorrect error message LSCF011I raised when trying to add a duplicate user proxy.
Description of Fix:  Added a new message LSCF019I: The object &ITEM already exists in user proxy.
Fix Availability Date:  07 December 2018
High Impact:  N
Reported Severity:  3

6.0.0.0_iFix002:  CDWA-526
Description of Issue:  CD Requester does not prevent the current user from deleting himself from Functional Authorities when the current user name does not exactly match the entry defined.
Description of Fix:  The check to prevent this has been updated to perform a case-insensitive comparison.
Fix Availability Date:  20 December 2018
High Impact:  N
Reported Severity:  4

6.0.0.0_iFix003:  CDUA-1235
Description of Issue:  Delete remote node whose alias node name with upper case letter is present, returns error code SPCG270E.
Description of Fix:  Change node name to lower case before validating whether node file exists or not. On UNIX, file name is case sensitive and validation fails if file name case doesn't match.
Fix Availability Date:  24 December 2018
High Impact:  N
Reported Severity:  3

6.0.0.0_iFix004:  CDWA-480
Description of Issue:  API applications issuing a stop command may receive an error message like "Connection Exception! End of file in CommunicationBuffer::Receive()."
Description of Fix:  For Stop node command send the response before executing the command and introduced a delay of 1000ms between response and command execution. 
Fix Availability Date:  8 January 2019
High Impact:  N
Reported Severity:  4

6.0.0.0_iFix005:  MFT-10036 / APAR IT27758
Description of Issue:  When changing properties of a previous Select Statistics query in CD Requester, the Date/Time Range filter may eventually get lost.
Description of Fix:  Added code to preserve the Date/Time Range settings.
Fix Availability Date:  14 January 2019
High Impact:  N
Reported Severity:  3

6.0.0.0_iFix006:  CDUA-1233
Description of Issue:  SEAServer node's Override,ClientAuth,EncryptData parameter's update request should return error and shall not be displayed over SPCLI.
Description of Fix:  Stop update/display operation from SPCLI over SEAServer node's Override/ClientAuth/EncryptData parameters.
Fix Availability Date:  05 February 2019
High Impact:  N
Reported Severity:  4

6.0.0.0_iFix007:  CDWA-501
Description of Issue:  When GET command used for the API "Translation Table Service" with a non-existing translationTableName, some garbage value is coming in the field "translation data".
Description of Fix:  Handled the case by throwing an error if user has given non-existing translation table name in GET command of "Translation Table Service" API.
Fix Availability Date:  22 February 2019
High Impact:  N
Reported Severity:  4

6.0.0.0_iFix008:  MFT-10153
Description of Issue:  Substitution variables &ERC, &EFDBK and &ETXT are logged with some, mostly internal statistics message, but are never used and have incorrect values.
Description of Fix:  Removed the unused substitution variables. 
Fix Availability Date:  22 February 2019
High Impact:  N
Reported Severity:  4

6.0.0.0_iFix009:  MFT-10055
Description of Issue:  Selecting Help > Help Topics in CD Secure+ Admin Tool opens the IBM Sterling Connect:Direct V5.2.0 documentation site.
Description of Fix:  Updated the URL to link to the IBM Connect:Direct for Windows 6.0 documentation site.
Fix Availability Date:  22 February 2019
High Impact:  N
Reported Severity:  3

6.0.0.0_iFix010:  CDWA-500
Description of Issue:  Netmap protocol value should not be changed when trying to update via "Netmap Path Service" API.
Description of Fix:  Handled the case by throwing an error if user tries to change the protocol value through "Netmap Path Service" API.
Fix Availability Date:  06 March 2019
High Impact:  N
Reported Severity:  4

6.0.0.0_iFix011:  MFT-10244 / APAR IT28634 / CVE-2018-12547
Description of Issue:  A vulnerability has been found in the IBM Runtime Environment Java Technology Edition, Version 8 used by IBM Sterling Connect:Direct for Microsoft Windows. IBM Sterling Connect:Direct for Microsoft Windows has addressed the applicable CVE.
Description of Fix:  Updated the IBM Runtime Environment Java.
Fix Availability Date:  01 April 2019
High Impact:  Y
Reported Severity:  2

All iFixes and fix packs listed above are accumulated in fix pack 1 (6.0.0.1).

iFixes after 6.0.0.1

6.0.0.1_iFix001:  CDWA-459
Description of Issue:  "select statistics recids=stop;" command fails with error LAPP005I: LAPP005I - Misuse of keyword  : stop
Description of Fix:  Implemented a new functionality to remove the checking of restricted keywords in record ids. 
Fix Availability Date:  11 April 2019
High Impact:  N
Reported Severity:  4

6.0.0.1_iFix002:  CDWA-722
Description of Issue:  No Result found for User Authority if try to execute the Get API with domain=*All&group=*All in WL installer
Description of Fix:  Make registry path White Label in function "SDCFI_group_list" to read group list in White Labeled installer 
Fix Availability Date:  16 April 2019
High Impact:  N
Reported Severity:  3

6.0.0.1_iFix003:  CDWA-725
Description of Issue:  error "parse WL Flag failed" while installation of non WL installer
Description of Fix:  Add check for "wlFlag" in "CD_SetPermissions" function and modify already present "if" condition for "wlFlag".
Fix Availability Date:  16 April 2019
High Impact:  N
Reported Severity:  3

6.0.0.1_iFix004:  CDWA-723
Description of Issue:  Executing a synch s+parmfile command through the Secure+ API fails with error LCCA082I after 6.0.0.1.
Description of Fix:  Set environment variables (regPath, WLBL_MODE) to determine the registry path.
Fix Availability Date:  16 April 2019
High Impact:  N
Reported Severity:  3

6.0.0.1_iFix005:  CDWA-607
Description of Issue:  Mismatch in parameters in POST and GET in netmap node for windows
Description of Fix:  Removed an extra parameter "tpName" that was coming in "select netmap node" response API.
Fix Availability Date:  30 April 2019
High Impact:  N
Reported Severity:  3

6.0.0.1_iFix006:  CDWA-535
Description of Issue:  Add Support for Operator user in Connect:Direct windows and CD Requester.
Description of Fix:  Local functional authority type template is now updated to include a new Operator user type. An Operator user has Read-only permissions to view configuration files and monitor file transfers but not modify, delete or submit a process. To support this functionality both, Sterling Connect:Direct Requester and Sterling Connect:Direct for Microsoft Windows server must be updated to 4.7.0.6, 4.8.0.1, 6.0.0.2 or later.
Fix Availability Date:  07 May 2019
High Impact:  Y
Reported Severity:  5

6.0.0.1_iFix007:  CDWA-749
Description of Issue:  Bad data occurring in event log entries for Process Ended and Process Flushed.
Description of Fix:  Resolved.
Fix Availability Date:  14 May 2019
High Impact:  Y
Reported Severity:  2

6.0.0.1_iFix008:  MFT-10091 / APAR IT28000
Description of Issue:  SPADMIN GUI displays serial number in decimal
Description of Fix:  Added code to convert Decimal serial number to Hex.
Fix Availability Date:  14 May 2019
High Impact:  N
Reported Severity:  4

All iFixes and fix packs listed above are accumulated in fix pack 2 (6.0.0.2).

iFixes after 6.0.0.2

6.0.0.2_iFix001:  CDWA-500
Description of Issue:  Netmap protocol value should not be changed when trying to update via "Netmap Mode Service" API.
Description of Fix:  Handled the case by throwing an error if user tries to change the protocol value through "Netmap Mode Service" API.
Fix Availability Date:  28 May 2019
High Impact:  N
Reported Severity:  4

6.0.0.2_iFix002:  CDWA-748
Description of Issue:  Support needed for 'No password local API Connections' and 'Run CD Process as the CD Windows Service Account'.
Description of Fix:  The two new Functional Authority features were added in this fix. 'No password local API Connections' feature allows a CD Client to connect using a valid userid and not having to supply a password if they connect to the localhost address. 'Run CD Process as the CD Windows Service Account' allows the submitter to submit a process with a valid userid and without a password. The CD process will run with the CD Windows Service Account credentials. 
Fix Availability Date:  28 May 2019
High Impact:  N
Reported Severity:  4

6.0.0.2_iFix003:  CDUA-1403
Description of Issue:  Invalid parameter "SPOV" coming in spcli output in KQV mode for seaserver.
Description of Fix:  Removed SPOV parameter from spcli output in KQV mode for seaserver. 
Fix Availability Date:  06 June 2019
High Impact:  N
Reported Severity:  3

6.0.0.2_iFix004:  CDWA-730
Description of Issue:  When the Application Interface for Java (AIJ) is sending "validate process" API with invalid (Out Of Range) value of CLASS parameter, CD Windows is validating the same without throwing any error.
Description of Fix:  Handled the case by putting a validation check at the time of parsing the command.
Fix Availability Date:  11 June 2019
High Impact:  N
Reported Severity:  3

6.0.0.2_iFix005:  CDWA-790
Description of Issue:  We currently only traverse the alt.comm.outbound list once; after retries only use comm.info.
Description of Fix:  Changed the SMGR altComm logic to traverse the comm.info and alt.comm.outbound lists for all retries until a connection is made. Once we have a successful connection to the remote node, we stick to that host/port.
Fix Availability Date:  12 June 2019
High Impact:  N
Reported Severity:  3

6.0.0.2_iFix006:  MFT-10337 / APAR IT29581
Description of Issue:  Client connections sporadically failling with LCOA006I and LCOT000I.
Description of Fix:  Added retries around initializing an internal CMGR message queue. Improved error handling and added a new error message LMSG003E.
Fix Availability Date:  28 June 2019
High Impact:  N
Reported Severity:  3

6.0.0.2_iFix007:  MFT-10375 / APAR IT29623
Description of Issue:  Key Certificate Label lost during an upgrade from version 4.7.0 or later, when the Secure+ configuration initially was created by a version prior to 4.7.0. The upgrade log shows unexpected PEM KeyStore open exceptions.
Description of Fix:  Improved the Upgrade Parmfile command to handle and clear settings created by an older version of Secure+.
Workaround:  Set the Key Certificate Label again after the upgrade.
Fix Availability Date:  04 July 2019
High Impact:  Y
Reported Severity:  2

6.0.0.2_iFix008:  CDWA-851
Description of Issue:  Server reports a wrong version number in legacy fields within the configuration report ([Server Property]CDVersion) and session exchange with a client (VERS).
Description of Fix:  Fixed. The use of these fields is deprecated.
Fix Availability Date:  11 July 2019
High Impact:  N
Reported Severity:  4

6.0.0.2_iFix009:  MFT-10447 / APAR IT29699
Description of Issue:  CD Configuration Utility (CDConfig.exe) fails to import User.cfg in 6.0.0.2_iFix002 and later: E005 'ProcessCopy' is not a valid keyword for type User. This error can also occur during an installation when importing a User.cfg file.
Description of Fix:  Fixed.
Fix Availability Date:  11 July 2019
High Impact:  N
Reported Severity:  2

6.0.0.2_iFix010:  CDWA-857
Description of Issue:  No UserAuthority is found for Operator role in WhiteLabeled Node, though the operator user authority was present for NonWhitelabeled Node.
Description of Fix:  Operator User Authority entry was missing in installshield registry in case of WL_NT(white label node), So added the operator user authority entry in installshield registry in case of WL_NT.
Fix Availability Date:  26 July 2019
High Impact:  N
Reported Severity:  3

6.0.0.2_iFix011:  CDWA-901
Description of Issue:  The limit on sessions defined on Snode is not accounted for when processes are rejected.
Description of Fix:  Session limits not honored correctly on SNODE after it rejected sessions due to session limit exceeded.
Fix Availability Date:  28 August 2019
High Impact:  N
Reported Severity:  3

6.0.0.2_iFix012:  MFT-10548 / APAR IT30236
Description of Issue:  Update setup prerequisites for Microsoft Visual C++ and PostgreSQL ODBC driver.
Description of Fix:  Fixed the install condition for Microsoft Visual C++ 2013 Redistributable Packages to resolve an incorrect message claiming that the installation of the package appears to have failed. Removed the Microsoft Visual C++ 2008 and psqlODBC (32-bit) setup prerequisites from the installer, so that they will no longer be installed. 
Fix Availability Date:  10 September 2019
High Impact:  N
Reported Severity:  3

6.0.0.2_iFix013:  MFT-10642 / APAR IT30584
Description of Issue:  The server periodically deletes statistics older than stat.max.age. During the cleanup process the server was not able to log new statistics, which could block other activities, such as CD processes or sessions, and made the server appear to be unresponsive.
Description of Fix: Removed the blocking code.
Fix Availability Date:  10 October 2019
High Impact:  N
Reported Severity:  3

6.0.0.2_iFix014:  MFT-10617 / APAR IT30763
Description of Issue:  Vulnerabilities have been found in PostgreSQL 9.5 used by IBM Connect:Direct for Microsoft Windows. IBM Connect:Direct for Microsoft Windows has addressed the applicable CVEs.
Description of Fix: Updated the CD Windows installer and the version of PostgreSQL.
Fix Availability Date:  30 October 2019
High Impact:  Y
Reported Severity:  2