DSXchange

When you call your support provider, or if you search this forum, you will learn that Reporting Assistant was deprecated in version 5.2, and has not been developed since. So it does not handle job sequences, it does not handle parallel jobs, and it's quite likely it doesn't handle everything in plug...

DSR_ExecJob is a helper subroutine. It's called when you submit a job run request from Director. Chances are that the job name or some aspect of the job's configuration can not be found because Repository indexing has become out of date or, as Arnd suggests, permissions in the Repository. Try the DS...

Change the trigger so that it does not handle non-zero return value as a failure code. Search the forum for examples.

Two separate streams into the same Oracle table. If the keys form disjoint sets, these streams can run in parallel.

Job parameters for DSN, user ID and password for SQL Server?

There was nothing about Control M in the original post. I answered the original question. I'd probably answer along the same lines of Ken if you'd introduced an external scheduler as part of the requirement. Or a ps -ef command.

If it's not your DataStage client folder (C:\Program Files\Ascential\DataStage) it's one of the sub-folders therein.

It is NOT on the server machine.

A Sequencer cannot fail. An "any" sequencer fires its output(s) when any of its inputs has fired; an "all" sequencer fires its output(s) when all of its inputs have fired. Your problem seems to be with a job sequence detecting a failure in one of your rouines (GetNextBatchNumber). I presume you are ...

If using ODBC stage you may need to increase MAXFETCHBUFF beyond its default of 8192 bytes.

Does the job abort? If so, reset the job in Director and let us know whether there is any message "from previous run..." (and post its contents).

Are you certain that it ran successfully once after the modification? That is, did you accidentally run the old version before compiling the new?

Your use of a "staging area" is best practice for achieving restartability (you have already done the transformations, why do them again just because the target database may be unavailable?). If overall speed is the ultimate criterion, you would lose the intermediate file, but at the cost of needing...

This message sometimes also occurs if there exists an explicit user profile or home directory that puts the user into a folder that is not a DataStage project. The solution is to change the profile or home directory, or write a startup profile script, so that the user is attached to a project.

The obvious question is what is different between your development and test environments. Check that the NLS settings, both project default and within your job design, are the same. Look in your job log. The second message posted in a job run displays all environment variable settings. Make sure all...

Sometimes this is caused by not having write permission to the folder on your client machine where the XML document is to be written. Otherwise, there is something in your job sequence that can not be found in the Repository. Check with your support provider as to the meaning of error code 2017.

Not off the top of my head. I'm not working at a site that has ProfileStage this week. Is there anything about command line interface in the manual?