DSXchange

Check whether you have a tab char in the column. Or you may have a null value in that char.

What is the error / mistake you noticed?

The same post was present in Server section and has been answered there.

Did you check whether you have 20 records into the transformer or out of the transformer following some logic embedded in the transformer?

Look for Open (OpenSeq), Read (ReadSeq) and Close (CloseSeq).

One option is to identify the jobs using the ftp stage and try which had been run on that time and had ftp-ed to that environment.

You can also trace the network of the origin to confirm whether it was datastage or any external mechanism that did it.

You may have lost the stages in the project. Is it a new import or did you run out of space or did anybody fiddle with the project?

Alternatively, the project indexes may be corrupted.

Before that, can you check whether you can see any stage in the toolbox and also use them in any (dummy) job.

If you are scheduling using DataStage, you can get it from your operating system scheduler.

You can move the jobs into categories via Manager.

You can include parameters one at a time. You can write your own script to include the values in one and split them in the logic.

You can use 'parameter manager' to add the params in number of jobs.

Can you explain the process in detail for others to follow and understand.

You can use stage variables or hash files to achieve the result.

But note that DataStage is an ETL tool and not a reporting tool. Reporting tools like BO, Cognos etc can achieve your requirement with very less skillset and effort.

Even though multi-valued may solve some of your problems such as bringing all possible values for a key together in one reference line and in a single fetch, if you need to do range lookups, you may be better-off having them in an uv table and performing an sql lookup. Shiva459, Can you provide more...

Maybe something was changed elsewhere !!??

If you want them to go on multiple columns, do you know the target as the target must be properly defined to hold the max number of columns?