Ibm® Sterling Connect: Direct

|
Ibm® Sterling Connect: Direct
|
bet | 1/5 | Sana | 22.03.2020 | Hajmi | 67,98 Kb. | | #8507 |
IBM® Sterling Connect:Direct® for Microsoft Windows 4.6.0
This document describes maintenance updates for IBM® Sterling Connect:Direct® for Microsoft Windows 4.6.0. It includes information on all product features, including the Server, Requester, Common Utilities, Secure+ and the SDK. Maintenance updates are always cumulative and provided as fix packs or interim fixes (iFixes).
Fix Packs
Fix packs deliver maintenance and updates to an existing product version of IBM Sterling Connect:Direct for Microsoft Windows. Fix packs are cumulative and include individual fixes (iFixes) as well as updates added since the previous fix pack and in any earlier fix pack. You only need to apply the latest available fix pack. Fix packs can be downloaded from the IBM Fix Central website at http://www.ibm.com/support/fixcentral/.
Review the Instructions for Applying IBM Sterling Connect:Direct for Microsoft Windows Fix Packs (CDWin460FixPackInstructions.pdf) document for details.
Interim Fixes (iFixes)
iFixes or test fixes are provided by IBM support in response to a customer case to address the reported issue. Once a fix has been successfully verified, it will be added to the next fix pack. Fixes are provided as replacement modules built on the latest available fix pack. See fix details for more information.
IMPORTANT: The required fix pack level must be installed prior to applying an fix.
To apply an iFix, follow these steps
1. Verify the information accompanying the fix matches your product, version and fix pack level. Use CD Admin Tool to verify that all requirements are met.
2. Close all Sterling Connect:Direct related user application, such as CD Admin Tool, CD Requester, CD Command Line Interface, etc.
3. Stop the Connect Direct v4.6.00 service.
4. Create a backup of your Sterling Connect:Direct installation folder, typically "C:\Program Files\Sterling Commerce\Connect Direct v4.6.00".
5. An iFix usually come as a zip file. Extract the zip file into a temporary folder. This will create a number of subfolder.
6. Copy only the subfolders that match your installation to your Sterling Connect:Direct installation, typically "C:\Program Files\Sterling Commerce\Connect Direct v4.6.00". Allow existing files to be overwritten.
IMPORTANT: you must exclude the Server\Secure+ folder from copying when Secure+ is not installed, that is you do not have a Server\Secure+ folder in your installation.
7. Restart the Connect Direct v4.6.00 service.
8. Test the fix and provide feedback to IBM support.
It is highly recommended to verify a new fix on a test system before applying it to a production environment.
iFixes after 4.6.00 (4.6.0.0)
4.6.00_iFix001: QC19017
Description of Issue: Unable to enter long names in the SQL Server combo box in DBWiz.
Description of Fix: The combo box has been updated to automatically scroll text to the left when the user types a character at the end of the line. This allows the user to enter longer MS SQL Server names.
Fix Availability Date: 07 April 2011
High Impact: N
Reported Severity: 4
4.6.00_iFix002: QC19008
Description of Issue: Long records broken apart at 23036 characters when sending text mode to remote platforms other than Windows and UNIX.
Description of Fix: Fixed an issue with setting an appropriate I/O buffer size.
Fix Availability Date: 07 April 2011
High Impact: N
Reported Severity: 3
4.6.00_iFix003: QC18989
Description of Issue: The Connect:Direct for Windows service unexpectedly terminates after encountering message LSFG006I. This error incorrectly occurred when a remote node tried to receive a file in text mode without specifying a record length and record.wrap=Y had been set in the local initialization parameters.
Description of Fix: Added coded to preserve the destination file information when sending as SNODE. Also improved the handling of LSFG006I and similar errors when reading the source file.
Fix Availability Date: 14 April 2011
High Impact: Y
Reported Severity: 4
4.6.00_iFix004: QC19169
Description of Issue: Incorrect or missing output in CLI (Direct.exe) with detail=yes.
Description of Fix: Fixed an issue in Select Statistics output of CTRC records, where Src and Dest values for CCode and Msgid were swapped when the local node was receiving the file. Enhanced output of LSST records by adding From, Src File and Dest File fields. Enhanced Select Process output to include Src File and Dest File names during a Copy step.
Fix Availability Date: 13 May 2011
High Impact: N
Reported Severity: 4
4.6.00_iFix005: QC19128
Description of Issue: PNODE dropped the connection after the session was rejected by the remote node, for example when session limits being reached. The remote node reported a network error.
Description of Fix: Updated the PNODE smgr state machine to send a FMH75 to the remote node and close the session gracefully.
Fix Availability Date: 01 June 2011
High Impact: N
Reported Severity: 3
4.6.00_iFix006: QC13829
Description of Issue: Processes using the built-in variable %PRAND occasionally hang in EXEC state after getting LUPC023I, LUPC006I and LSMM012E errors.
Description of Fix: According to the documentation %PRAND is a 6 hex digits pseudo-random number. Occasionally the function to substitute this variable only returned 5 digits, which caused a corrupted TCQ\PRC* file and the errors above. The code has been updated to ensure that the %PRAND value always returns 6 hex digits
Fix Availability Date: 01 June 2011
High Impact: N
Reported Severity: 2
4.6.00_iFix007: QC19330
Description of Issue: An existing process contained a SUBMIT-within-process step specifying additional variables for the subsequent process. When the process file was opened in CD Requester, the variables showed up for the wrong statement or were lost.
Description of Fix: The CD Requester parser incorrectly detected additional statements, for example when the process also contained file names like FILE=my_submit with no surrounding quotes. This caused variables to be added to the wrong statement. The function to detect statement keywords has been updated to resolve the issue.
Fix Availability Date: 30 June 2011
High Impact: N
Reported Severity: 3
4.6.00_iFix008: QC19325
Description of Issue: When a process was redirected by a remote Connect:Direct for z/OS PLEX manager, it did not continue immediately but was scheduled for a later retry using the short retry timer interval.
Description of Fix: The product has been updated to let the redirected process restart to its new destination as a soon as possible.
Fix Availability Date: 11 July 2011
High Impact: N
Reported Severity: 4
4.6.00_iFix009: QC19490
Description of Issue: RUN TASK/JOB using cmd() sysopts fails when the user specified "/C" within his command.
Description of Fix: The user's /C created a conflict with the way that the command is executed by Connect:Direct, which is "CMD.exe /C ". The conflict has been resolved.
Fix Availability Date: 28 July 2011
High Impact: N
Reported Severity: 3
4.6.00_iFix010: QC19489
Description of Issue: A text file is send to a remote node with strip.oneable(yes). If the source file ends with 0x0D-0A-1A, an additional empty record gets appended to the destination file.
Description of Fix: When reading the source file another record was detected following the last CR LF (0x0D-0A). This record only contained 0x1A, which later on got removed by strip.oneable processing. The record become empty, but still was sent to the remote node. Added look-ahead logic to ignore the last record if it only contains 0x1A.
Fix Availability Date: 04 August 2011
High Impact: N
Reported Severity: 4
4.6.00_iFix011: QC19805
Description of Issue: Configuration report updates.
Description of Fix: The configuration and ActiveDirectory reports have been slightly updated. Moreover protocol information will display correctly now.
Fix Availability Date: 08 September 2011
High Impact: N
Reported Severity: 4
4.6.00_iFix012: QC19718
Description of Issue: Process was removed from the TCQ after failing with Secure+ protocol mismatch (CSPA200E).
Description of Fix: Changed the behavior to put the process into 'Hold in Error' (HOLD HE) instead of removing it from the TCQ.
Fix Availability Date: 22 September 2011
High Impact: N
Reported Severity: 3
4.6.00_iFix013: QC19839
Description of Issue: A SUBMIT step failed with LCCA014I, but was logged with CC=0 and no MsgID in the Submit Ended record (SBED).
Description of Fix: Set step fields for MsgID and Condition Code properly on LCCA014I failures.
Fix Availability Date: 22 September 2011
High Impact: N
Reported Severity: 3
4.6.00_iFix014: QC19524
Description of Issue: FIPS mode integrity check fails when running Secure+ spcli/spadmin under IBM JVM: FIPS_check_dso fingerprint does not match.
Description of Fix: This has been resolved. The OpenSSL FIPS libraries have not been changed.
Fix Availability Date: 10 October 2011
High Impact: N
Reported Severity: 3
4.6.00_iFix015: QC20080
Description of Issue: Variable "&ECOD" not substituted in LSMG402I message within RTED record.
Description of Fix: While the related PSED record was complete, the RTED record was missing a value for "&ECOD" when logging LSMG402I. This has been fixed.
Fix Availability Date: 11 October 2011
High Impact: N
Reported Severity: 4
4.6.00_iFix016: QC19829
Description of Issue: Connect:Direct for Windows is setup with Microsoft SQL Server using Windows authentication. A user other than the installer attempted a wildcard copy that failed. Unfortunately the service failed to log statistics, went through database retries and finally initiated a shutdown. The Application event log showed error messages similar to:
[Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot open database "CDWINNT" requested by the login. The login failed. - Native Error 4060
[Microsoft][SQL Server Native Client 10.0][SQL Server]The INSERT permission was denied on the object 'CDNODEV4501STAT', database 'CDWINNT', schema 'dbo'. - Native Error 229
Description of Fix: Ensured that the application first reverts back to service account before setting an error, such as LCPS002I or LSFN003I.
Fix Availability Date: 12 October 2011
High Impact: Y
Reported Severity: 3
4.6.00_iFix017: QC20159
Description of Issue: Server crashed on receipt of a malicious X.509 certificate with long subject.
Description of Fix: Added a length check when formatting the audit info for statistics.
Fix Availability Date: 20 October 2011
High Impact: Y
Reported Severity: 3
All iFixes listed above are accumulated in fix pack 1 (4.6.0.1).
iFixes after Fix Pack 1 (4.6.0.1)
4.6.0.1_iFix001: QC20266
Description of Issue: A process had been submitted earlier with a remote node name, which was not defined in the netmap. After updating the netmap later on, the server rarely crashed.
Description of Fix: The issue only occurred intermittent. Under rare conditions an error handle become invalid while the server was refreshing its internal list of adjacent nodes after a netmap update. Error handling has been updated to avoid a potential access violation.
Fix Availability Date: 02 December 2011
High Impact: Y
Reported Severity: 2
4.6.0.1_iFix002: RTC103839
Description of Issue: Process Monitor (Select Process) on the SNODE is not updated when executing a non-COPY step. It still shows the process executing the last copy step, if any, even if the process has moved on to another step, like a RUN TASK.
Description of Fix: Added code to update the current step information in TCQ's shadow copy on the SNODE for steps other than COPY.
Fix Availability Date: 05 January 2012
High Impact: N
Reported Severity: 3
4.6.0.1_iFix003: RTC140740
Description of Issue: The local password is not copied across when using Sterling Control Center to duplicate proxy definitions.
Description of Fix: This is a side effect of the security fix for SR1363712 in Sterling Connect:Direct for Microsoft Windows 4.1.00 and later. With the fix in place and an API client requesting a proxy definition, the server no longer returns the real local password to any client, but sends a dummy password instead.
As a result, clients such as Sterling Control Center copy the dummy password across when duplicating the proxy definition.
This new iFix here adds a new initialization parameter "disable.proxy.password.security" allowing to disable the security fix for SR1363712. When set to 'Y', the server returns the real local password again. To ensure backwards compatibility with SR1363712, the default value is 'N' and the server returns a dummy password.
CAUTION: this initialization parameter is security related. It is highly recommend to only set disable.proxy.password.security=Y during the time while duplicating the proxy and return to disable.proxy.password.security=N afterwards.
Fix Availability Date: 25 January 2012
High Impact: N
Reported Severity: 4
4.6.0.1_iFix004: RTC309744
Description of Issue: The server does not report its version correctly to a client.
|
| |