IBM® Sterling Connect:Direct® for Microsoft Windows 4.8.0
Fix List Document

This document describes maintenance updates for IBM® Sterling Connect:Direct® for Microsoft Windows 4.8.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 Executable
•	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 applying a fix pack to IBM Sterling Connect:Direct for Microsoft Windows installed in a failover cluster environment, execute the iFix / fix pack installer on each machine in the cluster where the product is installed or can run. See the Cluster Service Guide for further instructions.
•	When installing or updating IBM Sterling Connect:Direct SDK for Windows and using the Active X controls, verify that the CDStats.ocx and CDSubmit.ocx components are registered correctly. If they do not function properly, use regsvr32.exe to first unregister and then register these components again.

About Fix Packs and iFixes

Fix packs and interim fixes (iFixes) deliver maintenance and updates to an existing product version of IBM Sterling 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.

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:

•	Sterling Connect:Direct iFix 4.8.0.0_iFix001
4.8.0.0-SterlingConnectDirectforMicrosoftWindows-x86-fp0000-if001.exe
•	Stand-alone Sterling Connect:Direct Requester fix pack 4.8.0.0
4.8.0.0-SterlingConnectDirectRequesterStandAlone-x86-fp0000.exe
•	Sterling Connect:Direct SDK/SDK.Net fix pack 4.8.0.0
4.8.0.0-SterlingConnectDirectSDK-x86-fp0000.exe

Before running the Setup Executable

•	Review the fix list document (CDWin480FixList.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 executable to apply a fix pack or iFix to an existing installation of IBM Sterling Connect:Direct for Microsoft Windows 4.8.0. Enable the patch mode 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 executable in Windows Explorer or run it without any arguments from the command line. This is equivalent to the following command:
<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
The command will wait for completion (/w) and return 0 if the operation was successful. Review the log file in case of failure. Include this log file when reporting an installation problem to IBM customer support.

Performing a new Installation or an Upgrade of an existing Installation

Use the installer executable to perform a fresh installation of IBM Sterling Connect:Direct for Microsoft Windows 4.8.0 or to upgrade from an existing older release. Enable the installation/upgrade mode by overwriting the command line.
Interactive Mode
To install or upgrade interactively, enter the following command line:
<InstallerExe> /v"/l*v CDWinInst.log"
Silent Mode
To install or upgrade in silent mode, enter the following command line:
<InstallerExe> /v" CD_SRVR_INI_FILE=C:\cd_srvr.ini /l*v CDWinInst.log /qn" /s /w
The command will wait for completion (/w) and return 0 if the operation was successful. Review the log file in case of failure. Include this log file when reporting an installation problem to IBM customer support.
For further options on customizing a silent installation, see the online documentation.

Description of iFixes and Updates

iFixes after 4.8.0.0

4.8.0.0_iFix001:  RTC560221 / APAR IT24146
Description of Issue:  The CD Configuration Utility (CDConfig) fails to validate tcp.api.port or tcp.host.port initialization parameters when they specify multiple listener addresses. The error is:
E018 Line contained extra unrecognized data ('::1;1363').
Description of Fix:  Resolved.
Fix Availability Date:  23 February 2018
High Impact:  N
Reported Severity:  4

4.8.0.0_iFix002:  RTC558935 / APAR IT24095
Description of Issue:  Secure+ incorrectly bypassed on the SNODE when it had no Secure+ remote node entry for the PNODE.
Description of Fix:  Resolved an issue with merging .Local and remote node settings. Also updated CSPA314W to show the node name in the message text.
Fix Availability Date:  14 May 2018
High Impact:  Y
Reported Severity:  3

4.8.0.0_iFix003:  RTC565091
Description of Issue:  Setup allows installation on unsupported Windows OS.
Description of Fix:  Updated the minimum OS requirements for Setup to match the Release Notes: Microsoft Windows 8, Microsoft Windows Server 2012 or higher (VersionNT>=602).
Fix Availability Date:  19 March 2018
High Impact:  Y
Reported Severity:  2

4.8.0.0_iFix004:  RTC557781 / APAR IT24600
Description of Issue:  Timer Retry logic can lose track of a process when a user manually releases the process from the Timer Retry queue and the timer fires while the process is still running. The process will not get a new timer but will remain in the Timer Retry queue appearing ‘stuck’.
Description of Fix:  Resolved.
Fix Availability Date:  29 March 2018
High Impact:  N
Reported Severity:  3

4.8.0.0_iFix005:  RTC565355 / APAR IT24943
Description of Issue:  Processes to a remote node can remain on the WAIT queue after a user has increased Max PNode Sessions in the netmap entry. The processes work fine again after restarting the local node.
Description of Fix:  Resolved an issue with checking if a process can run. Improved error reporting to log LSMG418I with CC=16 when an exception was caught in the PNODE session manager.
Fix Availability Date:  29 May 2018
High Impact:  N
Reported Severity:  3

4.8.0.0_iFix006:  RTC567875 / APAR IT25318 / CVE-2018-2602
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:  11 June 2018
High Impact:  Y
Reported Severity:  2