DSXchange

Read the value from the database
Set it in a variable
Pass it to the job via the parameters - via api if from OS, via job control if from DS Batches, via job routines if from sequencer.

But Wolfgang, I think the problem is that the 'source data file' is missing, which is not part of DataStage. This must not be tampered by DataStage during the upgrade. One option is that someone has removed it after the job ran successfully last time or some environment variables are disturbed. But ...

Try writing through an IPC stage. It then does not return any warning message.

But you still need to change your jobs for it.

Are you running on AIX?

How did you check your ulimit? Maybe that DS was initiated with lower ulimit value than the one in your profile.

DSLogInfo does throw that error if you pass only one arg.

The error is not thrown by the database but is done by DataStage.

If you reading from the db, check whether you are converting it into a string inside the cli.

If it is in a trans stage, use IConv.

You need to pass 2 params.

Call DSLogInfo(message, controller_name)

Convert it to a datetime.

Check the values in the numeric columns.

If it is just once, you can select the Print option to write in a file.

If you want literal values, you are better-off putting it in a sequential file and load it via a datastage job.

If you want it in post job, you need to set the status or land it in any file.

Doh!! So you were referring to 'concatenate' the files and not DataStage 'merge'. I got confused.

As Ray suggested, you can either use any DOS / Win command for concatenating and then use it in the job or use the command directly in the filter stage.

Please refer to the hash file information on the datastage help. That gives you the full information you need.

That is because you need a warning option in the link.