DSXchange

I've used the routine many times in the past, it does work. But if you have a spelling or capitalization error it is unforgiving and gives you the results that you are getting. As Ray has already suggested check the Stage and the Link names. Even if the Stage is spelled correctly, does it actually l...

rishabh wrote:...1. Invalid row termination character configuration...

have you checked your source data for an invalid/inappropriate termination character?

Luciana,

could you post your command line, most of the time the problem lies in the syntax of the dsjob command.

You mean something like "cd c:\temp | dir"?[/b]

Have you looked at the Parallel Job Advanced User Guide at the chapters 7 & 8 which describe the c++ interface? This describes the calls and header files.

Kartheek,

could you explain exactly where you are using a template and quote the error message you are getting? That would make analysis a lot easier.

The CWD (current working directory) of any shell command in DataStage will always be that of the DataStage project directory, so if you specify a relative path it will always start in that location. You should specify an absolute path if you want to use your own folder.

This sounds like the problem that is fixed with a patch from IBM/Ascential. eCase 60128.

I'm not sure what type of delayed write you are talking about. If it is the normal Windows mechanism then, in the normal course of events, DataStage wouldn't even notice that it is turned on or off. In case of system failure the chances of data corruption are of course higher with delayed writes tur...

kris - thanks! I had no idea where that acronym came from. This place is always a great source of information from so many different areas!

Craig - thanks for the sanity check... of course you are correct!

vardhan354 wrote:i tried with this dsjob -lognewest projectname jobname it is giving a message newest id = 50, statuscode = 0.

Try actually using the name of your project and the name of your job in the command; i.e. "dsjob -lognewest MyProject MyJob"

You will need to call the function as follows:

I think that the reason you aren't getting an output is that the "DSJ.ME" might not be valid in the after-job routine. Can you put a DSLogInfo() call into the routine and output the value of DSJ.ME? You could also do a "CALL DSLogInfo('My job name is "':DSGetJobInfo(DSJ.ME,DSJ.JOBNAME),'')"

look at the date/time modified of your bin/uv program; it might have been overwritten since those messages should not appear when starting DataStage.