DSXchange

dsdlockd can be used only for those process which are left orphaned.
For those one which are active need to be first stopped from Director.
Resource Cleanup, Clear Status, DS.TOOLS from TCL, Kill can be followed.

Ernie,
You are already deep into SOA
Soon we ll come up all our queries, when we upgrade to SOA.

We are missing something here. Let me confirm, the data passed either from Row Generator or Sequential file or data from Parameter is just the input argument to the Stored procedure called by the STP stage? And there is not change in connection parameters, like Schema, Tablename, usernaname or passw...

Paddu, Our Father was explaining how to represent the data in this forum, by enclosing in Code. As in the previous post. The sentence "Each word has one space between them." was within code tag which gives more clear picture and the same in this post didn't. Hope you haven't toyed something with you...

Is it part of the code?
What is the line number 33?
Have you included "INCLUDE DSINCLUDE JOBCONTROL.H" at first?

Does the statistics (row/sec) appear on the link when show performance static is enabled? Will it change to green and show up some value when it finishes OK.

You are missing something to mention here. Just to try, keep deleting the file that been created on the output directory. So that you can come to a conclusion that its due to only the overwriting on a same file, which still is not a issue any ways.

Hi Ajay, Welcome aboard :D !!! It may not be exactly the issue with Invocation ID. Focus on the error "Unable to create file /mpps/dev//etl/seqfiles/XYZ" Observer the double slash in the path "//". May be the parameter that were passed during when you call the job as Multiple Instance might be diffe...

Disable the Constraint for a while and load the data into table and check what is the actual data that been loaded (which were tyring to load previous time).

If you want to do a direct upgrade you can go upto 7.0.
Nevertheless you can do export and import of project to any latest version of Datastage.

When you choose the Write mode as Load, you can find "Index Mode" under "Optinos".

One work around would be, call the job, through a JobSequence. You can have the trigger condition to pass only if has Ok (not Warning nor FatalError).
But straight forward method is to find the reason why its giving out error and why the job is not aborting,

Use CDC.
COPY code can be ignored. Rest of the codes can have their corresponding DML statement.

By the way, why you need it, if Auto Purging from Datastage is possible? You can acheive this by setting appropriate value in Adminstrator or in Director.
If you need to write a script, you need to take care of Auto Purge entry. There are codes posted by Ray and Kim. Search for that.