Fix Availability Date - Ibm® Sterling Connect: Direct

|
Ibm® Sterling Connect: Direct
|
bet | 3/6 | Sana | 25.12.2019 | Hajmi | 79,91 Kb. | | #4856 |
Fix Availability Date: 09 September 2015
High Impact: N
Reported Severity: 2
4.7.0.3_iFix014: RTC477370 / APAR IT11470
Description of Issue: Add the ability to create a configuration report from the CLI.
Description of Fix: Updated the CLI (Direct.exe) and its internal help command to support the new parameter 'cdconfig' on the traceon command. The configuration report will be written to a file named cdconfig.txt created in the same folder as the specified trace file. For example, enter the following command line in the CLI to create a configuration report in C:\Temp\cdconfig.txt:
traceon file=C:\Temp\dummy.cdt config;
Fix Availability Date: 28 September 2015
High Impact: N
Reported Severity: 5
4.7.0.3_iFix015: RTC480632 / APAR IT11949 / CVE-2015-1788
Description of Issue: An OpenSSL denial of service vulnerability disclosed by the OpenSSL Project affects GSKit. IBM Sterling Connect:Direct for Microsoft Windows uses GSKit and addressed the applicable CVE.
Description of Fix: Updated the version of GSKit.
Fix Availability Date: 23 October 2015
High Impact: N
Reported Severity: 2
4.7.0.3_iFix016: RTC479415 / APAR IT11985
Description of Issue: File Allocation Retry has been configured, for example to let the process retry when a remote GDG dataset is in use (retry.msgids=SDEGDGRI). Occasionally a remote node returned the retry-able msgid with a Completion Code of 16 (fatal error) instead of CC=8. In these cases the process got stuck in TIMR RE with Hold=Y and did not retry.
Description of Fix: Ensured that the hold status is set to N when a process is scheduled for a retry. This allows File Allocation Retry even for fatal error conditions.
Fix Availability Date: 03 November 2015
High Impact: N
Reported Severity: 2
4.7.0.3_iFix017: RTC482167 / APAR IT12170
Description of Issue: A user manually modified a process text file outside of CD Requester and set $SNODE$="" in the CD Requester comments. When he opened the process in CD Requester afterwards, the SNODE value in the PROCESS statement got cleared out, too.
Description of Fix: When available, CD Requester uses its comment to determine which PNODE and SNODE this process was designed for. The logic has been enhanced to not overwrite the PNODE or SNODE when $PNODE$="" or $SNODE$="" is found in CD Requester comments.
Fix Availability Date: 09 November 2015
High Impact: N
Reported Severity: 5
4.7.0.3_iFix018: RTC482534 / APAR IT12247
Description of Issue: Improvements to the Secure+ API and CD Secure+ CLI (SPCli.cmd).
Description of Fix: Enhanced the "Delete KeyStoreEntry" and "Import KeyCert" commands. See the Help command in SPCli.cmd for new parameters.
Fix Availability Date: 14 December 2015
High Impact: N
Reported Severity: 5
4.7.0.3_iFix019: RTC487432 / APAR IT12990
Description of Issue: When parsing or validating a process, the parser silently truncates file names in COPY and SUBMIT statements when they are too long. It does not show any errors, allowing the process to be submitted with wrong file names.
Description of Fix: Process validation will fail and the parser returns an error as expected.
Fix Availability Date: 13 January 2016
High Impact: N
Reported Severity: 2
4.7.0.3_iFix020: RTC488558 / APAR IT13127 / CVE-2016-0201
Description of Issue: A vulnerability has been addressed in the GSKit component of IBM Sterling Connect:Direct for Microsoft Windows.
Description of Fix: Updated the version of GSKit.
Fix Availability Date: 14 January 2016
High Impact: Y
Reported Severity: 2
4.7.0.3_iFix021: RTC489446 / APAR IT13462
Description of Issue: When copying text files to or from an EBCDIC remote node, Connect:Direct Windows translates ASCII data to EBCDIC and vice versa as needed. In some cases, an alternative to the default ASCII to EBCDIC translation provided by Connect:Direct Windows is desired.
Description of Fix: While the product includes options for users to create their own custom xlate tables or to use codepage translation, for convenience, new xlate tables are provided that convert ISO-8859-1 ASCII text to IBM-037 EBCDIC and back. These xlate tables, ISOtoIBM.cdx and IBMtoISO.cdx, are located in the Server\xlate subfolder. They may be specified in copy step sysopts, or be made the default translation by specifying them in the Global Copy Parameters section of the initialization parameters.
Fix Availability Date: 28 January 2016
High Impact: N
Reported Severity: 5
4.7.0.3_iFix022: RTC489304 / APAR IT13617
Description of Issue: Unable to use Group Authorities with the "Domain Admins" or "Administrators" Windows groups.
Description of Fix: Previously Connect:Direct was ignoring any Windows group that did not have the SE_GROUP_ENABLED attribute set. This condition has been removed, so that these groups are no longer ignored.
Fix Availability Date: 04 February 2016
High Impact: N
Reported Severity: 2
4.7.0.3_iFix023: RTC485463 / APAR IT13624
Description of Issue: On a SUBMIT within process statement, occurrences of the word "local" or "remote" may incorrectly get replaced with "PNODE" and "SNODE". For example, passing along a variable &MYFILE=local.txt results in &MYFILE=PNODE.txt instead.
Description of Fix: Removed deprecated code.
Fix Availability Date: 04 February 2016
High Impact: N
Reported Severity: 3
4.7.0.3_iFix024: RTC485087 / APAR IT13734
Description of Issue: The Select Statistics command cannot filter for node or process names containing lower-case characters. Such names may come from a remote Sterling Connect:Direct UNIX node.
This issue only applies when the database is solidDB and the command is issued by a Windows SDK client, including CD Requester and the CLI. It does not apply to clients using the Application Interface for Java (AIJ).
Description of Fix: Updated the SDK - and thus its clients - to preserve the case for node and process name specified on Select Statistics commands. Note that the parameters pname, pnode, snode and rmtnode are case-sensitive when the database is solidDB.
Fix Availability Date: 11 February 2016
High Impact: N
Reported Severity: 3
4.7.0.3_iFix025: RTC490415 / APAR IT13950
Description of Issue: When the destination filename gets too long on a wildcard COPY step, the file will be sent with a truncated destination filename.
Description of Fix: Enhanced error handling for wildcard COPY steps and let the file fail with error LSMG265E instead: File name too long or invalid.
Also fixed an issue where the feedback code (FDBK) was not reported properly in the SCPA085I wildcard summary message.
Fix Availability Date: 24 February 2016
High Impact: N
Reported Severity: 2
4.7.0.3_iFix026: RTC493142 / APAR IT14002
Description of Issue: Processes may be coded with a snode that will invoke a Secure+ alias node when a session is attempted. In some cases, these session attempts can fail, reporting a CSPA201E message with reason text indicating "error setting ciphers".
Description of Fix: Fixed code so that processes coded with a snode that will invoke a Secure+ alias node when a session is attempted will work properly.
Fix Availability Date: 26 February 2016
High Impact: N
Reported Severity: 2
4.7.0.3_iFix027: RTC488932 / APAR IT14104
Description of Issue: Trying to create an alias node entry in Secure+ by using the CD Secure+ CLI (SPCli.cmd) or the Secure API fails with an error:
SPCL108E rc=8 All mandatory key word value pairs must be entered.
Description of Fix: Fixed. Note the command will succeed, but with valid warnings:
SPCG774W rc=4 Node: MYALIAS - warning: This node is an alias for MYNODE, validation not performed.
SPCG420I rc=4 Create remote node command successful.
Fix Availability Date: 03 March 2016
High Impact: N
Reported Severity: 3
4.7.0.3_iFix028: RTC494448 / APAR IT14242
Description of Issue: Trying to import an Initialization Parameters file (Initparms.cfg) fails with error LIPF008E for one of the following parameters: record.wrap, contact.name, contact.phone and descrip. Looking at the file, these parameters do not show a value assigned.
The file had been exported using CD Configuration Tool (CDConfig.exe) from a fresh installation, i.e. before the initialization parameters had not been applied at least once, like in CD Requester.
Description of Fix: Updated the installation to properly initialize the record.wrap registry key. The other parameters will default to now in alignment with other parameters.
Also updated server and CDConfig to ignore empty values rather than fail the operation.
Workaround: Edit the Initparm.cfg file, add missing values and try the import again - or - Apply the initialization parameters once, like from CD Requester, before doing the export.
Fix Availability Date: 09 March 2016
High Impact: N
Reported Severity: 3
4.7.0.4: RTC494171 / APAR IT14315 / CVE-2016-2542
Description of Issue: An InstallShield vulnerability was disclosed by Flexera. InstallShield is used by IBM Sterling Connect:Direct for Microsoft Windows.
Description of Fix: Addressed the applicable CVE.
Fix Availability Date: 09 March 2016
High Impact: Y
Reported Severity: 2
4.7.0.4: RTC456889 / APAR IT14578
Description of Issue: Sterling Connect:Direct for z/OS added support for zEDC, which adds hardware acceleration support to zLib compression, but requires a compression window size of 15. The default is currently 13.
Description of Fix: Changed the default Compression Windows size to 15.
Fix Availability Date: 16 March 2016
High Impact: N
Reported Severity: 3
4.7.0.4: n/a
Description of Issue: Fast and Secure Protocol (FASP).
Description of Fix: Added support for FASP. See the Release Notes for further information regarding support for FASP.
FASP requires a license key for use. Download the license key from Passport Advantage when you download the fix pack.
Fix Availability Date: 16 March 2016
High Impact: N
Reported Severity: 5
4.7.0.4: RTC494775, RTC494777 / APAR IT16911 / CVE-2016-5991, CVE-2016-5992
Description of Issue: IBM Sterling Connect:Direct for Microsoft Windows contains vulnerabilities that could allow a local user to increase their privileges or cause a denial of service when special conditions exist.
Description of Fix: Addressed the applicable CVEs.
Fix Availability Date: 17 March 2016
High Impact: Y
Reported Severity: 2
All iFixes and fix packs listed above are accumulated in fix pack 4 (4.7.0.4).
iFixes after 4.7.0.4
4.7.0.4_iFix001: RTC500056 / APAR IT14990
Description of Issue: 2GB FASP pull from Sterling Connect:Direct Windows to Sterling
Connect:Direct Windows via Sterling Secure Proxy (SSP) fails. The process hangs in the TCQ in EX status.
Description of Fix: Updated FaspStream components.
Fix Availability Date: 27 April 2016
High Impact: N
Reported Severity: 2
4.7.0.4_iFix002: RTC480005 / APAR IT13962
Description of Issue: Pipe characters are doubled (||) in a RUN TASK/JOB step on a Sterling Connect:Direct UNIX SNODE. This affects the way that the UNIX shell interprets the specified command line, because "|" and "||" have a different meaning.
Description of Fix: Fixed. Also resolved a memory leak when FMH71 format conversion has failed (LSMG613I).
Fix Availability Date: 02 May 2016
High Impact: N
Reported Severity: 2
4.7.0.4_iFix003: RTC500785 / APAR IT15059
Description of Issue: SHA-2 private keys.
Description of Fix: Added support for SHA-2 private keys to Secure+.
Fix Availability Date: 03 May 2016
High Impact: N
Reported Severity: 5
4.7.0.4_iFix004: RTC502167 / APAR IT15278
Description of Issue: Enhance the LSMG244I message to provide more details on failed logon attempts.
Description of Fix: The OS system error code is now logged as the feedback code (FDBK). Here are some typical error codes and their meaning:
1326: Logon failure - unknown user name or bad password.
1331: Logon failure - account currently disabled.
1385: Logon failure - the user has not been granted the requested logon type at this computer.
Fix Availability Date: 13 May 2016
High Impact: N
|
| |