DSXchange

Please report the actual specification you use in the Modify stage. It is pointless us trying to guess what you did, and possibly give misleading advice as a result.

Get into yur project, again with exclusive access, and execute the DS.CHECKER command. This will highlight and remove any hashed files orphaned by incompleted job deletion.

Hi, How to configure the ODBC.ini that allows me to have 2 databases with two different server IP addresses and with same password or is it possible to use 1 ODBC name with 2 database, 2 IP Address and same USERNAME and Password ? No. ODBC standards specify one DSN, one database (at a time). To cha...

... which you can do in the Director, by inspecting either the log of the job sequence or the log of the job, or the status detail of the job.

Uninstall and then clean out all Ascential entries from the Registry before trying your next installation.

What's changed? ("Nothing" is not the correct answer. Dig.)

Use one (not both) of the approaches suggested.

Particularly in a multi-machine configuration, or for a complex job, DSWaitForJob() may kick in too early. DSRunJob() is an asynchronous call, so returns immediately once the run request has been submitted. The job status does not change to starting until the score has been composed. The workaround ...

I believe that the project must be a project name, not a path.

Try setting the DSHOME environment variable to the path of the correct DataStage engine directory - the 7.5.2 one or the 8.0.1 one. It is from the UV.ACCOUNT hashed file in this directory that the pathname of the project is decoded.

By creating either a parallel routine or a Build stage and coding it in C++.

I too am not doing DataStage things this week and operating from memory. But you definitely have control, and the question has been asked and answered in the past. Search.

In terms of maintainability, the best way is to have a parent job sequence read the parameter file and supply whatever parameters are needed to the job sequence to which you refer.

ssunda6 wrote:Chulett,

There is no other log entry which shows the actual command executed.

Regards,
ssunda.

There should be, because of

Not that. A lock problem would not emit a "permission denied" error.