DSXchange

Vertical pivot can be implemented either in a transfomer or in a pivot stage. Search here for vertical pivot.

In most of the cases, it will work fine. But it is advised that one uses orchestrate schema for Enterprise stages & Connector wizard for Connector stages.

Sort and a vertical pivot. Search here & you will find many..

ravindras83 wrote:I have a situation where we get about 350 different source files (with different metadata). These files have date suffix in the name but the file name is distinct.

OP mentioned the suffix and that's why Eric suggested the date appending logic

Craig, that's a good one.. :) This may not cover all negative scenarios/error handling/exceptions, but can be a simple check. Assumption: You will not have any other files in that folder other than the expected 350 files ;) Instead of having a WFF stage in the loop, just have a command stage with ls...

It is because of having some functions in the your SQL. Do you have a cast or something like that? If you remove them, then you will not see this alert message. Of course the job runs fine

I don't see a valid reason for your loop to go infinite. Also, what you are doing is to check if a particular material process took more than 10 seconds & that's not at all needed... How many dashes do you expect in your "material"?

Check with IBM on this. I remember we fixed this issue in our environment after contacting IBM.

how does data look when you open with Textpad or UltraEdit?

Is someone importing without your knowledge? Is the current status static or changing?

Rohit, Even if you revert those 2 things(Admin setting & Env. parameter), your job should run fine sometimes and abort sometimes. That's why i asked you initially whether you face this error during your rerun. Check IBM site if this is an known issue.

Infinite loop means infinite Do you want to implement a StartTime and CurrentTime difference check and use an exit?

Share your routine here.

All the rows in the file got loaded into the table? I don't think so. There might be one or few records which is causing the abort. May be, you should use reject link and see.

Try whatever others suggested here. If no luck, contact IBM. In 2009, when we migrated our jobs from 7.5 to 8.0.1 & 8.1 eventually, we got this error. I don't remember exactly how it was fixed. But i guess we got a patch from IBM to fix this. But keep in mind that that was early days of version ...

Also, check if COUNTRY_CODE is used in derivation of the some other output column. I mean you may have used COUNTRY_CODE directly in some other derivation.