A fix is available
APAR status
Closed as program error.
Error description
Second sort key in LinkCollector is not used to sort records when "Collection algorithm" is "Sort/Merge" and multiple keys are set as "Sort key".
Local fix
Problem summary
**************************************************************** USERS AFFECTED: The problem only occurs when a link collector stage is used to merge multiple sources with the sort/merge attribute set. In addition multiple columns must be used in the sort specification and the columns have to be of type string. **************************************************************** PROBLEM DESCRIPTION: If the conditions mentioned in the users affected fields are met then the rows will not be emitted in the correct sorted order. **************************************************************** RECOMMENDATION: The only solution to the problem is to apply the patch. ****************************************************************
Problem conclusion
The problem was resolved with a minor code restructure which stopped unintialised variables from being used in the string comparison code for a column.
Temporary fix
Comments
APAR Information
APAR number
JR59455
Reported component name
WIS DATASTAGE
Reported component ID
5724Q36DS
Reported release
B50
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-05-06
Closed date
2018-05-23
Last modified date
2018-05-23
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WIS DATASTAGE
Fixed component ID
5724Q36DS
Applicable component levels
RB50 PSY
UP
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"InfoSphere DataStage"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.5"}]
Document Information
Modified date:
02 September 2021