DSXchange

Why not? Resist stupid requirements!

Then you can execute it through a before-job or after-job subroutine.

Any.

It's on the DataStage Designer toolbar. Open it then click Help to learn how it works. Or read about it in the Parallel Job Advanced Developer's Guide

Describe your job design more completely. There is not enough information in your post for any meaningful diagnosis.

Welcome aboard.

DataStage includes a Resource Estimation tool that can assess resource requirements for individual jobs. Start with that, and add the results for any jobs that you intend to run simultaneously.

tanaya.deshpande@tieto.co wrote:Though there are no duplicate primary keys in the database.

If that is true you can not get primary key violation warnings. Check again.

They will demand varying amounts, perhaps as much as 2GB, perhaps not. Use the Resource Estimation tool to get numbers. If the system can not supply all resources demanded, some waiting (for CPU) or paging (of memory) is likely to occur.

Do you have the Teradata Utilities and TPT installed on the new DataStage server?

Perhaps using the correct function name (DSSetUserStatus()) would be beneficial.

DataStage is basically the same, though there is a patch for Windows Server 2003 that allows as much as 3GB of memory to be accessed in a 32-bit environment.

There are lots of date manipulation Transforms and Routines supplied with the product and more here.

81002 is usually caused by a connected client exceeding its inactivity timeout. That timeout can be set using the Administrator client.

However an 81002 can also be caused by the client's agent process (dscs, dsapi_server or dsapi_slave) being killed on the engine (server).

It's also possible to code it as a Routine activity.

Magesh_bala wrote: I need to abort a job if ...

Never a good plan, in my opinion.