DSXchange

Check for any Unicode or NLS option to be changed.

List the available dataset available in the required pattern either by ExecuteCommand activity. Pass it as parameter to the job one after other.
You can also store it in a file and read and pass it as parameter in a loop by using Loop activity as well.

Hardly 2 or 3 post made other than that regards to Ray in Site/Forum. Now again another milestone. But in this case, it cannot be called as milestone, especially for Ray.
Much appropriate, if we create a alias as RayXchange.

Its not possible to execute dsjob in mainframe server, unless you have Datastage serever installed in that server. But you can explore some option, of triggering the script (which actually kicks off the datastage job) available in unix from Mainframe.

The tiemout setting is configurable. IPC is used between stages where the link buffering is required and happens to only that stage.
Where as the link buffering option can be enabled at job level or at project level. Which will reflect to all the links available in the job.

If its user defined SQL, try to have either Insert or Update or Deleter alone and check if that works for that table. If that works, you can check your code that been written. Perhaps you can past your code to get better suggestion from this forum as well.

What is the warning messages and what state the job was in?

If the column is decimal, give the default value equal in digit to the given spec. Like
Null Field Value - '000.0000'
Also check the stage on which the warning is appearing.

Or perform a search, you may get lot of post similar to this. You also got the key word DS_AUDIT.

Use transfer from "beforeRec" to "outputRec" this as a search keyword. You may find lot of post related to this issue.
Unfortunetly, most of those post might not have resolution.

I tested when I posted. I changed one user as Operator and restarted Datastage. But I was able to find the jobs, using that id. Now I could see that, the Operator user id has dstage as one of the group.

Be aware that, if you on a network, using Task manager will kill only the client session.

Datastage uses most of the avaiable functionality of Orchestrate (Not all).
And Datastage PX reads and write the Dataset using the underlying Orchestrate operator.

Hi Deepak,
Have a look at this.

DSRunJob(hJob17, DSJ.RUNRESET) Will reset the job. You need to use DSJ.RUNNORMAL to run the job again.
Reseting the finished job shouldnt be an issue, unless you expect to get its status. Perhaps you can check for the status and then you can reset.