DSXchange

Your server might be heavily taxed at the time the job run was requested. Does the error happen over and over again, every time you try to run it? What is the server load on your system?

A sequential file, can only read and write in sequential manner. That is, if a single file is being read or written to, ofcourse. Hence your error. And therefore, you need to clear the partitioning to get rid of the error.

Yes you do. This has been discussed many times before. Search on the error message.

To me, its as simple as keeping track of all the steps applied to bring the data from point A to point B. And as Ray already put in prolific words, the source-to-target mapping document will keep track of that lineage.

I think I posted a C routine to do this a while back. Search should be able to turn this up.

What is the specification of the terminator stage. Does it send a stop request to running jobs or just aborts without stopping the running jobs? An exeption handler, will handle any exceptions raised during execution which you did not handle in your design. Control is always good. But if they are in...

Doing a lookup against the database, directly, is your bottle neck. Unload your table to a hashed file and reference that hashed file. You should see a boost in your job performance.
P.S: Job tuning, sometimes, may and will require design changes. Make that clear to your client.

Change the target metadata to Integer. That should take care of it.

Ask your DBA to check the trace file to get exacts on what exactly happened.

Dot, space and then dot.

Naa, I would go for a transformer stage, just like the way you do it in a server job.

Naa, It was a lucky stroke of the "Submit" key.
Welcome back. Good to see posts from you. Keep it up.

I beat you to it, gateleys

Load your source in a staging table and pass a sql join. That will be the most feasible.

What was the issue?