DSXchange

Server job or parallel job?

Do it with stage variables in a Transformer stage. Detect that the value is the same as in the previous row. If so, add prefix and suffix, and increment the stage variable that contains the suffix.

Or you might just be lucky with the timing.

For the data file yes. For the COBOL file definition maybe - you can also import the "table definition" from a COBOL FD from the client, and usually do because they usually arrive via email.

Yes, the same issue as with the Sequential File stage - only one writer for each file. Another solution would be to write to separate files then cat them together in an after-job subroutine running ExecSH.

This is happening in your Oracle database, not in DataStage. Pull out the query you are using and talk with your Oracle DBA about why it might be generating this error.

Any database table. Or, as you note, a server shared container writing to a hashed file.

Is this from the log when you used the parameter? Because it looks to me very much like the CASE statement is properly included in the query.

The obvious one is to compare the output record to the original. Simply carry all the fields through (or join them downstream of the CASS stage).

It's whatever whoever installed the product set it to. There is no default value.

It still doesn't look like an Information Server error to me. Ask at your site about whether the message means anything within the Windows environment (for example).

Thank you for saving lots of other half days. :D

Make very certain that you include the terminating dot on each line of the file definition. Note also the character position on its line where "01" begins - you need to provide this information when importing the table definition from the COBOL file definition. If you want to stick with tr...

What about filenames ending in .dis ?

dr.murthy wrote:inrow num it doesnot give count the number of records

Yes it does.