I realize that this post is somewhat dated. I faced a similar issue in the recent past.
The job schematic (pertaining to the issue) is as below
Code: Select all
Modify Stage --------
Join Stage ------- Output
Aggregator Stage --------
The job used "Same" partitioning on both input links for the JOIN stage. In the aggregator stage that feeds to the JOIN stage, the colums were sorted as "case-insensitive" whereas the columns emanating from the Modify stage had the sorting based on case-sensitive option (default).
The job compiled fine at design time, but at run-time, the dreaded error message "The input interface does not contain component "sortRec"" was emitted.
IBM Engineering support was quite helpful in resolving this issue and came back with the following comment:
Although there's not a DataStage defect here, we're aware that the error message that's emitted, 'Fatal Error: The input interface does not contain component "sortRec"', is not very useful in identifying the cause of the failure. While it's not feasible to detect every erroneous job specification, instances such as the one in <stage_name> could be caught at design time; this is something we hope to address in a future release.
I think, when faced with this error, essentially it boils down to being meticulous about looking into each of the stages and hunting down the root cause of the issue. In my case, it was the "case", but could be different for others.