@Elle wrote:
Dear Kurt, I already said in my previous posts I cannot reproduce the issue with mock data (fake data generated by an algorithm). Not because I don't want to. It won't replicate. I also said I cannot provide the original data due to security issues. I simply don't have enabled the capability of Copy/Export/Send to ... I would be in violation of the company's policy.
Indeed, it's not rocket science to read through the replies before demanding things.
Then the problem is clearly with your data. If it can't be reproduced with a piece of code, it is simply not there where you're looking.
As others suggested, pull the dataset into SAS (WORK) so you get a SAS-only process, to make sure you don't suffer from a "Hadoop-Effect".
I also suspect that the code you showed is a very tiny part of the complete code, so you have ample opportunities of hidden side-effects there.
Start with simple code that creates t, like the code I gave you. If that does not work already, contact SAS technical support (they work under non-disclosure rules, so you can give them your data or access to your system).
If it works, expand the code until you either reach your intended functionality or the problem arises anew; then you'll know what's causing your problem.
One of the possible problem points can be SQL steps that don't specify a forced order for the output. SQL optimization may lead to unexpected reordering of data. See Maxim 31. And heed Maxim 34, so you can follow the development of your data through simply recreatable (and maintainable) steps.
... View more
