|
Ibm® Sterling Connect: Direct
|
| bet | 2/5 | | Sana | 22.03.2020 | | Hajmi | 67,98 Kb. | | #8507 |
Description of Fix: Starting with 4.6.0.1, IBM Sterling Connect:Direct for Microsoft Windows is following the standard IBM version number format. New version fields have been added to session info exchange between the server and any client.
Fix Availability Date: 25 January 2012
High Impact: N
Reported Severity: 4
4.6.0.1_iFix005: RTC310749
Description of Issue: Updating the server.path initialization parameter causes the server to stop working properly and failing to start up again.
Description of Fix: Made the server.path initialization parameter read-only. Any attempt to update this initialization parameters will be ignored, like it was already done for the (node) name parameter.
To reallocate the server path or change the node name, reinstall the product.
Fix Availability Date: 25 January 2012
High Impact: N
Reported Severity: 2
4.6.0.1_iFix006: RTC209605
Description of Issue: z/OS LRECL size on destination file not honored sending a Windows file with datatype=binary and codepage conversion specified.
Description of Fix: Fixed code so that z/OS LRECL size on destination file is honored sending a Windows file with datatype=binary and codepage conversion specified.
Fix Availability Date: 02 February 2012
High Impact: N
Reported Severity: 3
4.6.0.1_iFix007: RTC301336
Description of Issue: When PNODEID is specified in the process and the userid is not found under Functional Authorities, the pnode incorrectly considers proxies before trying to authenticate.
Description of Fix: Removed the proxy logic from the pnode, so that it directly attempts to authenticate the specified PNODEID.
Fix Availability Date: 02 February 2012
High Impact: N
Reported Severity: 3
4.6.0.1_iFix008: RTC314317 / APAR IC81503
Description of Issue: The Bytes Written count is calculated incorrectly when receiving in text mode. It is off by one for each record written.
Description of Fix: Increment the counter by two (CR+LF) for each record.
Fix Availability Date: 16 February 2012
High Impact: N
Reported Severity: 3
4.6.0.1_iFix009: RTC315850
Description of Issue: SRC and DST addresses are reversed in the LSMI003I 'SNODE session started' message.
Description of Fix: Swapped address/port values when being SNODE. Also slightly reduced the memory usage of session managers.
Fix Availability Date: 01 March 2012
High Impact: N
Reported Severity: 3
4.6.0.1_iFix010: RTC318047 / APAR IC81990
Description of Issue: Some statistics and TCQ get lost when solidDB shuts down abnormally.
Description of Fix: The issue does not occur when the solidDB service is stopped gracefully. To avoid the issue, transaction logging is enabled by setting LogEnabled=yes in the solid.ini file.
Fix Availability Date: 12 March 2012
High Impact: Y
Reported Severity: 2
All iFixes and fix packs listed above are accumulated in fix pack 2 (4.6.0.2).
iFixes after Fix Pack 2 (4.6.0.2)
4.6.0.2_iFix001: RTC319808 / APAR IC82224
Description of Issue: CD Message Lookup returns an error that it cannot find a message when the msgid entered by the user has trailing spaces.
Description of Fix: Improved usability of CdMsg by removing leading and trailing whitespaces as well as single or double quotes from the user's input before doing the message lookup.
Fix Availability Date: 22 March 2012
High Impact: N
Reported Severity: 4
4.6.0.2_iFix002: RTC318476 / APAR IC82613
Description of Issue: Connect:Direct Windows reports SCPA000I when sending to Connect:Direct z/OS and being sent back a SVSJ013I error with completion code -2135724032 (80B37000).
Description of Fix: Updated the code to treat negative completion codes returned from a remote side as an error.
Fix Availability Date: 30 March 2012
High Impact: N
Reported Severity: 2
4.6.0.2_iFix003: RTC318639 / APAR IC82617
Description of Issue: When logging LSMR003I, LSMR014I or LSMR015I errors for a long RUN TASK/JOB command, the error message may get truncated inappropriately. The Connect:Direct Java Application Interface (CDJAI) fails with a KQVString.parse() exception when retrieving this message in a Select Statistics command.
Description of Fix: Reworked the code that does the statistics logging for these error messages. A long command value will be truncated and preceded with "..." for the &EXE substitution data as needed, ensuring balanced double-quotes. The full sysopts will now be logged in the correct field (SOPT instead of SFIL). In addition, the OS error of the failure will now be logged in the feedback code.
As a side fix, an issue for was resolved, where the user's profile and environment was not unloaded after LSMG249I occurred.
Fix Availability Date: 19 April 2012
High Impact: N
Reported Severity: 3
4.6.0.2_iFix004: RTC323115 / APAR IC82703
Description of Issue: lcu.bat fails to run when installed from Sterling Connect:Direct for Windows SDK: "The system cannot find the path specified."
Description of Fix: Updated the SDK installer to trigger lcu.bat customization.
Workaround: Edit the lcu.bat file manually and set cdInstallDir to the fully qualified path of the installation directory, typically: set cdInstallDir=C:\Program Files\Sterling Commerce\Connect Direct v4.6.00
Fix Availability Date: 24 April 2012
High Impact: N
Reported Severity: 3
4.6.0.2_iFix005: RTC319554 / APAR IC83000
Description of Issue: Server crashes when building a path from restricted directory, relative path and filename exceeds the maximum length.
Description of Fix: Added code to detect and prevent this and raise an LSMG265E "File name too long or invalid" error message.
Fix Availability Date: 30 April 2012
High Impact: Y
Reported Severity: 3
4.6.0.2_iFix006: RTC326049 / APAR IC83126
Description of Issue: When SSL/TLS is enabled, updating the .SEAServer entry in Secure+ would fail even when External Authentication is disabled: "Error: The .SEAServer host name must be specified."
Description of Fix: Updated the validation of the .SEAServer entry. The error will appear only when External Authentication is enabled in .Local. Otherwise, a similar warning will appear when Override is enabled.
Fix Availability Date: 24 May 2012
High Impact: N
Reported Severity: 3
4.6.0.2_iFix007: RTC328994 / APAR IC84026
Description of Issue: SPCli and Secure+ API resolve symbolic links in certificate filenames.
Description of Fix: If the user specifies an absolute filename, SPCli and Secure+ API do not try to resolve any symbolic link, unless the path contains '..'.
Fix Availability Date: 06 June 2012
High Impact: N
Reported Severity: 4
4.6.0.2_iFix008: RTC332212 / APAR IC84282
Description of Issue: Trying to re-install Sterling Connect:Direct for Windows 4.6.0.2 with solidDB fails with an error: "Cannot create database because old log file sol00001.log exists in the log files directory"
Description of Fix: The installation always creates a new solidDB database. Updated the product installer to delete existing transaction logs (solNNNNN.log) in addition to deleting the existing database file (solid.db) when re-installing the product. Note that this fix is only available in a new product installer.
Workaround: Delete the "sol?????.log" files from the solidDB6.5\cdwinnt directory before re-installing.
Fix Availability Date: 14 June 2012
High Impact: N
Reported Severity: 3
4.6.0.2_iFix009: RTC347143 / APAR IC86529
Description of Issue: Installation adds obsolete ADMIN setting in functional authorities for *admin, *GENUSR and the installation userid. This setting shows up in Sterling Control Center.
Description of Fix: The ADMIN setting is not supported by Connect:Direct for Windows, but is ignored silently. While this has not been any issues, the default setting will be removed from future installers.
Fix Availability Date: 13 September 2012
High Impact: N
Reported Severity: 4
4.6.0.2_iFix010: RTC348095 / APAR IC86721
Description of Issue: When creating a new Secure+ node (or updating one) in Sterling Control Center, the Encrypt Data value in the Advance panel does not remain set.
Description of Fix: Added support for the Secure+ Process Override enhancement (QC19050) to the Secure+ API.
Fix Availability Date: 27 September 2012
High Impact: N
Reported Severity: 3
4.6.0.2_iFix011: RTC351347 / APAR IC86986
Description of Issue: Running CD Configuration Utility in GUI mode, it fails to extract configuration when the user has no write permission to the registry: "The node specified by CDNODE - v4.6.00 was not found in the registry". The same operation succeeds when running in quiet mode.
Description of Fix: Removed the need for write access in GUI mode and also enhanced the displayed error message to include the reason for the failure, like Access is denied.
Fix Availability Date: 04 October 2012
High Impact: N
Reported Severity: 4
4.6.0.2_iFix012: RTC350522 / APAR IC86809
Description of Issue: Connect:Direct z/OS is trying to send a file to Connect:Direct Windows in binary mode with a source BLKSIZE greater than the default (23040). For some reason, the initial session had failed in a very rare way that could cause the restart to fail with LCPR001I: Rec len in Comm buffer bigger than IO buffer size.
Description of Fix: Modified the calculation of the IO buffer size at the restart.
Fix Availability Date: 18 October 2012
High Impact: N
Reported Severity: 2
4.6.0.2_iFix013: RTC352750
Description of Issue: How to investigate RUN TASK steps that are still executing.
Description of Fix: Enhanced SMGR trace diagnostics for RUN TASK/JOB steps.
Fix Availability Date: 25 October 2012
High Impact: N
Reported Severity: 3
4.6.0.2_iFix014: RTC347170 / APAR IC88148
Description of Issue: A PNODE Delete/Flush Process command does not delete an executing PNODE process until the process' SNODE Run Task step completes.
Description of Fix: Modified Connect:Direct’s usage of the Microsoft Winsock facilities, enabling the SMGR to immediately receive instruction messages from the PMGR.
For users of the Connect:Direct Command Line Interface (CLI Direct.exe), please note:
The CLI’s DELETE PROCESS command is required to remove an executing (EXEC) process from the queue. Additionally, one of the HOLD or FORCE arguments to the DELETE PROCESS command must be set to YES. For example,
DELETE PROCESS FORCE=YES; /* Delete executing process from the queue */
DELETE PROCESS HOLD=YES; /* Delete executing process and place it in the HOLD queue */
The default for both FORCE and HOLD is NO. Therefore, at least one must be specified and set to YES in order for the process to be deleted when using the CLI. The DELETE PROCESS command is described in the Connect:Direct for Microsoft Windows System Guide.
Fix Availability Date: 19 November 2012
High Impact: N
Reported Severity: 5
4.6.0.2_iFix015: RTC366991 / APAR IC90331
Description of Issue: Silent upgrade fails as SolidDB is not the default database.
Description of Fix: When performing a silent upgrade from a previous version, SolidDB is now correctly set as the new default database.
Workaround: Set CD_DATABASE_TYPE=SOLIDDB in the silent installation property file (cd_srvr.ini).
Fix Availability Date: 21 February 2013
High Impact: N
Reported Severity: 3
4.6.0.2_iFix016: RTC368138
Description of Issue: Adding support for importing initialization parameters during the installation.
Description of Fix: A new installer property CD_INITPARMS_FILE has been added to Advanced\cd_srvr.ini. It can be used to specify an initialization parameters file for import during an installation. This is similar to the existing properties CD_USERAUTH_FILE and CD_NETMAP_FILE for importing user and netmap configuration files.
The CD Configuration Utility (CdConfig.exe) has been enhanced to support exporting and importing initialization parameters files. To perform the operation in silent mode, use the following commands:
CdConfig.exe /Q /PInitparms.cfg /* Export */
CdConfig.exe /Q /I /FInitparms.cfg /LCdConfig.log /* Import */
Make sure the service is stopped before running an import. Also note that the node "name" and "server.path" initialization parameters cannot be changed and will be ignored during the import.
Fix Availability Date: 14 March 2013
High Impact: N
Reported Severity: 5
4.6.0.2_iFix017: RTC365254 / APAR IC90865
|
| |
